<![CDATA[Smart Home Automation Forum - Portal]]> https://www.kincony.com/forum/ Sat, 23 May 2026 18:54:07 +0000 MyBB <![CDATA[problem with kc868 has v2]]> https://www.kincony.com/forum/showthread.php?tid=9348 Fri, 22 May 2026 05:56:49 +0800 Gianfranco Pepi]]> https://www.kincony.com/forum/showthread.php?tid=9348 Good morning, I also did some tests with the multimeter looking at your diagram and the board seems not to work, that is, the KC868 has v2. Using your tool to check and change the assignments of the inputs to the outputs, I don't know if it also shows the activation of the outputs, but every time I close and open the input, the RS485 adapter emits a signal and under the bar it shows me the last signal that arrived, so the inputs, so to speak, "work". Now I tried with the multimeter considering that I'm using only one 12 volt power supply for everything, so the grounds are equivalent! Here is the voltage between the +12 volts and the output, which according to your diagram should be negative, always remains at 6 volts without ever varying (I'm talking about an open circuit). I tried installing a classic relay that is powered by 12 volts and has a pilot input that can be set to receive either positive or negative inputs. Obviously, I set the input to negative and when I try to close the input, the result does n

.jpeg   WhatsApp Image 2026-05-21 at 07.52.47 (1).jpeg (Size: 60.51 KB / Downloads: 31)

.jpeg   WhatsApp Image 2026-05-21 at 07.52.47 (2).jpeg (Size: 95.9 KB / Downloads: 31)

.jpeg   WhatsApp Image 2026-05-21 at 07.52.47.jpeg (Size: 66.36 KB / Downloads: 31) ]]> Good morning, I also did some tests with the multimeter looking at your diagram and the board seems not to work, that is, the KC868 has v2. Using your tool to check and change the assignments of the inputs to the outputs, I don't know if it also shows the activation of the outputs, but every time I close and open the input, the RS485 adapter emits a signal and under the bar it shows me the last signal that arrived, so the inputs, so to speak, "work". Now I tried with the multimeter considering that I'm using only one 12 volt power supply for everything, so the grounds are equivalent! Here is the voltage between the +12 volts and the output, which according to your diagram should be negative, always remains at 6 volts without ever varying (I'm talking about an open circuit). I tried installing a classic relay that is powered by 12 volts and has a pilot input that can be set to receive either positive or negative inputs. Obviously, I set the input to negative and when I try to close the input, the result does n

.jpeg   WhatsApp Image 2026-05-21 at 07.52.47 (1).jpeg (Size: 60.51 KB / Downloads: 31)

.jpeg   WhatsApp Image 2026-05-21 at 07.52.47 (2).jpeg (Size: 95.9 KB / Downloads: 31)

.jpeg   WhatsApp Image 2026-05-21 at 07.52.47.jpeg (Size: 66.36 KB / Downloads: 31) ]]> <![CDATA[CRC Errors with ESP Home & N10203060_KU_V20_260324SP]]> https://www.kincony.com/forum/showthread.php?tid=9347 Thu, 21 May 2026 11:10:58 +0800 edalquist]]> https://www.kincony.com/forum/showthread.php?tid=9347 https://www.kincony.com/forum/showthread.php?tid=9157

