WTH is ZHA/Zigbee so unstable and hard to troubleshoot?

Hedda · January 7, 2025, 10:08am

Yes that is correct, they have the same problem regardless of which Zigbee Gateway you use.

Note that since the issue is bug in the device firmware the problem is sometimes only in a specific firmware version.

Most devices that are infamous for having these types of bugs have never gotten official firmware upgrades, (and many do not even support OTA updates at all), but some might have a new revision come with newer firmware from the factory without getting a new model number, so it can be a gamble buying old stock from a store or buying used hardware if it is one of those models that is known to have buggy firmware.

Hedda · January 8, 2025, 2:35pm

FYI, I posted a feature requerst to the zigpy/zha developers for that idea of having warning with comments for specific Zigbee device with known issue inside ZHA UI, so you guys could add to that list I started there with the infamously known problem products that I have read and/or used myself:

[REQUEST] Add some kind of blacklisting feature that lists and give users warnings user about devices known to have buggy firmware? · Issue #349 · zigpy/zha · GitHub

github.com/zigpy/zha

[REQUEST] Add some kind of blacklisting feature that lists and give users warnings user about devices known to have buggy firmware?

opened 02:27PM - 08 Jan 25 UTC

Hedda

Please consider adding some kind of blacklisting feature that maintains a list o…f "known bad devices and firmware" and gives users some kind of warnings about the problem seen for those devices that are known to have buggy firmware or hardware. Good or bad idea? I'm not suggesting those devices should be blacklisted as in blocked from working, but would be great with a UI warning inside ZHA. Z-Wave JS integration already has the equivalent feature where it show a custom warning text for device ID:s with know problem. Here are a few concrete examples of what devices/firmware that should probably be on such a list and what warning should be about: * Sonoff S26 Plug DE/FR/UK (Zigbee ID: "S26R2ZB") - ITead SKUs: S26R2ZBTPF, S26R2ZBTPE, and S26R2ZBTPG) * Warning: The first batch of this device mode is known to ship with firmware 2.0.0 have been proven to cause frequent disconnects and go offline after a period of time, including when operating as a Zigbee Router for other devices. A fix is available in firmware 2.1.1 and higher, but the older firmware does not support OTA, so devices have to be sent to Sonoff/ITead to get a replacement. * https://github.com/Koenkk/zigbee2mqtt/discussions/10909 * Tuya Zigbee USB Range Extender / USB Dongle Signal Repeater (Zigbee ID: "TS0207") - Tuya SKU: "RP280". * Warning: This device model has been proven to cause network stability issues. They are known to sometimes act as an black-hole for Zigbee traffic coming from non-Tuya devices under certain circumstances. * See more information in related discussion here -> https://github.com/zigpy/zigpy/discussions/736 * Tuya Smart Plug 16A with Power Monitoring (Zigbee ID: TS011F | _TZ3000_w0qqde0g | _TZ3000_gjnozsaz | _TZ3000_zloso4jk | _TZ3000_fgwhjm9j | _TZ3000_rdfh8cfs), white-label product so also sold under different brands and model names, such as ex. NAS-WR01B by Neo. * Warning: This device is buggy and sends large negative Electric Consumption (Energy Metering) Reports from time to time." * Aqara first-generation battery-operated sensors (many) * Warning: Aqara first-generation battery-operated sensors are known to not self-heal or automatically reconnect to any other Zigbee Router than what it was initially connected to. There are no firmware upgrades. _The workaround is to manually re-pair the device in-place if the it disconnects or you want it to connect to a other Zigbee Router device. * Xiaomi first-generation battery-operated sensors (many) * Warning: Aqara first-generation battery-operated sensors are known to not self-heal or automatically reconnect to any other Zigbee Router than what it was initially connected to. There are no firmware upgrades. _The workaround is to manually re-pair the device in-place if the it disconnects or you want it to connect to a other Zigbee Router device. * IKEA Trådfri devices XYZ with firmware XYZ The background why I think that the ZHA integration should have this feature is that noticed that the Z-Wave JS and the official Z-Wave integration for Home Assistant have a similar feature/function where they show a warning in Home Assistant's UI under the device inside the integration, presumably taken from a simple list with ID of specific devices (and device firmware) that are (often infamously) known to have buggy / bad firmware or hardware that is known to have a specific unwanted problem. See example these warnings users get for the "Neo Wall Plug Switch" (NAS-WR01ZE) for which there even is a Zigbee counterpart: * https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x0258/nas-wr01ze.json#L103 ![image](https://github.com/user-attachments/assets/f3e30883-714b-49c0-96d6-c7eb0c652b29) Another exammple Z-Wave device warning message is this shown for the "Qubino Mini Dimmer" (ZMNHHD): * https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x0159/zmnhhd.json#L308 ![image](https://github.com/user-attachments/assets/5af18537-c9a0-49fd-bcd7-193d12593f5a) Few more concrete Z-Wave device examples of warning messages can be found in node-zwave-js metadata for these Z-Wave devices: * Z-Wave.Me USB Z-Wave Mini Adapter ("ZME_UZB1") = "This controller has a bug in its USB implementation, which can cause issues with newer Linux kernel versions. Using a powered USB hub MAY help to work around the issue, but migrating to a different controller is recommended." * https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x0115/zme_uzb1.json * Nexa Trading AB ("ZPR-111") Smart Plug = "This device is buggy and sends large negative Meter Reports from time to time." * https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x0268/zpr111.json#L19 * Kemple Smart Socket "KP-SO-02" = "This device is buggy and sends large negative Meter Reports from time to time." * https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x041a/kp-so-02.json#L96

Cougar · January 17, 2025, 10:14pm

No, I mean these sensors. I’m not sure if it helps you, though

danieldeni · January 19, 2025, 7:28am

Are you sure those bulbs are not Zigbee routers?

From what I know, the official spec states that all mains powered (110/230V) Zigbee device should be a router.

I am only using Philips Hue lights and all types are routers. There’s only 1-2 models with built in battery that are end points only. All their buttons and sensors are end points as well.

I was running a combination of Z2M and ZHA for over a year, as power plugs with energy metering caused the whole Z2M network to slowdown so I had only my power plugs connected to ZHA.

Recently moved back from Z2M+ZHA to just ZHA, since I switched wall buttons from FriendsOfHue (ZGP) which is not supported by ZHA to the Philips Hue Tap Dial Switch which is just an endpoint device with battery.

That switch was added in ZHA 2024.10.0 release. Before it was added it constantly crashed ZHA, which is why I tried it in the past and moved back to the ZGP buttons with Z2M and all my lights in there.

PrairieSnpr · January 19, 2025, 2:40pm

The thing about specifications, is that manufacturers would actually need to follow them and most don’t bother. There are many mains powered devices that don’t route.

Here’s an example:

That said, I’m actually of the opinion that bulbs shouldn’t route, since they can be easily powered off.