There was an update issued by HA for the SLZB-06, well in my case it was.
Installed update and now nothing on my Zigbee network works, then found that Zigbee2MQTT will not start.
My SLZ is running v3.3.3.dev1
Considering it was running ok up until this notified update, there must be somnething wrong with this rev.
I would like to go back to the previous version, is this easy? Or any instructions, please?
TIA, Paul.
Update,
Re-applied the firmware on SLZB06 to 3.3.1, HA still throws up errors.
Going to try a HA restore.
Restored still Zig2mqtt does not load.
first time I have had an issue in 2 years like this.
How about you share those errors with us so people can actually help you?
Good call. Was trying to help myself!, Thank you!
[2026-05-30 19:22:43] info: z2m: Logging to console, file (filename: log.log)
[2026-05-30 19:22:43] info: z2m: Starting Zigbee2MQTT version 2.10.1 (commit #unknown)
[2026-05-30 19:22:43] info: z2m: Starting zigbee-herdsman (10.0.7)
[2026-05-30 19:22:43] info: zh:zstack:znp: Opening TCP socket with 192.168.64.249:6638
[2026-05-30 19:22:43] info: zh:zstack:znp: Socket connected
[2026-05-30 19:22:43] info: zh:zstack:znp: Socket ready
[2026-05-30 19:22:43] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2026-05-30 19:22:44] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2026-05-30 19:23:50] error: z2m: Error while starting zigbee-herdsman
[2026-05-30 19:23:50] error: z2m: Failed to start zigbee-herdsman
[2026-05-30 19:23:50] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2026-05-30 19:23:50] error: z2m: Exiting...
[2026-05-30 19:23:50] 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:68:23)
at ZnpAdapterManager.beginCommissioning (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:376:31)
at processTicksAndRejections (node:internal/process/task_queues:103:5)
at ZnpAdapterManager.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:90:21)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:135:16)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:146:29)
at Zigbee.start (/app/lib/zigbee.ts:70:27)
at Controller.start (/app/lib/controller.ts:111:29)
at start (/app/index.js:156:5))
at ZnpAdapterManager.beginCommissioning (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:378:23)
at ZnpAdapterManager.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:90:21)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:135:16)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:146:29)
at Zigbee.start (/app/lib/zigbee.ts:70:27)
at Controller.start (/app/lib/controller.ts:111:29)
at start (/app/index.js:156:5)
I had the same issue with ZHA. Spent 2 hours with Gemini helping me trying to reflash, etc., etc.
Finally, I changed my SLZB-06 that was my Thread Border Router to Zigbee and migrated and network came back. (Then I changed what was Zigbee SLZB-06 to Thread and brought that back).
Ultimately, it seems as if that flashed fresh firmware, whereas all my other tries did not.
I can try and manually from the webconsole of the SLZ, flash the dev firmware in.
It keeps complaining about the 'herdsman'
Up until I did the update all was working correctly!.
I have got 46 devices working on the Zigbee co-ord, I do not fancy re-pairing that lot!!
Help, I'm having the same problem. After updating the firmware to version v3.3.3.dev1, Zigbee2 MQTT stopped working. I downgraded to version v3.3.1, but everything remained the same.
I restored Home Assistant with an automatic backup from May 24th, but it still doesn't work. My family wasn't a fan of Home Assistant, and now without lighting at night, I'm screwed.
Does anyone have any idea what to do to solve this serious problem?
My best advice, although I can't make any guarantees, is to use the SLZB-06 web terminal to flash it to another mode (e.g. Open Thread Border Router). Then reboot it and Home Assistant. Then flash it back to Zigbee Coordinator and try to reinstall in Home Assistant. That is effectively what I did, albeit on a second SLZB-06 device.
Have a look at that URL for troubleshooting steps for Error: network commissioning timed out.
You'll probably have to rename your Z2M backup file to fix the issue. The troubleshooting page will explain what to do
Appreciate the input, but I cannot see anything referring to what you suggested.
Looking at the main page of Z2M, the start just has a spinning wheel.....
De-installed Z2m, reboot, re-installed.
Did @brad.trout suggested. No joy.
I do have a spare uPC and could restore to that, but I do not know if that will help.
Thanks all so far....
I had the same problem with ZHA. No more Zigbee since last SLZB update...
I re-flashed the zigbee coordinator's radio module with the exact same version, after I had previously downgraded the firmware to previous v3.3.1. (from coordinator's web interface)
Everything is fine again now for me (I rebooted coordinator from network and HA each time between steps).
Hope this helps!
Wasn't at home yesterday so couldn't reply properly. Let's try this again & see if we can get you back up & running...
Starting with the easiest method to the most involved:
1: Stop Z2M, unscrew the antenna on your SLZB-06, then start Z2M.
Screw the antenna back in & check the logs. If you still see the same errors, try method 2.
2: Stop Z2M, find the coordinator_backup.json (if you have Samba installed, it's in the \\HOMEASSISTANT\config\zigbee2mqtt folder. Rename it to something like oldcoordinator_backup.json& start Z2M. If you still see the same errors, try method 3.
3: Re-flash the coordinator firmware like @mr-bembel showed in the post above. Don't choose firmware which ends in dev, like v3.3.3.dev1, since that is a development version which may cause issues. Stick to v3.3.1, since that seems to be the latest stable release.
PS - not sure why people are seeing dev versions for firmware updates. According to the SM docs, it should only be pulling stable version for firmware updates.
Thank you @ShadowFist, appreciate you taking the time, and of course the others also.
I will try it now.....
KR, Paul
Shutdown HA after turning off autostart on Z2M, unplugged ethnet to SLZB, unscrewed aerial.
Reconnected SLZB, waited then powered on the HA.
When HA had settled, started Z2M
[10:56:40] INFO: Preparing to start...
[10:56:40] INFO: Socat not enabled
[10:56:41] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2026-05-31 10:56:44] info: z2m: Logging to console, file (filename: log.log)
[2026-05-31 10:56:44] info: z2m: Starting Zigbee2MQTT version 2.10.1 (commit #unknown)
[2026-05-31 10:56:44] info: z2m: Starting zigbee-herdsman (10.0.7)
[2026-05-31 10:56:45] info: zh:zstack:znp: Opening TCP socket with 192.168.64.249:6638
[2026-05-31 10:56:45] info: zh:zstack:znp: Socket connected
[2026-05-31 10:56:45] info: zh:zstack:znp: Socket ready
[2026-05-31 10:56:45] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2026-05-31 10:56:46] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2026-05-31 10:57:19] info: zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'
[2026-05-31 10:57:20] info: z2m: zigbee-herdsman started (reset)
[2026-05-31 10:57:20] info: z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240710,"transportrev":2},"type":"ZStack3x0"}'
[2026-05-31 10:57:20] info: z2m: Currently 0 devices are joined.
[2026-05-31 10:57:20] info: z2m: Connecting to MQTT server at mqtt://core-mosquitto:1883
[2026-05-31 10:57:20] info: z2m: Connected to MQTT server
[2026-05-31 10:57:20] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2026-05-31 10:57:21] info: z2m: Started frontend on port 8099
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c1388a5256393b/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m: Zigbee2MQTT started!
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000ab9ea9/switch_l1/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000ab9ea9/switch_l2/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000ab9ea9/switch_interlock/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c138483494bfab/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c1389fc3c14935/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c138f8bef1cdc8/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c138bca584e8b4/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000634056/switch_trigger_indicator/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c1383d36377caf/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c1380544e10075/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000632757/switch_trigger_indicator/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000abaecd/switch_l1/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000abaecd/switch_l2/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000abaecd/switch_interlock/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0xa4c138455e0f133c/switch/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100073b4ad/switch_child_lock/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100073b4ad/switch_window_detection/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100073b4ad/switch_valve_detection/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100073b4ad/switch_schedule/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100070177b/switch_child_lock/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100070177b/switch_window_detection/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100070177b/switch_valve_detection/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100070177b/switch_schedule/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000b26698/switch_l1/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000b26698/switch_l2/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef441000b26698/switch_interlock/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/0x54ef44100073d843/switch_child_lock/config', payload ''
[2026-05-31 10:57:21] info: z2m:mqtt: MQTT
I can also click on the app and it opens.
New issue is, all of my Zigbee devices are gone.
How do I get those back, please. I did take a copy of the config folder.....
Thanks @ShadowFist
You didn't need to shutdown HA. You can simply stop Z2M from the App page if it's still trying to start after you switched off autostart.
Did you screw the aerial back in after starting? I don't see it listed in the steps you followed.
Make sure the aerial is screwed back in & give it a few minutes. If the devices don't show up, go press a button on any zigbee switch & check if it reports anything to z2m
I could not shutdown Z2M as i was not given the option apart from a spinning wheel, hence why I shutdown.
As you can see, I have no devices.
I have pressed buttons, activated PIRs and nothing is shown on Reporting section of Z2M.
This is my network page
KR, Paul
You still haven't answered my question.
The aerial is back in, I have pressed buttons on devices Zigbee switches, like aqara wireless ones
Weird. The devices should be picked up on press, since their topics are reported in the MQTT messages you posted earlier & the Map still marks 17 siblings for your coordinator.
Double check the antenna is screwed in properly & try pressing a hardwired switch instead of a button. If that still doesn't work, restart Z2M & share what it's reporting.
