I brought the AG Pro in June of 2024 when i saw that it had all in one as a Gateway. It was advertised in such a way that it was all in one solution. But as soon as i received it, i found that many of the things advertised is not functioning out of the box. the Zigbee had to be used with tasmota and remaining functions like IR, RF, Tuya and to be with Kincony firmware. and on top of this both firmware cannot work together. I some how managed to flash the Tasmota firmware because i needed the ZHA integration.. and this worked until last month. Now the tasmota firmware has failed to recognize the Zigbee device inside. i tried rolling back to several tasmota version but it all remains the same. 

I sent a message to their support and all the response i get is to change the firmware. I feel dumped.. Kincony should have either fixed the firmware issues or informed the customer that these problems exits. 92$(inc Shipping) wasted.

Can I connect multiple DS18B20 sensors to one 47 GPIO in the native firmware?

KinCony Pi5 is a Raspberry Pi CM5 server for smart home automation and industrial automation control. It can use for home assistant local server. It's a Linux computer, you can install software by yourself, such as Node red. The product default CM5 version is CM5004000. It without Bluetooth and wifi, RAM:4G Lite version.

Model No. KinCony Pi5
Description: KinCony Automation Local Server – Pi5
Power supply: 12-24V DC
Processor: Raspberry Pi Compute Module 5
Size: 139mm*83mm*56mm
interfaces: Ethernet(RJ45)-LAN 1000Mbps IPv4/IPv6,USB-C
Installation method: DIN RAIL
2 × USB 3 sockets
microSD card socket for CM5 Lite modules
M.2 M key PCIe socket
1 × full-size HDMI 2.0 connectors
DIP SWITCH for jumpers

SDA:GPIO8
SCL:GPIO18

PCF8575: (input1-16): i2c address:0x22 by B16-core

P8:input1
P9:input2
P10:input3
P11:input4
P12:input5
P13:input6
P14:input7
P15:input8

P0:input9
P1:input10
P2:input11
P3:input12
P4:input13
P5:input14
P6:input15
P7:input16

ADS1115 (4CH ADC): i2c address:0x48
Analog input (A1: DC 0-5v)
Analog input (A2: DC 0-5v)
Analog input (A3: DC 4-20mA)
Analog input (A4: DC 4-20mA)

24C02 EPROM i2c address: 0x50
DS3231 RTC i2c address: 0x68

1-wire (pull-up resistance on PCB):
1-wire1:GPIO47
1-wire2:GPIO48
1-wire3:GPIO7
1-wire4:GPIO40

free GPIOs:
GPIO13
GPIO14
GPIO21

-----------------------
Ethernet (W5500) I/O define:

clk_pin: GPIO1
mosi_pin: GPIO2
miso_pin: GPIO41
cs_pin: GPIO42

interrupt_pin: GPIO43
reset_pin: GPIO44

--------------------
RS485:
RXD:GPIO38
TXD:GPIO39

Tuya module:
RXD:GPIO17
TXD:GPIO16

Tuya network button: Tuya module's P28
Tuya network LED: Tuya module's P16

ARM CPU TXD:GPIO4
ARM CPU RXD:GPIO6

SD Card:
SPI-MOSI:GPIO10
SPI-SCK:GPIO11
SPI-MISO:GPIO12
SPI-CS:GPIO9
SD-Detect: GPIO5

v3.12.0 improvement:
1. Adapt to new KinCony Controller: B8/B8M/B24/B24M/DM16
2. Sensor pull-up option: When PCB include pull-up resistor, "pull-up" will auto shown as enabled
3. Network webpage -- LAN mode will show the actual ethernet IP address
4. GSM phone list: Add ID numbers
5. Password-related inputs option added masking
6. Sensor configuration webpage: added sensor name
7. IFTTT "sensor channel" change to "sensor name" have preset
8. Removed default MQTT port number "1883"
9. IFTTT THEN actions: Add "step value" for AO (analog output)
10. improve previous version first time downloaded firmware boot up speed slowly issue.

