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.

[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

[kevdogg]

Smlight provided me a dev28 version because of the split channels being used. I don't think it's available. I'm not associated with company or special dev in anyway but just reached out through their support site after having issues with the reverse proxy. I'm not sure if there are any other changes however I'm assuming there has to be more since I'm guessing there was a dev27 at one time that had to tweak things compared to dev26 that was related to other issues. I honestly don't know. I was able to get up to 5 days on dev26 with no gui freeze before flashing dev28. If I can get up to 2 weeks with a stable gui ill introduce z2mqtt version 2.x to the equation and go from there. It would however speed up testing if I could monitor memory along the way since with a leak I could speed up this trial phase and see the leak before all of it was consumed and the gui becomes unresponsive...this of course assuming it's a leak.

…

On Mon, Jan 6, 2025 at 7:18 AM kbonnel ***@***.***> wrote: Do you mean Dev26, or did SMLIGHT provide you with a Dev28 version? I only see Dev26 on the website. I apologize if I gave the impression that it was totally a Z2M issue, that was not my intention. I only wanted to indicated that there seems to be issues with Z2M that triggered crashes on the 06 side. There was definitely a memory leak on the web server, and I recall in this thread there being discussions about the web server being rewritten to resolve that. I don't remember which version it was though. — Reply to this email directly, view it on GitHub <#21157 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH75V6JSMDCILLU6BLINHL2JJ7DFAVCNFSM6AAAAABCWKS5AKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZUHA4DEMA> . You are receiving this because you commented.Message ID: ***@***.***>

[drueppela]

@Farum-JRI

What puzzles me with this problem is, that I guess there are thousands? of SLZB-06 running in the world. I assume only a small percentage of us experience the stability issue!? Do we have anything specific in common? I tried to move mine to another location, which didn't help. This morning, I have tried to disable all devices but one, to see if this changes anything. Mine was totally stable until sometime in August 2024. My HA (v. 2024.12.5) runs in a Docker at my Synology NAS. I run v2.6.8.dev26 on my SLZB-06.

@Dinth & @Farum-JRI :

I propose to follow this "analytical" approach. I have three SLZB-06M and the coordinator crashes without gui-interaction. But a nightly reboot solves the symptoms. The other two SLZB-06 are running as routers without any problem.

@Dinth : Can you imagine creating a table in the first post in which we collect which error patterns we have and under which circumstances everything works and try to find out whether there is a pattern of what we have in common?

Perhaps we find a solution before the issue celebrates its first birthday in 23 days.

[WhimsySpoon]

@sphings79 whats your zigbee firmware version?

I installed 20240716 a few days ago and so far, so good.

[WhimsySpoon]

Maybe your problem is really not related to chatty devices. The full Z2M error log might help to understand the problem.

Of course. The next time it happens, I'll post the logs.

[techie-dreamer]

Thanks for the clarification. I've been running dev26 for a while and can confirm that the core freezing issue appears to have been solved.
However I've suffered the zigbee crashes and I don't have any chatty devices on the network (as confirmed by logs). That being said, I only recently updated the zigbee firmware (previously running a version from 2023), so hopefully that's solved too.

Maybe your problem is really not related to chatty devices. The full Z2M error log might help to understand the problem.

My logs were posted above & shared with smlight support in full. Indeed, removing my chatty devices (Aqara temperature sensors) & going back to having my SLZB-06 on 2.3.6 made system stable but what I don't understand is these sensors have been on the network for 6 months and been stable.

Something must have changed which is causing these lock-ups relating to the devices - it's hard to unpick what.... SLZB-06 device, z2mqtt, Home Assistant, MQTT...? Result is I'm stuck & don't want to add the removed devices back into the network.

All the details in this thread

[Tarik2142]

Thanks for the clarification. I've been running dev26 for a while and can confirm that the core freezing issue appears to have been solved.
However I've suffered the zigbee crashes and I don't have any chatty devices on the network (as confirmed by logs). That being said, I only recently updated the zigbee firmware (previously running a version from 2023), so hopefully that's solved too.

Maybe your problem is really not related to chatty devices. The full Z2M error log might help to understand the problem.

My logs were posted above & shared with smlight support in full. Indeed, removing my chatty devices (Aqara temperature sensors) & going back to having my SLZB-06 on 2.3.6 made system stable but what I don't understand is these sensors have been on the network for 6 months and been stable.

Something must have changed which is causing these lock-ups relating to the devices - it's hard to unpick what.... SLZB-06 device, z2mqtt, Home Assistant, MQTT...? Result is I'm stuck & don't want to add the removed devices back into the network.

All the details in this thread

Device reporting settings are configured by Z2M on pairing, but these settings could also be broken if you updated the firmware of these ZigBee devices and the new firmware had some bug that affected it.

[sphings79]

@sphings79 whats your zigbee firmware version?

I installed 20240716 a few days ago and so far, so good.

Me too

[kevdogg]

I'm not having any issue currently with dev28..still testing. 4 days no frozen gui

…

On Mon, Jan 6, 2025 at 9:26 AM Tarik2142 ***@***.***> wrote: new webserver did not meet expectations, so starting with dev24 the old one was returned, but now SSE runs separately from the webserver, on port 81. As it turned out, this causes problems when using proxies. One of the users was given a separate experimental build of dev28 that combined the webserver and SSE back on port 80 for testing. But by this comment, I can say that it seems that this experiment failed and in the future SSE and webserver will remain separate (as it is now in dev26). — Reply to this email directly, view it on GitHub <#21157 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH75V4DVGVTGEOB3QKDWZ32JKODVAVCNFSM6AAAAABCWKS5AKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZVGAZTEMI> . You are receiving this because you commented.Message ID: ***@***.***>

[habitats-tech]

I assume dev28 is more or less the same as dev26. dev26 is for certain the most reliable FW version; see below. Socket uptime has to do with Z2M. So with dev26 no webUI freeze, tested on both Blink and Quantum browser engines (e.g. Chromium and Firefox based browsers). For most of us dev26 should be the go to FW version at present.

[hellboy-wien]

Update: Running without problem since: see Picture

[matata86]

@kevdogg Can you send me dev 28, please?

[kbonnel]

I suspect if you open up a ticket with smlight support they would send it over.

https://support.smlight.tech/supportcenter/public/en/customer/login

[Sortberg]

@kevdogg Can you send me dev 28, please?

https://smlight.tech/flasher/firmware/bin/slzb06x/core/

[sphings79]

Dev29 is out. I don’t understand why there were no changelogs …

[tomtom13]

Dev29 is out. I don’t understand why there were no changelogs …

as a software engineer - trust me, this is something everybody forgets, specially in dev release .... specially if you don't know if the root cause was truly fixed.

[kevdogg]

Hey I'd love to but not sure I can for licensing purposes...I obtained it from the smlight forums directly

…

On Wed, Jan 8, 2025 at 10:59 AM matata86 ***@***.***> wrote: @kevdogg <https://github.com/kevdogg> Can you send me dev 28, please? — Reply to this email directly, view it on GitHub <#21157 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH75V4F6FKI7DCJFFYVZVD2JVKQRAVCNFSM6AAAAABCWKS5AKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZXGYYTENY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Sortberg]

Hey I'd love to but not sure I can for licensing purposes...I obtained it from the smlight forums directly
…
On Wed, Jan 8, 2025 at 10:59 AM matata86 @.> wrote: @kevdogg https://github.com/kevdogg Can you send me dev 28, please? — Reply to this email directly, view it on GitHub <#21157 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABH75V4F6FKI7DCJFFYVZVD2JVKQRAVCNFSM6AAAAABCWKS5AKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZXGYYTENY . You are receiving this because you were mentioned.Message ID: @.>

https://smlight.tech/flasher/firmware/bin/slzb06x/core/

[psychedelicu]

Hey guys! Does somebody knows if i can run both zigbee and thread on the same time on SLZB-06M?

[kbonnel]

You use to be able too with specific firmware’s but it isn’t recommended anymore. I know you used to be able with sonoff’s dongle-e with the multi pan firmware (I think that is what it was called). I guess there were issues though and now they recommended using openthread border firmware.

[tomtom13]

What I'm wondering is why they don't release the source code as open-source ? they make money from hardware sales, but make software that keeps having issues and having more people looking into it would lead to finding the actual cause of crash and make their software more reliable.

BTW, I've had the same problems as others people have, when left over a longer period of time it the SLZB06 will lock up and GUI will only how in simple text (like most of the JS stuff didn't download along with the page). What I've found was that IF the home assistant is regularly rebooted this problem doesn't seem to happen. When going on holiday and just leaving everything running without any upgrades / reboots - things crash. I reboot often because I've got plenty of add-ons.

