<![CDATA[Smart Home Automation Forum - KC868-A series and Uair Smart Controller]]>

<![CDATA[Smart Home Automation Forum - KC868-A series and Uair Smart Controller]]> https://www.kincony.com/forum/ Sun, 10 May 2026 21:30:26 +0000 MyBB <![CDATA[B24M: Need help connecting a wall switch to control MOSFET output]]> https://www.kincony.com/forum/showthread.php?tid=9308 Sun, 03 May 2026 05:24:09 +0800 maher]]> https://www.kincony.com/forum/showthread.php?tid=9308
.jpeg

WhatsApp Image 2026-05-02 at 11.19.33 PM.jpeg (Size: 85.54 KB / Downloads: 32)
Hi KinCony team,
I have a B24M board. I want to connect a physical wall switch to a "Digital Input" and use it to turn a device on/off on the "MOSFET Output".
Could you please tell me the GPIO numbers for the inputs and outputs to use in Home Assistant?
Thanks!
.jpeg

WhatsApp Image 2026-05-02 at 11.19.33 PM.jpeg (Size: 85.54 KB / Downloads: 32) ]]>
.jpeg

WhatsApp Image 2026-05-02 at 11.19.33 PM.jpeg (Size: 85.54 KB / Downloads: 32) ]]> <![CDATA[Analoge input for door sensors?]]> https://www.kincony.com/forum/showthread.php?tid=9295 Tue, 28 Apr 2026 20:35:57 +0800 Elgatoguiri]]> https://www.kincony.com/forum/showthread.php?tid=9295 I've just noticed that the board has 4 analog input. Can I use those for switches? I have 3 magnetic reed switches (door sensors) that I'd like to connect there.

I use this board with HomeAssistant with esphome. If it's possible to connect the switches to the analog input what is the esphome code for them?

Thanks!]]> I've just noticed that the board has 4 analog input. Can I use those for switches? I have 3 magnetic reed switches (door sensors) that I'd like to connect there.

I use this board with HomeAssistant with esphome. If it's possible to connect the switches to the analog input what is the esphome code for them?

Thanks!]]> <![CDATA[KC868-A16S: Can ESP32 read the manual control extender buttons?]]> https://www.kincony.com/forum/showthread.php?tid=9292 Sat, 25 Apr 2026 19:54:37 +0800 markusd1984]]> https://www.kincony.com/forum/showthread.php?tid=9292 I am using the KC868-A16S with custom ESPHome firmware. I have the physical button board plugged into the Manual Control Extender sockets (Ports B, C, D) to control relays 1-16s as backup in case Nextion K028 Screen dies.

When I press these physical buttons, the relays trigger perfectly (as expected). However, my software UI gets out of sync because the ESP32 does not detect that the relay state has changed.

My questions:

Is it possible for the ESP32 to read the state of these manual control extender buttons (or read the actual hardware relay state) via software/I2C?
Or are these extenders purely hardware-level overrides that bypass the ESP32 completely?
If they bypass the ESP32, what hardware modification (e.g., jumper wires) is required so ESPHome knows when a manual button was pressed?

Thank you!]]> I am using the KC868-A16S with custom ESPHome firmware. I have the physical button board plugged into the Manual Control Extender sockets (Ports B, C, D) to control relays 1-16s as backup in case Nextion K028 Screen dies.

When I press these physical buttons, the relays trigger perfectly (as expected). However, my software UI gets out of sync because the ESP32 does not detect that the relay state has changed.

My questions:

Is it possible for the ESP32 to read the state of these manual control extender buttons (or read the actual hardware relay state) via software/I2C?
Or are these extenders purely hardware-level overrides that bypass the ESP32 completely?
If they bypass the ESP32, what hardware modification (e.g., jumper wires) is required so ESPHome knows when a manual button was pressed?

Thank you!]]> <![CDATA[KC868-16A crashing in infinite loop]]> https://www.kincony.com/forum/showthread.php?tid=9232 Mon, 13 Apr 2026 06:57:37 +0800 vdeconinck]]> https://www.kincony.com/forum/showthread.php?tid=9232
I bought a KC868-16A about one year ago and did some tests but I never used it because I didn't have time.
Now I want to finish my project, but the board has stopped responding completely.

I connected it via USB to get the logs:

Code:
ELF file SHA256: d62704405

Rebooting...

ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0030,len:7112

load:0x40078000,len:15624

load:0x40080400,len:4

load:0x40080404,len:3876

entry 0x4008064c

