KC868-AG RF - sending repeated signals - Printable Version +- Smart Home Automation Forum (https://www.kincony.com/forum) +-- Forum: Technical Support (https://www.kincony.com/forum/forumdisplay.php?fid=1) +--- Forum: KC868-A series and Uair Smart Controller (https://www.kincony.com/forum/forumdisplay.php?fid=6) +--- Thread: KC868-AG RF - sending repeated signals (/showthread.php?tid=6734) |
KC868-AG RF - sending repeated signals - PhilW - 09-18-2024 I'm new to this HW, so maybe I'm missing something. I have a remote 433mhz that I "learned" on the Web UI. When I transmit the signal, it is being sent around 5 times, triggering the receiving device to turn on and off and on again etc. Basically, the device (ventilator) beeps when it gets a signal, and I'm hearing around 5 beeps. Is there any way to configure this behavior? Or should I flash the device with a different fimware? Can I just flash esphome on it - and hope to fix this somehow that way? Current firmware: v2.2.4 RE: KC868-AG RF - sending repeated signals - PhilW - 09-18-2024 I guess I found it - "RF repeat count" in the system settings. I lowered it to 30. Looks like I can only set this globally, not per item. I have not yet found a way to export the "learned" RF signals - I checked in MQTT, there was nothing other than a state. So I think I will try to flash ESPhome next. RE: KC868-AG RF - sending repeated signals - admin - 09-18-2024 if you want customsize define every RF learned channel, use ESPHome is better. RE: KC868-AG RF - sending repeated signals - PhilW - 09-19-2024 A bit off topic, but interestingly, when I use the learn & transmit functionality of the KCS firmware, it works. When I use ESPhome with either the data from the dumped RF log or using raw signals I got from FlipperZero, it does not work. from the log: [22:44:20][I][remote.drayton:236]: Received Drayton: address=0x7837 (0xf06e), channel=0x00c command=0x030 in esphome: button: - platform: template name: Turn on Ceiling Fan on_press: - remote_transmitter.transmit_drayton: address: '0x7837' channel: '0x00c' command: '0x030' The investigation continues :-) |