Zigbee Devices not available in MQTT but can be controlled (slowly) via Z2M

I’m in a situation where a bunch of my ZigBee devices (predominantly those with physical power rather than battery power) are not populating as online

If i go into the device in Z2M interface and used the exposes tab, the device will control, but very slowly


and i get this message
image

The availability continues to show as offline however.
This availability is reflected (as you would expect) in Home Assistant

I’ve been having some issues with an ethernet cable so have been messing with my network. I did knock the USB for my Zigbee dongle out during this but it’s now back in (and seemingly works since i can send commands see above) I can’t see how this is related, but mentioning in case

I have obviously done a full reboot of Home Assistant with no impact

Anyone got any ideas?!

In Z2M interface seeing

z2m: Publish 'set' 'state' to 'Study Ceiling Light' failed: 'Error: ZCL command 0xa4c138a2c1ff2453/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)'

Solving my own issue. Unplugging the USB and inserting into a different port solved it. Very odd that a restart didn’t

Hello vaderag,

Do you have a 1 or 2 meter extension cable on the Zigbee Dongle? It sounds like you are getting radio interference from the computer.

Yeah - they’re on a 2 meter cable

1 Like

You were lucky that the coordinator picked up its previous serial device path. If you want to fix it properly, you need to change your Z2M port: config to use by-id instead. Have a look here for more info.

PS - your battery devices didn’t fail because Z2M checks in on battery devices every 25 hours or so (mains devices are checked every few minutes). You would have absolutely woken up to all devices being offline tomorrow morning.

Thankfully it’s already like that (probably from when I set it up 3 years ago :rofl:)

It’s testament to how stable Z2M usually is that this is the first issue I’ve had in a long time

1 Like