Zigbee2MQTT - Re-installation issue

Configuration Zigbee
1

I installed a new HA this morning, after many tests in my pervious one.
It is installed as Debian + HA, and soon after the HA installation, I tried to install MQTT and Zigbee2MQTT.
MQTT seens to start with no problems, but Z2M not (but is possible the problem is on MQTT). When I start the Z2M I see this error message:

TypeError: Cannot read properties of undefined (reading ‘mqtt’)
at read (/app/lib/util/settings.ts:326:11)
at getInternalSettings (/app/lib/util/settings.ts:406:21)
at Object.reRead (/app/lib/util/settings.ts:684:5)
at start (/app/index.js:93:14)

I’ve tried to remove and add them again, change some configs but anything has worked.
Does anyone could help me with that?
My Z2M config file 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: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://core-mosquitto:1883
  user: mqtt-user
  password: xxxxxxxxxxxxx
serial:
  port: /dev/ttyUSB0
zigbee_herdsman_debug: false

Thanks a lot.

2

Assume you rin the mosquitto directly on HA as a add-on?
Can you send the rest of your log.
The MQTT user you use, is it created in HA with admin rights? Remember it need to have username with big/small letters as created

3

Since add-on version 1.25.0-1 the add-on logic changed.

Existing installations should be able to safely remove the Zigbee2MQTT
configuration from the add-on configuration as these values should have
already been persisted to the configuration file.

So I guess you did a clean install of HA but kept the zigbee2mqtt config which should be saved in
/config/zigbee2mqtt, correct?
If so, take a look at /config/zigbee2mqtt/configuration.yaml and adapt/check the settings there.
If I get the add-on documentation (which isn’t very clear to be honest) right, the only add-on option that really matters (for existing installations) is data_path and all the other options can be ignored.

For example, this is my currently running add-on config:

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: {}
4

Overnight i suddenly have an issue with Zigbee2mqtt.
This is the third time that suddenly my config is messed up suddenly.
After the issue i updated to the newest version.
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 and that gave me this error in the flash programmer app.
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. ```