Failed to start zigbee-herdsman

Configuration Zigbee
1

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;

  • Core 2025.3.3
  • Supervisor 2025.03.3
  • Operating System 15.0

My Z2M config is as per below;

data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: “-d -d”
log: false
mqtt:
server: mqtt://core-mosquitto:1883
user: [masked]
password: [masked]
serial:
port: tcp://192.168.1.97:6638
baudrate: 115200
adapter: zstack
disable_led: false
advanced:
homeassistant_legacy_entity_attributes: false
homeassistant_legacy_triggers: false
legacy_api: false
legacy_availability_payload: false
transmit_power: 20
device_options:
legacy: false

The log files looks as per below in Z2M;

[13:26:56] INFO: Preparing to start…
[13:26:56] INFO: Socat not enabled
[13:26:56] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
[2025-03-20 13:26:57] info: z2m: Logging to console, file (filename: log.log)
[2025-03-20 13:26:57] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #unknown)
[2025-03-20 13:26:57] info: z2m: Starting zigbee-herdsman (3.2.7)
[2025-03-20 13:26:57] info: zh:zstack:znp: Opening TCP socket with 192.168.1.97:6638
[2025-03-20 13:26:57] info: zh:zstack:znp: Socket connected
[2025-03-20 13:26:57] info: zh:zstack:znp: Socket ready
[2025-03-20 13:26:57] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-03-20 13:26:58] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-03-20 13:28:04] error: z2m: Error while starting zigbee-herdsman
[2025-03-20 13:28:04] error: z2m: Failed to start zigbee-herdsman
[2025-03-20 13:28:04] error: z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions
[2025-03-20 13:28:04] error: z2m: Exiting…
[2025-03-20 13:28:04] 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)

The add-on fails to boot and thus I’m not able to control any of my zigbee devices.

If any further information is needed please let me know.

2

The error messages include a link to troubleshooting instructions. Did you check/try them?

3

Same here. Today the firmware of my SLZB-06 (ccordinator) was updated to v2.8.2.dev3 (20250318). I restored an HA backup but still the same.

4

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

5

I see, mine never update today I could see that I was still on the same fireware.

6

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.

7

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.

8

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.

9

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).

10

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.

11

Thanks, I’ll give this a try

12

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.

13

what do you mean by dupilcate network issue?

14

i was referring to the error message:
network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby

15

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!

16

Could you let us know where/how do you change the zigbee channel on SLZB-06? I can’t seem to locate this setting.

17

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!

1 Like
18

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.