HP23 - ZigBee issues / Zigbee dying after several hours - anyone?

Devices
1

Hi,

anyone here, who face problems with his Zigbee network, sensors stops updating their values, control of devices do not work and only Homey restart helps?

If you try to ping Zigbee device from developer interface, you get ZigbeeDaemon error.

image

It usually happens with Homey uptime of 4 - 21 hours and fully randomly.

I’m looking for cases with firmware > rc133 including.

If so, can you include your firmware version, number of Zigbee devices you have and system diag. report when it happened and also confirmation if you contacted Athom about that?

Thanks to all of you.

2 Likes
2

This is the related LOG to this error (before RC133 it was different)

Jul 10 05:02:23 homey-redacted homey-pro[938]: 2023-07-10T05:02:23.616Z Server HTTP GET /manager/system/
Jul 10 05:02:23 homey-redacted homey-pro[938]: 2023-07-10T05:02:23.624Z Zigbeed Restarting
Jul 10 05:02:24 homey-redacted homey-pro[938]: 2023-07-10T05:02:24.192Z CPCd [05:02:23:596838] Info : Endpoint socket #12: Client disconnected. 0 connections
Jul 10 05:02:24 homey-redacted homey-pro[938]: [05:02:23:597116] Info : Client disconnected
Jul 10 05:02:24 homey-redacted homey-pro[938]: 2023-07-10T05:02:24.612Z Zigbeed zigbeed[176]: [C] Platform------: mCpcBusSpeed = 115200
Jul 10 05:02:24 homey-redacted homey-pro[938]: zigbeed[176]: [I] Platform------: RCP reset: RESET_SOFTWARE
Jul 10 05:02:24 homey-redacted homey-pro[938]: zigbeed[176]: [D] Platform------: Wait response: tid=0 key=0
Jul 10 05:02:25 homey-redacted homey-pro[938]: 2023-07-10T05:02:25.195Z CPCd [05:02:24:601968] Info : New client connection using library v4.2.2.0
Jul 10 05:02:25 homey-redacted homey-pro[938]: [05:02:24:607182] Info : Opened connection socket for ep#12
Jul 10 05:02:25 homey-redacted homey-pro[938]: [05:02:24:607414] Info : Endpoint socket #12: Client connected. 1 connections
Jul 10 05:02:25 homey-redacted homey-pro[938]: 2023-07-10T05:02:25.960Z Network getNetworkInterfaceStatus wlan0
Jul 10 05:02:25 homey-redacted homey-pro[938]: 2023-07-10T05:02:25.962Z Network getNetworkInterfaceStatus wlan0
Jul 10 05:02:25 homey-redacted homey-pro[938]: 2023-07-10T05:02:25.968Z Network getNetworkInterfaceStatus eth1
Jul 10 05:02:25 homey-redacted homey-pro[938]: 2023-07-10T05:02:25.970Z Network getNetworkInterfaceStatus eth1
Jul 10 05:02:26 homey-redacted homey-pro[938]: 2023-07-10T05:02:26.021Z Homey [log][ManagerApi] IO homey:manager:system:getInfo → Success 200
Jul 10 05:02:26 homey-redacted homey-pro[938]: 2023-07-10T05:02:26.023Z Server HTTP GET /manager/system/ → Success 200
Jul 10 05:02:26 homey-redacted homey-pro[938]: 2023-07-10T05:02:26.627Z Zigbeed zigbeed[176]: [D] Platform------: Spinel send: cmd:PROP_VALUE_GET: prop:PROTOCOL_VERSION, iid:01, tid:01
Jul 10 05:02:26 homey-redacted homey-pro[938]: 2023-07-10T05:02:26.628Z Zigbeed zigbeed[176]: [D] Platform------: Wait response: tid=1 key=1
Jul 10 05:02:27 homey-redacted homey-pro[938]: 2023-07-10T05:02:27.594Z Homey [log][ManagerApi] IO homey:manager:system:getMemoryInfo → Success 200
Jul 10 05:02:28 homey-redacted homey-pro[938]: 2023-07-10T05:02:28.644Z Bluez stopDiscovery
Jul 10 05:02:28 homey-redacted homey-pro[938]: 2023-07-10T05:02:28.646Z Zigbeed zigbeed[176]: [W] Platform------: Wait for response timeout
Jul 10 05:02:28 homey-redacted homey-pro[938]: zigbeed[176]: [W] Platform------: RCP failure detected
Jul 10 05:02:28 homey-redacted homey-pro[938]: zigbeed[176]: [W] Platform------: Trying to recover (1/100)
Jul 10 05:02:28 homey-redacted homey-pro[938]: zigbeed[176]: [I] Platform------: RCP reset: RESET_SOFTWARE
Jul 10 05:02:28 homey-redacted homey-pro[938]: zigbeed[176]: [D] Platform------: Wait response: tid=0 key=0
Jul 10 05:02:30 homey-redacted homey-pro[938]: 2023-07-10T05:02:30.659Z Zigbeed zigbeed[176]: [D] Platform------: Spinel send: cmd:PROP_VALUE_SET: prop:PHY_ENABLED, iid:01, tid:01
Jul 10 05:02:30 homey-redacted homey-pro[938]: 2023-07-10T05:02:30.659Z Zigbeed zigbeed[176]: [D] Platform------: Wait response: tid=1 key=32
Jul 10 05:02:31 homey-redacted homey-pro[938]: 2023-07-10T05:02:31.636Z Homey [log][ManagerApi] IO homey:manager:devices:getDevice
Jul 10 05:02:31 homey-redacted homey-pro[938]: 2023-07-10T05:02:31.637Z Homey [log][ManagerApi] IO homey:manager:devices:getDevice → Success 200
Jul 10 05:02:31 homey-redacted homey-pro[938]: 2023-07-10T05:02:31.642Z Homey [log][ManagerApi] IO homey:manager:devices:getDevice
Jul 10 05:02:31 homey-redacted homey-pro[938]: 2023-07-10T05:02:31.642Z Homey [log][ManagerApi] IO homey:manager:devices:getDevice → Success 200
Jul 10 05:02:32 homey-redacted homey-pro[938]: 2023-07-10T05:02:32.675Z Zigbeed zigbeed[176]: [W] Platform------: Wait for response timeout
Jul 10 05:02:32 homey-redacted homey-pro[938]: 2023-07-10T05:02:32.675Z Zigbeed zigbeed[176]: [W] Platform------: RCP failure detected
Jul 10 05:02:32 homey-redacted homey-pro[938]: zigbeed[176]: [W] Platform------: Trying to recover (2/100)
Jul 10 05:02:32 homey-redacted homey-pro[938]: zigbeed[176]: [I] Platform------: RCP reset: RESET_SOFTWARE
Jul 10 05:02:32 homey-redacted homey-pro[938]: 2023-07-10T05:02:32.676Z Zigbeed zigbeed[176]: [D] Platform------: Wait response: tid=0 key=0
Jul 10 05:02:33 homey-redacted homey-pro[938]: 2023-07-10T05:02:33.603Z zigbee:controller:60:a4:23:ff:fe:07:c5:34 send ZCL frame error Request "sendZCLFrame" failed with unexpected ember status: 40
Jul 10 05:02:33 homey-redacted homey-pro[938]: 2023-07-10T05:02:33.605Z zigbee:controller:60:a4:23:ff:fe:07:c5:34 send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:34 homey-redacted homey-pro[938]: 2023-07-10T05:02:34.692Z Zigbeed zigbeed[176]: [D] Platform------: Spinel send: cmd:PROP_VALUE_SET: prop:PHY_ENABLED, iid:01, tid:01
Jul 10 05:02:34 homey-redacted homey-pro[938]: zigbeed[176]: [D] Platform------: Wait response: tid=1 key=32
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.103Z Homey [log][ManagerApi] IO homey:manager:devices:getDevice
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.103Z Homey [log][ManagerApi] IO homey:manager:devices:getDevice → Success 200
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.518Z zigbee:controller:cc:86:ec:ff:fe:93:3a:68 send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.521Z zigbee:controller:a4:c1:38:d2:78:7c:9f:de send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.528Z zigbee:controller:cc:86:ec:ff:fe:3a:b4:26 send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.528Z zigbee:controller:a4:c1:38:f2:72:50:92:19 send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.529Z zigbee:controller:a4:c1:38:bb:a5:f3:56:1a send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.534Z zigbee:controller:a4:c1:38:8e:e6:dc:8e:cd send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.681Z Server HTTP GET /manager/system/
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.734Z Network getNetworkInterfaceStatus wlan0
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.740Z Network getNetworkInterfaceStatus eth1
Jul 10 05:02:35 homey-redacted homey-pro[938]: 2023-07-10T05:02:35.748Z Server HTTP GET /manager/system/ → Success 200
Jul 10 05:02:36 homey-redacted homey-pro[938]: 2023-07-10T05:02:36.707Z Zigbeed zigbeed[176]: [W] Platform------: Wait for response timeout
Jul 10 05:02:36 homey-redacted homey-pro[938]: 2023-07-10T05:02:36.707Z Zigbeed zigbeed[176]: [W] Platform------: RCP failure detected
Jul 10 05:02:36 homey-redacted homey-pro[938]: zigbeed[176]: [W] Platform------: Trying to recover (3/100)
Jul 10 05:02:36 homey-redacted homey-pro[938]: zigbeed[176]: [I] Platform------: RCP reset: RESET_SOFTWARE
Jul 10 05:02:36 homey-redacted homey-pro[938]: 2023-07-10T05:02:36.708Z Zigbeed zigbeed[176]: [D] Platform------: Wait response: tid=0 key=0
Jul 10 05:02:38 homey-redacted homey-pro[938]: 2023-07-10T05:02:38.315Z zigbee:controller:50:32:5f:ff:fe:4a:29:12 send ZCL frame error Timeout after 15000ms
Jul 10 05:02:38 homey-redacted homey-pro[938]: 2023-07-10T05:02:38.315Z zigbee:controller:50:32:5f:ff:fe:4a:29:12 send ZCL frame { endpointId: 1, clusterId: 6 }
Jul 10 05:02:38 homey-redacted homey-pro[938]: 2023-07-10T05:02:38.723Z Zigbeed zigbeed[176]: [D] Platform------: Spinel send: cmd:PROP_VALUE_SET: prop:PHY_ENABLED, iid:01, tid:01
Jul 10 05:02:38 homey-redacted homey-pro[938]: 2023-07-10T05:02:38.724Z Zigbeed zigbeed[176]: [D] Platform------: Wait response: tid=1 key=32
Jul 10 05:02:40 homey-redacted homey-pro[938]: 2023-07-10T05:02:40.739Z Zigbeed zigbeed[176]: [W] Platform------: Wait for response timeout
Jul 10 05:02:40 homey-redacted homey-pro[938]: 2023-07-10T05:02:40.739Z Zigbeed zigbeed[176]: [W] Platform------: RCP failure detected
Jul 10 05:02:40 homey-redacted homey-pro[938]: zigbeed[176]: [W] Platform------: Trying to recover (4/100)