Attached Files

  KCS_A2V3_V3.12.0.zip (Size: 1.07 MB / Downloads: 328)
  KCS_A6V3_V3.12.0.zip (Size: 1.04 MB / Downloads: 332)
  KCS_A8V3_V3.12.0.zip (Size: 1.09 MB / Downloads: 323)
  KCS_A16V3_V3.12.0.zip (Size: 1.11 MB / Downloads: 387)
  KCS_A32PRO_V3.12.0.zip (Size: 1.08 MB / Downloads: 296)
  KCS_AG8_V3.12.0.zip (Size: 1.06 MB / Downloads: 267)
  KCS_ALR_V3.12.0.zip (Size: 1.02 MB / Downloads: 286)
  KCS_B8_V3.12.0.zip (Size: 1.1 MB / Downloads: 283)
  KCS_B8M_V3.12.0.zip (Size: 1.1 MB / Downloads: 322)
  KCS_B16_V3.12.0.zip (Size: 1.1 MB / Downloads: 284)
  KCS_B16M_V3.12.0.zip (Size: 1.1 MB / Downloads: 274)
  KCS_B24_V3.12.0.zip (Size: 1.1 MB / Downloads: 261)
  KCS_B24M_V3.12.0.zip (Size: 1.1 MB / Downloads: 282)
  KCS_DM16_V3.12.0.zip (Size: 1.07 MB / Downloads: 276)
  KCS_F8_V3.12.0.zip (Size: 1.09 MB / Downloads: 290)
  KCS_F16_V3.12.0.zip (Size: 1.1 MB / Downloads: 299)
  KCS_F24_V3.12.0.zip (Size: 1.1 MB / Downloads: 282)
  KCS_G1_V3.12.0.zip (Size: 1.06 MB / Downloads: 287)
  KCS_KC_TA_V3.12.0.zip (Size: 1.05 MB / Downloads: 247)
  KCS_N60_V3.12.0.zip (Size: 986.2 KB / Downloads: 296)
  KCS_T16M_V3.12.0.zip (Size: 1.05 MB / Downloads: 288)
  KCS_T32M_V3.12.0.zip (Size: 1.07 MB / Downloads: 290)
  KCS_T64M_V3.12.0.zip (Size: 1.07 MB / Downloads: 287)
  KCS_T128M_V3.12.0.zip (Size: 1.07 MB / Downloads: 278)
  KCS_Z1_V3.12.0.zip (Size: 1.21 MB / Downloads: 308)

I have a kc868-h32b I can log in to the webpanel just fine with ethernet and I can see it has firmware H32B_Pro_V1.19

I can connect the USB-C to my windows 10 machine. And it shows up as COM4. 
I can click "OPEN PORT" as soon as the device restarts
But when I click on the bootloader detect button nothing happens

I've tried restarting the device more than 50 times. With varying timings and Baudrates. But no change. I never get the results shown in the youtube video

How do I debug this, what am I doing wrong? 
Is the USB C version different than what is shown in the video?

Attached Files

Thumbnail(s)
   

Can you provide a solution to utilise the KC868-D 8 and 16 channel dimmer over KC868-HAv2 RS485 interface 
I would like to use multiple KC868-HAv2 (8 of them) connecting over RS485 to the Dimming module and all to the F16 device

I want to use some of the switch paddles for the dimmer and others to switch the outputs on the F16.
thanks

rpiboot_setup.exe for CM5 lite USB driver.

  rpiboot_setup.zip (Size: 32.75 MB / Downloads: 330)

Hi,

Could you please post a picture of the cct for the GPIOs 13 14 and 40 pls. I will be configuring one of these as an output.

I want to interface it to a 24v Flow meter that has a reset line when pulled low.

Thank you

Hello. can you tell me how I can connect the esprog debugger(jtag) to this board?  I have a problem with pin io15 (TDO), which is powered by 3v all the time, and it seems to me that this is interfering with debugging. Of course, I can cut the track for debugging time. But as a novice developer, I am tormented by the question: How did you debug on this board via JTAG? I don't want to use printf()
If this information is not for general use, then please reply by email or in private messages.

Attached Files

Image(s)