KinCony Z1 Problem

[siwybug]

Hello, I purchased a KinCony Z1. I have already tried many different ways of flashing various firmware versions, but the device is generally unstable. It connects to Wi-Fi and to MQTT, but nothing more than that works. No MQTT entities appear and nothing is discovered automatically. When I try to add ZigBee devices, it scans for them, detects them, pairs successfully, sends signals, and everything seems fine — but after a short while, those devices disappear.

[admin]

do you use the zigbee products bought from KinCony?

[siwybug]

I haven’t used Zigbee products from KinCony (does it really only work with KinCony hardware?). That said, it still isn’t detected in MQTT at all. I’m programming IR and RF, and none of it is being organized or exposed in MQTT. What should the syntax of an MQTT command look like for the Z1 to execute any instruction? I’ve already tried all possible combinations and nothing works.

[admin]

1: make sure zigbee product should MUST be zigbee3.0 standard protocol. We suggest purchasing Zigbee products from KinCony. We have tested many zigbee3.0 products in market, actually there are not 3.0 standard protocol.
2: if you want to use RF and IR function by MQTT, here are mqtt about it: https://www.kincony.com/forum/showthread.php?tid=7612

[siwybug]

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.

[siwybug]

I (3756) wifi:wifi driver task: 3fcd7a20, prio:23, stack:6656, core=0
I (3786) wifi:wifi firmware version: ccaebfa
I (3786) wifi:wifi certification version: v7.0
I (3786) wifi:config NVS flash: enabled
I (3786) wifi:config nano formating: disabled
I (3786) wifi:Init data frame dynamic rx buffer num: 32
I (3786) wifi:Init static rx mgmt buffer num: 5
I (3786) wifi:Init management short buffer num: 32
I (3786) wifi:Init static tx buffer num: 16
I (3786) wifi:Init tx cache buffer num: 32
I (3786) wifi:Init static tx FG buffer num: 2
I (3786) wifi:Init static rx buffer size: 1600
I (3786) wifi:Init static rx buffer num: 10
I (3786) wifi:Init dynamic rx buffer num: 32
I (3786) wifi_init: rx ba win: 6
I (3786) wifi_init: accept mbox: 6
I (3786) wifi_init: tcpip mbox: 32
I (3786) wifi_init: udp mbox: 6
I (3786) wifi_init: tcp mbox: 6
I (3786) wifi_init: tcp tx win: 5744
I (3786) wifi_init: tcp rx win: 5744
I (3786) wifi_init: tcp mss: 1440
I (3786) wifi_init: WiFi/LWIP prefer SPIRAM
I (3786) wifi_init: WiFi IRAM OP enabled
I (3786) wifi_init: WiFi RX IRAM OP enabled
W (3786) wifiassword length matches WPA2 standards, authmode threshold changes from OPEN to WPA2
I (3796) phy_init: phy_version 680,a6008b2,Jun 4 2024,16:41:10
I (3836) wifi:mode : sta (30:ed:a0:3b:14:58)
I (3836) wifi:enable tsf
I (3836) main: Heap free after wifi_init: 189499
I (3836) web_server: Starting HTTP Server on port: '80'
I (3836) kc_event: Registered handler for event: KC_RF_EVENTS, event id: 1
I (3836) kc_event: Registered handler for event: KC_IR_EVENTS, event id: 1
I (3836) kc_event: Registered handler for event: KC_INPUT_EVENTS, event id: 0
I (3836) kc_event: Registered handler for event: KC_OUTPUT_EVENTS, event id: 0
I (3836) main: Heap free after web_server: 179975
I (3836) main: Heap free after key_task: 175531
I (3836) ntp: tz:UTC-1
I (3836) main: Heap free after ntp_task: 171087
I (3836) mqtt: kc_mqtt enable=0
I (3836) main: Heap free after mqtt_init: 171087
I (3836) mqtt: kc_mqtt enable=0
I (3836) main: Heap free after cloud_init: 171087
I (3846) UDP SERVER: Socket created
I (3846) UDP SERVER: Socket bound, port 4001
I (3846) main: Heap free after udp_server_init: 162347
I (3846) main: Heap free after tcp_server_init: 162347
I (3846) wifi:new:<2,0>, old:<1,0>, ap:<255,255>, sta:<2,0>, prof:1, snd_ch_cfg:0x0
I (3846) wifitate: init -> auth (0xb0)
I (3846) main: Heap free after tcp_client_init: 162087
I (3846) gpio: GPIO[2]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (3856) RF: RCSwitch->nReceiverInterrupt=9 gpio_pin_sel=512
I (3866) gpio: GPIO[9]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
1970/01/01 08:00:26.123 kc_timer@0026 timer::time_rf_100ms create ok
I (3886) RF: Start RF receiver
I (3896) main: Heap free after rf433_init: 156851
I (3906) ir: create IR RX channel
I (3906) gpio: GPIO[1]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (3916) ir: register RX done callback
I (3926) ir: enable IR RX channels
I (3926) ir: Start IR receiver
I (3936) ir: Start IR tx
1970/01/01 08:00:26.189 kc_timer@0026 timer::ir_save_timer create ok
I (3956) main: Heap free after ir_init: 139183
I (3966) kc_res_sensor: Resource with device_id 100663296 added
...
I (4156) main: Heap free after sensor_init: 132311
I (4156) main: Heap free after homekit_init: 132311
I (4156) main: Heap free after loxone_init: 132311
I (4156) homeassistant: Added RF button accessory for ID 1
I (4166) homeassistant: Added RF button accessory for ID 2
I (4166) homeassistant: Added RF button accessory for ID 3
I (4166) homeassistant: Added RF button accessory for ID 4
I (4166) homeassistant: Home Assistant Service Start
[HomeAssistant]Other event id:7
E (4166) esp-tls: [sock=52] connect() error: Host is unreachable
E (4166) transport_base: Failed to open a new connection: 32772
E (4166) mqtt_client: Error transport connect
I (4166) kc_event: Registered handler for event: KC_INPUT_EVENTS, event id: 0
I (4166) kc_event: Registered handler for event: KC_RF_EVENTS, event id: 1
I (4166) kc_event: Registered handler for event: KC_IR_EVENTS, event id: 1
I (4166) main: Heap free after ha_init: 108315
I (4166) gpio: GPIO[44]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (4166) gpio: GPIO[21]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (4166) main: Heap free after zg_init: 108315
I (4166) main: Heap RAM create: 108315
I (4166) main: Free memory: 7868744 bytes
I (4166) kc_event: Registered handler for event: KC_WS2812_EVENTS, event id: 2
I (4176) kc_ws2812: Initializing WS2812 LEDs
I (4176) kc_ws2812: WS2812 initialization complete
I (4176) main_task: Returned from app_main()
I (4466) wifitate: auth -> assoc (0x0)
I (4496) wifitate: assoc -> run (0x10)
I (4516) wifi:connected with GOOSE, aid = 36, channel 2, BW20, bssid = 9a:44:89:70:88:70
I (4516) wifiecurity: WPA3-SAE, phy: bgn, rssi: -55
I (4516) wifi:pm start, type: 1