I'm now not getting any data and the following logs repeating over and over:
Code:
[20:07:41.184][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=100 count=68
[20:07:41.189][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=200 count=68
[20:07:41.189][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=600 count=68
[20:07:41.412][W][modbus:063]: Stop waiting for response from 1 424ms after last send
[20:07:41.447][W][modbus:219]: CRC check failed 1ms after last send
[20:07:41.455][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 3ms after last send
[20:07:41.468][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:41.713][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:41.732][W][modbus:219]: CRC check failed 1ms after last send
[20:07:41.737][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:41.751][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:41.994][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:42.015][W][modbus:219]: CRC check failed 2ms after last send
[20:07:42.021][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 5ms after last send
[20:07:42.036][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 23ms after last send
[20:07:42.402][W][modbus:063]: Stop waiting for response from 1 389ms after last send
[20:07:42.423][W][modbus:219]: CRC check failed 1ms after last send
[20:07:42.429][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:42.443][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:42.684][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:42.705][W][modbus:219]: CRC check failed 1ms after last send
[20:07:42.710][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:42.726][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:42.969][W][modbus:063]: Stop waiting for response from 1 266ms after last send
[20:07:43.007][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.012][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 3ms after last send
[20:07:43.026][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.407][W][modbus:063]: Stop waiting for response from 1 401ms after last send
[20:07:43.426][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.432][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:43.445][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.690][W][modbus:063]: Stop waiting for response from 1 265ms after last send
[20:07:43.710][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.715][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:43.730][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.975][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:43.996][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.001][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:44.012][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:44.402][W][modbus:063]: Stop waiting for response from 1 411ms after last send
[20:07:44.422][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.428][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:44.441][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:44.687][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:44.722][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.728][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 3ms after last send
[20:07:44.741][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:44.984][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.004][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.013][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.024][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.407][W][modbus:063]: Stop waiting for response from 1 403ms after last send
[20:07:45.425][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.430][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.444][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.687][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.718][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.718][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.727][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.971][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.992][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.998][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:46.011][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send


There are no other changes to the system, just completed that ARM firmware update and flashed the example ESP Home config]]> https://www.kincony.com/forum/showthread.php?tid=9157

I'm now not getting any data and the following logs repeating over and over:
Code:
[20:07:41.184][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=100 count=68
[20:07:41.189][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=200 count=68
[20:07:41.189][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=600 count=68
[20:07:41.412][W][modbus:063]: Stop waiting for response from 1 424ms after last send
[20:07:41.447][W][modbus:219]: CRC check failed 1ms after last send
[20:07:41.455][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 3ms after last send
[20:07:41.468][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:41.713][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:41.732][W][modbus:219]: CRC check failed 1ms after last send
[20:07:41.737][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:41.751][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:41.994][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:42.015][W][modbus:219]: CRC check failed 2ms after last send
[20:07:42.021][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 5ms after last send
[20:07:42.036][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 23ms after last send
[20:07:42.402][W][modbus:063]: Stop waiting for response from 1 389ms after last send
[20:07:42.423][W][modbus:219]: CRC check failed 1ms after last send
[20:07:42.429][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:42.443][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:42.684][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:42.705][W][modbus:219]: CRC check failed 1ms after last send
[20:07:42.710][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:42.726][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:42.969][W][modbus:063]: Stop waiting for response from 1 266ms after last send
[20:07:43.007][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.012][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 3ms after last send
[20:07:43.026][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.407][W][modbus:063]: Stop waiting for response from 1 401ms after last send
[20:07:43.426][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.432][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:43.445][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.690][W][modbus:063]: Stop waiting for response from 1 265ms after last send
[20:07:43.710][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.715][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:43.730][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.975][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:43.996][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.001][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:44.012][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:44.402][W][modbus:063]: Stop waiting for response from 1 411ms after last send
[20:07:44.422][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.428][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:44.441][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:44.687][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:44.722][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.728][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 3ms after last send
[20:07:44.741][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:44.984][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.004][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.013][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.024][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.407][W][modbus:063]: Stop waiting for response from 1 403ms after last send
[20:07:45.425][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.430][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.444][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.687][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.718][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.718][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.727][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.971][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.992][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.998][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:46.011][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send


There are no other changes to the system, just completed that ARM firmware update and flashed the example ESP Home config]]> <![CDATA[RS485]]> https://www.kincony.com/forum/showthread.php?tid=9343 Wed, 20 May 2026 14:06:19 +0800 kriftoft@gmail.com]]> https://www.kincony.com/forum/showthread.php?tid=9343
Problem with RS485 - AG8 send message but module with sim7600 not receive. Other function good, but TEM2=W2 dont work.Please help
http://photos.google.com/photo/AF1QipPgX...BpkWOr8yfn
https://photos.google.com/photo/AF1QipNF...AxY-YFgdf3
https://photos.google.com/photo/AF1QipNW...vnehA8visj]]>
Problem with RS485 - AG8 send message but module with sim7600 not receive. Other function good, but TEM2=W2 dont work.Please help
http://photos.google.com/photo/AF1QipPgX...BpkWOr8yfn
https://photos.google.com/photo/AF1QipNF...AxY-YFgdf3
https://photos.google.com/photo/AF1QipNW...vnehA8visj]]> <![CDATA[Questions about KinCony F16]]> https://www.kincony.com/forum/showthread.php?tid=9342 Tue, 19 May 2026 18:58:08 +0800 yazeed]]> https://www.kincony.com/forum/showthread.php?tid=9342
I want to buy the KinCony F16 16-Channel ESP32-S3 Removable Relay Controller for my car (offroad)
https://shop.kincony.com/products/kincon...1712290981

I have watched all the videos by KinCony  engineer on YouTube, but I would like direct confirmation from you on the following questions:

- Does the F16 work with DC lights and DC devices? What is the max amps or watts per channel in DC?

- How much current can each channel handle on 12V DC continuously?

- Is there Home Assistant integration, and can I connect the F16 to Home Assistant via WiFi?

- Can the F16 tolerate heat of 60-70°C inside the vehicle?

- The F16 needs 12V DC power. Can I connect it directly to my vehicle's 12V battery, or does it need an external Buck Converter / TVS Diode for protection against car voltage spikes (alternator load dump up to 100V)? If protection is needed, what product do you recommend for vehicle installation?

- Can I connect an external switch to an input so it triggers the relay directly, without waiting for Home Assistant?

- Have any customers used the F16 in cars or vans before?

Thanks,
Yazeed]]>
I want to buy the KinCony F16 16-Channel ESP32-S3 Removable Relay Controller for my car (offroad)
https://shop.kincony.com/products/kincon...1712290981

I have watched all the videos by KinCony  engineer on YouTube, but I would like direct confirmation from you on the following questions:

- Does the F16 work with DC lights and DC devices? What is the max amps or watts per channel in DC?

- How much current can each channel handle on 12V DC continuously?

- Is there Home Assistant integration, and can I connect the F16 to Home Assistant via WiFi?

- Can the F16 tolerate heat of 60-70°C inside the vehicle?

- The F16 needs 12V DC power. Can I connect it directly to my vehicle's 12V battery, or does it need an external Buck Converter / TVS Diode for protection against car voltage spikes (alternator load dump up to 100V)? If protection is needed, what product do you recommend for vehicle installation?

- Can I connect an external switch to an input so it triggers the relay directly, without waiting for Home Assistant?

- Have any customers used the F16 in cars or vans before?

Thanks,
Yazeed]]> <![CDATA[Las Firmware ?]]> https://www.kincony.com/forum/showthread.php?tid=9340 Mon, 18 May 2026 18:22:48 +0800 jltluc57]]> https://www.kincony.com/forum/showthread.php?tid=9340 I currently have firmware version 2.2.12 on my KC868_A16 board.
Is there a newer firmware version?

Could you provide a link?

Thank you]]> I currently have firmware version 2.2.12 on my KC868_A16 board.
Is there a newer firmware version?

Could you provide a link?

Thank you]]> <![CDATA[Energy calculation for negative currents]]> https://www.kincony.com/forum/showthread.php?tid=9337 Sun, 17 May 2026 20:22:20 +0800 GWS]]> https://www.kincony.com/forum/showthread.php?tid=9337

.png   2026-05-17 111107_N30_Energy.png (Size: 28.17 KB / Downloads: 66)

Although current was negatieve and power too the energy is positive.
Also noticed that in a phase where current was pos at first and neg later the energy keeps adding which makes the energy calculation incorrect.

Energy is defined as a 32-bit float so it should be able to handle pos and negatieve loads.]]>

.png   2026-05-17 111107_N30_Energy.png (Size: 28.17 KB / Downloads: 66)

Although current was negatieve and power too the energy is positive.
Also noticed that in a phase where current was pos at first and neg later the energy keeps adding which makes the energy calculation incorrect.

Energy is defined as a 32-bit float so it should be able to handle pos and negatieve loads.]]> <![CDATA[Suggestion for Kincony board for project]]> https://www.kincony.com/forum/showthread.php?tid=9335 Sun, 17 May 2026 07:24:38 +0800 igor_quintal]]> https://www.kincony.com/forum/showthread.php?tid=9335
I have a smart home running with Home Assistant for quite some time. To automate all the lights, I created a central hub where all lights connect on my breaker panel (as the picture shows). I went with a very simple setup, using a Sonoff Basic flashed with Tasmota for each light switch. It works! But it is not great, and some relays are starting to fail. Also, buying new ones and flashing them with Tasmota is a little bit of a hassle. I wanted something better like a multiple channel relay. And that's when I recently saw KinCony!

It seems perfect to what I need. But there are so many board options available that I'm a little confused of which one to get. I want something that is reliable and safe, to be used in a DIN rail with up to 16 channels. Integration with Home Assistant is a must, but from what I saw, all boards support ESP Home. So what kind of board do you guys recommend? I saw that there were cheaper and more expensive ones, but I did not get the difference between them.

Thanks a lot!

[Image: aedsdfvibnxg1.jpeg]]]>
I have a smart home running with Home Assistant for quite some time. To automate all the lights, I created a central hub where all lights connect on my breaker panel (as the picture shows). I went with a very simple setup, using a Sonoff Basic flashed with Tasmota for each light switch. It works! But it is not great, and some relays are starting to fail. Also, buying new ones and flashing them with Tasmota is a little bit of a hassle. I wanted something better like a multiple channel relay. And that's when I recently saw KinCony!

