Zigbee devices report status but do not respond to commands

joekaiser · February 1, 2023, 7:15pm

At 2am this morning (determined looking at the logbook) my zigbee network went offline. Usually this only happens to a few devices and cycling the power fixes it. Not today.

Every Zigbee device on my network is unresponsive to HomeAssistant, but oddly enough they still report a status. For example, I can manually press a switch and HASS sees the light turn off and on. But if I try to toggle the same light in the app (or web ui) nothing happens. This is happening across every device and different manufacturers. (Sengled, Inovelli, GE, Ikea).

My zwave devices are responding fine. I have tried rebooting the system, moving the stick to another USB port, and I have a USB extender coming tomorrow.

Other than the USB extender, is there anything I can try?

Controller: Nortek HUSBZB-1 Zigbee/Zwave stick. Running 6.7.8-373 - I’m fairly confident that is the latest.
Using ZHA integration

edit - added only relevant log I can find but from what I can tell this just means HASS can’t connect

Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:486
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 11:18:13 AM (69 occurrences)
Last logged: 11:32:24 AM

[0x2F30:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0x4E09:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0x4E09:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0x4E09:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0x2F30:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]

joekaiser · February 2, 2023, 5:21pm

I’m not sure yet but I might have fixed this.

At one point I noticed some buttons are responding, butt their target device (i.e. a light) isn’t. So It made me wonder if something was up with my mesh.

I took a look at my network visualization and started to group devices by working/not-working. I realized everything that wasn’t working was connected in some way to a specific router.
Take a look at the picture below. Anything to the right wasn’t working. Devices on the left were.

I saw that the devices on the right were all connected to the node highlighted. I reset that node and re-added it to the network. All devices are working now. Hopefully this isn’t just a fluke

bartkummel · January 11, 2024, 4:18pm

Thanks for posting your solution. I had a similar situation today, but had no clue where to start fixing. This post pushed me in the right direction. After turning off and on again the bulb that turns out to be the “middle man” for most other Zigbee devices, everything started working again.