SLZB-06 freezing every few days

[Dinth]

Hi. Recently i have migrated from ZBDongle-P to SLZB-06 (powered over PoE) and while it works great when it works, every few days SLZB-06 is completely freezing and the whole mesh goes down.
Zigbee2MQTT log only shows this:

Zigbee2MQTT:warn  2024-02-02 09:00:01: Failed to ping 'Baby room uplight' (attempt 1/1, Read 0x0017880108aca49e/11 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
Zigbee2MQTT:warn  2024-02-02 09:00:12: Failed to ping 'Shed floodlight' (attempt 1/1, Read 0x04cd15fffeddcf9c/11 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
Zigbee2MQTT:warn  2024-02-02 09:00:23: Failed to ping 'Zigbee repeater first floor' (attempt 1/1, Read 0x00124b002447f894/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
Zigbee2MQTT:warn  2024-02-02 09:00:34: Failed to ping 'Private office CRT screen' (attempt 1/1, Read 0x0c4314fffef7a0e7/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
Zigbee2MQTT:warn  2024-02-02 09:00:45: Failed to ping 'Landing cabinets light 3' (attempt 1/1, Read 0x385b44fffe0c4a11/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
Zigbee2MQTT:warn  2024-02-02 09:00:56: Failed to ping 'Master bedroom light 2' (attempt 1/1, Read 0x842e14fffe125b08/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
Zigbee2MQTT:warn  2024-02-02 09:01:07: Failed to ping 'Zigbee repeater ground floor' (attempt 1/1, Read 0x00124b002447f8d4/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))

If i now restart Z2M im getting:

[09:07:29] INFO: Preparing to start...
[09:07:29] INFO: Socat not enabled
[09:07:30] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:error 2024-02-02 09:07:52: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-02-02 09:07:52: Failed to start zigbee
Zigbee2MQTT:error 2024-02-02 09:07:52: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-02-02 09:07:52: Exiting...
Zigbee2MQTT:error 2024-02-02 09:07:52: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
    at Zigbee.start (/app/lib/zigbee.ts:60:27)
    at Controller.start (/app/lib/controller.ts:106:27)
    at start (/app/index.js:107:5)

On the SLZB-06 side there's nothing suspicious - normal temperatures, everything seems to work except no connected client:

setup | start
L_Y,L_B | status: 1
ConfigHelper | load config
ConfigHelper | config open: Ok
setup | Config loaded
setup | Device type: SLZB-06
[ZBCHK] | Connection OK
Network | init
Network | EVENT_ETH_START
Network | EVENT_ETH_CONNECTED
Network | ETH init: OK
setup | Filesystem size: 3456
setup | Filesystem used: 368
setup | done
Network | [MDNS] Started
Network | EVENT_ETH_GOT_IP
Network | ETH MAC: D4:8A:FC:A1:DF:6F IPv4: 10.10.25.10 GW: 10.10.0.1 Speed: 100Mbps DNS1: 10.10.0.1 DNS2: 0.0.0.0
taskZB | [taskZB] Starting server on port: 6638
Network | fireNetworkUp
Web | Webserver started
time | time sync start
internet | connected
time | timezone: GMT0BST,M3.5.0/1,M10.5.0
time | Wednesday, January 31 2024 17:00:47
taskTimeSync | Heap: 1448
stats | Statistics sent
stats | Heap: 2436
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
taskZB | New client
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
taskZB | New client
taskZB | Client disconnected
Network | EVENT: 0
Network | EVENT: 2
Network | EVENT: 3
taskZB | New client

Seems that Z2M is trying to connect but the connection drops.

My Z2M config is as follows:

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: {}
serial:
  port: tcp://10.10.25.10:6638
  baudrate: 115200
  adapter: zstack
  disable_led: false
advanced:
  transmit_power: 20

When this happens i need to completely restart ESP32 and Zigbee stack via the SLZB-06 web panel. SLZB-06 is running on the latest firmware v2.0.16 / 20230507

[Dinth]

It may be related to #18192

[Dabbadoeber]

I stumbled open this thread, since a couple of days I got the same problem.... hopefully there is a fix soon. For me only power cycling the stick will bring the network back.

[Dabbadoeber]

I have connected ZHA to the same dongle:
Socket connected: | Yes, 2 client
Trying to check if the problem occurs on Z2M and ZHA then i should be related to the SLZB-06 dongle.
Maybe power issues ?

i used this guide to do so:

https://smarthomescene.com/guides/how-to-use-zigbee2mqtt-and-zha-with-a-single-coordinator/

[Dabbadoeber]

Problem is defently with the SLZB-06 as Both ZHA and Z2m dont have a connection anymore.

[Dinth]

After a month of suffering pain of instable/dead Zigbee mesh i have a few things to add:

1. I have tried both PoE and USB-C power and there is no difference - so the problem doesnt seem to be related to power.
2. Approx 2 times in 3 its still not possible to connect to the Zigbee gateway after restarting it, so often i need to restart it a couple of times before Z2M/ZHA can connect to it.
3. I have tried to export radio to ZHA and the problem exists in ZHA but feels little bit different. In Z2M i am noticing errors and devices dropping off gradually before the adapter freezes, but i believe ZHA was running rock stable until the moment the adapter freezes.
4. SMLight support before they have stopped responding to my emails suggested that the problem may be in the adapter and/or Z2M not able to handle some of the errors in my Zigbee mesh. I have tried switching the power off for an hour from all the devices and i have removed some dodgy routers from my mesh. It may be a coincidence, but after each of those actions the adapter was indeed working for considerably longer before freezing. Unfortunately after a freeze and next restart of the adapter everything went back to normal, that means adapter freezing quite often.

[Dabbadoeber]

I am only using Busch jeager switch on my network, i have splitted the network in my House into 3 parts.
this is because the busch jeager cannot handle to much devices.
If the Coordinator becomes onresponsive the BJ ZLL Switch still work, that is, switches that i have "bind" are still operational.
accept that no information is send to Z2M/Home assitant
i still have a usb dongle think these SLZB-6 crap wil go on e-Bay /Markplaats.

[tomtom13]

It's funny how SMLight give that excuse, while whole internet doesn't seem to go down just because one person plugged in a dodgy router / server. When my light bulb burns down whole city doesn't loose electricity because of that.
From the whole thread and people interaction with their "support" I think they effed up, but they have the "rockstar programmers" that can do no wrong and they put blame on everything else and their marketing is now on charm offence.

[Dabbadoeber]

I have created a new Zigbee2mqtt container on my Qnap en moved over everything (configuration.yaml, coordinator.json)
Also downgrade the SLZB-6 to version v0.9.9
and started, until now it seems ok (hopefully it wil keep running)

[Dinth]

Could you please keep us updated? I will also try flashing it next time my adapter freezes, but maybe i am going to try coordinator firmware?

[Dinth]

Also have you flashed 0.9.9 via the UI?
I can flash the older 2.0.17, but when trying 0.9.9 im getting OTA write error.

[Dabbadoeber]

i did flash it trough the ota.

I thought i had it running for a while, but in the night it stopped again.......
I only have 13 devices on this network, I just finished pairing them all to a USB SONOFF Zigbee 3.0 USB Dongle Plus-P.
I don’t like this because its running in a docker container on a Qnap nas, I don’t know if the link to port: /dev/ttyUSB0 will remain after reboot or something.
The pairing only took me about 1 hour.
Did save the database and configuration.yaml (only for the devices) and used this on the new network.
I didn’t had to remove cover or anything to pair the switches again.
So it was the most convenient way to go for me.
Did order a Zigstart UZG so maybe this will be better.

For now No more SLZB-6 for me.

[Dabbadoeber]

I did the transition to the sonoff dongle, but still Z2M Freezes (but not as much, and restarting docker fixes it) , zo maybe it is Z2m After all, going back to : koenkk/zigbee2mqtt:1.34.0
see if this runs stable.

[Dinth]

What is your hardware? I've been googling the errors im seeing and i have seen one post somewhere where a person was suggesting that this may be due to low disk write/read speeds and that replacing his drive (where the Z2M container was running from) to SSD has fixed those issues.
Although this doesnt explain why ZHA is also affected...

[Dinth]

Just got SNZB-06M today which has a completely different Zigbee chip and will be testing it.

On the other hand, i found something what may be helpful with such faulty SNZB-06 as i had before - apparently it can be flashed with ESPHome and still run as a Zigbee coordinator (its actually burried on their wiki) but on a completely different firmware.

[Dinth]

And SNZM-06M is still experiencing the same issue, a different device on a different chip (TI one).

[Dabbadoeber]

Hi back after a whille, i downgrade Z2M to [1.34.0] it has been running for a week with out issues (sonoff dongle)
today i changed everything to a UZG-01 , where i Write the IEEE from the dongle onto the UZG-01.
so i dont need to pair al devices again.

Hardware @ the moment is a Qnap NAS TVS-H874X, so this should not be a problem i think
is is a hassle with usb though, so thats why i preffer a LAN Coordinator.

[Dabbadoeber]

Pfff 100 devices , i only have 13 on this nework , split my home in 3 diffrent networks because of issues with slow ZLL devices, to much zigbee traffic made them freeze.
maybe switch on debug log in Z2M too see wich devices spams the network

[ViggoGaming]

Hi back after a whille, i downgrade Z2M to [1.34.0] it has been running for a week with out issues (sonoff dongle)

today i changed everything to a UZG-01 , where i Write the IEEE from the dongle onto the UZG-01.

so i dont need to pair al devices again.

Hardware @ the moment is a Qnap NAS TVS-H874X, so this should not be a problem i think

is is a hassle with usb though, so thats why i preffer a LAN Coordinator.

Hey. Do you mind sharing how you downgraded Z2M to version 1.34.0?

[dbroome1978]

It might be fixed on the next release.
See
#21462 (comment)

[Dinth]

Thanks, it has crashed again for me today.
I dont think its actually caused by one of the devices chattering/Zigbee being overloaded - once it happens Z2M stops receiving any messages from the mesh.

[Dabbadoeber]

I am using docker (Container station) so i recreated the image, and instead of the :latest tag is used :1.34.0
must say after HASS update i had some trouble (could not communicate with MQTT server) but since i updated this everyhing has been quite stable

[mremedi2023]

Same here, my lan zigbee is down

[guzmanregueiro]

I have the same problem. Every 3/4 hours it freezes

[Dinth]

@mremedi2023 @guzmanregueiro Have you tried the latest firmware (20240710) ?

[guzmanregueiro]

Yes. And now 20240716

[mremedi2023]

Yes

[Matriciel]

Hi,
Where are you find the firmware ?

[nonamejuju]

I have the same problem here. The SLEB-06 was rock solid for the past few months, but now Z2mqtt can't connect to it every few days. A hard reboot of the dongle fix it. Dongle connected in Ethernet with USB power. Maybe a new update of Home assistant changed something ?

[Dinth]

Which versions are you using (particularly Z2M and firmware)?
I had the problem since i migrated to PoE coordinators (back in January), Z2M update to 1.39.0 made it much worse, and then the latest firmware 20240710 fixed it.
HA is most definetely not a problem here, it wouldnt cause your coordinator to freeze.

I remember seeing some comments in the past connecting this issue to a slow disk i/o on Z2M host, so send us your spec please

Also if nothing else helps, i also remember seeing some comments from user who fixed that issue by downgrading Z2M to a really old version (1.34 maybe?), but dont remember specifically which one

[nonamejuju]

For SLZB-06 :

• Core firmware version: v2.5.0
• Zigbee Coordinator Revision: 20240710

Zigbee2MQTT :

• Current version: 1.39.1-1

Home Assistant:

• Core 2024.8.2
• Supervisor 2024.08.0
• Operating System 13.1
• Frontend 20240809.0

Running on a BMAX B4 Plus Mini PC Intel N100 16GB 512GB SSD, with promox, the coordinator is behind an ethernet switch, and I'm running in parallel ZHA with a Sonoff ZBDongle-E connected directly in USB for the talky devices. I will investigate the logs and try different config and testing things and report back.

[Dinth]

ok, ssd this rules out slow disk i/o.
I would first try reverting Z2M back to 1.38

[foufoutos21]

I have two controllers SLZB-06 and I was quite happy with their performance for the last months.
Lately I have a lot of strange errors and freezes of the whole MQTT structure. I'm using 3 coordinators in a multistorey building as the only workable solution. One usb coordinator connected to Home assistant pc (a FUTRO thin client with 4GB ram and 256GB mSATA SSD) and the two SLZB-06 via POE LAN.
First observation was the broken web interface of the devices.
Then SSE errors during connection to the web interfaces, then noticed freeze of Z2M instances. Lately is not accessible at all and collapse of my Home automation system.
SLZB-06 are not reliable, are not stable and they are not offering any kind of support.
I have try any possible firmware available in their web flasher, any combination of zigbee firmware but in vain!

Zigbee2 MQTT version 1.39.1-1 Home Assistant Core 2024.8.2 on 13.1 OS
SLZB-06 with 0.99 and 2.5.0 /2.3.6 core frmware, unsure what zigbee firmware is running as I'm testing everything is available.
Frustrated and disappointed!
Any assistance is welcomed

[nonamejuju]

For SLZB-06 :

• Core firmware version: v2.5.0
• Zigbee Coordinator Revision: 20240710

Zigbee2MQTT :

• Current version: 1.39.1-1

Home Assistant:

• Core 2024.8.2
• Supervisor 2024.08.0
• Operating System 13.1
• Frontend 20240809.0

Running on a BMAX B4 Plus Mini PC Intel N100 16GB 512GB SSD, with promox, the coordinator is behind an ethernet switch, and I'm running in parallel ZHA with a Sonoff ZBDongle-E connected directly in USB for the talky devices. I will investigate the logs and try different config and testing things and report back.

All right after a month I don't have any problem.

I have moved it to another location, next to my Sonoff ZBDongle-E and Wi-Fi router. On paper, it's a worse location than the previous one (which was in the middle of the house), but there have been no more disconnections or freezes since. I also updated to the latest Z2MQTT version that was released. It's worth noting that the SLZB-06 is now connected directly to my main Wi-Fi router via Ethernet, instead of being behind a switch. Hope this help someone !

[mremedi2023]

Same here, I keep having problems, definitely Zigbee technology is not stable, much less user-friendly, with more than 70 devices, I am about to move everything to WiFi as I had before and without problems. El dom, 25 ago 2024 a la(s) 2:41 p.m., foufoutos21 ***@***.***) escribió:

…

I have two controllers SLZB-06 and I was quite happy with their performance for the last months. Lately I have a lot of strange errors and freezes of the whole MQTT structure. I'm using 3 coordinators in a multistorey building as the only workable solution. One usb coordinator connected to Home assistant pc (a FUTRO thin client with 4GB ram and 256GB mSATA SSD) and the two SLZB-06 via POE LAN. First observation was the broken web interface of the devices. Then SSE errors during connection to the web interfaces, then noticed freeze of Z2M instances. Lately is not accessible at all and collapse of my Home automation system. SLZB-06 are not reliable, are not stable and they are not offering any kind of support. I have try any possible firmware available in their web flasher, any combination of zigbee firmware but in vain! Zigbee2 MQTT version 1.39.1-1 Home Assistant Core 2024.8.2 on 13.1 OS SLZB-06 with 0.99 and 2.5.0 /2.3.6 core frmware, unsure what zigbee firmware is running as I'm testing everything is available. Frustrated and disappointed! Any assistance is welcomed — Reply to this email directly, view it on GitHub <#21157 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BENWU6TMBYDBYDFX4XQLVX3ZTIJLZAVCNFSM6AAAAABCWKS5AKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANBUGQYTIMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[foufoutos21]

I can spot the culprit in my setup but my third coordinator is a usb sonoff stick with z2m same as others (1.39.1-1) and it's rock solid.
My next step is such controller in raspberry pi with POE or (maybe) I'll give a try to ZigStar UZG-01.

[Blackduke77]

Wonderful, I have been having the same issues, and from this thread, we are not going to get to the bottom of it. Has anyone tested a working alternative

[Blackduke77]

I am going to try and go back to firmware 20240315

[joelegg]

Has anybody had any luck running the slz b06 with zha? Tempted to move over there to see if that works. The xzg-01 also crashed for me.

[TheDescender]

I have the default SLZB-06 and it has actually worked stable with ZHA for couple months now. The ZHA mapping shows some end-devices dopped sometime, but they still work through their bind, so in practice its stable. Using Z2M network crashes within days.

Idk how people have been saying their SLZB or UZG-01 are stable with Z2M, i've only experienced pain, suffering and sleepless nights.

[joelegg]

Interesting. I just sent automation to reset z2m twice a day to see if that lets it run longer.

[habitats-tech]

Idk how people have been saying their SLZB or UZG-01 are stable with Z2M, i've only experienced pain, suffering and sleepless nights.

This is the billion dollar question each one of us has. I am trying to understand the issue, from own testing and feedback from others, so we can all hopefully get an understanding of what is causing such behaviour.

[habitats-tech]

In case you want to follow my experiments and provide feedback, at present I have the below running with no issues. If you want to contribute with either feedback or devices you can donate for testing feel free to connect.

HW: SLZB-06, SLZB-06P7, SLZB-06M, UZG-01 (PoE coordinator mode)
SW: Latest Mosquitto MQTT broker running in LXC in Proxmox VE 8.x (always latest)
SW: Latest Z2M (2.1.1) running in LXC in Proxmox VE 8.x (always latest)
SW: Latest ZHA in HAOS running in KVM in Proxmox VE 8.x (always latest)

HW ZB Device vendors: SONOFF, Tuya

[rouke-broersma]

In case you want to follow my experiments and provide feedback, at present I have the below running with no issues. If you want to contribute with either feedback or devices you can donate for testing feel free to connect.

HW: SLZB-06, SLZB-06P7, SLZB-06M, UZG-01 (PoE coordinator mode)
SW: Latest Mosquitto MQTT broker running in LXC in Proxmox VE 8.x (always latest)
SW: Latest Z2M (2.1.1) running in LXC in Proxmox VE 8.x (always latest)
SW: Latest ZHA in HAOS running in KVM in Proxmox VE 8.x (always latest)

HW ZB Device vendors: SONOFF, Tuya

I have zero issues with sonoff temp sensors, some tuya and hue lights. When I add sonoff trvzb everything shits the bed. Currently just don't have the trv's connected 🫠

[tammeryousef1006]

i already ordered SLZB-06 , this topic here kinda scares me , should i cancel it or continue with it ? bearing in mind im a user of z2m and have sonoff dongle working perfectly , but i wanted SLZB-06 to use as central zigbee standalone that provides zha and z2m , i got 54 zigbee devices

[gabeszakem]

I have changed back my device ti sonoff dongle. I only suffered with Slzb-06p7. Alwayes freezed or just stopped, I have tested as coordinator and router with many kind of variation firmwares, but nothing positive feedback. Now I use again my sonof dongle for months without any problem.
If i could, i never buy slzb.

[tomtom13]

Just keep the order and get your self something else as well just in case. But don't get under illusion like I did that other versions of slzb will be faultless if 06 is crashing.
This however depends on your budget.

I shall add that it's funny that zigbee was supposed to be cheap IOT automation magic, yet is turns out that people are spending pretty penny and solid chunk of time on implementing the redundancies and solving manufacturer issues just to get basic stability. But don't get strange ideas that land of wifi automation is any better - people that got on that band wagon are now fighting with having devices that don't support WPA3, and to have wifi 7 (AX) you are required to have WPA3, while their network is supper busy with devices talking over each other making everything crawl to a halt ... fun, right ?

[tomtom13]

I have changed back my device ti sonoff dongle. I only suffered with Slzb-06p7. Alwayes freezed or just stopped, I have tested as coordinator and router with many kind of variation firmwares, but nothing positive feedback. Now I use again my sonof dongle for months without any problem. If i could, i never buy slzb.

What makes that situation even worse is that one can't flog it on ebay since it won't work for other leading to battle where buyer will claim that hardware is faulty since it's crashing. FUN ;)

[tammeryousef1006]

I have changed back my device ti sonoff dongle. I only suffered with Slzb-06p7. Alwayes freezed or just stopped, I have tested as coordinator and router with many kind of variation firmwares, but nothing positive feedback. Now I use again my sonof dongle for months without any problem. If i could, i never buy slzb.

isnt there firmware fixes ? is the issue remain with few devices too or if over than 30 devices ?

[tomtom13]

isnt there firmware fixes ? is the issue remain with few devices too or if over than 30 devices ?
I gave up 3 or 4 weeks ago. UZG been running perfectly since then with 172 devices.

Why would one care if the issue is absent with 30 devices ? you just invite problems later on. If wheels on your car fall off at 100mph, will you still drive it in the city at 30mph ? Maybe just to get by until you find something reliable but defo not purchasing that car in the first place. Zigbee was designed to work with tens of thousands of devices - that's where the "MESH" comes in place.

BTW. anybody want some scrap bits ?

(just joking I'll check in an year if this thread is resolved or when UZG shi** the bed)

[tomtom13]

I find it very particular that since a certain person related to "the industry" came here and started praising how fantastic SLZB is for them without a fault and getting into personal insults contest - right after that a myriad of people shown up praising how great the SLZB is. I find it extra peculiar, since one has to have that device -> be so satisfied with it to start searching specifically for it crashing -> go on GH and add their reply specifically to that thread within the issue on how the device is faultless and they never had a problem with it.

[tammeryousef1006]

@tomtom13 @gabeszakem many thanks for reply , is there any such device that can be zigbee lan-ethernet and much stable with z2m ?

[tomtom13]

I had luck with UZG-01, but some report having issue with it. This threat is confusing enough for one to think that some marketing department is false reporting on uzg ... but my advice would be to keep your old usb dongle and workout a quick switch over procedures. I now have several configs in notepad, backup files etc to shuffle between stuff. Something that I really really really don't fancy but I didn't have a choice but to do.

[sphings79]

I also have a Zigstar UZG 01 running. Much better than SLZB

[Matriciel]

I have a SLZB-06P7 and 48 modules without problems for several weeks.
Currently, it has been working without problems for more than 9 days.
However, I do not use HA but only Z2M with Jeedom (in France).

[Matriciel]

Latest stable: 2.7.1 for core and 20240716 for Zigbee

[WhimsySpoon]

Same. I've had two weeks of stability since installing 2.7.1 / 20240716 on a P7 using z2m.

[drjjr2]

Yesterday I checked the web UI to see how long my system had been running (20 days). Then last night I noticed devices not working. Reset the ESP32 and Zigbee and now it's working again. 2.7.1 running 20240716 on SLZB-06P7

[tomtom13]

I had p7 and p10 crash within hours with 2.7.1, but my network had 171 items in it. After which I gave up with slzb. Bare in mind that small networks allow direct to coordinator connections, without hops through intermediary router (a lightbulb for example), which may mask or postpone some issues.

[WhimsySpoon]

About an hour after my post above, my network crashed and I had to power cycle the dongle.

[joelegg]

Well I just setup Sky connect with Z2M. Re pair took 30 mins (60+ devices saved config so it was quick ). Up for 24 hours. Please let it stay online now

Maybe a future version of the slb will be more stable

[WhimsySpoon]

I may have discovered something important with the crashing on my P7:

tl;dr: removing a router from the network causes it to crash after a few hours.

Detail:

A few days ago, I commented that my network had been stable for weeks. Shortly after posting that comment, I disconnect an illuminated mirror controlled by a Sonoff ZBMINI relay from a bathroom that was about to be remodelled. I didn't mark it as disabled in Z2M. nor did I remove it from the network first (as it would eventually be reinstalled). A few hours later, I had to post this comment because my network had crashed and I had to power cycle my P7.

Yesterday, I installed a brand new Sonoff ZBMINIR2 and joined it to my network. I did this at around 1300hrs. It spent most of the day on the network (long enough for it to become established in routes), but I isolated the power to it at ~2200hrs before going to bed.

This morning at ~0600, the house was in darkness and none of my lights were responding; the network had again crashed.

Unfortunately, I didn't have time to grab any logs before I restarted the network.

These were two similar (but not identical) Sonoff router devices, but I'm more inclined to think that the removal of a router device itself is causing the collapse and crash.

I'm going to isolate the power to the new device again at the same time tonight and hope that it does it again. This time, I'll be prepared to grab logs in the morning.

[tomtom13]

This might be a factor but I have a floor lamp that constantly is being switched ON and OFF (power wise), and I was unable to find a correlation. I've made sure that it remains connected to the power all the time and it had no effect on slzb crashing. After switching away from slzb I've relaxed by gestapo stance on it never being touched by users and networks is still stable.

[WhimsySpoon]

Correction, I do have the logs.

Things looked fine until 0536, then every device started firing:

failed (SRSP - AF - dataRequest after 6000ms))

There was a failed (Data request failed with error: 'MAC no ack' (233))) four minutes earlier for the new device that I'd taken offline.

The SRSP error is listed on the z2m documentation states:

If after some uptime Zigbee2MQTT crashes with errors like: SRSP - AF - dataRequest after 6000ms or SRSP - ZDO - mgmtPermitJoinReq after 6000ms it means the adapter has crashed.

[techie-dreamer]

I

Correction, I do have the logs.

Things looked fine until 0536, then every device started firing:

failed (SRSP - AF - dataRequest after 6000ms))

There was a failed (Data request failed with error: 'MAC no ack' (233))) four minutes earlier for the new device that I'd taken offline.

The SRSP error is listed on the z2m documentation states:

If after some uptime Zigbee2MQTT crashes with errors like: SRSP - AF - dataRequest after 6000ms or SRSP - ZDO - mgmtPermitJoinReq after 6000ms it means the adapter has crashed.

I believe I have the same issue.
This has been long running & things seemed to improve after removing 'chatty devices', now I've got only devices which behave & over last 48 hours the adapter seems to crash every 12-24 hours. Power cycling the adapter corrects the problem (have got watchdog enabled in z2mqtt too).

Here's a snippet of logs when everything went unresponsive form z2mqtt:

2025-03-01 08:41:44] �[32minfo�[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Dimmer.Kitchen.DiningPendant","ieee_address":"0xf4b3b1fffef5f8e8"},"type":"device_announce"}'
[2025-03-01 08:41:44] �[32minfo�[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Dimmer.Kitchen.DiningPendant","ieee_address":"0xf4b3b1fffef5f8e8"},"type":"device_announce"}'
[2025-03-01 08:41:45] �[32minfo�[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Dimmer.Kitchen.IslandPendant","ieee_address":"0xf4b3b1fffedc08db"},"type":"device_announce"}'
[2025-03-01 08:41:51] �[31merror�[39m: 	z2m: Failed to read state of 'Dimmer.Kitchen.DiningWall' after reconnect (ZCL command 0xf4b3b1fffef5f8cb/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
[2025-03-01 08:41:57] �[31merror�[39m: 	z2m: Failed to read state of 'Dimmer.Landing.Kids' after reconnect (ZCL command 0xf4b3b1fffecf0673/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
[2025-03-01 08:42:03] �[31merror�[39m: 	z2m: Failed to read state of 'Dimmer.Kitchen.DiningCeiling' after reconnect (ZCL command 0xf4b3b1fffef5fc6b/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
[2025-03-01 08:42:09] �[31merror�[39m: 	z2m: Failed to read state of 'LightBulb.Bathroom.Main.LED2' after reconnect (ZCL command 0x001788010c32eaad/11 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
[2025-03-01 08:42:15] �[31merror�[39m: 	z2m: Failed to read state of 'Dimmer.Kitchen.IslandPendant' after reconnect (ZCL command 0xf4b3b1fffedc08db/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
[2025-03-01 08:42:15] �[32minfo�[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/PIR.Stairs.58', payload '{"battery":97,"device_temperature":21,"illuminance":77,"linkquality":87,"occupancy":false,"power_outage_count":8,"voltage":2995}'
[2025-03-01 08:42:21] �[31merror�[39m: 	z2m: Failed to read state of 'Dimmer.Kitchen.DiningPendant' after reconnect (ZCL command 0xf4b3b1fffef5f8e8/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - UTIL - assocGetWithAddress after 6000ms))
[2025-03-01 08:42:33] �[31merror�[39m: 	z2m: Failed to read state of 'Dimmer.Kitchen.DiningPendant' after reconnect (ZCL command 0xf4b3b1fffef5f8e8/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
[2025-03-01 08:42:40] �[32minfo�[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/VibrationSensor.LoftFront.15', payload '{"angle":52,"angle_x":1,"angle_x_absolute":89,"angle_y":39,"angle_y_absolute":51,"angle_z":51,"battery":63,"device_temperature":10,"linkquality":83,"power_outage_count":30,"sensitivity":null,"strength":12,"vibration":false,"voltage":2945,"x_axis":25,"y_axis":803,"z_axis":1005}'
[2025-03-01 08:42:44] �[32minfo�[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Dimmer.Kitchen.DiningCeiling","ieee_address":"0xf4b3b1fffef5fc6b"},"type":"device_announce"}'
[2025-03-01 08:42:44] �[32minfo�[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Dimmer.Kitchen.DiningCeiling","ieee_address":"0xf4b3b1fffef5fc6b"},"type":"device_announce"}'

Here's the set-up:
smlight Adapter: SLZB-06
smlight Core Firmware: v2.7.1
smlight Zigbee Firmware: 20221226
Zigbee2MQTT: 2.1.1-1
HA Core: 2025.2.5
HA Supervisor 2025.02.4
HA Operating System 14.2

[andregoncalvespires]

Do you really want a solution? Be careful when choosing the devices you add to your network. Remove all devices that generate spam, or put them on a smaller dedicated network. MMWAVE and Tuya energy monitors are network busters.

For ember driver, use https://nerivec.github.io/z2m-ember-helper/#stats to analyze which devices are causing problems.

My network is stable with SLZB06M since fw 2.7.1 and even now with 2.8 dev.

[tomtom13]

Yeah, but I had plenty of those "chatty devices" like tuya power sockets on sonoff usb dongle ... network was stable, and if the device decided to be extra naughty it would crash out of network. I switched to SLZB and it was working OK for quite some time, but then firmwares became rotten and I couldn't find a right combination of zigbee and esp32 firmware through downgrades. Now I have 5 devices that produce a message every 2 seconds and everything runs smooth. Users should not be forced to create competing networks when zigbee standard allows that messaging frequency.

[sndrod]

Hoping that someone can help.

I successfully set up a second coordinator (SLZB-6M). I then moved all my lights to the coordinator from Netatmo.

Then I restarted both Z2Ms and then they BOTH only show the lights on one of the SLZBs - of where there are only 2. Meaning I have lost connection to 50 light switches, worth about $5k. Because they think they are connected to the SLZB, they now cannot be found by the Netatmo device either.

I have checked Z2m>Settings>about and they have difference IEE addresses for each of the Z2M instances in HA

All the devices have gone from MQTT.

I have tried turning all the lights off at the main power and that does not help. THe devices are not found when power comes back on, even when join is set. I have also unplugged the SLZB and reconnected and that made no difference.

I restored a backup from HA from when they did work and that made no difference.

Also when I do join on Z2M it also does not find the devices that were on the SLZB, however all the green pairling lights on the 50 switches turn green - showing that the SLZB is somehow talking to these devices.

In the RAW Json file of Z2M, I can see the devices are in there, they are just not on the front UI or talking to MQTT

Can anyone suggest anything?

many thanks

[sndrod]

I have now restored most of the devices by stopping both Z2M instances before copying over the DB from a backup, then starting them one by one. I assume that by copying over the DB whilst one was still running, the DB in memory from the other Z2M instance was overwriting it.

However, I have not been able to restore the two devices in the garage, as these were not in the old DB file, and the two other devices. They are also not found anywhere in the TAR files from the backup.

The weird thing is that if I click on "permit join" these devices do light up in pairing mode, so they are somehow known by SLZB. Now, when I do "permit Join" these devices do not show up, even though clicking "permit join" puts them into pairing mode. Still does not work even if they are power cycled etc..

I have another device that is successfully interviewed but then immediately leaves the network.

All these devices are of the same type (light switches) and it is not possible to factory reset these devices.

Two questions:

1. Do you have any thoughts on how to reconnect the devices that the SLZB cannot find?

2. Should the two coordinators share the same .db under the homeassistant/zibee2mqtt folder, and otherwise how do you know what is connected to each Z2M instance and SLZB?

Many thanks

Dan

[sndrod]

I was thinking it might be possible to copy an entry into the db, as I know the IEEE address, but I do not know the nwkAddr. The coordinator must know this somehow because it turns the lights green when I press on join. But I do not know how to find that out...

[rouke-broersma]

Should the two coordinators share the same .db under the homeassistant/zibee2mqtt folder, and otherwise how do you know what is connected to each Z2M instance and SLZB?

???? I don't know what you're trying to do but whatever it is, stop trying to do it. You cannot share anything between two coordinators. They must form distinct networks, they must have their own z2m instances with their own databases with their own root folders. They must have their own mqtt topics. You can't connect a device to both. You can't share the database from one to the other.

[sndrod]

I am trying to add an entry in the Z2M database for one device, for which I know the IEEE address, but not the nwkAddr

[sndrod]

The reason my nightmare started was because the two coordinators were sharing a DB. They have to have different paths within configuration. This wasn't pointed out in the set up videos I used, and your comment got me thinking and trying that out.... so now it is working perfectly. Two SLZB-06m coordinators in two different parts of the property working perfectly on Z2M!

All good, and thanks very much for your help.

[hqsone]

Same problem, SLZB-06P7. Please, tell, how I can find "spamming" devices? I have a lot different models of smart plugs with energy monitoring for example.

[Coldness00]

You can check the logs in info mode.
Or you can also see on map if the a device is quickly flashing.

[Coldness00]

I switched to the latest dev version and activated in Network Tab: Disable mDNS.
Since then all good on my side

[kbonnel]

Good to know. I was still having a lot of issues with "ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT" errors, which seemed to be due to potential timeouts with the adapter and z2m. That seemed to be fixed with an updated zigbee firmware that had a high buffer setting, but it didn't seem to make a difference on my 06m.

I am now testing my USB sonoff zdongle-e dongle and so far am not getting those errors. Been running ok for 3 days so far.

[mballoni]

Hi!
Still good without mDNS after these past two weeks?

[Coldness00]

I had a just 1 crach and it fixed him self in less that 3min

[tomtom13]

Just to rub it int ;) Sorry but after the switch problems are gone.

[kbonnel]

Good to know. I have been running without issue on my usb sonoff dongle for over a week.

[tomtom13]

More "rubbing it in" ;)

[habitats-tech]

I have created 3 threads to document issues and findings pertaining to SLZB and UZG hubs, so we can all contribute from a single point of reference to the continuous improvement of zigbee2mqtt for the aforementioned hubs.

#26839 - ember SLZB
#26838 - zstack SLZB
#26840 - zstack UZG

[Feriman22]

I solved this by enabling "Allow multi-threaded socket connection" under "Z2M and ZHA".

Edit: Enabling this made things worse, so I had to disable it.

The real issue is probably one spamming device; in my case, it's a presence sensor. I will build my own from scratch.

[lejstef]

I'm using ZHA. Tested enabling "Allow multi-threaded socket connection", but that only made the problem worse. Started freezing multiple times per day.