It seems perfect to what I need. But there are so many board options available that I'm a little confused of which one to get. I want something that is reliable and safe, to be used in a DIN rail with up to 16 channels. Integration with Home Assistant is a must, but from what I saw, all boards support ESP Home. So what kind of board do you guys recommend? I saw that there were cheaper and more expensive ones, but I did not get the difference between them.

Thanks a lot!

[Image: aedsdfvibnxg1.jpeg]]]> <![CDATA["KCS" v3.25.0 firmware BIN file download]]> https://www.kincony.com/forum/showthread.php?tid=9334 Sat, 16 May 2026 13:13:21 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9334
1. Daylight saving time adaptation (add DST configuration to firmware system + IFTTT automatic adjustment to new time)
2. Multi-channel configuration support for the Wiegand protocol
3. Display cumulative online duration on the web page (web + MQTT + HA)
4. Support for third-party sensor integration using the standard Modbus protocol
5. add send IR signal to ALL GPIO channels
6. add mqtt "force update" option for home assistant


.png   wiegand-multi.png (Size: 94.14 KB / Downloads: 189)

.png   HA-mqtt-force-update.png (Size: 65.01 KB / Downloads: 184)

.png   modbus-sensor.png (Size: 81.12 KB / Downloads: 181)

.png   DST.png (Size: 62.41 KB / Downloads: 188)

