My zigbee is now unstable, restarting every few minutes..... Its a SLZB-07

[vwkombi]

My home assistant life has seen me convert from tuya online stuff, to slowly replaced with ESPHome, and then slowly replaces with zigbee.

I have not added any new stuff for a while.

My latest fun in HA was finding out aboue this matter hub, and that I can connect my google home to all my HA stuff. I found out my vlans were blocking that (even though mdns etc was fine), so i resigned to moving my HA server to the IOT lan with the IOT things. Instantly the google home stuff started working… But I got a strange side affect - which could be a coincidence so I am looking for help.

My zigbee was crashing.

[2025-07-14 19:25:30] error:	zh:ember:uart:ash: Received frame with CRC error
[2025-07-14 19:26:04] error:	zh:ember:ezsp: ERROR Transaction failure; status=ASH_ERROR_TIMEOUTS. Last Frame: [FRAME: ID=52:SEND_UNICAST Seq=38 Len=7].
[2025-07-14 19:26:04] error:	zh:ember: Adapter fatal error: ASH_ERROR_TIMEOUTS
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: ASH COUNTERS since last clear:
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Total frames: RX=62, TX=103
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: DATA frames : RX=61, TX=40
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: DATA bytes : RX=872, TX=501
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Retry frames: RX=0, TX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: ACK frames : RX=0, TX=62
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: CRC errors : RX=1
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Comm errors : RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Length < minimum: RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Length > maximum: RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Bad controls : RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Bad lengths : RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Bad ACK numbers : RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Out of buffers : RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Retry dupes : RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Out of sequence : RX=0
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: ACK timeouts : RX=0
[2025-07-14 19:26:04] error:	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:SEND_UNICAST Seq=38 Len=7].
[2025-07-14 19:26:04] error:	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:SEND_UNICAST Seq=38 Len=7].
[2025-07-14 19:26:04] error:	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:SEND_UNICAST Seq=38 Len=7].
[2025-07-14 19:26:04] error:	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:SEND_UNICAST Seq=38 Len=7].
[2025-07-14 19:26:04] error:	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:SEND_UNICAST Seq=38 Len=7].
[2025-07-14 19:26:04] error:	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:SEND_UNICAST Seq=38 Len=7].
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: Port closed.
[2025-07-14 19:26:04] info:	zh:ember:uart:ash: ======== ASH stopped ========
[2025-07-14 19:26:04] info:	zh:ember:ezsp: ======== EZSP stopped ========
[2025-07-14 19:26:04] info:	zh:ember: ======== Ember Adapter Stopped ========
[2025-07-14 19:26:04] error:	z2m: Adapter disconnected, stopping
[2025-07-14 19:26:04] info:	z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/bridge/state’, payload ‘{state:offline}’
[2025-07-14 19:26:04] info:	z2m: Disconnecting from MQTT server
[2025-07-14 19:26:04] info:	z2m: Stopping zigbee-herdsman…
[2025-07-14 19:26:04] info:	z2m: Stopped zigbee-herdsman
[2025-07-14 19:26:04] info:	z2m: Stopped Zigbee2MQTT

Now I had not changed anything, but I did some gooling, moved USB ports, changed the extention cable, plugged direct in, restarted the host in between. No help. So I updated the firmware, also no help (I think it was the same anyway).

Version infos -

