Smart Home Automation Forum
Portal

Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  

Search Forums

(Advanced Search)

Forum Statistics
» Members: 9,463
» Latest member: kokqa
» Forum threads: 4,176
» Forum posts: 20,755

Full Statistics

Online Users
There are currently 46 online users.
» 0 Member(s) | 35 Guest(s)
AhrefsBot, Applebot, Bing, Crawl, PetalBot, bot

Latest Threads
KC868-H32B V5.08 firmware
Forum: News
Last Post: admin
Yesterday, 11:53 PM
» Replies: 23
» Views: 7,534
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:40 AM
» Replies: 0
» Views: 14
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:39 AM
» Replies: 0
» Views: 11
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:38 AM
» Replies: 0
» Views: 7
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:37 AM
» Replies: 0
» Views: 10
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:36 AM
» Replies: 0
» Views: 7
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:35 AM
» Replies: 0
» Views: 8
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:33 AM
» Replies: 0
» Views: 6
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:32 AM
» Replies: 0
» Views: 7
[arduino code examples fo...
Forum: B2
Last Post: admin
Yesterday, 06:30 AM
» Replies: 0
» Views: 12

  "KCS" v3.24.3 firmware BIN file download
Posted by: admin - 04-13-2026, 03:02 AM - Forum: "KCS" v3 firmware - No Replies

v3.24.3 improvement:
1: add debounce capability to digital input ports.
2: support wiegand protocol for access control panel.
3: add RS485 bridge protocol, support TR RS485 device digital input and sensor feedback for MASTER controller's mqtt message.
4: fixed bug when IF conditon have multi DI.



Attached Files
.zip   KCS_A2V3_V3.24.3.zip (Size: 1.17 MB / Downloads: 233)
.zip   KCS_A6V3_V3.24.3.zip (Size: 1.14 MB / Downloads: 237)
.zip   KCS_A8V3_V3.24.3.zip (Size: 1.2 MB / Downloads: 226)
.zip   KCS_A16V3_V3.24.3.zip (Size: 1.21 MB / Downloads: 280)
.zip   KCS_A32PRO_V3.24.3.zip (Size: 1.18 MB / Downloads: 189)
.zip   KCS_AG8_V3.24.3.zip (Size: 1.16 MB / Downloads: 203)
.zip   KCS_AIO_HYBRID_V3.24.3.zip (Size: 1.39 MB / Downloads: 238)
.zip   KCS_ALR_V3.24.3.zip (Size: 1.15 MB / Downloads: 221)
.zip   KCS_B4_V3.24.3.zip (Size: 1.2 MB / Downloads: 204)
.zip   KCS_B4M_V3.24.3.zip (Size: 1.2 MB / Downloads: 220)
.zip   KCS_B8_V3.24.3.zip (Size: 1.2 MB / Downloads: 209)
.zip   KCS_B8M_V3.24.3.zip (Size: 1.2 MB / Downloads: 220)
.zip   KCS_B16_V3.24.3.zip (Size: 1.2 MB / Downloads: 242)
.zip   KCS_B16M_V3.24.3.zip (Size: 1.2 MB / Downloads: 229)
.zip   KCS_B24_V3.24.3.zip (Size: 1.2 MB / Downloads: 219)
.zip   KCS_B24M_V3.24.3.zip (Size: 1.2 MB / Downloads: 194)
.zip   KCS_B32M_V3.24.3.zip (Size: 1.2 MB / Downloads: 197)
.zip   KCS_DM4_V3.24.3.zip (Size: 1.2 MB / Downloads: 215)
.zip   KCS_DM8_V3.24.3.zip (Size: 1.2 MB / Downloads: 194)
.zip   KCS_DM16_V3.24.3.zip (Size: 1.17 MB / Downloads: 206)
.zip   KCS_DM32_V3.24.3.zip (Size: 1.21 MB / Downloads: 197)
.zip   KCS_F4_V3.24.3.zip (Size: 1.2 MB / Downloads: 197)
.zip   KCS_F8_V3.24.3.zip (Size: 1.2 MB / Downloads: 185)
.zip   KCS_F16_V3.24.3.zip (Size: 1.21 MB / Downloads: 198)
.zip   KCS_F24_V3.24.3.zip (Size: 1.21 MB / Downloads: 227)
.zip   KCS_F32_V3.24.3.zip (Size: 1.21 MB / Downloads: 224)
.zip   KCS_G1_V3.24.3.zip (Size: 1.16 MB / Downloads: 212)
.zip   KCS_KC_TA_V3.24.3.zip (Size: 1.16 MB / Downloads: 196)
.zip   KCS_N10_V3.24.3.zip (Size: 1.07 MB / Downloads: 200)
.zip   KCS_N20_V3.24.3.zip (Size: 1.07 MB / Downloads: 225)
.zip   KCS_N30_V3.24.3.zip (Size: 1.07 MB / Downloads: 213)
.zip   KCS_N60_V3.24.3.zip (Size: 1.08 MB / Downloads: 206)
.zip   KCS_T16M_V3.24.3.zip (Size: 1.15 MB / Downloads: 196)
.zip   KCS_T32M_V3.24.3.zip (Size: 1.17 MB / Downloads: 188)
.zip   KCS_T64M_V3.24.3.zip (Size: 1.17 MB / Downloads: 244)
.zip   KCS_T128M_V3.24.3.zip (Size: 1.17 MB / Downloads: 194)
.zip   KCS_TR_V3.24.3.zip (Size: 1.13 MB / Downloads: 210)
.zip   KCS_Z1_V3.24.3.zip (Size: 1.3 MB / Downloads: 210)
Print this item

  KC868-16A crashing in infinite loop
Posted by: vdeconinck - 04-12-2026, 10:57 PM - Forum: KC868-A series and Uair Smart Controller - Replies (11)

Hi,

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

Print this item

  Current and Power not adding up for some sensors
Posted by: edalquist - 04-12-2026, 03:42 PM - Forum: N60 - Replies (10)

I'm working on getting my N60 wired up. I'm using the ESPHome YAML plus firmware update from https://www.kincony.com/forum/showthread.php?tid=9157

The listed watts does not line up with the calculated Volts * Amps for each sensor and some of them are significantly off.

Looking at just some sensors

L1 1 - 0.135A * 124.98V = 16.8723W   - 10.1W shown (6W low)
L1 2 - 0.664A * 124.98V = 82.98672W - 82.1W shown (accurate)
L1 3 - 0.134A * 124.98V = 16.74732W - 8.9W shown (7W low)
L1 4 - 2.791A * 124.98V = 348.81918W - 202W shown (146W low)
L1 5 - 1.138A * 124.98V = 142.22724W - 130.8W shown (12W low)

   

Here is the exact ESPHome config I'm using:

.txt   n60_base.txt (Size: 67.34 KB / Downloads: 150)

Print this item

  T16M
Posted by: H_spadacini - 04-11-2026, 03:07 PM - Forum: News - Replies (1)

M. Xuwei,  le professeur d'université de  Hangzhou;
il me reste plus qu'une solution !
1° ) vous retourner le produit a vos bon soins a mes frais 
2° ) racheté un module E8V3 pour pourvoir finir mon coffret
3° ) Revoir l'organisation de mon coffret en plus grand en tenant compte de l'occupation du module E8V3
pour ma baie Serveur.
P.J : schéma en développement du faire de revoir tout la conception.  Schema coffret securite baie