Based on ChatGPT :

Based on the log provided, it appears that the system is experiencing RCP (Remote Control Protocol) failures and subsequent resets. The exact cause of these failures can vary, but here are a few possible reasons:

Software or firmware issues: RCP failures can occur due to bugs or issues in the software or firmware running on the Homey Pro system. It's possible that a software component or a specific operation is causing instability or triggering errors, leading to the need for a reset.

Communication or connectivity problems: RCP failures can also result from communication or connectivity issues between different components of the system. This can be caused by network disruptions, intermittent connection problems, or issues with the Zigbee network itself.

Resource limitations: If the system is running low on system resources like memory or processing power, it may struggle to handle the incoming requests or maintain stable connections. This can lead to errors and necessitate a reset to recover.

Hardware issues: In some cases, hardware problems can manifest as RCP failures. Faulty components, overheating, or other hardware-related issues can cause intermittent errors and require a reset to restore normal operation.

To determine the exact cause of the resets, it would be necessary to analyze further logs, system diagnostics, or consult the manufacturer’s documentation or support channels. Additionally, if the issue persists or significantly impacts system functionality, it may be advisable to contact the Homey Pro support team for assistance.

Still if it’s only me… ? Anyone ?

HOwever, those logs are not accessible to regular users unfortunately.

The key for regular user is to see error :
obrazek
in Homey Developer Tools when the issue occurs and when you check Homey memory details, you will see that some of those daemons are missing :
obrazek
(you can check on mobile and on web app as well)