.png   uptime.png (Size: 47.84 KB / Downloads: 186)

.zip   KCS_A2V3_V3.25.0.zip (Size: 1.18 MB / Downloads: 33)

.zip   KCS_A6V3_V3.25.0.zip (Size: 1.15 MB / Downloads: 41)

.zip   KCS_A8V3_V3.25.0.zip (Size: 1.21 MB / Downloads: 44)

.zip   KCS_A16V3_V3.25.0.zip (Size: 1.22 MB / Downloads: 45)

.zip   KCS_A32PRO_V3.25.0.zip (Size: 1.19 MB / Downloads: 36)

.zip   KCS_AG8_V3.25.0.zip (Size: 1.17 MB / Downloads: 30)

.zip   KCS_AGV3_V3.25.0.zip (Size: 1.12 MB / Downloads: 29)

.zip   KCS_AIO_HYBRID_V3.25.0.zip (Size: 1.4 MB / Downloads: 37)

.zip   KCS_ALR_V3.25.0.zip (Size: 1.16 MB / Downloads: 27)

.zip   KCS_B4_V3.25.0.zip (Size: 1.21 MB / Downloads: 29)

.zip   KCS_B4M_V3.25.0.zip (Size: 1.21 MB / Downloads: 31)

.zip   KCS_B8_V3.25.0.zip (Size: 1.21 MB / Downloads: 31)

