Overall, there is a problem with the KinCony KCS firmware version 3. After adding RF (radio) remotes, the corresponding entities suddenly appeared in MQTT and the RF section is visible. However, the infrared (IR) section is still not visible. So there seems to be something wrong with the infrared part of the firmware.
Even when I try to send commands from an external client, using the same topic structure as the RF (radio) tree and attempt to control the infrared, it still does not work. Nothing is transmitted — I’m checking with a camera and there is absolutely no IR signal being emitted. Nothing happens at all.
{"uniq_id":"30EDA03B1458_button_rf_button3","~":"homeassistant/button/30EDA03B1458rf_button3","name":"RF Transmit 3","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","cmd_t":"~/set","payload_press":"PRESS"}
This is what the topic structure looks like for RF, and I’m trying to create a similar topic for IR using an external client. However, it does not work in any way. It does not accept any combination at all.
As for ZigBee, I’m using devices from Sonoff, for example the presence sensor model SNZB-06P, and it is fully compliant with ZigBee 3.0.
I have already tested many different devices and every time it is exactly the same. The device appears in the table below for a very short moment, along with its ID and other details, and literally after 2–3 seconds it disappears completely.
However, when I connect the same devices through ZigBee2MQTT using a modified Sonoff stick, they start working immediately. It is definitely ZigBee 3.0 — there is no other protocol involved.
So there is clearly something wrong with this firmware.
Even when I try to send commands from an external client, using the same topic structure as the RF (radio) tree and attempt to control the infrared, it still does not work. Nothing is transmitted — I’m checking with a camera and there is absolutely no IR signal being emitted. Nothing happens at all.
{"uniq_id":"30EDA03B1458_button_rf_button3","~":"homeassistant/button/30EDA03B1458rf_button3","name":"RF Transmit 3","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","cmd_t":"~/set","payload_press":"PRESS"}
This is what the topic structure looks like for RF, and I’m trying to create a similar topic for IR using an external client. However, it does not work in any way. It does not accept any combination at all.
As for ZigBee, I’m using devices from Sonoff, for example the presence sensor model SNZB-06P, and it is fully compliant with ZigBee 3.0.
I have already tested many different devices and every time it is exactly the same. The device appears in the table below for a very short moment, along with its ID and other details, and literally after 2–3 seconds it disappears completely.
However, when I connect the same devices through ZigBee2MQTT using a modified Sonoff stick, they start working immediately. It is definitely ZigBee 3.0 — there is no other protocol involved.
So there is clearly something wrong with this firmware.