3

For me it looks like rc133 solved most of the problems with the zigbeedemonerror, but before that i had the same problem with crashes.

1 Like
4

Yes, me! 48 Zigbee devices and plenty of daily restarts later (Including constantly having to reconnect my Ikea Blinds) I am still experiencing this today. Even running into this on the latest version 10.0.0-rc.139. I am absolutely fed up, even my old homey 2016 wasn’t as bad as this and its got far less compute than the 2023 version. I have also noted that the processor of Homey is less busy when this daemon is killed or stops working so it either looks like a memory leak or something to that effect! I reported to Homey but cant seem to see if there is a fix for this or its just lost in the rest of the issues.

1 Like
5

I’m being told I’m the only one - have you done any modifications on your Homey?
With the deamon killed indeed the CPU cycles going down, that’s something I have observed as well… will PM you

6

Have any of you solved these issues?

I’m having around 30 zigbee devices and a HP23 with extreme problems and delays. Have done all basic troubleshooting and checked wifi channel overlapping etc…

I had a case with Athom and they say this is a known issue that their developers are prioritizing. But my case was closed because it’s a known issue apparently…

7

Do you also have the same issue that devices stop responding after a while completely ?

Unfortunately issue itself is not really resolved but true is that Athom improved those Zigbee daemon restart procedures, so even it’s still crashing, it self-recovers at-least.