I (4516) wifi:dp: 1, bi: 102400, li: 3, scale listen interval from 307200 us to 307200 us
I (4516) wifiet rx beacon pti, rx_bcn_pti: 0, bcn_timeout: 25000, mt_pti: 0, mt_time: 10000
I (4526) kc_event: Firing event [network_status], type=WiFi, status=connected
I (4536) wifi:<ba-add>idx:0 (ifx:0, 9a:44:89:70:88:70), tid:6, ssn:1, winSize:64
I (4546) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (5066) wifi:<ba-del>idx:0, tid:6
I (5066) wifi:<ba-add>idx:0 (ifx:0, 9a:44:89:70:88:70), tid:6, ssn:2, winSize:64
I (5526) esp_netif_handlers: sta ip: 192.168.241.188, mask: 255.255.0.0, gw: 192.168.0.1
I (5526) wifi station: got ip : 192.168.241.188
I (5536) wifi:<ba-add>idx:1 (ifx:0, 9a:44:89:70:88:70), tid:0, ssn:1, winSize:64
I (7846) ifttt: start ifttt task
[HomeAssistant]Other event id:7
[HomeAssistant]mqtt connect success
E (9166) mqtt_client: Publish message cannot be created
E (9166) mqtt_client: Publish message cannot be created
E (9166) mqtt_client: Publish message cannot be created
E (9176) mqtt_client: Publish message cannot be created
[HomeAssistant]send discovery:
{"uniq_id":"30EDA03B1458_button_rf_button4","~":"homeassistant/button/30EDA03B1458rf_button4","name":"RF Transmit 4","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","cmd_t":"~/set","payload_press":"PRESS"}
[HomeAssistant]send discovery:
{"uniq_id":"30EDA03B1458_binary_sensor_rf4","~":"homeassistant/binary_sensor/30EDA03B1458rf4","name":"rf4","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","stat_t":"~/state","payload_on":"ON","payload_off":"OFF"}
[HomeAssistant]send discovery:
{"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"}
[HomeAssistant]send discovery:
{"uniq_id":"30EDA03B1458_binary_sensor_rf3","~":"homeassistant/binary_sensor/30EDA03B1458rf3","name":"rf3","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","stat_t":"~/state","payload_on":"ON","payload_off":"OFF"}
[HomeAssistant]send discovery:
{"uniq_id":"30EDA03B1458_button_rf_button2","~":"homeassistant/button/30EDA03B1458rf_button2","name":"RF Transmit 2","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","cmd_t":"~/set","payload_press":"PRESS"}
[HomeAssistant]send discovery:
{"uniq_id":"30EDA03B1458_binary_sensor_rf2","~":"homeassistant/binary_sensor/30EDA03B1458rf2","name":"rf2","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","stat_t":"~/state","payload_on":"ON","payload_off":"OFF"}
[HomeAssistant]send discovery:
{"uniq_id":"30EDA03B1458_button_rf_button1","~":"homeassistant/button/30EDA03B1458rf_button1","name":"RF Transmit 1","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","cmd_t":"~/set","payload_press":"PRESS"}
[HomeAssistant]send discovery:
{"uniq_id":"30EDA03B1458_binary_sensor_rf1","~":"homeassistant/binary_sensor/30EDA03B1458rf1","name":"rf1","device":{"name":"Z1","identifiers":"30EDA03B1458","manufacturer":"KinCony","model":"Z1"},"config_topic":"~/config","avty_t":"30EDA03B1458/avail","stat_t":"~/state","payload_on":"ON","payload_off":"OFF"}

See Event from IR and RF have the same event ID: 1.

And then there are errors: E (9166) mqtt_client: Publish message cannot be created

Is the firmware you're sharing the factory version or an OTA update?
If it's an OTA update, can you share the factory version to repair the firmware?

[admin]

which KCS v3 firmware version you are using?

[siwybug]

I used the latest version 3.19.1 but I also tested previous versions up to 3.11 and the effect is exactly the same, in fact, on some of the older versions there is an additional problem that causes the entire gateway to freeze, the gateway freezes completely and has micro resets. Therefore, in my opinion, there is probably a problem with the main program. If what you are sharing is an OTA update, then I would ask you to share the factory firmware that will fix this error for me.

[siwybug]

will you help?

[admin]

after China New Year holidays, we will test it , then feedback to you.