Hello,
I have a KC868-A16 running KCS v2.2.20,
integrated with Home Assistant via MQTT.
Input 16 reads an auxiliary contact of a latching relay (Finder 20.22)
to get the real ON/OFF state of a light. While the contact is closed
(input ON), I occasionally get a false OFF lasting 1-2 seconds, then
the input goes back to ON by itself. These glitches are published
immediately via MQTT.
I saw in this thread that you added an input debounce option
("input delay time") to the KCS v3 firmware for the KC868-A16v3:
https://www.kincony.com/forum/showthread.php?tid=9119
My questions:
1. Is there (or will there be) a KCS firmware with the same debounce
option for the KC868-A16 with ESP32 (not v3)?
2. What is the maximum debounce time that can be set? In my case
I would need about 2-3 seconds.
3. Is the debounce setting global or can it be set per input?
4. If I upgrade from KCS v2 to v3, do the MQTT topics and the JSON
payload format (e.g. {"input16":{"value":true}}) stay the same?
Thank you!
I have a KC868-A16 running KCS v2.2.20,
integrated with Home Assistant via MQTT.
Input 16 reads an auxiliary contact of a latching relay (Finder 20.22)
to get the real ON/OFF state of a light. While the contact is closed
(input ON), I occasionally get a false OFF lasting 1-2 seconds, then
the input goes back to ON by itself. These glitches are published
immediately via MQTT.
I saw in this thread that you added an input debounce option
("input delay time") to the KCS v3 firmware for the KC868-A16v3:
https://www.kincony.com/forum/showthread.php?tid=9119
My questions:
1. Is there (or will there be) a KCS firmware with the same debounce
option for the KC868-A16 with ESP32 (not v3)?
2. What is the maximum debounce time that can be set? In my case
I would need about 2-3 seconds.
3. Is the debounce setting global or can it be set per input?
4. If I upgrade from KCS v2 to v3, do the MQTT topics and the JSON
payload format (e.g. {"input16":{"value":true}}) stay the same?
Thank you!