Additionally my network is rather big: 171 devices, most of which are Philips hue bulbs, and version of SLZB06 based on CC2652P.

[kevdogg]

"as a software engineer - trust me, this is something everybody forgets, specially in dev release .... specially if you don't know if the root cause was truly fixed." I get they might know the root cause might not be fixed but it would be nice to know how it differs from dev 26/28.

…

On Fri, Jan 10, 2025 at 4:48 PM Tomasz Kusmierz ***@***.***> wrote: Dev29 is out. I don’t understand why there were no changelogs … as a software engineer - trust me, this is something everybody forgets, specially in dev release .... specially if you don't know if the root cause was truly fixed. — Reply to this email directly, view it on GitHub <#21157 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH75VYO3776TZJBHGBB67T2KBE3RAVCNFSM6AAAAABCWKS5AKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBQGMZTGNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tomtom13]

Hey, don't shoot the messenger. I've been at both ends of the stick: as a guy that just kept pumping out "hey try this one" (with spaghettini and the wall analogy coming to mind), and a guy that was testing "yet another firmware that was only distinguishable via checksum, but had the same revision number". Trust me, if you end up doing md5 or sha to distinguish between files you know that either dev is pinned to the wall or they don't care.

Anyway, I've had this problem for better part of the year without moaning, but now I guess I'm going for zigstar to dip my toes and see whenever they release firmware that can survive a month without nurturing it line an egg (me on a fifth whisky going through aliexpress just to stop this admin madness).

