<![CDATA[Smart Home Automation Forum - KC868-A series and Uair Smart Controller]]> https://www.kincony.com/forum/ Thu, 09 Jul 2026 02:30:17 +0000 MyBB <![CDATA[Firmware for KCS 868 A8 v 1.7 board]]> https://www.kincony.com/forum/showthread.php?tid=9569 Fri, 03 Jul 2026 23:10:58 +0800 zali]]> https://www.kincony.com/forum/showthread.php?tid=9569
I have a KC868 A8, after watching your video on Youtube I downloaded firmware KCS_KC868_A8_V1.9.1 and KCS_KC868_A8_V2.2.20. I am able to flash both versions but it doesn't show all option on its webpage or incomplete options. fx. I don't see the option to bind input and output port together.
Could you please send me the ulr link to download the compatible firmware version.

Best regards

Zulfqar]]>
I have a KC868 A8, after watching your video on Youtube I downloaded firmware KCS_KC868_A8_V1.9.1 and KCS_KC868_A8_V2.2.20. I am able to flash both versions but it doesn't show all option on its webpage or incomplete options. fx. I don't see the option to bind input and output port together.
Could you please send me the ulr link to download the compatible firmware version.

Best regards

Zulfqar]]> <![CDATA[Force sensitive sensor with kc868-A]]> https://www.kincony.com/forum/showthread.php?tid=9547 Fri, 26 Jun 2026 14:16:31 +0800 Elgatoguiri]]> https://www.kincony.com/forum/showthread.php?tid=9547
I have a Force sensitive resistor: https://www.aliexpress.com/p/order/index...76dbGk3szT

I'd like to know if it's possible to directly connect it to the board and use it as switch in esphome. 

Thanks!]]>
I have a Force sensitive resistor: https://www.aliexpress.com/p/order/index...76dbGk3szT

I'd like to know if it's possible to directly connect it to the board and use it as switch in esphome. 

Thanks!]]> <![CDATA[The watch shows the wrong time in standalone mode.]]> https://www.kincony.com/forum/showthread.php?tid=9492 Tue, 16 Jun 2026 04:06:16 +0800 rosnoteh]]> https://www.kincony.com/forum/showthread.php?tid=9492 The watch shows the wrong time in standalone mode. The controller is connected to a local network without internet access. Time zone - UTC+3.
Turn on the controller. Click "Synchronize browser time".
The controller's clock shows the same time as the computer's clock. Turn off the controller, and then turn on the controller. The controller clock shows the time 3 hours later.
Turn off the controller again, and then turn on the controller. The controller clock shows the time 6 hours later.]]> The watch shows the wrong time in standalone mode. The controller is connected to a local network without internet access. Time zone - UTC+3.
Turn on the controller. Click "Synchronize browser time".
The controller's clock shows the same time as the computer's clock. Turn off the controller, and then turn on the controller. The controller clock shows the time 3 hours later.
Turn off the controller again, and then turn on the controller. The controller clock shows the time 6 hours later.]]> <![CDATA[KC868-A16v3 integration with 5V sensors and loads ?]]> https://www.kincony.com/forum/showthread.php?tid=9371 Fri, 29 May 2026 20:31:19 +0800 Alx]]> https://www.kincony.com/forum/showthread.php?tid=9371
I am planning a project based on the KC868-A16 v3.1 (REV:1.6) board. My peripheral types include 5V digital sensors (TTL/CMOS) and low-power 5V loads.

Could you please help me with the following technical questions:
  1. LO0 and LO1 with 5V: The official documentation specifies 12V/24V for the LO0 and LO1 power supply. Is it safe and functionally possible to apply a 5V external voltage to these specific channels instead?
  2. Onboard 5V VCC Usage for LO0 and LO1: Can I use the internal 5V VCC rail from the board to power the LO0 and LO1 loads? The total load current will be under 1A, which is within the XL1509-5 regulator capacity. Are there any internal limitations preventing this?
  3. 16 Digital Inputs with 5V logic: How can I modify all 16 Digital Inputs (INPUT1 and INPUT2) to safely and accurately read active 5V digital signals (TTL/CMOS)? What is the exact hardware modification procedure for the PCB?

