Help, my Zigbee2mqtt network broken after power outage

I’m in need of some serious help please? I can no longer get any zigbee device to pair to my HA. Raspberry Pi4(4GB), 256GB SSD with a Sonoff Zigbee 3.0 USB dongle Plus and Zigbee2MQTT.

We had a power outage/surge yesterday and since then my Zigbee2MQTT network has been misbehaving. Everything in HomeAssistant looked ok but I could not turn on any device through the Zigbee2MQTT dashboard or Lovelace dashboard. My first step after the outage was to turn power off for the whole house a few minutes and when powered back up everything looked ok. This did appear to help but not everything was working, however the automations associated with the devices appeared to work ok. Only Zigbee2MQTT is affected all other devices and entities appear to work as expected.

So this morning the morning automations all worked ok but still I couldn’t control anything through the dashboard. When I deleted a few devices from Zigbee2MQTT I was unable to get them to pair again. These “test” devices were Hue bulbs and I could pair them in the Hue App, if I deleted them from the Hue app I still couldn’t pair them in Zigbee2MQTT.

Here’s the code from Zigbee2MQTT

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:
  base_topic: zigbee2mqtt
  user: mqtt_user
  password: *******
  server: mqtt://192.168.1.16:1883
serial:
  port: /dev/ttyUSB0

and from Mosquitto broker

logins: []
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
  active: false
  folder: mosquitto

Here’s the log from the mosquitto start up,

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] mosquitto.sh: executing... 
[16:01:14] INFO: Certificates found: SSL is available
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[16:01:14] INFO: Starting NGINX for authentication handling...
[16:01:15] INFO: Starting mosquitto MQTT broker...
1658070075: Warning: Mosquitto should not be run as root/administrator.
[16:01:16] INFO: Successfully send discovery information to Home Assistant.
[16:01:16] INFO: Successfully send service information to the Supervisor.

The log from zigbee2mqtt,

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/socat.sh
[14:59:14] INFO: Socat not enabled, marking service as down
cont-init: info: /etc/cont-init.d/socat.sh exited 0
cont-init: info: running /etc/cont-init.d/zigbee2mqtt.sh
cont-init: info: /etc/cont-init.d/zigbee2mqtt.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 socat (no readiness notification)
services-up: info: copying legacy longrun zigbee2mqtt (no readiness notification)
[14:59:17] INFO: Handing over control to Zigbee2MQTT Core ...
> [email protected] start
> node index.js
Zigbee2MQTT:info  2022-07-17 14:59:23: Logging to console and directory: '/config/zigbee2mqtt/log/2022-07-17.14-59-23' filename: log.txt
Zigbee2MQTT:info  2022-07-17 14:59:23: Starting Zigbee2MQTT version 1.26.0 (commit #unknown)
Zigbee2MQTT:info  2022-07-17 14:59:23: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-17 14:59:27: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-07-17 14:59:27: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-17 14:59:27: Currently 1 devices are joined:
Zigbee2MQTT:info  2022-07-17 14:59:27: 0x00237efe601dd5ee (0x00237efe601dd5ee): Not supported (Unknown)
Zigbee2MQTT:info  2022-07-17 14:59:27: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2022-07-17 14:59:27: Connecting to MQTT server at mqtt://192.168.1.16:1883
Zigbee2MQTT:info  2022-07-17 14:59:27: Connected to MQTT server
Zigbee2MQTT:info  2022-07-17 14:59:27: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2022-07-17 14:59:27: Started frontend on port 0.0.0.0:8099
Zigbee2MQTT:info  2022-07-17 14:59:27: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"unknown","coordinator":{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"},"log_level":"info","network":{"channel":11,"extendedPanID":"0x00124b0024c9ee61","panID":6754},"permit_join":false,"version":"1.26.0"}'
Zigbee2MQTT:info  2022-07-17 14:59:27: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2022-07-17 15:00:32: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-17 15:00:32: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254,"value":true},"status":"ok","transaction":"v6s70-1"}'
Zigbee2MQTT:error 2022-07-17 16:01:10: Not connected to MQTT server!
Zigbee2MQTT:info  2022-07-17 16:01:16: Connected to MQTT server
Zigbee2MQTT:info  2022-07-17 16:01:16: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'

As a novice I can’t see anything wrong here anybody able to shed any light?

I’m not sure if this is relevant but, since I first installed the Sonoff stick I had an unknown device, which I initially thought was from a bad flash, but I’ve reflashed and I get the same thing. I even ordered another stick and I get the same issue, here’s an extract from the log showing the “spurious” device,

Zigbee2MQTT:info  2022-07-17 14:59:27: Currently 1 devices are joined:
Zigbee2MQTT:info  2022-07-17 14:59:27: 0x00237efe601dd5ee (0x00237efe601dd5ee): Not supported (Unknown)

For tonight I’ve rejoined all the hue bulbs and switches to the Hue app, but I still can’t join the Aqara temperature sensors and Blind Motor

I should add that I may now have introduced errors into the config as I’ve been trying to debug, but I think I put things back to as they were???

The error must be in the Zigbee2MQTT as my Tasmota devices are all working correctly, but I still can’t see the error…

Time to give it a rest for today, tomorrow hopefully will bring fresh thoughts.

As my system is quite small I’ve decided to cut my losses and reinstall. Gives me a clean slate and removes all those original “tests” (mistakes) I made!

OK, found the issue! Somehow the Zigbee stick got moved and was too near the SSD. Moved them appart and it now works. Trouble is I’ve deleted everything and need to repair everything. When I first put the SSD in, by chance I had everything separated sufficiently, with hindsight I sometimes had issues pairing and maybe I was just on the limit of functionality.

A BIG lesson learned but I have a clean system, at least for a while!?