[habitats-tech]

For whatever is worth, UZG-01 is very reliable although not frequently updated. The router FW of UZG-01 is old, but works, although not without unexpected reboots, but operationally UZG-01 as a coordinator and/or router is reliable, meaning errors, when they occasionally arise, are auto-corrected without intervention.

Updating UZG-01 FW can be troublesome in some network environments, as per my experience (UZG-01 would not update on say network-A, but if moved to network-B would update with no issues).

In any case UZG-01 can be relied upon.

I would also like to state that SLZB is reliable as per my experience, excluding the recent issues with core FW.

I have several UZG and SLZB in use and my experience is positive. It seems people are experiencing issues with certain brands or products, which might cause similar issues to both UZG and SLZB. It seems Aqara is one such brand.

For me Sonoff is the best brand for Zigbee products. As per my experience Sonoff is configurable (e.g. reporting) and operationally reliable.
Tuya products can be hit and miss, quality is usually questionable, and most are not very configurable.

[matata86]

https://xzg.xyzroe.cc/

Have you tried this firmware?
What are your experiences?
Is it possible to upgrade while keeping the devices paired in Z2M?

[habitats-tech]

Yes running this FW version since it came out. Very reliable as I have coordinators running non-stop since it came out.

[habitats-tech]

Yes updating the FW does not require re-pairing if memory serves me well.

[habitats-tech]

When updating anything zigbee, if changes do not affect the IEEE address and the type of FW stack (e.g. zstack or ember), you are good to go.

[habitats-tech]

A few more points for Z2M networks in general.

