Zigbee-Herdsman failing to load

Configuration Zigbee
1

I have been trying to get Zigbee2MQTT to work for a while now after a major crash and had to set up everything again, including the broker in LXC container in Proxmox.
I’ve tried findin the solution but so far i’m getting nowhere.
This is the log output from Zigbee2MQTT addon in HASS:

[10:40:39] INFO: Preparing to start…
[10:40:39] INFO: Socat not enabled
[10:40:39] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[2025-06-23 10:42:07] info: z2m: Logging to console, file (filename: log.log)
[2025-06-23 10:42:08] info: z2m: Starting Zigbee2MQTT version 2.4.0 (commit #unknown)
[2025-06-23 10:42:08] info: z2m: Starting zigbee-herdsman (4.1.0)
[2025-06-23 10:42:08] info: zh:zstack:znp: Opening TCP socket with 192.168.1.66:6638
[2025-06-23 10:42:08] info: zh:zstack:znp: Socket connected
[2025-06-23 10:42:08] info: zh:zstack:znp: Socket ready
[2025-06-23 10:42:08] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-06-23 10:42:09] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-06-23 10:43:16] error: z2m: Error while starting zigbee-herdsman
[2025-06-23 10:43:16] error: z2m: Failed to start zigbee-herdsman
[2025-06-23 10:43:16] error: z2m: Check xxxx for possible solutions
[2025-06-23 10:43:16] error: z2m: Exiting…
[2025-06-23 10:43:16] 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:363: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:154:16)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
at Zigbee.start (/app/lib/zigbee.ts:71:27)
at Controller.start (/app/lib/controller.ts:102:13)
at start (/app/index.js:149:5))
at ZnpAdapterManager.beginCommissioning (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:365: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:154:16)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
at Zigbee.start (/app/lib/zigbee.ts:71:27)
at Controller.start (/app/lib/controller.ts:102:13)
at start (/app/index.js:149:5)
[10:43:16] INFO: Preparing to start…
[10:43:17] INFO: Socat not enabled
[10:43:17] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/

my config is:

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
serial:
port: tcp://[192.168.1.66:6638]
baudrate: 115200
adapter: zstack
disable_led: false
rtscts: false
advanced:
transmit_power: 20

I’m using SLZB-06 Zigbee Ethernet PoE coordinator

1 Like
2

pretty sure this needs to be

port: tcp://192.168.1.66:6638
3

it is, was having problem posting this because of to many links

4

Take the antenna off your SLZB-06, restart Zigbee2MQTT, once Zigbee2MQTT is running, turn the antenna back on.

Another solution here:

  • If you had your Zigbee network before and such an error appears with the new Zigbee adapter, try to switch off the Zigbee routers that were connected to your previous Zigbee network and restart Zigbee2MQTT.

(in fact it is the same solution, making sure the routers can’t talk to the coordinator)

5

None of this worked for mine. It’s just an expensive doorstop at the moment. I really do not have the time to recreate my entire Zigbee network again from scratch.

6

Sorry for your troubles and it’s definitely your choice moving forward. Just understand, folks on this forum volunteer their help using experience and knowledge to assist.

7

It’s a good bit of kit when it works, however the issue the OP is experiencing is a common one. If you get the POE adapter to work everything is great until it stops working (firmware upgrade in this instance) - then you will find switching back to your old coordinator works without issue (in my case a ZZH!). I don’t understand why the POE coordinators suffer from this imaginary PAN issue. I powered off the entire house (Internet and HA server are on a separate power supply) and it still gave me the error - there were no Zigbee routers on at all.

I understand we are all volunteers - but even the distributor/manufacturer of mine couldn’t assist. These are not drop in replacements as they appear to be advertised.

8

You are right, they aren’t drop in replacements. A ton of variables like chip vendors, internal power amplifiers, firmware, integration to the OS, etc…

Possibly a marketing scheme :thinking:

1 Like
9

This seems to have worked, I will test a bit more with adding some devices, but for now I don’t get errors on it.
Thank you :slight_smile:

10

There’s a couple of threads here mentioning there was a bug that the SMlight coordinator switched back to USB mode after a firmware update. Maybe try checking that in the coordinator setup page.

EDIT, right on cue, I found another thread from 3 hours ago where it mentions this

11

In case of the OP, that was not the case. The ‘network with the same panId or extendedPanId already exists nearby’ can happen with any adapter (USB or Ethernet)

12

Yes yes, I’m fully aware, thanks. I was replying to the other person who mentioned issues after firmware updates