[0;32mI (29) boot: ESP-IDF 5.1.5 2nd stage bootloader[0m

[0;32mI (29) boot: compile time Jan 18 2025 19:20:33[0m

[0;32mI (29) boot: Multicore bootloader[0m

[0;32mI (33) boot: chip revision: v3.1[0m

[0;32mI (37) boot.esp32: SPI Speed      : 40MHz[0m

[0;32mI (42) boot.esp32: SPI Mode       : DIO[0m

[0;32mI (46) boot.esp32: SPI Flash Size : 4MB[0m

[0;32mI (51) boot: Enabling RNG early entropy source...[0m

[0;32mI (56) boot: Partition Table:[0m

[0;32mI (60) boot: ## Label            Usage          Type ST Offset   Length[0m

[0;32mI (67) boot:  0 otadata          OTA data         01 00 00009000 00002000[0m

[0;32mI (75) boot:  1 phy_init         RF data          01 01 0000b000 00001000[0m

[0;32mI (82) boot:  2 app0             OTA app          00 10 00010000 001c0000[0m

[0;32mI (90) boot:  3 app1             OTA app          00 11 001d0000 001c0000[0m

[0;32mI (97) boot:  4 nvs              WiFi data        01 02 00390000 0006d000[0m

[0;32mI (105) boot: End of partition table[0m

[0;32mI (109) esp_image: segment 0: paddr=001d0020 vaddr=3f400020 size=1d6ech (120556) map[0m

[0;32mI (161) esp_image: segment 1: paddr=001ed714 vaddr=3ffb0000 size=025e4h (  9700) load[0m

[0;32mI (165) esp_image: segment 2: paddr=001efd00 vaddr=40080000 size=00318h (   792) load[0m

[0;32mI (167) esp_image: segment 3: paddr=001f0020 vaddr=400d0020 size=4c58ch (312716) map[0m

[0;32mI (288) esp_image: segment 4: paddr=0023c5b4 vaddr=40080318 size=09bfch ( 39932) load[0m

[0;32mI (305) esp_image: segment 5: paddr=002461b8 vaddr=50000000 size=00020h (    32) load[0m

[0;32mI (310) boot: Loaded app from partition at offset 0x1d0000[0m

[0;32mI (311) boot: Disabling RNG early entropy source...[0m

[0;32m[I][logger:120]: Log initialized[0m

[0;35m[C][safe_mode:136]: Unsuccessful boot attempts: 10[0m

[1;31m[E][safe_mode:148]: Boot loop detected[0m

[1;31m[E][component:420]: safe_mode set Error flag: unspecified[0m

[0;32m[I][app:089]: Running through setup()[0m

E (11278) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:

E (11278) task_wdt:  - loopTask (CPU 1)

E (11278) task_wdt: Tasks currently running:

E (11278) task_wdt: CPU 0: IDLE0

E (11278) task_wdt: CPU 1: loopTask

E (11278) task_wdt: Aborting.

E (11278) task_wdt: Print CPU 1 backtrace

Backtrace: 0x4000c04d:0x3ffbb670 0x40083db2:0x3ffbb690 0x400f5916:0x3ffbb6b0 0x400e875c:0x3ffbb6f0 0x400d81eb:0x3ffbb730 0x40114fed:0x3ffbb7d0 0x400db5df:0x3ffbb7f0 0x400db02b:0x3ffbb810 0x400d9ce1:0x3ffbb840 0x400dd5e2:0x3ffbb870 0x400d678f:0x3ffbb910

ELF file SHA256: d62704405

Rebooting...

[...]

E (11278) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:

E (11278) task_wdt:  - loopTask (CPU 1)

E (11278) task_wdt: Tasks currently running:

E (11278) task_wdt: CPU 0: IDLE0

E (11278) task_wdt: CPU 1: loopTask

E (11278) task_wdt: Aborting.

E (11278) task_wdt: Print CPU 1 backtrace

Backtrace: 0x4000bfed:0x3ffbb640 0x40085b1f:0x3ffbb650 0x40083a46:0x3ffbb670 0x40083da6:0x3ffbb690 0x400f5916:0x3ffbb6b0 0x400e875c:0x3ffbb6f0 0x400d81eb:0x3ffbb730 0x40114fed:0x3ffbb7d0 0x400db5df:0x3ffbb7f0 0x400db02b:0x3ffbb810 0x400d9ce1:0x3ffbb840 0x400dd5e2:0x3ffbb870 0x400d678f:0x3ffbb910

etc.

I disconnected everything (only left power and USB-C) and it still crashes.

I flashed it with the Kincony firmware but no response.
The serial log via USB is now:

Code:
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0030,len:6652

ho 0 tail 12 room 4

load:0x40078000,len:15052

load:0x40080400,len:3836

entry 0x4008069c

[0;32mI (29) boot: ESP-IDF v4.4.7 2nd stage bootloader[0m

[0;32mI (29) boot: compile time 15:12:15[0m

[0;32mI (29) boot: Multicore bootloader[0m

[0;32mI (32) boot: chip revision: v3.1[0m

[0;32mI (36) boot.esp32: SPI Speed      : 40MHz[0m

[0;32mI (41) boot.esp32: SPI Mode       : DIO[0m

[0;32mI (45) boot.esp32: SPI Flash Size : 4MB[0m

[0;32mI (50) boot: Enabling RNG early entropy source...[0m

[0;32mI (55) boot: Partition Table:[0m

[0;32mI (59) boot: ## Label            Usage          Type ST Offset   Length[0m

[0;32mI (66) boot:  0 nvs              WiFi data        01 02 00009000 00026000[0m

[0;32mI (74) boot:  1 phy_init         RF data          01 01 0003f000 00001000[0m

[0;32mI (81) boot:  2 factory          factory app      00 00 00040000 003b0000[0m

[0;32mI (89) boot: End of partition table[0m

[0;32mI (93) esp_image: segment 0: paddr=00040020 vaddr=3f400020 size=102078h (1056888) map[0m

[0;32mI (484) esp_image: segment 1: paddr=001420a0 vaddr=3ffb0000 size=0339ch ( 13212) load[0m

[0;32mI (489) esp_image: segment 2: paddr=00145444 vaddr=40080000 size=0abd4h ( 43988) load[0m

[0;32mI (508) esp_image: segment 3: paddr=00150020 vaddr=400d0020 size=a7ca8h (687272) map[0m

[0;32mI (757) esp_image: segment 4: paddr=001f7cd0 vaddr=4008abd4 size=05228h ( 21032) load[0m

[0;32mI (773) boot: Loaded app from partition at offset 0x40000[0m

[0;32mI (774) boot: Disabling RNG early entropy source...[0m

[0;32mI (785) cpu_start: Multicore app[0m

[0;32mI (785) cpu_start: Pro cpu up.[0m

[0;32mI (786) cpu_start: Starting app cpu, entry point is 0x40081278[0m

[0;32mI (0) cpu_start: App cpu up.[0m

[0;32mI (805) cpu_start: Pro cpu start user code[0m

[0;32mI (806) cpu_start: cpu freq: 240000000[0m

[0;32mI (806) cpu_start: Application information:[0m

[0;32mI (810) cpu_start: Project name:     KC868_A16[0m

[0;32mI (815) cpu_start: App version:      v2.2.20[0m

[0;32mI (820) cpu_start: Compile time:     Apr  2 2026 15:12:09[0m

[0;32mI (826) cpu_start: ELF file SHA256:  b7c54ce742331a6d...[0m

[0;32mI (832) cpu_start: ESP-IDF:          v4.4.7[0m

[0;32mI (837) cpu_start: Min chip rev:     v0.0[0m

[0;32mI (842) cpu_start: Max chip rev:     v3.99 [0m

[0;32mI (847) cpu_start: Chip rev:         v3.1[0m

[0;32mI (852) heap_init: Initializing. RAM available for dynamic allocation:[0m

[0;32mI (859) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM[0m

[0;32mI (865) heap_init: At 3FFC5190 len 0001AE70 (107 KiB): DRAM[0m

[0;32mI (871) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM[0m

[0;32mI (877) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM[0m

[0;32mI (884) heap_init: At 4008FDFC len 00010204 (64 KiB): IRAM[0m

[0;32mI (891) spi_flash: detected chip: generic[0m

[0;32mI (895) spi_flash: flash io: dio[0m

[0;32mI (900) cpu_start: Starting scheduler on PRO CPU.[0m

[0;32mI (0) cpu_start: Starting scheduler on APP CPU.[0m

[0;32mI (914) main: [APP] Startup..[0m

[0;32mI (917) main: [APP] Free memory: 223808 bytes[0m

[0;32mI (922) main: [APP] IDF version: v4.4.7[0m

[0;32mI (985) NVS: save default system config.[0m

[0;32mI (991) NVS: save default network config.[0m

[0;32mI (997) NVS: save default tuya config.[0m

[0;32mI (1002) NVS: save default protocol config.[0m

[0;32mI (1009) NVS: save default input config.[0m

[0;32mI (1012) NVS: save default output config.[0m

[0;32mI (1017) NVS: save default name config.[0m

[0;32mI (1025) NVS: save default state.[0m

[0;32mI (1029) NVS: save default config.[0m

[0;32mI (1035) NVS: save default config.[0m

[0;32mI (1039) NVS: save default config.[0m

[0;32mI (1155) NVS: save default config.[0m

[0;32mI (1370) NVS: init nvs finish.[0m

[0;31mE (6371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:[0m

[0;31mE (6371) task_wdt:  - IDLE0 (CPU 0)[0m

[0;31mE (6371) task_wdt: Tasks currently running:[0m

[0;31mE (6371) task_wdt: CPU 0: main[0m

[0;31mE (6371) task_wdt: CPU 1: IDLE1[0m

[0;31mE (6371) task_wdt: Print CPU 0 (current core) backtrace[0m

Backtrace: 0x400F1456:0x3FFB0B90 0x40082C75:0x3FFB0BB0 0x40008541:0x3FFC7610 0x40088625:0x3FFC7630 0x400F3C0E:0x3FFC7650 0x400D9D51:0x3FFC7680 0x400D85BA:0x3FFC7710 0x40175DF7:0x3FFC7730

[0;31mE (6371) task_wdt: Print CPU 1 backtrace[0m

Backtrace: 0x40085585:0x3FFB1190 0x40082C75:0x3FFB11B0 0x4000BFED:0x3FFC8550 0x4008CC92:0x3FFC8560 0x400F16BF:0x3FFC8580 0x400F16CB:0x3FFC85B0 0x400D4E16:0x3FFC85D0 0x4008AE18:0x3FFC85F0

[0;31mE (11371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:[0m

[0;31mE (11371) task_wdt:  - IDLE0 (CPU 0)[0m

[0;31mE (11371) task_wdt: Tasks currently running:[0m

[0;31mE (11371) task_wdt: CPU 0: main[0m

[0;31mE (11371) task_wdt: CPU 1: IDLE1[0m

[0;31mE (11371) task_wdt: Print CPU 0 (current core) backtrace[0m

Backtrace: 0x400F1456:0x3FFB0B90 0x40082C75:0x3FFB0BB0 0x40008541:0x3FFC7610 0x40088625:0x3FFC7630 0x400F3C0E:0x3FFC7650 0x400D9D51:0x3FFC7680 0x400D85BA:0x3FFC7710 0x40175DF7:0x3FFC7730

etc.

Any idea why the watchdog is not reset?

What is your advice?

Kind regards

Vincent]]>
I bought a KC868-16A about one year ago and did some tests but I never used it because I didn't have time.
Now I want to finish my project, but the board has stopped responding completely.

I connected it via USB to get the logs:

Code:
ELF file SHA256: d62704405

Rebooting...

ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0030,len:7112

load:0x40078000,len:15624

load:0x40080400,len:4

load:0x40080404,len:3876

entry 0x4008064c

[0;32mI (29) boot: ESP-IDF 5.1.5 2nd stage bootloader[0m

[0;32mI (29) boot: compile time Jan 18 2025 19:20:33[0m

[0;32mI (29) boot: Multicore bootloader[0m

[0;32mI (33) boot: chip revision: v3.1[0m

[0;32mI (37) boot.esp32: SPI Speed      : 40MHz[0m

[0;32mI (42) boot.esp32: SPI Mode       : DIO[0m

[0;32mI (46) boot.esp32: SPI Flash Size : 4MB[0m

[0;32mI (51) boot: Enabling RNG early entropy source...[0m

[0;32mI (56) boot: Partition Table:[0m

[0;32mI (60) boot: ## Label            Usage          Type ST Offset   Length[0m

[0;32mI (67) boot:  0 otadata          OTA data         01 00 00009000 00002000[0m

[0;32mI (75) boot:  1 phy_init         RF data          01 01 0000b000 00001000[0m

[0;32mI (82) boot:  2 app0             OTA app          00 10 00010000 001c0000[0m

[0;32mI (90) boot:  3 app1             OTA app          00 11 001d0000 001c0000[0m

[0;32mI (97) boot:  4 nvs              WiFi data        01 02 00390000 0006d000[0m

[0;32mI (105) boot: End of partition table[0m

[0;32mI (109) esp_image: segment 0: paddr=001d0020 vaddr=3f400020 size=1d6ech (120556) map[0m

[0;32mI (161) esp_image: segment 1: paddr=001ed714 vaddr=3ffb0000 size=025e4h (  9700) load[0m

[0;32mI (165) esp_image: segment 2: paddr=001efd00 vaddr=40080000 size=00318h (   792) load[0m

[0;32mI (167) esp_image: segment 3: paddr=001f0020 vaddr=400d0020 size=4c58ch (312716) map[0m

[0;32mI (288) esp_image: segment 4: paddr=0023c5b4 vaddr=40080318 size=09bfch ( 39932) load[0m

[0;32mI (305) esp_image: segment 5: paddr=002461b8 vaddr=50000000 size=00020h (    32) load[0m

[0;32mI (310) boot: Loaded app from partition at offset 0x1d0000[0m

[0;32mI (311) boot: Disabling RNG early entropy source...[0m

[0;32m[I][logger:120]: Log initialized[0m

[0;35m[C][safe_mode:136]: Unsuccessful boot attempts: 10[0m

[1;31m[E][safe_mode:148]: Boot loop detected[0m

[1;31m[E][component:420]: safe_mode set Error flag: unspecified[0m

[0;32m[I][app:089]: Running through setup()[0m

E (11278) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:

E (11278) task_wdt:  - loopTask (CPU 1)

E (11278) task_wdt: Tasks currently running:

E (11278) task_wdt: CPU 0: IDLE0

E (11278) task_wdt: CPU 1: loopTask

E (11278) task_wdt: Aborting.

E (11278) task_wdt: Print CPU 1 backtrace

Backtrace: 0x4000c04d:0x3ffbb670 0x40083db2:0x3ffbb690 0x400f5916:0x3ffbb6b0 0x400e875c:0x3ffbb6f0 0x400d81eb:0x3ffbb730 0x40114fed:0x3ffbb7d0 0x400db5df:0x3ffbb7f0 0x400db02b:0x3ffbb810 0x400d9ce1:0x3ffbb840 0x400dd5e2:0x3ffbb870 0x400d678f:0x3ffbb910

ELF file SHA256: d62704405

Rebooting...

[...]

E (11278) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:

E (11278) task_wdt:  - loopTask (CPU 1)

E (11278) task_wdt: Tasks currently running:

E (11278) task_wdt: CPU 0: IDLE0

E (11278) task_wdt: CPU 1: loopTask

E (11278) task_wdt: Aborting.

E (11278) task_wdt: Print CPU 1 backtrace

Backtrace: 0x4000bfed:0x3ffbb640 0x40085b1f:0x3ffbb650 0x40083a46:0x3ffbb670 0x40083da6:0x3ffbb690 0x400f5916:0x3ffbb6b0 0x400e875c:0x3ffbb6f0 0x400d81eb:0x3ffbb730 0x40114fed:0x3ffbb7d0 0x400db5df:0x3ffbb7f0 0x400db02b:0x3ffbb810 0x400d9ce1:0x3ffbb840 0x400dd5e2:0x3ffbb870 0x400d678f:0x3ffbb910

etc.

I disconnected everything (only left power and USB-C) and it still crashes.

I flashed it with the Kincony firmware but no response.
The serial log via USB is now:

Code:
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0030,len:6652

ho 0 tail 12 room 4

load:0x40078000,len:15052

load:0x40080400,len:3836

entry 0x4008069c

[0;32mI (29) boot: ESP-IDF v4.4.7 2nd stage bootloader[0m

[0;32mI (29) boot: compile time 15:12:15[0m

[0;32mI (29) boot: Multicore bootloader[0m

[0;32mI (32) boot: chip revision: v3.1[0m

[0;32mI (36) boot.esp32: SPI Speed      : 40MHz[0m

[0;32mI (41) boot.esp32: SPI Mode       : DIO[0m

[0;32mI (45) boot.esp32: SPI Flash Size : 4MB[0m

[0;32mI (50) boot: Enabling RNG early entropy source...[0m

[0;32mI (55) boot: Partition Table:[0m

[0;32mI (59) boot: ## Label            Usage          Type ST Offset   Length[0m

[0;32mI (66) boot:  0 nvs              WiFi data        01 02 00009000 00026000[0m

[0;32mI (74) boot:  1 phy_init         RF data          01 01 0003f000 00001000[0m

[0;32mI (81) boot:  2 factory          factory app      00 00 00040000 003b0000[0m

[0;32mI (89) boot: End of partition table[0m

[0;32mI (93) esp_image: segment 0: paddr=00040020 vaddr=3f400020 size=102078h (1056888) map[0m

[0;32mI (484) esp_image: segment 1: paddr=001420a0 vaddr=3ffb0000 size=0339ch ( 13212) load[0m

[0;32mI (489) esp_image: segment 2: paddr=00145444 vaddr=40080000 size=0abd4h ( 43988) load[0m

[0;32mI (508) esp_image: segment 3: paddr=00150020 vaddr=400d0020 size=a7ca8h (687272) map[0m

[0;32mI (757) esp_image: segment 4: paddr=001f7cd0 vaddr=4008abd4 size=05228h ( 21032) load[0m

[0;32mI (773) boot: Loaded app from partition at offset 0x40000[0m

[0;32mI (774) boot: Disabling RNG early entropy source...[0m

[0;32mI (785) cpu_start: Multicore app[0m

[0;32mI (785) cpu_start: Pro cpu up.[0m

[0;32mI (786) cpu_start: Starting app cpu, entry point is 0x40081278[0m

[0;32mI (0) cpu_start: App cpu up.[0m

[0;32mI (805) cpu_start: Pro cpu start user code[0m

[0;32mI (806) cpu_start: cpu freq: 240000000[0m

[0;32mI (806) cpu_start: Application information:[0m

[0;32mI (810) cpu_start: Project name:     KC868_A16[0m

[0;32mI (815) cpu_start: App version:      v2.2.20[0m

[0;32mI (820) cpu_start: Compile time:     Apr  2 2026 15:12:09[0m

[0;32mI (826) cpu_start: ELF file SHA256:  b7c54ce742331a6d...[0m

[0;32mI (832) cpu_start: ESP-IDF:          v4.4.7[0m

[0;32mI (837) cpu_start: Min chip rev:     v0.0[0m

[0;32mI (842) cpu_start: Max chip rev:     v3.99 [0m

[0;32mI (847) cpu_start: Chip rev:         v3.1[0m

[0;32mI (852) heap_init: Initializing. RAM available for dynamic allocation:[0m

[0;32mI (859) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM[0m

[0;32mI (865) heap_init: At 3FFC5190 len 0001AE70 (107 KiB): DRAM[0m

[0;32mI (871) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM[0m

[0;32mI (877) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM[0m

[0;32mI (884) heap_init: At 4008FDFC len 00010204 (64 KiB): IRAM[0m

[0;32mI (891) spi_flash: detected chip: generic[0m

[0;32mI (895) spi_flash: flash io: dio[0m

[0;32mI (900) cpu_start: Starting scheduler on PRO CPU.[0m

[0;32mI (0) cpu_start: Starting scheduler on APP CPU.[0m

[0;32mI (914) main: [APP] Startup..[0m

[0;32mI (917) main: [APP] Free memory: 223808 bytes[0m

[0;32mI (922) main: [APP] IDF version: v4.4.7[0m

[0;32mI (985) NVS: save default system config.[0m

[0;32mI (991) NVS: save default network config.[0m

[0;32mI (997) NVS: save default tuya config.[0m

[0;32mI (1002) NVS: save default protocol config.[0m

[0;32mI (1009) NVS: save default input config.[0m

[0;32mI (1012) NVS: save default output config.[0m

[0;32mI (1017) NVS: save default name config.[0m

[0;32mI (1025) NVS: save default state.[0m

[0;32mI (1029) NVS: save default config.[0m

[0;32mI (1035) NVS: save default config.[0m

[0;32mI (1039) NVS: save default config.[0m

[0;32mI (1155) NVS: save default config.[0m

[0;32mI (1370) NVS: init nvs finish.[0m

[0;31mE (6371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:[0m

[0;31mE (6371) task_wdt:  - IDLE0 (CPU 0)[0m

[0;31mE (6371) task_wdt: Tasks currently running:[0m

[0;31mE (6371) task_wdt: CPU 0: main[0m

[0;31mE (6371) task_wdt: CPU 1: IDLE1[0m

[0;31mE (6371) task_wdt: Print CPU 0 (current core) backtrace[0m

Backtrace: 0x400F1456:0x3FFB0B90 0x40082C75:0x3FFB0BB0 0x40008541:0x3FFC7610 0x40088625:0x3FFC7630 0x400F3C0E:0x3FFC7650 0x400D9D51:0x3FFC7680 0x400D85BA:0x3FFC7710 0x40175DF7:0x3FFC7730

[0;31mE (6371) task_wdt: Print CPU 1 backtrace[0m

Backtrace: 0x40085585:0x3FFB1190 0x40082C75:0x3FFB11B0 0x4000BFED:0x3FFC8550 0x4008CC92:0x3FFC8560 0x400F16BF:0x3FFC8580 0x400F16CB:0x3FFC85B0 0x400D4E16:0x3FFC85D0 0x4008AE18:0x3FFC85F0

[0;31mE (11371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:[0m

[0;31mE (11371) task_wdt:  - IDLE0 (CPU 0)[0m

[0;31mE (11371) task_wdt: Tasks currently running:[0m

[0;31mE (11371) task_wdt: CPU 0: main[0m

[0;31mE (11371) task_wdt: CPU 1: IDLE1[0m

[0;31mE (11371) task_wdt: Print CPU 0 (current core) backtrace[0m

Backtrace: 0x400F1456:0x3FFB0B90 0x40082C75:0x3FFB0BB0 0x40008541:0x3FFC7610 0x40088625:0x3FFC7630 0x400F3C0E:0x3FFC7650 0x400D9D51:0x3FFC7680 0x400D85BA:0x3FFC7710 0x40175DF7:0x3FFC7730

etc.

Any idea why the watchdog is not reset?

What is your advice?

Kind regards

Vincent]]> <![CDATA[KC868-A16 v1.6 – relays 9–16 not working in ESPHome]]> https://www.kincony.com/forum/showthread.php?tid=9214 Tue, 07 Apr 2026 04:55:29 +0800 dilo@interia.eu]]> https://www.kincony.com/forum/showthread.php?tid=9214
I use KC868-A16 (version 1.6).

I flashed ESPHome and I can control relays 1–8 correctly.
But relays 9–16 are not working.

I2C scan shows:
0x21, 0x22, 0x24, 0x25

PCF8574 at 0x24 works fine.
PCF8574 at 0x25 is detected but relays don’t respond.

I tried different pin mappings but still only first 8 relays work.

Can you provide correct ESPHome YAML for this hardware version?

Thank you.
I can provide logs or photos if needed.]]>
I use KC868-A16 (version 1.6).

I flashed ESPHome and I can control relays 1–8 correctly.
But relays 9–16 are not working.

I2C scan shows:
0x21, 0x22, 0x24, 0x25

PCF8574 at 0x24 works fine.
PCF8574 at 0x25 is detected but relays don’t respond.

I tried different pin mappings but still only first 8 relays work.

Can you provide correct ESPHome YAML for this hardware version?

Thank you.
I can provide logs or photos if needed.]]> <![CDATA[Connecting Nextion NX3224K028 HMI display to KC868-A16S?]]> https://www.kincony.com/forum/showthread.php?tid=9179 Sat, 28 Mar 2026 00:43:08 +0800 markusd1984]]> https://www.kincony.com/forum/showthread.php?tid=9179
If yes, I need clarification on how to wire it safely:

Which pins for TX/RX? I know I cannot use the I2C header (GPIO 4/5) because it runs the PCF8574 relay chips.
The Boot Issue: If I use the GSM header (GPIO 13/15), how do I prevent the ESP32 from failing to boot? (Since GPIO 15 is a strapping pin and Nextion holds it HIGH).
Power & Pinout: Where is the safest place to pull 5V/GND, and what is the exact physical pin order on the board so I wire my custom cable correctly?

I want to use it as a backup to control the relays in case HA / network is offline (to manage my heating thermal actuators).

Thanks in advance!]]>
If yes, I need clarification on how to wire it safely:

Which pins for TX/RX? I know I cannot use the I2C header (GPIO 4/5) because it runs the PCF8574 relay chips.
The Boot Issue: If I use the GSM header (GPIO 13/15), how do I prevent the ESP32 from failing to boot? (Since GPIO 15 is a strapping pin and Nextion holds it HIGH).
Power & Pinout: Where is the safest place to pull 5V/GND, and what is the exact physical pin order on the board so I wire my custom cable correctly?

I want to use it as a backup to control the relays in case HA / network is offline (to manage my heating thermal actuators).

Thanks in advance!]]> <![CDATA[A8 brick]]> https://www.kincony.com/forum/showthread.php?tid=9134 Wed, 18 Mar 2026 16:50:02 +0800 kid]]> https://www.kincony.com/forum/showthread.php?tid=9134

.pdf

flash.pdf (Size: 74.75 KB / Downloads: 114)

It is the first time ever I had such an issue with an esp device. And I use them a lot - with WLED, custom procects etc. Is there maybe something wrong with the pcb design?

I hoped by buying a more expensive relais board to get not into trouble.]]> <![CDATA[PinOut AOI KC868-A8V3]]> https://www.kincony.com/forum/showthread.php?tid=9061 Fri, 20 Feb 2026 18:25:56 +0800 JuDie07]]> https://www.kincony.com/forum/showthread.php?tid=9061 I have already found all possible AIO/pinouts on your website, but mostly only version 1.3 (without SD card).
I need exactly this physical pin assignment (1-8).
I have the GPIO assignment “SPI-MOSI: GPIO10, SPI-SCK: GPIO11....”
Thanks in advance.]]> I have already found all possible AIO/pinouts on your website, but mostly only version 1.3 (without SD card).
I need exactly this physical pin assignment (1-8).
I have the GPIO assignment “SPI-MOSI: GPIO10, SPI-SCK: GPIO11....”
Thanks in advance.]]> <![CDATA[KC868-A16 UART pins]]> https://www.kincony.com/forum/showthread.php?tid=9055 Wed, 18 Feb 2026 23:37:17 +0800 sign_in]]> https://www.kincony.com/forum/showthread.php?tid=9055
I just got an A16 board. I read the design review (https://www.kincony.com/esp32-board-16-c...dware.html) but I didn't really find any proper solution to connect RX / TX UART TTL pins to the board (for my R503 fingerprint sensor).

Could someone please help me how to connect that sensor / use UART with that board?

Thanks and best regards!
Stefan]]>
I just got an A16 board. I read the design review (https://www.kincony.com/esp32-board-16-c...dware.html) but I didn't really find any proper solution to connect RX / TX UART TTL pins to the board (for my R503 fingerprint sensor).

Could someone please help me how to connect that sensor / use UART with that board?

Thanks and best regards!
Stefan]]> <![CDATA[Kincony A-128 – Digital Output LEDs glowing when OFF + module freezes when switching]]> https://www.kincony.com/forum/showthread.php?tid=9037 Tue, 10 Feb 2026 17:57:16 +0800 krzemodam2]]> https://www.kincony.com/forum/showthread.php?tid=9037 I am experiencing two possibly related issues with my Kincony A-128 controller.

Issue 1 – Digital Output LEDs glowing when OFF
Some Digital Output LEDs are glowing dimly even when the outputs are OFF in the control panel.
When I turn an output ON, the LED becomes much brighter (normal behavior).
Details:

One section has 8 LEDs dimly ON
Another section has 4 out of 8 LEDs dimly ON
The remaining 14 sections work correctly
The issue always affects the same sections
LEDs are visible directly on the board
I may have accidentally caused a short circuit on these outputs during wiring

Issue 2 – Module freezes when switching all outputs ON
When I use Home Assistant and press a button that turns all relays ON at once, the following happens:

The module freezes
All channels turn OFF
Home Assistant shows the device as offline
The module does not reconnect automatically
I have to disconnect power completely and power it on again for Home Assistant to discover it again

Important observations:

If I turn the outputs on slowly / step by step, the problem does not occur
The problem only appears when switching many outputs ON simultaneously

Load and power details

Most outputs are connected to 6A relays
Some outputs are connected to WAGO 16A relays (higher current consumption)
All relays and the A-128 module are powered from the same 24V power supply
Control voltage and relay supply voltage are both 24V

Questions

Could the dimly glowing LEDs indicate damaged output channels?
Could the freeze/offline behavior be caused by power supply overload or voltage drop when switching all outputs at once?
Is this a known behavior of the A-128 when driving many relays simultaneously?
Has anyone experienced similar issues with A-128 and Home Assistant?

I am attaching photos of the board showing the glowing LEDs.
I can also provide:

Firmware version
Power supply specifications
Voltage measurements during switching

Thank you for any help or suggestions.
Best regards

.jpeg

Screenshot_20260203_235908_Home.jpeg (Size: 52.06 KB / Downloads: 90)

.jpeg

20260209_152754.jpeg (Size: 274.22 KB / Downloads: 95)

.jpeg

20260209_152651.jpeg (Size: 259.25 KB / Downloads: 91) ]]> I am experiencing two possibly related issues with my Kincony A-128 controller.

One section has 8 LEDs dimly ON
Another section has 4 out of 8 LEDs dimly ON
The remaining 14 sections work correctly
The issue always affects the same sections
LEDs are visible directly on the board
I may have accidentally caused a short circuit on these outputs during wiring

Issue 2 – Module freezes when switching all outputs ON
When I use Home Assistant and press a button that turns all relays ON at once, the following happens:

The module freezes
All channels turn OFF
Home Assistant shows the device as offline
The module does not reconnect automatically
I have to disconnect power completely and power it on again for Home Assistant to discover it again

Important observations:

If I turn the outputs on slowly / step by step, the problem does not occur
The problem only appears when switching many outputs ON simultaneously

Load and power details

Most outputs are connected to 6A relays
Some outputs are connected to WAGO 16A relays (higher current consumption)
All relays and the A-128 module are powered from the same 24V power supply
Control voltage and relay supply voltage are both 24V

Questions

Could the dimly glowing LEDs indicate damaged output channels?
Could the freeze/offline behavior be caused by power supply overload or voltage drop when switching all outputs at once?
Is this a known behavior of the A-128 when driving many relays simultaneously?
Has anyone experienced similar issues with A-128 and Home Assistant?

I am attaching photos of the board showing the glowing LEDs.
I can also provide:

Firmware version
Power supply specifications
Voltage measurements during switching

Thank you for any help or suggestions.
Best regards

.jpeg

Screenshot_20260203_235908_Home.jpeg (Size: 52.06 KB / Downloads: 90)

.jpeg

20260209_152754.jpeg (Size: 274.22 KB / Downloads: 95)

.jpeg

20260209_152651.jpeg (Size: 259.25 KB / Downloads: 91) ]]> <![CDATA[Relay board wiring error?]]> https://www.kincony.com/forum/showthread.php?tid=8962 Thu, 22 Jan 2026 22:58:31 +0800 Elgatoguiri]]> https://www.kincony.com/forum/showthread.php?tid=8962 I've wired the controller up with a relay board but it acts a bit strange.
All the MOSFET LEDs are on at all the time.

The relay board uses 3 pins for power options. It is set to VCC JD-VCC.

The relays work when controlled from homeassistant through esphome with a little quirk. When homeassistant switches are off the relays turn on. So it works the opposite way.

The relay board gets its own power and ground.

Are the LEDs supposed to be on at all the time when a relay board is used ?

Is the opposite switching direction a configuration error or I wired something up incorrectly?

This is my esphome config for the board:

Code:
uart:

  - id: rs485

    tx_pin: GPIO13

    rx_pin: GPIO16

    baud_rate: 9600

remote_receiver:

  pin:

    number: GPIO2

    ignore_strapping_warning: true

remote_transmitter:

  pin:

    number: GPIO15

    ignore_strapping_warning: true

  carrier_duty_percent: 100%

i2c:

  sda: GPIO4

  scl:

    number: GPIO5

    ignore_strapping_warning: true

pcf8574:

  - id: inputs_1_8

    address: 0x22

    pcf8575: false

  - id: inputs_9_16

    address: 0x21

    pcf8575: false

  - id: outputs_1_8

    address: 0x24

    pcf8575: false

  - id: outputs_9_16

    address: 0x25

    pcf8575: false

binary_sensor:

  - platform: gpio

    name: "KC868-A16-HT1"

    pin:

      number: GPIO32

      inverted: true

  - platform: gpio

    name: "KC868-A16-HT2"

    pin:

      number: GPIO33

      inverted: true

  - platform: gpio

    name: "KC868-A16-HT3"

    pin:

      number: GPIO14

      inverted: true

  - platform: gpio

    name: "KC868-A16-X01"

    pin:

      pcf8574: inputs_1_8

      number: 0

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y01

    on_release: 

      then:

        - switch.turn_off: out_y01

  - platform: gpio

    name: "KC868-A16-X02"

    pin:

      pcf8574: inputs_1_8

      number: 1

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y02

    on_release:

      then:

        - switch.turn_off: out_y02

  - platform: gpio

    name: "KC868-A16-X03"

    pin:

      pcf8574: inputs_1_8

      number: 2

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y03

    on_release:

      then:

        - switch.turn_off: out_y03

  - platform: gpio

    name: "KC868-A16-X04"

    pin:

      pcf8574: inputs_1_8

      number: 3

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y04

    on_release: 

      then:

        - switch.turn_off: out_y04

  - platform: gpio

    name: "KC868-A16-X05"

    pin:

      pcf8574: inputs_1_8

      number: 4

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y05

    on_release: 

      then:

        - switch.turn_off: out_y05

  - platform: gpio

    name: "KC868-A16-X06"

    pin:

      pcf8574: inputs_1_8

      number: 5

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y06

    on_release: 

      then:

        - switch.turn_off: out_y06

  - platform: gpio

    name: "KC868-A16-X07"

    pin:

      pcf8574: inputs_1_8

      number: 6

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y07

    on_release: 

      then:

        - switch.turn_off: out_y07

  - platform: gpio

    name: "KC868-A16-X08"

    pin:

      pcf8574: inputs_1_8

      number: 7

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y08

    on_release: 

      then:

        - switch.turn_off: out_y08

  - platform: gpio

    name: "KC868-A16-X09"

    pin:

      pcf8574: inputs_9_16

      number: 0

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y09

    on_release: 

      then:

        - switch.turn_off: out_y09

  - platform: gpio

    name: "KC868-A16-X10"

    pin:

      pcf8574: inputs_9_16

      number: 1

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y10

    on_release: 

      then:

        - switch.turn_off: out_y10

  - platform: gpio

    name: "KC868-A16-X11"

    pin:

      pcf8574: inputs_9_16

      number: 2

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y11

    on_release: 

      then:

        - switch.turn_off: out_y11

  - platform: gpio

    name: "KC868-A16-X12"

    pin:

      pcf8574: inputs_9_16

      number: 3

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y12

    on_release: 

      then:

        - switch.turn_off: out_y12

  - platform: gpio

    name: "KC868-A16-X13"

    pin:

      pcf8574: inputs_9_16

      number: 4

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y13

    on_release: 

      then:

        - switch.turn_off: out_y13

  - platform: gpio

    name: "KC868-A16-X14"

    pin:

      pcf8574: inputs_9_16

      number: 5

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y14

    on_release: 

      then:

        - switch.turn_off: out_y14

  - platform: gpio

    name: "KC868-A16-X15"

    pin:

      pcf8574: inputs_9_16

      number: 6

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y15

    on_release: 

      then:

        - switch.turn_off: out_y15

  - platform: gpio

    name: "KC868-A16-X16"

    pin:

      pcf8574: inputs_9_16

      number: 7

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y16

    on_release: 

      then:

        - switch.turn_off: out_y16

switch:

  - platform: gpio

    name: "KC868-A16-Y01"

    id: out_y01

    pin:

      pcf8574: outputs_1_8

      number: 0

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y02"

    id: out_y02

    pin:

      pcf8574: outputs_1_8

      number: 1

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y03"

    id: out_y03

    pin:

      pcf8574: outputs_1_8

      number: 2

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y04"

    id: out_y04

    pin:

      pcf8574: outputs_1_8

      number: 3

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y05"

    id: out_y05

    pin:

      pcf8574: outputs_1_8

      number: 4

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y06"

    id: out_y06

    pin:

      pcf8574: outputs_1_8

      number: 5

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y07"

    id: out_y07

    pin:

      pcf8574: outputs_1_8

      number: 6

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y08"

    id: out_y08

    pin:

      pcf8574: outputs_1_8

      number: 7

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y09"

    id: out_y09

    pin:

      pcf8574: outputs_9_16

      number: 0

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y10"

    id: out_y10

    pin:

      pcf8574: outputs_9_16

      number: 1

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y11"

    id: out_y11

    pin:

      pcf8574: outputs_9_16

      number: 2

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y12"

    id: out_y12

    pin:

      pcf8574: outputs_9_16

      number: 3

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y13"

    id: out_y13

    pin:

      pcf8574: outputs_9_16

      number: 4

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y14"

    id: out_y14

    pin:

      pcf8574: outputs_9_16

      number: 5

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y15"

    id: out_y15

    pin:

      pcf8574: outputs_9_16

      number: 6

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y16"

    id: out_y16

    pin:

      pcf8574: outputs_9_16

      number: 7

      mode: OUTPUT

      inverted: true

Thanks !

PXL_20260122_144524688.jpg (Size: 2.87 MB / Downloads: 129) ]]> I've wired the controller up with a relay board but it acts a bit strange.
All the MOSFET LEDs are on at all the time.

The relay board uses 3 pins for power options. It is set to VCC JD-VCC.

The relays work when controlled from homeassistant through esphome with a little quirk. When homeassistant switches are off the relays turn on. So it works the opposite way.

The relay board gets its own power and ground.

Are the LEDs supposed to be on at all the time when a relay board is used ?

Is the opposite switching direction a configuration error or I wired something up incorrectly?

This is my esphome config for the board:

Code:
uart:

  - id: rs485

    tx_pin: GPIO13

    rx_pin: GPIO16

    baud_rate: 9600

remote_receiver:

  pin:

    number: GPIO2

    ignore_strapping_warning: true

remote_transmitter:

  pin:

    number: GPIO15

    ignore_strapping_warning: true

  carrier_duty_percent: 100%

i2c:

  sda: GPIO4

  scl:

    number: GPIO5

    ignore_strapping_warning: true

pcf8574:

  - id: inputs_1_8

    address: 0x22

    pcf8575: false

  - id: inputs_9_16

    address: 0x21

    pcf8575: false

  - id: outputs_1_8

    address: 0x24

    pcf8575: false

  - id: outputs_9_16

    address: 0x25

    pcf8575: false

binary_sensor:

  - platform: gpio

    name: "KC868-A16-HT1"

    pin:

      number: GPIO32

      inverted: true

  - platform: gpio

    name: "KC868-A16-HT2"

    pin:

      number: GPIO33

      inverted: true

  - platform: gpio

    name: "KC868-A16-HT3"

    pin:

      number: GPIO14

      inverted: true

  - platform: gpio

    name: "KC868-A16-X01"

    pin:

      pcf8574: inputs_1_8

      number: 0

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y01

    on_release: 

      then:

        - switch.turn_off: out_y01

  - platform: gpio

    name: "KC868-A16-X02"

    pin:

      pcf8574: inputs_1_8

      number: 1

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y02

    on_release:

      then:

        - switch.turn_off: out_y02

  - platform: gpio

    name: "KC868-A16-X03"

    pin:

      pcf8574: inputs_1_8

      number: 2

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y03

    on_release:

      then:

        - switch.turn_off: out_y03

  - platform: gpio

    name: "KC868-A16-X04"

    pin:

      pcf8574: inputs_1_8

      number: 3

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y04

    on_release: 

      then:

        - switch.turn_off: out_y04

  - platform: gpio

    name: "KC868-A16-X05"

    pin:

      pcf8574: inputs_1_8

      number: 4

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y05

    on_release: 

      then:

        - switch.turn_off: out_y05

  - platform: gpio

    name: "KC868-A16-X06"

    pin:

      pcf8574: inputs_1_8

      number: 5

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y06

    on_release: 

      then:

        - switch.turn_off: out_y06

  - platform: gpio

    name: "KC868-A16-X07"

    pin:

      pcf8574: inputs_1_8

      number: 6

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y07

    on_release: 

      then:

        - switch.turn_off: out_y07

  - platform: gpio

    name: "KC868-A16-X08"

    pin:

      pcf8574: inputs_1_8

      number: 7

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y08

    on_release: 

      then:

        - switch.turn_off: out_y08

  - platform: gpio

    name: "KC868-A16-X09"

    pin:

      pcf8574: inputs_9_16

      number: 0

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y09

    on_release: 

      then:

        - switch.turn_off: out_y09

  - platform: gpio

    name: "KC868-A16-X10"

    pin:

      pcf8574: inputs_9_16

      number: 1

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y10

    on_release: 

      then:

        - switch.turn_off: out_y10

  - platform: gpio

    name: "KC868-A16-X11"

    pin:

      pcf8574: inputs_9_16

      number: 2

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y11

    on_release: 

      then:

        - switch.turn_off: out_y11

  - platform: gpio

    name: "KC868-A16-X12"

    pin:

      pcf8574: inputs_9_16

      number: 3

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y12

    on_release: 

      then:

        - switch.turn_off: out_y12

  - platform: gpio

    name: "KC868-A16-X13"

    pin:

      pcf8574: inputs_9_16

      number: 4

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y13

    on_release: 

      then:

        - switch.turn_off: out_y13

  - platform: gpio

    name: "KC868-A16-X14"

    pin:

      pcf8574: inputs_9_16

      number: 5

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y14

    on_release: 

      then:

        - switch.turn_off: out_y14

  - platform: gpio

    name: "KC868-A16-X15"

    pin:

      pcf8574: inputs_9_16

      number: 6

      mode: INPUT

      inverted: true

    on_press:

      then:

        - switch.turn_on: out_y15

    on_release: 

      then:

        - switch.turn_off: out_y15

  - platform: gpio

    name: "KC868-A16-X16"

    pin:

      pcf8574: inputs_9_16

      number: 7

      mode: INPUT

      inverted: true

    on_press: 

      then:

        - switch.turn_on: out_y16

    on_release: 

      then:

        - switch.turn_off: out_y16

switch:

  - platform: gpio

    name: "KC868-A16-Y01"

    id: out_y01

    pin:

      pcf8574: outputs_1_8

      number: 0

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y02"

    id: out_y02

    pin:

      pcf8574: outputs_1_8

      number: 1

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y03"

    id: out_y03

    pin:

      pcf8574: outputs_1_8

      number: 2

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y04"

    id: out_y04

    pin:

      pcf8574: outputs_1_8

      number: 3

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y05"

    id: out_y05

    pin:

      pcf8574: outputs_1_8

      number: 4

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y06"

    id: out_y06

    pin:

      pcf8574: outputs_1_8

      number: 5

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y07"

    id: out_y07

    pin:

      pcf8574: outputs_1_8

      number: 6

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y08"

    id: out_y08

    pin:

      pcf8574: outputs_1_8

      number: 7

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y09"

    id: out_y09

    pin:

      pcf8574: outputs_9_16

      number: 0

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y10"

    id: out_y10

    pin:

      pcf8574: outputs_9_16

      number: 1

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y11"

    id: out_y11

    pin:

      pcf8574: outputs_9_16

      number: 2

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y12"

    id: out_y12

    pin:

      pcf8574: outputs_9_16

      number: 3

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y13"

    id: out_y13

    pin:

      pcf8574: outputs_9_16

      number: 4

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y14"

    id: out_y14

    pin:

      pcf8574: outputs_9_16

      number: 5

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y15"

    id: out_y15

    pin:

      pcf8574: outputs_9_16

      number: 6

      mode: OUTPUT

      inverted: true

  - platform: gpio

    name: "KC868-A16-Y16"

    id: out_y16

    pin:

      pcf8574: outputs_9_16

      number: 7

      mode: OUTPUT

      inverted: true

Thanks !

PXL_20260122_144524688.jpg (Size: 2.87 MB / Downloads: 129) ]]> <![CDATA[Debuter avec KC868-A16 v1.66]]> https://www.kincony.com/forum/showthread.php?tid=8894 Fri, 09 Jan 2026 19:27:05 +0800 jflala]]> https://www.kincony.com/forum/showthread.php?tid=8894 J'ai plusieurs questions,
- je cherche à l'aide de la carte KC868-A16 v1.6 à communiquer en MODBUS TCP avec un automate Crouzet EM4, déjà est ce que cela est possible avec la carte V1.6 ?
je voudrais recuperer des valeurs de capteurs de température sur la carte pour les utiliser dans le programme du EM4.
- Par ou commencer avec cette carte ? quelle firme installer de base et ensuite quelle fichier bin me conseillez vous ?
- Précision mon automate Crouzet EM4 et connecter au reseau Ethenet de mon installation qui comporte et communique également avec
une installation home assistant.
Par avance merci de votre aide]]> J'ai plusieurs questions,
- je cherche à l'aide de la carte KC868-A16 v1.6 à communiquer en MODBUS TCP avec un automate Crouzet EM4, déjà est ce que cela est possible avec la carte V1.6 ?
je voudrais recuperer des valeurs de capteurs de température sur la carte pour les utiliser dans le programme du EM4.
- Par ou commencer avec cette carte ? quelle firme installer de base et ensuite quelle fichier bin me conseillez vous ?
- Précision mon automate Crouzet EM4 et connecter au reseau Ethenet de mon installation qui comporte et communique également avec
une installation home assistant.
Par avance merci de votre aide]]> <![CDATA[Board output not responding to input commands]]> https://www.kincony.com/forum/showthread.php?tid=8876 Sat, 03 Jan 2026 20:02:48 +0800 Elgatoguiri]]> https://www.kincony.com/forum/showthread.php?tid=8876 Finally I've received the kc868-a16 unit and got it working. Or at least somewhat working. I've flashed the kcs_kc868_a16_v2.2.18 firmware and it seems to be working. The board boots up and I can connect to it through the browser but I can't control it.
In the monitor tab there is the output section and I can click on ALL ON or ALL OFF and the squares go green or gray but the board doesn't do anything. The led indicators don't turn on and checking with a multimeter there isn't anything opening or closing.
I've tried shorting the digital inputs but that doesn't do anything either.

Link for the problem: https://youtube.com/shorts/ekwEwoERshc

Am I missing something? Do I need to set up anything else?

Thanks!]]> Finally I've received the kc868-a16 unit and got it working. Or at least somewhat working. I've flashed the kcs_kc868_a16_v2.2.18 firmware and it seems to be working. The board boots up and I can connect to it through the browser but I can't control it.
In the monitor tab there is the output section and I can click on ALL ON or ALL OFF and the squares go green or gray but the board doesn't do anything. The led indicators don't turn on and checking with a multimeter there isn't anything opening or closing.
I've tried shorting the digital inputs but that doesn't do anything either.

Link for the problem: https://youtube.com/shorts/ekwEwoERshc

Am I missing something? Do I need to set up anything else?

Thanks!]]> <![CDATA[kincony a16 modbus + WallPad wall switch]]> https://www.kincony.com/forum/showthread.php?tid=8861 Wed, 31 Dec 2025 00:59:56 +0800 wchpikus]]> https://www.kincony.com/forum/showthread.php?tid=8861 I need help with setup wallpad using modbus:
google drive with manual:
https://drive.google.com/drive/folders/1...drive_link

i have some errors, code from ai Smile

[17:49:15.467][D][modbus_controller:039]: Modbus command to device=2 register=0x100B no response received - removed from send queue [17:49:15.705][W][modbus_controller:284]: Duplicate modbus command found: type=0x4 address=4107 count=1

any user tryed this wall pad?

esphome:
name: kincony_a16_wall_switch
platform: ESP32
board: esp32dev

wifi:
ssid: "YOUR_WIFI"
password: "YOUR_PASSWORD"

logger:
baud_rate: 0

api:
ota:

uart:
id: rs485_uart
tx_pin: GPIO17
rx_pin: GPIO16
baud_rate: 9600
stop_bits: 1

modbus:
id: modbus1
uart_id: rs485_uart

modbus_controller:
- id: wallpad
address: 0x02
modbus_id: modbus1
setup_priority: -10
update_interval: 200ms

# ======================
# RELAYS (Kincony A16)
# ======================
switch:
- platform: gpio
id: relay_1
name: "Relay 1"
pin: GPIO32
on_turn_on:
- script.execute: led_1_on
on_turn_off:
- script.execute: led_1_off

- platform: gpio
id: relay_2
name: "Relay 2"
pin: GPIO33
on_turn_on:
- script.execute: led_2_on
on_turn_off:
- script.execute: led_2_off

- platform: gpio
id: relay_3
name: "Relay 3"
pin: GPIO25
on_turn_on:
- script.execute: led_3_on
on_turn_off:
- script.execute: led_3_off

- platform: gpio
id: relay_4
name: "Relay 4"
pin: GPIO26
on_turn_on:
- script.execute: led_4_on
on_turn_off:
- script.execute: led_4_off

# ======================
# BUTTON INPUTS (RS485)
# ======================
binary_sensor:
- platform: modbus_controller
modbus_controller_id: wallpad
name: "Button 1"
register_type: holding
address: 0x100B
bitmask: 0x0001
on_press:
- switch.toggle: relay_1

- platform: modbus_controller
name: "Button 2"
register_type: holding
address: 0x100B
bitmask: 0x0002
on_press:
- switch.toggle: relay_2

- platform: modbus_controller
name: "Button 3"
register_type: holding
address: 0x100B
bitmask: 0x0004
on_press:
- switch.toggle: relay_3

- platform: modbus_controller
name: "Button 4"
register_type: holding
address: 0x100B
bitmask: 0x0008
on_press:
- switch.toggle: relay_4

# ======================
# LED CONTROL SCRIPTS
# ======================
script:
- id: led_1_on
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0101 # White LED ON

- id: led_1_off
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0001 # Yellow LED

- id: led_2_on
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0102

- id: led_2_off
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0002

- id: led_3_on
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0104

- id: led_3_off
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0004

- id: led_4_on
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0108

- id: led_4_off
then:
- modbus_controller.write_register:
id: wallpad
address: 0x1008
value: 0x0008]]> <![CDATA[Kc868a newbie questions]]> https://www.kincony.com/forum/showthread.php?tid=8827 Thu, 18 Dec 2025 23:40:08 +0800 Elgatoguiri]]> https://www.kincony.com/forum/showthread.php?tid=8827 I'm about to buy my first KC868 module but I have some very basic questions.

I had a tuya wifi relay board before and that created 13 switches which saturated my wifi network. If I flash esphome on this kc868 board will it create 16 switches on the network or just one device?

I need to have toggle switches able to control the relays and at the same time I want to be able control the switches from homeassistant. So if the toggle switch is on I still want to be able to turn the relay off.
This means if the toggle switch is at off state and I turn the relay on remotely then changing the manual switch to on will do nothing because the relay is already on.

Thx!]]> I'm about to buy my first KC868 module but I have some very basic questions.

I had a tuya wifi relay board before and that created 13 switches which saturated my wifi network. If I flash esphome on this kc868 board will it create 16 switches on the network or just one device?

I need to have toggle switches able to control the relays and at the same time I want to be able control the switches from homeassistant. So if the toggle switch is on I still want to be able to turn the relay off.
This means if the toggle switch is at off state and I turn the relay on remotely then changing the manual switch to on will do nothing because the relay is already on.

Thx!]]>