After migrating around 80 Hue lights and 8 Hue motion detectors from Hue Bridges to ZHA with SkyConnect, I ran into the two issues that I subsequently found as open Github issues in the core repository:
-
“Failed to enqueue message after 3 attempts: <EmberStatus.NETWORK_BUSY: 161>” The Errors almost always occur when controlling Zigbee groups
(Automations issue/ ZHA Network busy errors after migrating to Skyconnect dongle · Issue #86411 · home-assistant/core · GitHub) -
Hue Motion Sensors SML001 becomes unavailable
(https://github.com/home-assistant/core/issues/89311)
Both issues have been open for months, so I currently have no hope of a solution.
So I switched to Zigbee2MQTT a week ago. As the move had to be made device by device, I used a free Conbee II stick for Z2MQTT.
As a result, the pairing process was much faster and more stable than with ZHA and the two problems mentioned above did not occur here. Groups work rock solid and the Hue SML001s remain stable in the network.
However, I have now run into the problem that a few commands in the Zigbee network are not executed with “failed (no response received)”.
I found the issue in the zigbee2mqtt repository. (https://github.com/Koenkk/zigbee2mqtt/issues/11647) This seems to be a problem specifically with the Conbee stick.
As there is no “Change coordinator” function in Z2M, I would now have to redo everything for the third time. And great: The Conbee does not support the backup function of Z2M.
But I don’t know where to migrate now?
-
Zigbee2MQTT with SkyConnect with the option to migrate to ZHA later when the bugs are maybe fixed.
-
Back to ZHA with SkyConnect - means replacing 15 Hue SML001 and using HA groups instead of Zigbee groups (which is also not recommended).
-
or do I buy a SONOFF Zigbee 3.0 USB Dongle Plus -P and do Zigbee2MQTT with SONOFF -P
-
or go back to the Hue bridges
Any recommendations?
For whom does a large Zigbee network with Hue motion detectors and Zigbee groups work stable and if so, with which integration/coordinator combination?
And yes: Extension cable, 2.4 GHz WiFi overlap etc. is all clear and not the reason.