Zigbee2Mqtt suddenly doesn't work anymore without any changes made. (version1.26.0-1)

Configuration Zigbee
1

Overnight i suddenly have an issue with Zigbee2mqtt.
This is the third time that suddenly my config is messed up. :roll_eyes:
After the issue i updated to the newest version, i thought i would solve it easily.
I hope somebody can help me out, i am already working on it to get it resolved for 2 days.
I deinstalled everything and did a complete reinstall with an update to the newest version.
I use a Zigbee sonoff 3.0 stick.

My Current version: 1.26.0-1. It looks like it updated overnight.
Which config do you have in this version because after the update i do get this message in the log, and also do have a 502: Bad Gateway.

My config: In the new version it should look at current settings in the kept config in the config folder.


data_path: /share/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: {}
serial: {}

My error log is as follows

Zigbee2MQTT:info  2022-07-24 18:16:42: Starting Zigbee2MQTT version 1.26.0 (commit #unknown)
Zigbee2MQTT:info  2022-07-24 18:16:42: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:error 2022-07-24 18:16:42: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-07-24 18:16:42: Failed to start zigbee
Zigbee2MQTT:error 2022-07-24 18:16:42: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-07-24 18:16:42: Exiting...
Zigbee2MQTT:error 2022-07-24 18:16:42: Error: spawn udevadm ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

In the meantime i also upgraded my stick (because i thought it maybe had an issue with the firmware) and that gave me this error in the flash programmer app. So it was never updated.
So after all it was a tuff Home assistant weekend.

>Reading file: C:/Users/jurje/OneDrive/Afbeeldingen/Sillicon/CC1352P2_CC2652P_launchpad_coordinator_20220219.hex.

>Start flash verify ...

>Verification failed at address 0x00000004 (in page 0). Expected 0xD1, read 0xC9.

>Reset target ...

>Reset of target successful. ```
2

I have exactly done this but it doesn’t work. It looks like something is still active from an old version it looks like maybe.

3

Not sure why you Sonoff dongle is not working, however you need to solve this before you get Z2M to work.
Whay happens if you take the dongle and attach to a Windows PC? Will it show errors? Which specefic guide do you use to firmware upgrade?

4

It is not the dongle. I have transferred everthing to ZHA and now everything is working.
Are there any pros or cons working with Zigbee2mqtt instead of ZHA. It works great and easy to install.

1 Like
5

The addon will produce the same error if the device is not reachable. You did not specify a port in serial. For me the error was gone after changing the line serial: {} to serial: port: tcp://IP:PORT where IP and PORT identify my zigstar LAN gateway’s address.