I have today experienced issues, without (as far as I’m aware) changing anything related to Z2M or the adapter I’m using.
I’m running;
Zigbee2MQTT version 2.1.3-1 as an add-on in HA
SLZB-06 (POE) as my adapter
core firmware version: v2.7.1 and the zigbee firmware revision: 20240710.
When rebooting my Home Assistant server which runs, HAOS as per below;
I tried to update the channel from 25 to 20 and now the Z2M addon starts however I can’t see any of the devices.
When switching back to 25 I can still start the add-on, however no devices there either.
So the question is, will it be possible to retrieve or do I now consider if I should;
a) start over on HAOS from scratch or;
b) install z2m outside of the HAOS as a docker container on my unraid server and do a factory reset of the SLZB-06 and then set everything up from scratch
I am in the same condition. Same adapter. Same error. Nothing was changed as it happened overnight. I woke up to unresponsive zigbee devices and found the same error in the logs.
I was in the same boat with herdman not starting. Turned out that on the connection mode was set to USB instead of ethernet (as I had it connected over ethernet). This post helped me solve this.
In my case, after much testing, the solution was to unplug the SLZB-06 and plug it back in, even though it sounds like a joke.
The device was accessible and responded to commands, including a software reset, but some parts of it were blocked after the update.
Strange. I did do a disconnect and reconnect for mine, but it seems to have not made a difference. I even deleted the state.json and database.db (after backing them up) to see if it would reload from the coordinator_backup.json, but the logs do not indicate it even tried to restore from the backup. It continues to insist there is a duplicate network (which of course, there isn’t).
I had similar issues today. I have tried to reflash to Revision: 20240710, instead of Revision: 20250318 - seems to be helping.
I’m reffering to Zigbee OTA update section.
Hi
i am in the same situation. Installed the new zigbee firmware and got the duplicate network issue. Reinstalling the old firmware and restarting the whole device does not solve the issue. At the moment i am clueless.
I found out through much troubleshooting, that something had changed the zigbee channel on me from 11 to 15. I did not change it (I was fast asleep), but the coordinator firmware updated, and that seems to have somehow triggered all this. I have since set the channel back and now my devices have returned.
Check your zigbee channel!
You can find the setting in your configuration.yaml file in the config folder of your z2m service.
You don’t change it on the adapter directly.
Make a backup of your config before messing with it!
Meanwhile I got firmware v2.8.2.dev3 (20250318) running, after moving back to old one and now again to the newest. No error messages anymore, but I had to rejoin the devices. So in general, the new firmware is working, but I have no idea what the root cause was.
Problem same for me with my SLZB-06. Rock solid for a couple of years but now, zigbee2mqtt shuts down with the herdsman error, and I have to powercycle the SLZB-06 to get it to restart. This is a pain as I dont continously monitor HA so usually only find out when a critical automaton fails.
In HA, go to Settings > Devices & Services > Devices tab. Search for Zigbee2MQTT. It’ll take you to the “device” page for your z2m addon.
Under the “sensors” panel, you should see an entity named binary_sensor.zigbee2mqtt_running (if it’s not there, click the “+6 disabled entities” under the sensors panel).