.zip   KCS_B8M_V3.25.0.zip (Size: 1.21 MB / Downloads: 31)

.zip   KCS_B16_V3.25.0.zip (Size: 1.21 MB / Downloads: 33)

.zip   KCS_B16M_V3.25.0.zip (Size: 1.21 MB / Downloads: 37)

.zip   KCS_B24_V3.25.0.zip (Size: 1.21 MB / Downloads: 33)

.zip   KCS_B24M_V3.25.0.zip (Size: 1.21 MB / Downloads: 30)

.zip   KCS_B32M_V3.25.0.zip (Size: 1.21 MB / Downloads: 36)

.zip   KCS_DM4_V3.25.0.zip (Size: 1.22 MB / Downloads: 30)

.zip   KCS_DM8_V3.25.0.zip (Size: 1.22 MB / Downloads: 30)

.zip   KCS_DM16_V3.25.0.zip (Size: 1.19 MB / Downloads: 26)

.zip   KCS_DM32_V3.25.0.zip (Size: 1.22 MB / Downloads: 35)

.zip   KCS_F4_V3.25.0.zip (Size: 1.21 MB / Downloads: 30)

.zip   KCS_F8_V3.25.0.zip (Size: 1.21 MB / Downloads: 34)

.zip   KCS_F16_V3.25.0.zip (Size: 1.22 MB / Downloads: 34)

.zip   KCS_F24_V3.25.0.zip (Size: 1.22 MB / Downloads: 45)

.zip   KCS_F32_V3.25.0.zip (Size: 1.22 MB / Downloads: 36)

.zip   KCS_G1_V3.25.0.zip (Size: 1.17 MB / Downloads: 36)

.zip   KCS_KC_TA_V3.25.0.zip (Size: 1.17 MB / Downloads: 29)

.zip   KCS_N10_V3.25.0.zip (Size: 1.08 MB / Downloads: 34)

.zip   KCS_N20_V3.25.0.zip (Size: 1.08 MB / Downloads: 33)

.zip   KCS_N30_V3.25.0.zip (Size: 1.08 MB / Downloads: 32)

.zip   KCS_N60_V3.25.0.zip (Size: 1.09 MB / Downloads: 39)

.zip   KCS_T16M_V3.25.0.zip (Size: 1.16 MB / Downloads: 34)

.zip   KCS_T32M_V3.25.0.zip (Size: 1.18 MB / Downloads: 35)

.zip   KCS_T64M_V3.25.0.zip (Size: 1.18 MB / Downloads: 33)

.zip   KCS_T128M_V3.25.0.zip (Size: 1.18 MB / Downloads: 36)

.zip   KCS_TR_V3.25.0.zip (Size: 1.14 MB / Downloads: 35)

.zip   KCS_Z1_V3.25.0.zip (Size: 1.31 MB / Downloads: 29) ]]>
1. Daylight saving time adaptation (add DST configuration to firmware system + IFTTT automatic adjustment to new time)
2. Multi-channel configuration support for the Wiegand protocol
3. Display cumulative online duration on the web page (web + MQTT + HA)
4. Support for third-party sensor integration using the standard Modbus protocol
5. add send IR signal to ALL GPIO channels
6. add mqtt "force update" option for home assistant


.png   wiegand-multi.png (Size: 94.14 KB / Downloads: 189)

.png   HA-mqtt-force-update.png (Size: 65.01 KB / Downloads: 184)

