I’m running the latest versions of HAOS and integrations on a Proxmox NUC, and SLZB-06 in PoE coordinator mode.
For the past couple weeks I have been having issues with Zigbee devices not responding, I found rebooting the coordinator once a day “solved” the problem.
This morning I got a message from HAOS to update the SLZB-06 Zigbee firmware:
Dev firmware
Revision: 20250318 Release notes Test firmware
Try this firmware if your ZigBee network hangs periodically and you need to reboot the coordinator
Seemed like this was gonna solve the issue I was having so I installed it. Now ALL my zigbee devices have gone offline, and Zigbee2MQTT is broken and unresponsive.
I immediately rolled back the SLZB-06 Zigbee firmware to the previous version. That did not help. Turned it off and back on again - nope. I uninstalled and reinstalled Zigbee2MQTT. That didn’t help. I loaded a nightly backup from 4 hours before. That did not solve the problem either.
I can view the SLZB-06 web config page, and it appears to be operating normally.
Under Add-Ons I can see Zigbee2MQTT is not running. My configuration file has not changed in any way. I can manually start the service, however it remains unresponsive, I can not view the Zigbee2MQTT main page and devices never come back online. After a couple minutes, it stops again. Here’s the logs (exact same set of messages each time I restart it):
[13:38:06] INFO: Preparing to start...
[13:38:06] INFO: Socat not enabled
[13:38:07] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-03-21 13:38:07] info: z2m: Logging to console, file (filename: log.log)
[2025-03-21 13:38:07] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #unknown)
[2025-03-21 13:38:07] info: z2m: Starting zigbee-herdsman (3.2.7)
[2025-03-21 13:38:07] info: zh:zstack:znp: Opening TCP socket with 192.168.1.75:6638
[2025-03-21 13:38:07] info: zh:zstack:znp: Socket connected
[2025-03-21 13:38:07] info: zh:zstack:znp: Socket ready
[2025-03-21 13:38:07] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-03-21 13:38:08] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-03-21 13:39:14] error: z2m: Error while starting zigbee-herdsman
[2025-03-21 13:39:14] error: z2m: Failed to start zigbee-herdsman
[2025-03-21 13:39:14] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-03-21 13:39:14] error: z2m: Exiting...
[2025-03-21 13:39:14] error: z2m: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby (Error: AREQ - ZDO - stateChangeInd after 60000ms
at Object.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/waitress.ts:67:23)
at ZnpAdapterManager.beginCommissioning (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:372:31)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at ZnpAdapterManager.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:91:21)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:158:16)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:142:13)
at start (/app/index.js:161:5))
at ZnpAdapterManager.beginCommissioning (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:374:23)
at ZnpAdapterManager.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:91:21)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:158:16)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:142:13)
at start (/app/index.js:161:5)
I’m literally back to where I was before installing the firmware, but Zigbee is now totally dead RIP
I have the same problem with the new version.-20250318
-in the description of the new version it refers to EZSP
-strange because zslb 06p has z-stack version
Try to make a back up of your Z2M somewhere (just in case to have it), then remove all current backups from Z2M folder and syart Z2M kinda from scratch. This error frequently happens when zigbee channel is changed (for example, from chanbel 25 to channel 15 or do)
Ended up having to uninstall Z2M and start from scratch. Was able to salvage my device database, but I still have to reconfigure all 60 ZB devices around the house. There goes my weekend…
Had the same issue. After the firmware update.
Nothing worked. I changed the firmware to the previous one and the core from beta to the last stable. (2.7.1)
No luck!
I did a backup of all files in my zigbee2mqtt folder and switched from channel 15 to 20 and back. After that I had to copy my backup files into the folder.
After that I had to repair all devices. The names were recognized by using the database file.
Fortunately it was my second device which is installed in our basement. So I had to repair only 6 devices.
I ended up reverting to the July 2024 version of the antenna and restoring the Zigbee2mqtt plugin to a previous version! After power cycling the devices, they started working again.
So I went into configuration.yaml in the Zigbee2Mqtt and changed the zigbee channel to 20 instead of in my case 15. Restart, the shutdown and change back. Then also power cycle all powered devices.
I just noticed SMLight has pulled that update without any notice. I also wrote to support and got no reply back. So I suppose we can’t expect any support on this issue.
My solution, as posted above, was to delete all traces of Z2M, rollback the ZB firmware, reinstall Z2M fresh, and then add all ZB devices back onto the network. That took me an entire day.
There is a newer DEV update available now (Revision: 20250321), but I think I’ll pass
One similar broken setup also here. I was able to restore by stopping Z2M, downgrading firmware, changing the port from 25 to 15 in configuration.yaml, start Z2M (which starts, but without devices), then change port back to 25, start Z2M (still no devices, log says the port has changed), stop Z2M, restore configuration and database files from backup, restart Z2M, and devices were back.
I’ve read from somewhere that the next restart / reboot might again break everything so fingers crossed someone is working on a real fix.
Good sir… Do you actually realize you were my absolute lifesaver? For whatever reason – I can no longer trace how it happened – 2 of my 3 Z2M instances simply refused to work anymore. Following your instructions, I managed to fix it at 1 a.m. and was finally able to get to sleep.
Same here, but restored following your indications, thanks a lot. After that, updated Z2M to 2.2.0-1, and now wondering if it worth to try again the zigbee firmware update with the new Z2M version. Have anybody tried?
yes, I tried.
after zigbee update, z2m still doesn’t start.
-I stopped z2m, in yaml I changed the zigbee channel to 15, start Z2M.
-z2m starts but without the devices, then stop z2m, in yaml I changed the zigbee channel back to what I had, start z2m then I performed a restore from the last backup and that’s it.
-it’s been working without problems for 3 days
Oh, I thought it was just me! Mine actually burned out, I think due to this firmware update since I don’t recall it working after I clicked to update. I also smelled a very distinct smell of burned plastic…
RIP