Starting Zigbee2MQTT without watchdog.
[2025-07-14 19:24:47] info: z2m: Logging to console, file (filename: log.log)
[2025-07-14 19:24:47] info: z2m: Starting Zigbee2MQTT version 2.5.1 (commit #unknown)
[2025-07-14 19:24:47] info: z2m: Starting zigbee-herdsman (4.3.1)
[2025-07-14 19:24:47] info: zh:ember: Using default stack config.
[2025-07-14 19:24:47] info: zh:ember: ======== Ember Adapter Starting ========
[2025-07-14 19:24:47] info: zh:ember:ezsp: ======== EZSP starting ========
[2025-07-14 19:24:47] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-07-14 19:24:47] info: zh:ember:uart:ash: Serial port opened
[2025-07-14 19:24:47] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-07-14 19:24:49] info: zh:ember:uart:ash: ======== ASH connected ========
[2025-07-14 19:24:49] info: zh:ember:uart:ash: ======== ASH started ========
[2025-07-14 19:24:49] info: zh:ember:ezsp: ======== EZSP started ========
[2025-07-14 19:24:49] info: zh:ember: Adapter EZSP protocol version (13) lower than Host. Switched.
[2025-07-14 19:24:49] info: zh:ember: Adapter version info: {“ezsp”:13,“revision”:“7.4.1 [GA]”,“build”:0,“major”:7,“minor”:4,“patch”:1,“special”:0,“type”:170}
[2025-07-14 19:24:49] info: zh:ember: [STACK STATUS] Network up.
[2025-07-14 19:24:49] info: zh:ember: [INIT TC] Adapter network matches config.
[2025-07-14 19:24:49] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast.
[2025-07-14 19:24:49] info: z2m: zigbee-herdsman started (resumed)
[2025-07-14 19:24:49] info: z2m: Coordinator firmware version: ‘{“meta”:{“build”:0,“ezsp”:13,“major”:7,“minor”:4,“patch”:1,“revision”:“7.4.1 [GA]”,“special”:0,“type”:170},“type”:“EmberZNet”}’

I have 32 zigbee devices, and some are more important that others, so I am not adverse to deleting it all and re-starting again - if that may help… Everyone has got used to the lights going on and off by thenselves, so this takes a bit to get used to to go back to the dark ages.

The watchdog only seems to keep it going a bit, then gives up, so it is down now, I can start it, but it will stop with a few minutes…

[francisp (Francis)]

Running on a Pi ? Using a USB2 port and not a USB3 port ? Checked for interference ?

[AlvaroHA]

Do you have any Zigbee device acting as repeaters? A healthy Zigbee network needs them.

@francisp question also, any USB or 2.4 wifi interference?

This is a great thread to start Zigbee network optimization: a how-to guide

[vwkombi]

Running on a dedicated n100 mini pc.
Using usb2, and cable extender. But tried others.
There is one repeater, but all plugs are routers also.
Note, this has all been fine for many months.
Just hit out of the blue (unless related to move to iot vlan, which does not seem related).

I have since started deleting devices to see if that helps so far not

[AlvaroHA]

I also started to have issues on my network after months of stability, so I think that is not always a sign for not having issues down the line.

Hardware wise seems you should be ok for a healthy network.

Without re-reading that post that I linked, the only other thing that I tweaked on my network after having issues was the channel. Scan your neighbourhood WiFi channels and choose a new Zigbee one depending on that.

Note: Seeing the logs you posted, may be a driver/firmware/MQTT configuration related issue. Check this for some background.

[mmstano (Matt Stano)]

I used nmcli to create a virtual interface on my Home Assistant machine so HAOS can send/receive traffic from both, LAN and IoT networks, and circumvent mDNS and AVAHI discovery issues. I only allow phones, personal tablets, and gaming consoles on my main LAN, while everything else sits in an IoT network (both use vlan). I didn’t want to allow firewall access from my IoT to LAN while my HA machine sits on the IoT network and even though I allow access for LAN to see IoT, mDNS and AVAHI discovery was extremely fickle. I tried setting up reflectors, but couldn’t get it to work. Doing the virtual interface was very easy to setup and I never have to worry about what device sits on what network for HA to discover or mess with my firewall to allow traffic or open ports between the networks. YMMV. The only other thing I had to do was define a different hostname to the IoT IP address for HA in the router. I also went the extra mile and setup CrowdSec and Firewall Bouncer add-ons for more security. More info here - Configuring VLAN adapters on Home Assistant Yellow - #5 by justynnuff