.png   modbus-sensor.png (Size: 81.12 KB / Downloads: 181)

.png   DST.png (Size: 62.41 KB / Downloads: 188)

.png   uptime.png (Size: 47.84 KB / Downloads: 186)

.zip   KCS_A2V3_V3.25.0.zip (Size: 1.18 MB / Downloads: 33)

.zip   KCS_A6V3_V3.25.0.zip (Size: 1.15 MB / Downloads: 41)

.zip   KCS_A8V3_V3.25.0.zip (Size: 1.21 MB / Downloads: 44)

.zip   KCS_A16V3_V3.25.0.zip (Size: 1.22 MB / Downloads: 45)

.zip   KCS_A32PRO_V3.25.0.zip (Size: 1.19 MB / Downloads: 36)

.zip   KCS_AG8_V3.25.0.zip (Size: 1.17 MB / Downloads: 30)

.zip   KCS_AGV3_V3.25.0.zip (Size: 1.12 MB / Downloads: 29)

.zip   KCS_AIO_HYBRID_V3.25.0.zip (Size: 1.4 MB / Downloads: 37)

.zip   KCS_ALR_V3.25.0.zip (Size: 1.16 MB / Downloads: 27)

.zip   KCS_B4_V3.25.0.zip (Size: 1.21 MB / Downloads: 29)

.zip   KCS_B4M_V3.25.0.zip (Size: 1.21 MB / Downloads: 31)

.zip   KCS_B8_V3.25.0.zip (Size: 1.21 MB / Downloads: 31)

.zip   KCS_B8M_V3.25.0.zip (Size: 1.21 MB / Downloads: 31)

.zip   KCS_B16_V3.25.0.zip (Size: 1.21 MB / Downloads: 33)

.zip   KCS_B16M_V3.25.0.zip (Size: 1.21 MB / Downloads: 37)

.zip   KCS_B24_V3.25.0.zip (Size: 1.21 MB / Downloads: 33)

.zip   KCS_B24M_V3.25.0.zip (Size: 1.21 MB / Downloads: 30)

.zip   KCS_B32M_V3.25.0.zip (Size: 1.21 MB / Downloads: 36)

.zip   KCS_DM4_V3.25.0.zip (Size: 1.22 MB / Downloads: 30)

.zip   KCS_DM8_V3.25.0.zip (Size: 1.22 MB / Downloads: 30)

.zip   KCS_DM16_V3.25.0.zip (Size: 1.19 MB / Downloads: 26)

.zip   KCS_DM32_V3.25.0.zip (Size: 1.22 MB / Downloads: 35)

.zip   KCS_F4_V3.25.0.zip (Size: 1.21 MB / Downloads: 30)

.zip   KCS_F8_V3.25.0.zip (Size: 1.21 MB / Downloads: 34)

.zip   KCS_F16_V3.25.0.zip (Size: 1.22 MB / Downloads: 34)

.zip   KCS_F24_V3.25.0.zip (Size: 1.22 MB / Downloads: 45)

.zip   KCS_F32_V3.25.0.zip (Size: 1.22 MB / Downloads: 36)

.zip   KCS_G1_V3.25.0.zip (Size: 1.17 MB / Downloads: 36)

.zip   KCS_KC_TA_V3.25.0.zip (Size: 1.17 MB / Downloads: 29)

.zip   KCS_N10_V3.25.0.zip (Size: 1.08 MB / Downloads: 34)

.zip   KCS_N20_V3.25.0.zip (Size: 1.08 MB / Downloads: 33)

.zip   KCS_N30_V3.25.0.zip (Size: 1.08 MB / Downloads: 32)

.zip   KCS_N60_V3.25.0.zip (Size: 1.09 MB / Downloads: 39)

.zip   KCS_T16M_V3.25.0.zip (Size: 1.16 MB / Downloads: 34)

.zip   KCS_T32M_V3.25.0.zip (Size: 1.18 MB / Downloads: 35)

.zip   KCS_T64M_V3.25.0.zip (Size: 1.18 MB / Downloads: 33)

