Zigbee2MQTT stops working daily since the 2025.8 update

Configuration Zigbee
,
1

Hi, I’m new to HA (since may 2025) and I’m using a slzb-06m zigbee coördinator together with zigbee2mqtt. I had it working fine, but since the new update the z2m constantly stops working on regulair basis (2-3 times a day). It helps to stopt to add-on and then turn in on again, but I did not had this problem before the update. Does somebody know how to fix this?

my config 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: false
mqtt:
server: mqtt://core-mosquitto:1883
user: xxxxxxxx
password: xxxxxxx
client_id: zigbee2mqtt-slzb06m
keepalive: 60
version: 5
serial:
port: tcp://192.168.68.70:6638
baudrate: 115200
adapter: ember
rtscts: false
disable_led: false
advanced:
log_level: info
transmit_power: 20
force_onboarding: false
watchdog: default

I use a slzb006-m. I connect it by WIFI and is set op zigbee coördinator.

2

I would start looking there. Using WIFI to pass crucial server data is not recommended.

1 Like
3

First question that comes up: what does the Zigbee2mqtt log say around the crash?

1 Like
4

Wifi is not best, and your network can cause coordinator loose connection. Best way is to use usb for power and LAN cable for network.

1 Like
5

It often shows the following:

error: z2m: Adapter disconnected, stopping
Or
error: zh:ember: Adapter fatal error: ERROR_SERIAL_INIT
error: zh:ember:uart:ash: Port Error: read ETIMEDOUT

6

I use HA on a virtual machine. Before the SLZB I used the sonoff dongle, which constantly failed due to the port being lost. That’s why I switched to WiFi, which didn’t showed problems until the update.

7

many reasons to this, if update bug cause this, more have trouble. look at log, this will give you info. and try with lan cable, then you see on same happen

1 Like
8

Look for any firmware upgrade to the slzb. They released a firmware update recently to address a lockup on the device which caused zigbee2mqtt to crash.

That being said, after the update I still get lockups and the way to restore it is to restart the zigbee coordinator (don’t need to restart the whole slzb device) and then start back zigbee2mqtt.

I actually created an automation to monitor zigbee2mqtt and if it goes down to do those 2 tasks and notify me.

1 Like
9

Add comment to the Z2M issue on github: Z2M stops working · Issue #28402 · Koenkk/zigbee2mqtt · GitHub . Even if the root cause would be in SLZB, Z2M should restart instead of stopping, as that solves it.

10

Did you enable the watchdog ?

image
image659×391 3.65 KB

1 Like
11

I got watchdog enabled with default settings. In the logs I see that it also reboot by watchdog sometimes. However, I also noticed that some devices turned to unavailable. I got the newest version of the slzb and I rebooted it a few times by cutting the power on and off. I will try it now with de reboot buttong.

I made a few days ago also an automation which turns of the z2m, reboots the slzb and turns back on the z2m. however, even then it does not always works afterwards

12

For wifi I use a TP-link Deco, which is connected to my router. I have the slzb connected by wifi to the TP-link deco. I have the IP reserved on the deco.
I also just noticed that some devices don’t work, I have an aqara W100 and it does not recognize buttons being pushed. However, other devices do work, like the Philips hue remote.

13

I did a factory reset on the slzb, reconected every device (not by forgetting the device, but by setting the device in pairing mode) and I had to manually change the settings of every device again. It works for now. Most of the problems are gone.

Z2M stops multiple times a day, but it restarts immediately. I changed to ethernet as recommended by someone above.