Btw, I just re-paired (maintenance, without removal) recently some of the devices (Aqara), even Athom is silent about that process (I exactly asked if it’s required because of firmware changelog suggesting something like that but receive no comment at all), it looks like that pairing some devices (mostly those reporting irregularly) helps - but it depends what exactly your issue is.

re changelog - here is where the things got improved without any additional communication (eg. if repair is required for those of us who migrated etc)

## v10.0.4

* Fixed an issue that could result in difficulties repairing devices after a migration from Homey Pro (2016—2019).
* Fixed an issue that could result in Zigbee devices not being configured properly after a repair.
* Fixed an issue that could result in empty device settings after a repair.
* Fixed an issue that could mark a device as successfully repaired even though it was not.
* Fixed an issue that could result in "Zigbee is busy" errors.
8

Yes, issues starts after around 1-2 hours after I re-add all my devices (yesterday after a factory reset it worked up to 6 hours even). The issues are at the beginning extreme delays (10min-2hours+), but after a few days it stops working completely.

I have around 30 Sunricher Wall dimmers that are Zigbee (all powered devices).

Worth mentioning is that I´m coming from a Homey Pro 2019 and did a migration and repair of the devices. But since then I´ve removed all devices completely and added them fresh.

1 Like
9

@NeVroe @stuartp44 , how is your Zigbee experience nowadays ?

10

@Sharkys Not good, unfortunatly, I have started migration to Home Assistant and only use Homey Pro to interact with my Home Assistant. I am still undecided if I want to go the whole hog and just use Home Assistant pure. But I was pritty disapointed to say the least. I have far less problems with Home Assistant that I did with Homey pure.

1 Like