Try channel 26 with all the different devices you have. In my experience this benefits Tuya devices as for some reason they do not miss reporting schedule as frequently. I have extensively tried channels 25, etc. but always Tuya for some reason randomly lose their reporting schedule (some take days before they suddenly start reporting again). This does not happen (missing the reporting schedule frequently) on channel 26.

Additionally set your coordinator to signal strength 8-12. As low as possible, as it benefits wireless signal congestion. I have routers almost 10m away from coordinator (set at 12 signal strength), and they communicate with no issues.

[Sortberg]

Do you have any indication of the signal strength? Or is it your own experience? Doesn't the 'map' get weaker if it doesn't send on 20?

[janstadt]

So i am running dev26 with the most recent zigbee firmware and i went through today and repaired everything. It worked for a few hours and then i noticed some of my automations not firing and come to find that all the door sensors (xiaomi mijia ones mostly) were unavailable. I tested out channel 26 and 25, no difference, things still just become unknown in HASS (im not running the smlight integration). I just dropped the transmit power down to 12 from 20 and we will see how that goes, but man oh man is this frustrating. Going back to channel 25 with transmit power of 12. I went around and repaired the goofed up door sensors. Im gonna just wait and see how things go for a while. Gotta leave the devices and coordinator alone cuz its hard to know what changes are affecting things.

[tomtom13]

my 2 pennies here. I've been running on channel 25 for very long time and never had problem with 2.4G wifi interference. I live in a detached house and everybody around me sit on channel 1 (including me) for wifi 2.4G. Only problem is that damn dongle crashing.

[habitats-tech]

Do you have any indication of the signal strength? Or is it your own experience? Doesn't the 'map' get weaker if it doesn't send on 20?

Focusing on battery devices, a high LQI value does not guarantee better operation of the device. Obviously this also depends on the quality of the device, but in my experience a well behaved device even with an LQI of 3 operates flawlessly.

When the coordinator was on 20 a lot more router devices were connecting with the end result being congestion. When set to 12 the network became more efficient with less devices connecting to the coordinator. To my experience the less devices connecting to the coordinator the better. Again based on my experience avoid connecting battery operated devices directly to the coordinator, they can destabilise the zigbee network. The above are for larger networks, but if you can follow best design practices even on a small network you can benefit long term. You never know when you become rich to afford a larger zigbee network. 😊

[habitats-tech]

Snapshot of the coordinator connections with transmit power at 12. Closest router is 2m and furthest router is 12m.

[Sortberg]

This evening it has been running without issues since 7/1. Then this error appeared, as you can see in the log... What kind of error is this?
FFS....................................................................................

z2m - 11-1-2025-486e6e9b_zigbee2mqtt_2025-01-11T21-46-54.430Z.log
SLZB06P7 - Crash.txt

[habitats-tech]

This is a zigbee socket error. For some reason communication to the socket times out. I have found this error common when using ember (SLZB06M) coordinators, but you are using zstack.

[Tarik2142]

It looks like the network connection was lost for a while. This is some network error.

[doff-1]

So I've been following this thread after I had some stability issues.
during the development of this thread I downgraded my SLZB-06M to 2.3.6 and reconnected the SLZB integration in Home Assistant via IP instead of mDNS.
Since that I haven't really had any issues.
Logging in to the device now I notice a slowdown of the web interface, but everything is still up and running.

To sum it up:
SLZB-06M in coordinator mode
Connected and powered by PoE
108 zigbee devices on the network
Core: 2.3.6
Radio: 20231030
ZHA (NOT z2m)
Home Assistant SLZB addon configured with IP

currently device uptime is 39days and 21hrs
Z2M/ZHA uptime is 2 days, because of recent HA updates.

Btw. Which radio firmware is recommended for ZHA?

[sphings79]

Today my switch deactivated the Port of the SLZB-06:

Blocked by Spanning Tree Protocol to prevent a network loop. This port will be automatically re-enabled when the loop is no longer detected.

There is only the stick connected to that port.

---

EDIT: Im on DEV29

[Tarik2142]

For this to happen you need to connect the device simultaneously via ethernet and wifi but the device only uses one interface at a time