.zip   KCS_T128M_V3.25.0.zip (Size: 1.18 MB / Downloads: 36)

.zip   KCS_TR_V3.25.0.zip (Size: 1.14 MB / Downloads: 35)

.zip   KCS_Z1_V3.25.0.zip (Size: 1.31 MB / Downloads: 29) ]]> <![CDATA[Reset Total Energy only works per chip]]> https://www.kincony.com/forum/showthread.php?tid=9332 Fri, 15 May 2026 03:00:22 +0800 GWS]]> https://www.kincony.com/forum/showthread.php?tid=9332
I have made some changes to my setup and one of the reasons is that the calculations were not correct.

Tried to reset the BL0910 chips  but Clear all does not seem to clear the Total Energy values Confused . Just found out that "Clear Energy 1/2/3" so per chip did actually work.  Smile]]>
I have made some changes to my setup and one of the reasons is that the calculations were not correct.

Tried to reset the BL0910 chips  but Clear all does not seem to clear the Total Energy values Confused . Just found out that "Clear Energy 1/2/3" so per chip did actually work.  Smile]]> <![CDATA[Factor settings and calculations]]> https://www.kincony.com/forum/showthread.php?tid=9331 Thu, 14 May 2026 17:27:23 +0800 GWS]]> https://www.kincony.com/forum/showthread.php?tid=9331
I see some weird bahavior on my N30 that I do not understand:

Using CT with factor 1000:1 and after measering the actual curren with MID approved device I found that factor 2.1 was the best.
When I save the factor 2.1 it results in 2.0999... etc and that might very well be because of how the factor is binary processed in the chip.
So initially I started with setting all factors to 2.1 (for testing I have now set CH01 to factor 2 and CH02 to 1)

But on Channel 2 (first 901 chip) I got strange values and the Power Factor keeps changing in the header of the dat for that chip.
On the other two chips it stays on 1.0000 and the data looked correct.

When I move the CT connector for 1..10 to the position of the 11..20 I see that CH12 is displaying the expected values.
Looks like CHIP 1 is behaving differtent from CHIP 2&3.

Any idea what could cause this?

Related to this I would like to know how to best set the factors I it necessary to set all columns with same factor? (Please provide a field for the default setting for all columns)
Power = Voltage * Current
Energy = Power over time accumulated. It is not fully clear if I need the factor (2.1) there also, or should it be 1 since the power is already corrected.

Thanks,
GWS

.png   2026-05-14 111107_N30_Monitor.png (Size: 82.7 KB / Downloads: 50)

.png   2026-05-14 111226_N30_Energy-Configuration.png (Size: 76.53 KB / Downloads: 48) ]]>
I see some weird bahavior on my N30 that I do not understand:

Using CT with factor 1000:1 and after measering the actual curren with MID approved device I found that factor 2.1 was the best.
When I save the factor 2.1 it results in 2.0999... etc and that might very well be because of how the factor is binary processed in the chip.
So initially I started with setting all factors to 2.1 (for testing I have now set CH01 to factor 2 and CH02 to 1)

But on Channel 2 (first 901 chip) I got strange values and the Power Factor keeps changing in the header of the dat for that chip.
On the other two chips it stays on 1.0000 and the data looked correct.

When I move the CT connector for 1..10 to the position of the 11..20 I see that CH12 is displaying the expected values.
Looks like CHIP 1 is behaving differtent from CHIP 2&3.

Any idea what could cause this?

Related to this I would like to know how to best set the factors I it necessary to set all columns with same factor? (Please provide a field for the default setting for all columns)
Power = Voltage * Current
Energy = Power over time accumulated. It is not fully clear if I need the factor (2.1) there also, or should it be 1 since the power is already corrected.

Thanks,
GWS

.png   2026-05-14 111107_N30_Monitor.png (Size: 82.7 KB / Downloads: 50)

.png   2026-05-14 111226_N30_Energy-Configuration.png (Size: 76.53 KB / Downloads: 48) ]]>