Thank you.]]>
I am planning a project based on the KC868-A16 v3.1 (REV:1.6) board. My peripheral types include 5V digital sensors (TTL/CMOS) and low-power 5V loads.

Could you please help me with the following technical questions:
  1. LO0 and LO1 with 5V: The official documentation specifies 12V/24V for the LO0 and LO1 power supply. Is it safe and functionally possible to apply a 5V external voltage to these specific channels instead?
  2. Onboard 5V VCC Usage for LO0 and LO1: Can I use the internal 5V VCC rail from the board to power the LO0 and LO1 loads? The total load current will be under 1A, which is within the XL1509-5 regulator capacity. Are there any internal limitations preventing this?
  3. 16 Digital Inputs with 5V logic: How can I modify all 16 Digital Inputs (INPUT1 and INPUT2) to safely and accurately read active 5V digital signals (TTL/CMOS)? What is the exact hardware modification procedure for the PCB?

Thank you.]]> <![CDATA[KC868-A16v3 schematic]]> https://www.kincony.com/forum/showthread.php?tid=9369 Thu, 28 May 2026 19:25:58 +0800 Alx]]> https://www.kincony.com/forum/showthread.php?tid=9369
Recently, I bought a KC868-A16v3.
Could you please confirm whether this schematic is valid for my KC868-A16v3?

https://www.kincony.com/download/KC868-A...ematic.pdf

Thank you in advance for your prompt reply.]]>
Recently, I bought a KC868-A16v3.
Could you please confirm whether this schematic is valid for my KC868-A16v3?

https://www.kincony.com/download/KC868-A...ematic.pdf

