Addon: Zigbee2MQTT cannot be started

I can no longer start the Zigbee2MQTT addon, so my HA no longer works.

Error message:
[23:41:44] INFO: Preparing to start…
[23:41:44] INFO: Socat not enabled
[23:41:45] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2023-09-12 23:41:47: Logging to console and directory: ‘/config/zigbee2mqtt/log/2023-09-12.23-41-46’ filename: log.txt
Zigbee2MQTT:info 2023-09-12 23:41:47: Starting Zigbee2MQTT version 1.29.1 (commit #unknown)
Zigbee2MQTT:info 2023-09-12 23:41:47: Starting zigbee-herdsman (0.14.83)
Zigbee2MQTT:error 2023-09-12 23:41:47: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-09-12 23:41:47: Failed to start zigbee
Zigbee2MQTT:error 2023-09-12 23:41:47: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2023-09-12 23:41:47: Exiting…
Zigbee2MQTT:error 2023-09-12 23:41:47: Error: Error while opening serialport ‘Error: Error: No such file or directory, cannot open /dev/ttyACM0’
at SerialPort. (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:91:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:76:22)
at /app/node_modules/@serialport/stream/dist/index.js:112:18

Configuration:
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

serial
port: /dev/ttyACM0
adapter: ezsp

I use the SONOFF ZBDongle-E

I was abroad for a long time until now, so I don’t know exactly how long the problem has existed.

My guess is that the SONOFF is probably broken. What is the best way to test this or do you have an idea what I could do?

Thanks and best regards

Hi, have you tried by unplugging your coordinator?

What Nick4 said +

Better to use /dev/serial/by-id/…

The sonoff stick was defect so I bought a new one and Home Assistant recognize it again but I have still an issue with the Zigbee2MQTT Addon.

Mosquito Broker is started.
Zigbee2MQTT Addon (Current version: 1.29.1-1) started automaticly but I cannot open the Addon and cannot stop the Addon too. When I click on restart then I will receive the following protocol:
[14:24:48] INFO: Preparing to start…
[14:24:48] INFO: Socat not enabled
[14:24:49] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2023-09-29 14:24:50: Logging to console and directory: ‘/config/zigbee2mqtt/log/2023-09-29.14-24-50’ filename: log.txt
Zigbee2MQTT:info 2023-09-29 14:24:50: Starting Zigbee2MQTT version 1.29.1 (commit #unknown)
Zigbee2MQTT:info 2023-09-29 14:24:50: Starting zigbee-herdsman (0.14.83)
Zigbee2MQTT:info 2023-09-29 14:24:53: zigbee-herdsman started (resumed)
Zigbee2MQTT:info 2023-09-29 14:24:53: Coordinator firmware version: ‘{“meta”:{“maintrel”:"3 ",“majorrel”:“6”,“minorrel”:“10”,“product”:8,“revision”:“6.10.3.0 build 297”},“type”:“EZSP v8”}’
Zigbee2MQTT:info 2023-09-29 14:24:53: Currently 32 devices are joined:
Zigbee2MQTT:info 2023-09-29 14:24:53: Tisch Raum (0x00178801096f206e): 929001953101 - Philips Hue White and Color Ambiance GU10 (Router)
[…]
Zigbee2MQTT:info 2023-09-29 14:24:53: Zigbee: disabling joining new devices.
Zigbee2MQTT:info 2023-09-29 14:24:53: Connecting to MQTT server at mqtt://core-mosquitto:1883
Zigbee2MQTT:warn 2023-09-29 14:25:12: Device ‘Bewegungsmelder Flur’ left the network
Zigbee2MQTT:error 2023-09-29 14:25:26: MQTT error: connect ECONNREFUSED 172.30.33.5:1883
Zigbee2MQTT:error 2023-09-29 14:25:26: MQTT failed to connect, exiting…
Zigbee2MQTT:info 2023-09-29 14:25:26: Stopping zigbee-herdsman…
Zigbee2MQTT:info 2023-09-29 14:25:26: Stopped zigbee-herdsman

But under information is marked with green and I have the possibility to click on Stop or Restart (but stop doesnot work)

I receive the following error description when opening the Addon:
The add-on doesn’t seem to be ready yet, maybe it is still starting. Do you want to try again?
When I click on try again then it will not work too.

Does anyone have an idea and can support me with my issue?

Thanks

Zigbee2MQTT can’t login to your mqtt broker. Is your username and password correct ?

I can’t remember that I have specific login data for Mosquitto.
How can I check this?

That is the protocol from Mosquitto:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[17:07:37] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[17:07:37] INFO: Starting NGINX for authentication handling…
[17:07:38] INFO: Starting mosquitto MQTT broker…
2023-09-29 17:07:38: Warning: Mosquitto should not be run as root/administrator.
2023-09-29 17:07:38: mosquitto version 2.0.11 starting
2023-09-29 17:07:38: Config loaded from /etc/mosquitto/mosquitto.conf.
2023-09-29 17:07:38: Loading plugin: /usr/share/mosquitto/go-auth.so
2023-09-29 17:07:38: ├── Username/password checking enabled.
2023-09-29 17:07:38: ├── TLS-PSK checking enabled.
2023-09-29 17:07:38: └── Extended authentication not enabled.
2023-09-29 17:07:38: Opening ipv4 listen socket on port 1883.
2023-09-29 17:07:38: Opening ipv6 listen socket on port 1883.
2023-09-29 17:07:38: Opening websockets listen socket on port 1884.
2023-09-29 17:07:38: Error: Unable to create websockets listener on port 1884.
[15:07:38] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[15:07:38] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

If it is the add-on, just create a user and password in HA, and add that user/pwd in your Zigbee2MQTT configuration.

Thanks so far, the user was deactivated. I activate the user now but when I click on devices > Mosquitto > Configuration > Re-Configure MQTT: Then the user and password is maintained correctly but when I click on ok then an error message appears: Please enter the connection information of your MQTT broker. Connection failed.

It seems that Mosquitto is running now without any changes…