Hi i have HA Green with Sonoff P usb and have been trying to do the Zigbee2mqtt addon. Followed loads of video on how to do. So ensured ZHA is not installed on dongle. Added mqtt and mosquitto broker added configuration into zigvee2mqtt for adapter, port, serial, passwords etc. When i start Zigbee2mqtt it co es up with configuraton page that i check and submit. Checking log the start fails to start up herdsman .
Any suggestions on what i need to ammend
You need to paste the logs for us to see if you want us to help.
One of the lines in the logs will point you to check the troubleshooting site here Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT. A couple of lines below it will be the actual reason why it failed. Grab that reason & look it up on that page - there’s be troubleshooting steps to follow
Log file below:-
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[21:04:57] INFO: Preparing to start...
[21:04:57] INFO: Socat not enabled
[21:04:58] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[2025-12-23 21:05:42] info: z2m: Logging to console, file (filename: log.log)
[2025-12-23 21:05:43] info: z2m: Starting Zigbee2MQTT version 2.7.1 (commit #unknown)
[2025-12-23 21:05:43] info: z2m: Starting zigbee-herdsman (7.0.4)
[2025-12-23 21:05:43] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_b497da16a9a0ef11ac96a6a361ce3355-if00-port0","baudRate":115200,"rtscts":true,"autoOpen":false}
[2025-12-23 21:05:43] info: zh:zstack:znp: Serialport opened
[2025-12-23 21:05:44] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-12-23 21:05:45] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-12-23 21:06:03] error: z2m: Error while starting zigbee-herdsman
[2025-12-23 21:06:03] error: z2m: Failed to start zigbee-herdsman
[2025-12-23 21:06:03] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-12-23 21:06:03] error: z2m: Exiting...
[2025-12-23 21:06:04] error: z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:115:27)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:143:29)
at Zigbee.start (/app/lib/zigbee.ts:70:27)
at Controller.start (/app/lib/controller.ts:101:13)
at start (/app/index.js:149:5)
Also not sure why everytime i start Zigbee2MQTT i get the “Onboarding page is available at http://0.0.0.0:8099/”
Have you followed my previous instructions? You can see the URL & the “Error: SRSP - SYS - ping after 6000ms” right there.
I am 75% confident your issue is ZHA starting up automatically due to autodiscovery. Check your integrations page - if you see a Discovered integrations section with ZHA there, click ignore
So my SONOFF Zigbee 3.0 USB Dongle Plus zha is in my ignored list do I need to move to disabled?
Probably yes and what I usually do is to unplugged coordinator and plug it int, And then restart z2m. Usually helps.
So I have disconnected SONOFF, checked SONOFF integration is ignored, restarted HA and after plugging SONOFF back into USB on HA I restarted Z2M but still getting same error message and Z2M doesn’t start
Would like to help you men but I don’t know.
I dont use haos. I use docker.
There is a problem with your coordinator.
It could be mqtt as z2m will not work is mqtt is not working.
Usually if this is a usb coordinator it need to be plugged in usb3, usually marked as blue on comps.
Thanks do you know if there I a particular firmware that needs flashing to the SONOFF dongle to make it a Z2M coordinator. I did flash to latest available but wonder if that was for ZHA perhaps. Thanks for you help
I’m not sure that this will help you. I have my coordinator for a few years and never flashed firmware on it. You usually flash firmware on coordinatior because there is valid reason to do that.
Not because there is new firmware out there.
You messed up something, but what it is it’s hard to tell.
I have tested nearly all available firmwares for the SONOFF Zigbee 3.0 USB Dongle Plus | ZBDongle-P in Coordinator mode. THIS firmware seems to be the most reliable and stable one.
Please do not recommend people plug in zigbee coordinators in a usb3 port. There’s multiple warnings both in this forum and from official sources that usb3 is a major source of interference on the 2.4gHz spectrum.
Usb2 has no such issues and has plenty of bandwidth available for zigbee needs.
Post your Z2M config here pls. Make sure you remove any passwords & the network key from the post.
Also, can you share a screenshot of your integrations page? I have a feeling you had 2 autodiscovered integrations - Sonoff & ZHA, but you only disabled the Sonoff one.
Tnx for heads up. I didn’t know this.
1 Like
Appreciate the help. Z2M config :-
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:
user: Mqtt_user
password: **********
base_topic: Zigbee2mqtt
server: Mqtt://192.168.0.4:1883
serial:
port: /dev/ttyUSB0
Probably your stick is not recognized.
Did you try to configure it like in documentation
You’re definitely missing the adapter: line under serial. That’s at least 1 reason why it’s not starting.
Also, please format your code properly. We can’t tell if you have indentation errors too
You probably mean:
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:
user: Mqtt_user
password: **********
base_topic: Zigbee2mqtt
server: Mqtt://192.168.0.4:1883
serial:
port: /dev/ttyUSB0
Now SSH to the CLI and execute:
ls -l /dev/serial/by-id
The output should look similar to:
total 0
lrwxrwxrwx 1 root root 13 Dec 4 19:21 usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 -> ../../ttyUSB0
Note the usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 (the output on your HA server may vary!)
Replace within your Z2M configuration:
serial:
port: /dev/ttyUSB0
with:
serial:
port: >-
/dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0
(again, the output on your HA server may vary!)
…and add:
adapter: zstack
below the above port definition.
Furthermore replace:
server: Mqtt://192.168.0.4:1883
with:
server: mqtt://192.168.0.4:1883
The Z2M configuration file should look similar to:
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:
user: Mqtt_user
password: **********
base_topic: Zigbee2mqtt
server: mqtt://192.168.0.4:1883
serial:
port: >-
/dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0
adapter: zstack
1 Like
So this morning I removed the SONOFF and connected my ZBT-2 instead. Updated the adapter setting in config and Z2M now up and running. So it must be something to do with the SONOFF.
The reason I wanted another adapter/coordinator was firstly to setup Z2M so I can move my zigbee devices across but secondly I have some Matter devices that I want to add to HA so thought I needed another adaptor.
Any advise on how to add Matter/Thread would be great. Perhaps I could use the SONOFF device.
Just to add in removed ZBT-2 and put back in SONOFF changed Serial and adapter to zstack and baudrate to 115200 and Z2M fails to start with herdsman error again so my assumption is SONOFF is the issue.
Thought I would use the SONOFF OpenThread for my Matter devices but it appears that the P version doesn’t do OpenThread and I’m assuming I can add OpenThread to the ZBT-2 as it’s doing Zigbee2MQTT