Thank you in advance for your prompt reply.]]> <![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: 111)
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: 111) ]]>
.jpeg   WhatsApp Image 2026-05-02 at 11.19.33 PM.jpeg (Size: 85.54 KB / Downloads: 111)
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: 111) ]]> <![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:
  1. 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?
  2. Or are these extenders purely hardware-level overrides that bypass the ESP32 completely?
  3. 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:
  1. 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?
  2. Or are these extenders purely hardware-level overrides that bypass the ESP32 completely?
  3. 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
I (29) boot: ESP-IDF 5.1.5 2nd stage bootloader
I (29) boot: compile time Jan 18 2025 19:20:33
I (29) boot: Multicore bootloader
I (33) boot: chip revision: v3.1
I (37) boot.esp32: SPI Speed      : 40MHz
I (42) boot.esp32: SPI Mode       : DIO
I (46) boot.esp32: SPI Flash Size : 4MB
I (51) boot: Enabling RNG early entropy source...
I (56) boot: Partition Table:
I (60) boot: ## Label            Usage          Type ST Offset   Length
I (67) boot:  0 otadata          OTA data         01 00 00009000 00002000
I (75) boot:  1 phy_init         RF data          01 01 0000b000 00001000
I (82) boot:  2 app0             OTA app          00 10 00010000 001c0000
I (90) boot:  3 app1             OTA app          00 11 001d0000 001c0000
I (97) boot:  4 nvs              WiFi data        01 02 00390000 0006d000
I (105) boot: End of partition table
I (109) esp_image: segment 0: paddr=001d0020 vaddr=3f400020 size=1d6ech (120556) map
I (161) esp_image: segment 1: paddr=001ed714 vaddr=3ffb0000 size=025e4h (  9700) load
I (165) esp_image: segment 2: paddr=001efd00 vaddr=40080000 size=00318h (   792) load
I (167) esp_image: segment 3: paddr=001f0020 vaddr=400d0020 size=4c58ch (312716) map
I (288) esp_image: segment 4: paddr=0023c5b4 vaddr=40080318 size=09bfch ( 39932) load
I (305) esp_image: segment 5: paddr=002461b8 vaddr=50000000 size=00020h (    32) load
I (310) boot: Loaded app from partition at offset 0x1d0000
I (311) boot: Disabling RNG early entropy source...
[I][logger:120]: Log initialized
[C][safe_mode:136]: Unsuccessful boot attempts: 10
[E][safe_mode:148]: Boot loop detected
[E][component:420]: safe_mode set Error flag: unspecified
[I][app:089]: Running through setup()
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
I (29) boot: ESP-IDF v4.4.7 2nd stage bootloader
I (29) boot: compile time 15:12:15
I (29) boot: Multicore bootloader
I (32) boot: chip revision: v3.1
I (36) boot.esp32: SPI Speed      : 40MHz
I (41) boot.esp32: SPI Mode       : DIO
I (45) boot.esp32: SPI Flash Size : 4MB
I (50) boot: Enabling RNG early entropy source...
I (55) boot: Partition Table:
I (59) boot: ## Label            Usage          Type ST Offset   Length
I (66) boot:  0 nvs              WiFi data        01 02 00009000 00026000
I (74) boot:  1 phy_init         RF data          01 01 0003f000 00001000
I (81) boot:  2 factory          factory app      00 00 00040000 003b0000
I (89) boot: End of partition table
I (93) esp_image: segment 0: paddr=00040020 vaddr=3f400020 size=102078h (1056888) map
I (484) esp_image: segment 1: paddr=001420a0 vaddr=3ffb0000 size=0339ch ( 13212) load
I (489) esp_image: segment 2: paddr=00145444 vaddr=40080000 size=0abd4h ( 43988) load
I (508) esp_image: segment 3: paddr=00150020 vaddr=400d0020 size=a7ca8h (687272) map
I (757) esp_image: segment 4: paddr=001f7cd0 vaddr=4008abd4 size=05228h ( 21032) load
I (773) boot: Loaded app from partition at offset 0x40000
I (774) boot: Disabling RNG early entropy source...
I (785) cpu_start: Multicore app
I (785) cpu_start: Pro cpu up.
I (786) cpu_start: Starting app cpu, entry point is 0x40081278
I (0) cpu_start: App cpu up.
I (805) cpu_start: Pro cpu start user code
I (806) cpu_start: cpu freq: 240000000
I (806) cpu_start: Application information:
I (810) cpu_start: Project name:     KC868_A16
I (815) cpu_start: App version:      v2.2.20
I (820) cpu_start: Compile time:     Apr  2 2026 15:12:09
I (826) cpu_start: ELF file SHA256:  b7c54ce742331a6d...
I (832) cpu_start: ESP-IDF:          v4.4.7
I (837) cpu_start: Min chip rev:     v0.0
I (842) cpu_start: Max chip rev:     v3.99 
I (847) cpu_start: Chip rev:         v3.1
I (852) heap_init: Initializing. RAM available for dynamic allocation:
I (859) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (865) heap_init: At 3FFC5190 len 0001AE70 (107 KiB): DRAM
I (871) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (877) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (884) heap_init: At 4008FDFC len 00010204 (64 KiB): IRAM
I (891) spi_flash: detected chip: generic
I (895) spi_flash: flash io: dio
I (900) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (914) main: [APP] Startup..
I (917) main: [APP] Free memory: 223808 bytes
I (922) main: [APP] IDF version: v4.4.7
I (985) NVS: save default system config.
I (991) NVS: save default network config.
I (997) NVS: save default tuya config.
I (1002) NVS: save default protocol config.
I (1009) NVS: save default input config.
I (1012) NVS: save default output config.
I (1017) NVS: save default name config.
I (1025) NVS: save default state.
I (1029) NVS: save default config.
I (1035) NVS: save default config.
I (1039) NVS: save default config.
I (1155) NVS: save default config.
I (1370) NVS: init nvs finish.
E (6371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (6371) task_wdt:  - IDLE0 (CPU 0)
E (6371) task_wdt: Tasks currently running:
E (6371) task_wdt: CPU 0: main
E (6371) task_wdt: CPU 1: IDLE1
E (6371) task_wdt: Print CPU 0 (current core) backtrace

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

E (6371) task_wdt: Print CPU 1 backtrace

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

E (11371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (11371) task_wdt:  - IDLE0 (CPU 0)
E (11371) task_wdt: Tasks currently running:
E (11371) task_wdt: CPU 0: main
E (11371) task_wdt: CPU 1: IDLE1
E (11371) task_wdt: Print CPU 0 (current core) backtrace

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
I (29) boot: ESP-IDF 5.1.5 2nd stage bootloader
I (29) boot: compile time Jan 18 2025 19:20:33
I (29) boot: Multicore bootloader
I (33) boot: chip revision: v3.1
I (37) boot.esp32: SPI Speed      : 40MHz
I (42) boot.esp32: SPI Mode       : DIO
I (46) boot.esp32: SPI Flash Size : 4MB
I (51) boot: Enabling RNG early entropy source...
I (56) boot: Partition Table:
I (60) boot: ## Label            Usage          Type ST Offset   Length
I (67) boot:  0 otadata          OTA data         01 00 00009000 00002000
I (75) boot:  1 phy_init         RF data          01 01 0000b000 00001000
I (82) boot:  2 app0             OTA app          00 10 00010000 001c0000
I (90) boot:  3 app1             OTA app          00 11 001d0000 001c0000
I (97) boot:  4 nvs              WiFi data        01 02 00390000 0006d000
I (105) boot: End of partition table
I (109) esp_image: segment 0: paddr=001d0020 vaddr=3f400020 size=1d6ech (120556) map
I (161) esp_image: segment 1: paddr=001ed714 vaddr=3ffb0000 size=025e4h (  9700) load
I (165) esp_image: segment 2: paddr=001efd00 vaddr=40080000 size=00318h (   792) load
I (167) esp_image: segment 3: paddr=001f0020 vaddr=400d0020 size=4c58ch (312716) map
I (288) esp_image: segment 4: paddr=0023c5b4 vaddr=40080318 size=09bfch ( 39932) load
I (305) esp_image: segment 5: paddr=002461b8 vaddr=50000000 size=00020h (    32) load
I (310) boot: Loaded app from partition at offset 0x1d0000
I (311) boot: Disabling RNG early entropy source...
[I][logger:120]: Log initialized
[C][safe_mode:136]: Unsuccessful boot attempts: 10
[E][safe_mode:148]: Boot loop detected
[E][component:420]: safe_mode set Error flag: unspecified
[I][app:089]: Running through setup()
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
I (29) boot: ESP-IDF v4.4.7 2nd stage bootloader
I (29) boot: compile time 15:12:15
I (29) boot: Multicore bootloader
I (32) boot: chip revision: v3.1
I (36) boot.esp32: SPI Speed      : 40MHz
I (41) boot.esp32: SPI Mode       : DIO
I (45) boot.esp32: SPI Flash Size : 4MB
I (50) boot: Enabling RNG early entropy source...
I (55) boot: Partition Table:
I (59) boot: ## Label            Usage          Type ST Offset   Length
I (66) boot:  0 nvs              WiFi data        01 02 00009000 00026000
I (74) boot:  1 phy_init         RF data          01 01 0003f000 00001000
I (81) boot:  2 factory          factory app      00 00 00040000 003b0000
I (89) boot: End of partition table
I (93) esp_image: segment 0: paddr=00040020 vaddr=3f400020 size=102078h (1056888) map
I (484) esp_image: segment 1: paddr=001420a0 vaddr=3ffb0000 size=0339ch ( 13212) load
I (489) esp_image: segment 2: paddr=00145444 vaddr=40080000 size=0abd4h ( 43988) load
I (508) esp_image: segment 3: paddr=00150020 vaddr=400d0020 size=a7ca8h (687272) map
I (757) esp_image: segment 4: paddr=001f7cd0 vaddr=4008abd4 size=05228h ( 21032) load
I (773) boot: Loaded app from partition at offset 0x40000
I (774) boot: Disabling RNG early entropy source...
I (785) cpu_start: Multicore app
I (785) cpu_start: Pro cpu up.
I (786) cpu_start: Starting app cpu, entry point is 0x40081278
I (0) cpu_start: App cpu up.
I (805) cpu_start: Pro cpu start user code
I (806) cpu_start: cpu freq: 240000000
I (806) cpu_start: Application information:
I (810) cpu_start: Project name:     KC868_A16
I (815) cpu_start: App version:      v2.2.20
I (820) cpu_start: Compile time:     Apr  2 2026 15:12:09
I (826) cpu_start: ELF file SHA256:  b7c54ce742331a6d...
I (832) cpu_start: ESP-IDF:          v4.4.7
I (837) cpu_start: Min chip rev:     v0.0
I (842) cpu_start: Max chip rev:     v3.99 
I (847) cpu_start: Chip rev:         v3.1
I (852) heap_init: Initializing. RAM available for dynamic allocation:
I (859) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (865) heap_init: At 3FFC5190 len 0001AE70 (107 KiB): DRAM
I (871) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (877) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (884) heap_init: At 4008FDFC len 00010204 (64 KiB): IRAM
I (891) spi_flash: detected chip: generic
I (895) spi_flash: flash io: dio
I (900) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (914) main: [APP] Startup..
I (917) main: [APP] Free memory: 223808 bytes
I (922) main: [APP] IDF version: v4.4.7
I (985) NVS: save default system config.
I (991) NVS: save default network config.
I (997) NVS: save default tuya config.
I (1002) NVS: save default protocol config.
I (1009) NVS: save default input config.
I (1012) NVS: save default output config.
I (1017) NVS: save default name config.
I (1025) NVS: save default state.
I (1029) NVS: save default config.
I (1035) NVS: save default config.
I (1039) NVS: save default config.
I (1155) NVS: save default config.
I (1370) NVS: init nvs finish.
E (6371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (6371) task_wdt:  - IDLE0 (CPU 0)
E (6371) task_wdt: Tasks currently running:
E (6371) task_wdt: CPU 0: main
E (6371) task_wdt: CPU 1: IDLE1
E (6371) task_wdt: Print CPU 0 (current core) backtrace

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

E (6371) task_wdt: Print CPU 1 backtrace

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

E (11371) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (11371) task_wdt:  - IDLE0 (CPU 0)
E (11371) task_wdt: Tasks currently running:
E (11371) task_wdt: CPU 0: main
E (11371) task_wdt: CPU 1: IDLE1
E (11371) task_wdt: Print CPU 0 (current core) backtrace

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:

  1. Which pins for TX/RX? I know I cannot use the I2C header (GPIO 4/5) because it runs the PCF8574 relay chips.
  2. 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).
  3. 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:

  1. Which pins for TX/RX? I know I cannot use the I2C header (GPIO 4/5) because it runs the PCF8574 relay chips.
  2. 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).
  3. 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: 206)

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.]]>

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

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
  1. Could the dimly glowing LEDs indicate damaged output channels?
  2. Could the freeze/offline behavior be caused by power supply overload or voltage drop when switching all outputs at once?
  3. Is this a known behavior of the A-128 when driving many relays simultaneously?
  4. 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: 183)

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

.jpeg   20260209_152651.jpeg (Size: 259.25 KB / Downloads: 178) ]]> 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
  1. Could the dimly glowing LEDs indicate damaged output channels?
  2. Could the freeze/offline behavior be caused by power supply overload or voltage drop when switching all outputs at once?
  3. Is this a known behavior of the A-128 when driving many relays simultaneously?
  4. 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: 183)

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

.jpeg   20260209_152651.jpeg (Size: 259.25 KB / Downloads: 178) ]]>