#Z2M randomly stopped working.

1 messages · Page 1 of 1 (latest)

manic marsh
#

I woke up this morning to all my Zigbee devices being unavaiable though HA, but still reachable and controllable through Z2M. I rebooted the Z2M hub and it fails to start now. The original error I was getting was Unauth from HA to Z2M. Any help is much appreciated. I've done everything from changing ports, restoring from a known working backup, etc.

📎 message.txt
marble kayak
manic marsh
#

It shouldnt be. Its outside my server rack with i think an 8ft cable.

#

There a chance my dongle is dead?

manic marsh
#

@marble kayak sorry forgot to directly reply

marble kayak
#

Just trying to eliminate stuff. Randomly is odd.

manic marsh
#

At 12:02 this morning all my zigbee devices went unavailable. But if I logged onto mqtt (seperate vm) I was able to control all the lights just fine. There was just some weird auth issue that wasnt allowing HA to connect to Z2M. So I figured id just restore the zigbee VM to a know good state and now I get these errors when brining up the docker

manic marsh
marble kayak
#

My next try would be because you are identifying authorization issues, is look at the login from Z2M and MQTT, maybe change the password and login to a name that doesn't include the work mqtt and see if anything changes. Check that other things are happy with the MQTT broker to HA connection, that kind of thing.
Remote possibility is interference on the zigbee channel from a WIFI channel, but it doesn't sound like that to me.

manic marsh
#

I would like to update the auth stuff but I cant even get the docker to start.

manic marsh
# marble kayak My next try would be because you are identifying authorization issues, is look a...

So I decied to start fresh. And this is what I get now:

[2025-11-14 13:19:45] info:     z2m: Logging to console, file (filename: log.log)
[2025-11-14 13:19:45] info:     z2m: Starting Zigbee2MQTT version 2.6.2 (commit #4d247f3ae129ee7318eeede877ffdbbd27444693
)
[2025-11-14 13:19:45] info:     z2m: Starting zigbee-herdsman (6.1.5)
[2025-11-14 13:19:45] info:     zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"b0f41eb029afed11ba13374e71c9e8b5","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_b0f41eb029afed11ba13374e71c9e8b5-if00-port0","vendorId":"10c4","productId":"ea60"} => zstack: 4
[2025-11-14 13:19:45] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2025-11-14 13:19:45] info:     zh:zstack:znp: Serialport opened
[2025-11-14 13:20:02] info:     zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2025-11-14 13:20:02] info:     z2m: zigbee-herdsman started (reset)
[2025-11-14 13:20:02] info:     z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240710,"transportrev":2},"type":"ZStack3x0"}'
[2025-11-14 13:20:02] info:     z2m: Currently 0 devices are joined.
[2025-11-14 13:20:02] info:     z2m: Connecting to MQTT server at mqtt://localhost:1883
[2025-11-14 13:20:02] error:    z2m: MQTT failed to connect, exiting... ()
[2025-11-14 13:20:02] info:     z2m: Stopping zigbee-herdsman...
[2025-11-14 13:20:11] info:     zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2025-11-14 13:20:11] info:     zh:zstack:znp: closing
[2025-11-14 13:20:11] info:     zh:zstack:znp: Port closed
[2025-11-14 13:20:11] info:     z2m: Stopped zigbee-herdsman
#

I am beyond confused now. AM I supposed to have a seperate MQTT server on the host going? I never had one before.

#

nvm thats on HA

#

Im just a tard atm

marble kayak
#

Zigbee2mqtt talks to HA thru an MQTT server that is also connected to HA. It can be an add-on, a separate docker, native, or maybe even cloud (but don't do cloud) Broker. I believe there are other ways but that is the default and most used.

a seperate MQTT server
An MQTT broker (server) separate from the Z2M instance, yes, but the broker can my used by other things as well.

manic marsh
#

Okay well I set the ip to HA and Im back to the orignal errors. I am at a loss

# 
Onboarding page is available at http://0.0.0.0:8080/
[2025-11-14 13:42:10] info:     z2m: Logging to console, file (filename: log.log)
[2025-11-14 13:42:10] info:     z2m: Starting Zigbee2MQTT version 2.6.2 (commit #4d247f3ae129ee7318eeede877ffdbbd27444693
)
[2025-11-14 13:42:10] info:     z2m: Starting zigbee-herdsman (6.1.5)
[2025-11-14 13:42:10] info:     zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"b0f41eb029afed11ba13374e71c9e8b5","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_b0f41eb029afed11ba13374e71c9e8b5-if00-port0","vendorId":"10c4","productId":"ea60"} => zstack: 4
[2025-11-14 13:42:10] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2025-11-14 13:42:10] info:     zh:zstack:znp: Serialport opened
[2025-11-14 13:42:28] info:     zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2025-11-14 13:42:28] info:     z2m: zigbee-herdsman started (reset)
[2025-11-14 13:42:28] info:     z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240710,"transportrev":2},"type":"ZStack3x0"}'
[2025-11-14 13:42:28] info:     z2m: Currently 0 devices are joined.
[2025-11-14 13:42:28] info:     z2m: Connecting to MQTT server at mqtt://10.10.2.10:1883
[2025-11-14 13:42:29] error:    z2m: MQTT failed to connect, exiting... (Connection refused: Not authorized)
[2025-11-14 13:42:29] info:     z2m: Stopping zigbee-herdsman...
[2025-11-14 13:42:37] info:     zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2025-11-14 13:42:37] info:     zh:zstack:znp: closing
[2025-11-14 13:42:37] info:     zh:zstack:znp: Port closed
[2025-11-14 13:42:37] info:     z2m: Stopped zigbee-herdsman
iothub@iothub:~/Zigbee$
# 
services:
    zigbee2mqtt:
        container_name: zigbee2mqtt
        image: koenkk/zigbee2mqtt
        restart: unless-stopped
        volumes:
            - ./data:/app/data
            - /run/udev:/run/udev:ro
        ports:
            # Frontend port
            - 8080:8080
        environment:
            - TZ=America/Denver
        devices:
            # Make sure this matched your adapter location
            - /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_b0f41eb029afed11ba13374e71c9e8b5-if00-port0:/dev/ttyUSB0
# 
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://10.10.2.10:1883
  user: cyberhome
  password: redacted
serial:
  port: /dev/ttyUSB0
  adapter: zstack
  baudrate: 115200
  rtscts: false
advanced:
  log_level: info
  channel: 25
  network_key:
    - 163
    - 55
    - 248
    - 185
    - 127
    - 92
    - 117
    - 154
    - 208
    - 31
    - 204
    - 200
    - 72
    - 19
    - 245
    - 227
  pan_id: #
#

I think it all looks correct but IDK anymore

#

@marble kayak

#

Thats the brand new docker compose and everything. I can always restore from earlier when I first saw it broken if that will help.

marble kayak
#

So posting the network keys and the panID is like telling me your WIFI passwoed...
I don't know what's happening at this point. Out of ideas.

#

This doesn't seem to be your problem, but I spotted this:

port: /dev/ttyUSB0
Might want to use the long url with the by-id path if you have more than one dongle.

#

The TTY ports can sometimes change internally, so it is suggested to use the /serial/by-id/ URL that always talks to your dongle by serial so it is always right.
You can find out that that is by using:
https://my.home-assistant.io/redirect/hardware/

If you are using a Container installation, this is how to see the /serial/by-id/ URL:
ls -l /dev/serial/by-id

manic marsh
#

But I appreciate your help. Thank you for trying

marble kayak
manic marsh