#Should I NOT configure my Zigbee controller in HA's devices?

1 messages · Page 1 of 1 (latest)

tropic mesa
#

Running HA in a docker container, I did the setup for mosquitto, and now I'm working on the setup for zigbee2mqtt.
Whether I'm doing the onboarding or not, zigbee2mqtt fails to start with the following message:
(Pasting the logs after because discord doesn't like me)

At the moment, my HA's docker configuration file does connect to the device too using this:

    devices:
     - /dev/sonoff_zigbee:/dev/ttyUSB0

Should I remove that from HA, or it has to be there too?
More importantly, what could be the issue why it can't connect to the adapter?
Would it mean I'd have to flash a firmware on it? (I haven't flashed a firmware on the adapter ever.)

# 
zigbee2mqtt    | [2025-06-11 23:34:10] info:     z2m: Logging to console, file (filename: log.log)
zigbee2mqtt    | [2025-06-11 23:34:11] info:     z2m: Starting Zigbee2MQTT version 2.4.0 (commit #bdb94da46e0461337f4a61b4f2a6bfa5172f608f
zigbee2mqtt    | )
zigbee2mqtt    | [2025-06-11 23:34:11] info:     z2m: Starting zigbee-herdsman (4.1.0)
zigbee2mqtt    | [2025-06-11 23:34:11] info:     zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"fc3f57136152ef1196b22e53cc32aab1","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fc3f57136152ef1196b22e53cc32aab1-if00-port0","vendorId":"10c4","productId":"ea60"} => zstack: 4
zigbee2mqtt    | [2025-06-11 23:34:11] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":true,"autoOpen":false}
zigbee2mqtt    | [2025-06-11 23:34:11] info:     zh:zstack:znp: Serialport opened
zigbee2mqtt    | [2025-06-11 23:34:11] info:     zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
zigbee2mqtt    | [2025-06-11 23:34:12] info:     zh:zstack:znp: Skip bootloader for CC2652/CC1352
# 
zigbee2mqtt    | [2025-06-11 23:34:31] error:     z2m: Error while starting zigbee-herdsman
zigbee2mqtt    | [2025-06-11 23:34:31] error:     z2m: Failed to start zigbee-herdsman
zigbee2mqtt    | [2025-06-11 23:34:31] error:     z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
zigbee2mqtt    | [2025-06-11 23:34:31] error:     z2m: Exiting...
zigbee2mqtt    | [2025-06-11 23:34:31] error:     z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
zigbee2mqtt    |     at ZStackAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:114:27)
zigbee2mqtt    |     at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
zigbee2mqtt    |     at Zigbee.start (/app/lib/zigbee.ts:71:27)
zigbee2mqtt    |     at Controller.start (/app/lib/controller.ts:102:13)
zigbee2mqtt    |     at start (/app/index.js:149:5)
chrome thunder
#

mqqt addon> config> serial: enter this and adapt your zigbee hardwareid to your zigbeestick:

#

port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
adapter: zstack

#

u can find the id in settings>hardware>usb

#

would remove it from docker

tropic mesa
#

HA is able to use the adapter, it's zigbee2mqtt that doesn't start.

lavish stone
#

HA doesn’t

#

Z2M publishes to MQTT, HA autodiscovers the devices on the MQTT broker

tropic mesa
#

Ok, so I remove it from HA, because it could be interfering with zigbee2mqtt I guess. 1sec

lavish stone
#

Not sure if you can run ZHA inside the container version of HA or not

#

But you’re this close anyway

#

Also I believe you have the device backward in the docker compose

#

First is the device on the local host, second is what you want the device mapped to in the container

#

I don’t think it’s called /dev/sonoff_Zigbee on your Linux box unless you made an alias for it or something

tropic mesa
lavish stone
#

On the Linux machine?

tropic mesa
#

Yup

lavish stone
#

Ok cool just checking

chrome thunder
#

adding it "by-id"is more consistent, as it binds the device and not the usb-port

lavish stone
#

But this will work for now (I agree should be by-id)

tropic mesa
#

Yup! They were just fighting over it!

image.png
#

Now I need to understand what you guys meant by "by-id" 😛

#

I simply use port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 with these values rather than port: /dev/ttyUSB0, or I need to find an id before?

#

nevermind, you said where to find the id...

tropic mesa
#

(Asking because I don't see a "hardware" section)

chrome thunder
#

yes

#

oh for the id, im running haos, so for me it is under settings - hardware in ha

#

dont know about docker to be honest..

tropic mesa
#

In docker, you don't have the USB hardware listed in there.

#

I think I could use the feedback that zigbee2mqtt to get the id: I have this line:
zigbee2mqtt | [2025-06-12 00:13:20] info: zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"fc3f57136152ef1196b22e53cc32aab1","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fc3f57136152ef1196b22e53cc32aab1-if00-port0","vendorId":"10c4","productId":"ea60"} => zstack: 4

#

The id probably is usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fc3f57136152ef1196b22e53cc32aab1-if00-port0"

#

In my case though, I don't think it would work though since the docker container doesn't know about the actual hardware of the host unless it's bound.

chrome thunder
#

listed in your first pic: try usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fc3f57136152ef1196b22e53cc32aab1-if00-port0

#

dont know, but i would give it a try

#

have to go right now, good luck and hope you succeed