heureusement, mes idées ont toujours ont une bonne fin,  vu certaines tournent en chine nucléaire( en autre)
Cordialement.[url=https://acrobat.adobe.com/id/urn:aaid:sc:EU:71ac351c-118f-4725-a222-c172c1c96bcb][/url]

Print this item

  KC868-A4 with Tuya app
Posted by: Klemen - 04-11-2026, 02:51 PM - Forum: "KCS" v2 firmware system - Replies (1)

Hi,

I have a KC868-a4 board, with fimware 2.2.20 installed. I purchased tuya licence and everithing on the board seems to work, except that the board is always offline in tuya app. Already tried several things, multiple resets,... I have no idea, how to set in to online state. Any idea?

Print this item

  T16M en panne
Posted by: H_spadacini - 04-10-2026, 02:05 PM - Forum: News - Replies (4)

[Image: view?usp=sharing]
Monsieur l'administrateur;
 voici votre lien photo , Angry , je me répète le T16M est connecte sur l'alimentation Meanwell LRS-350-24 :
Présence 24 Vdc au sortie de l'alimentation
le plus (+) alimentation avec le plus (+) du T16M & le moins (-) alimentation  avec le moins (-) du T16M ,sur son bornier 
U = 24 Vdc.
Borne inferieur - Fil Bleu = -
Borne supérieur - Fil rouge = +
l'alimentation est état "on" , le voyant de l'alimentions (Pwr)est état  "on" , présence 24 Vdc en sortie alimentation mais  le dit relais ne s'allume plus son Pwr état "off" , il a fonctionne 5 mm depuis plus rien malgré la présence tension 24 Vdc a ces bornes
Tout a été vérifier au contrôleur de tension
la commande a bien était faite est livrée contrairement au propos du SAV Kincony, réclamation fait a Aliexpress a ce jour , attends un retour rapide ..
Cordialement

Print this item

  T16M
Posted by: H_spadacini - 04-09-2026, 06:20 PM - Forum: News - Replies (1)

Angry Angry Bon au vu du peu de fois de l'ingénieur Kincony face a moi ingénieur avec plus 40 années de pratiques (a la retraite) notamment en nucléaire.
j'ai pas le choix d(attendre la fin du mois, renvoyer le relais a Kincony a mes frais.
Racheter un relais car la garantie Kincony = aucune .
merci Kincony..
mon projet est stoppé actuellement sans ce relais

Print this item

  Digital input GND
Posted by: Korenktom - 04-09-2026, 05:35 PM - Forum: KC868-A32/A32 Pro - Replies (2)

Hello,

I have a question about the wiring diagram of the Kincony KC868 A32 board. The board has 32 digital inputs, where each group of 8 inputs shares one GND pin.

My question is: Does it matter which GND I use for the signal inputs, or do I need to follow a specific mapping - for example, inputs 1-8 only against the GND designated for that group? Or can I use just one GND pin for all 32 inputs?

Thank you for clarification.

Print this item

  A8v3
Posted by: Saif Kitany - 04-09-2026, 10:14 AM - Forum: "KCS" v3 firmware - Replies (3)

I have A8v3 and i downloaded the firmware.
I’m trying to connect to it by tuya.
The tuya led on pcb is blinking, but when i open tuya app, it doesnt discover the device!

Print this item

  kincony esp32s3
Posted by: H_spadacini - 04-09-2026, 07:17 AM - Forum: News - Replies (1)

Monsieur,
suite a la réponse de M Thiago Alves (autonomylogic.com) :

Hi HSPADACINI,
 
This hardware is not compatible with OpenPLC. OpenPLC only provides drivers for plain ESP32. Your device has more than just an ESP32 and therefore requires additional drivers to handle I/O. You will have to reach out to the device manufacturer asking them to contact us about adding support for their platform on our software.
 
 
Thanks,

Question pour Kincony :

serait-il possible d'avoir une exemple de programmation pouvant rendre la plateforme compatible avec OpenPlc programme open source disponible sous Git ,fonctionnant avec Arduino plc, cela faciliterai les programmes complexes sur Kincony
Cordialement.

Print this item