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

[mattnl]

Hi all,
I also have the SLZB-06M since 2 weeks. I have never had a freeze of the device since. So far it is rock stable.
Device is connected via Ethernet/PoE and I am just using Zigbee2MQTT, no home assistant.
Core firmware 2.5.8 and now 2.6.8.dev9

[TheDescender]

As a developer, I believe the problem is not the HA integration itself, but the SLZB API. The same API is used in the Web UI. So the HA integration often (I think every 15 minutes or less) takes information from the device, which causes a memory leak on SLZB. If you disable the UI (socket connected setting), everything works perfectly, but the UI and integration stop working because the APIs are not available with this setting

Have you actually seen a stable environment with the Web UI disabled through the option in the security settings? My SLZB-06 literally bricks the network every day or 2 days even on v2.8.6.dev16, And if so, how do you interface with the SLZB-06 to troubleshoot and flash new firmware if not through the UI?

Mine has been stable for a couple of days now, no signs of instability yet, I’ve disabled the webui as well. I just shut down z2m when i need access to the UI, quite simple. Once you have access you can disable the setting if you want access with z2m active.

Makes sense. Will try that as well then. What Core and Radio firmware versions u running? And you have an SLZB-06 or another Variant? Just wanna make sure i'm using the same config for troubleshooting. Half the time I don't trust the settings in the webUI, since I tried to disable LEDs and that just doesn't work at all.

[Kuchiru]

As a developer, I believe the problem is not the HA integration itself, but the SLZB API. The same API is used in the Web UI. So the HA integration often (I think every 15 minutes or less) takes information from the device, which causes a memory leak on SLZB. If you disable the UI (socket connected setting), everything works perfectly, but the UI and integration stop working because the APIs are not available with this setting

Have you actually seen a stable environment with the Web UI disabled through the option in the security settings? My SLZB-06 literally bricks the network every day or 2 days even on v2.8.6.dev16, And if so, how do you interface with the SLZB-06 to troubleshoot and flash new firmware if not through the UI?

Mine has been stable for a couple of days now, no signs of instability yet, I’ve disabled the webui as well. I just shut down z2m when i need access to the UI, quite simple. Once you have access you can disable the setting if you want access with z2m active.

Makes sense. Will try that as well then. What Core and Radio firmware versions u running? And you have an SLZB-06 or another Variant? Just wanna make sure i'm using the same config for troubleshooting. Half the time I don't trust the settings in the webUI, since I tried to disable LEDs and that just doesn't work at all.

Im on dev16 with the latest zigbee firmware, i have a 06M.

[TheDescender]

Aight, I'll run the same then. Starting to feel like the base 06 might just be a shit model then. Since I'm reading people with the 06M having their issues solved.

[Kuchiru]

The only other differences i can come up with is what is powering the device (which brand/make) and what kind of cable you’re using. Mine is powered by an unifi poe switch with pure copper UTP cable (never CCA UTP for POE devices!)

[TheDescender]

Agreed CCA is trash for any POE application. Currently powering it over usb-c with a samsung adapter for testing, so it should draw all the power it needs. No shot there's any usb interference since there's not even any data coming over that interface. I'll try your method with the disabled interface now and see how I get on. Worst case I'll just return the thing once my UZG gateway arrives.

[KHV8]

Have same problem as others report.
During reboots of Home Assistant I got the problem several times today. Tried to remove the SLZB integration from Home Assistant. During several test restart of Home Assistant I have not seen the problem..
I think the error is created by SLZB integration.

[alju67]

Running Core 2.6.8.dev9 / Zigbee 7.4.5.0 / with HA integration since 2 days, and no error so far
Just upgraded to Core 2.6.8.dev13 / Zigbee 7.4.5.0 / with HA integration / Z2M 1.42

[arfond]

@alju67 - how do you upgrade to dev? Possible via the web interface?

[jeroenbeuz]

@alju67 - how do you upgrade to dev? Possible via the web interface?

Go here: https://smlight.tech/flasher/#SLZB-06
Select the OTA version you want. Upload it on the web portal of the device.

[Tarik2142]

dev14 is available for download!
https://smlight.tech/flasher/firmware/bin/slzb06x/core/slzb-06-v2.6.8.dev14-ota.bin

[drjjr2]

Are there any release notes or anything to suggest what makes it better than dev9?

[Tarik2142]

Are there any release notes or anything to suggest what makes it better than dev9?

After a crash, the device reboots instead of freezing forever.
Fixed a crash when initializing the SMLIGHT SLZB integration

[drjjr2]

Awesome. Thank you.

[habitats-tech]

For anyone reading this thread and using SLZB-06x adapters please do the following to get back to a stable setup:

In HA delete all SLZB devices.

Install core FW v2.6.8.dev14 - we need as many people as possible on this version!

In HA just click ignore in the newly discovered SLZB.

Manually add SLZB and just type the IP address. This action bypasses mDNS. Example below, replace with your SLZB IPv4 address.

You should now have a very stable SLZB environment. Tested on SLZB-06, SLZB-06P7 and SLZB-06M. If you still experience issues please post here, as well as to SMLIGHT so we are all aware of potential issues and even might be able to assist.

[habitats-tech]

Any core FW above dev14 is stable (up to the time of writing this message). dev 16 addresses issues related to the IEEE address, which at the time of writing this message is the only version available (supersedes any other dev version).

[dsiebel]

Running v2.6.8.dev14 with HA integration configured via static IP, for 3d 4h now.
No crashes / freezes so far.

[Sortberg]

Is there experience on whether this works?

V2.6.8 added SMLIGHT integration manually in HA.

[Kuchiru]

Is there experience on whether this works?

V2.6.8 added SMLIGHT integration manually in HA.

We're all basically trying this and reporting when something does or doesn't happen, no dev build has 'proven' itself thus far as we're barely a week from the last release.

[Sortberg]

Okay. Well, I will also write in here with my experiences. So far, the best I've tried is with an automation that takes the power via a smart plug to my coordinator every night at 3 a.m.

[fti7]

v2.6.8.dev14 crashed after an Week. SLZB Integration was active without IP.
Updated now to dev16

[habitats-tech]

dev14 was only out on Dec 2, possibly a lower FW version?

[habitats-tech]

dev16 fixes IEEE address issues, not stability related issues.

[drjjr2]

Should we be stopping Z2M prior to updating the device firmware to these dev versions? Or cycling power on it or anything else special?

[habitats-tech]

No need to power cycle. The FW update will close and then open the connection.

[TheDescender]

@habitats-tech Installed dev16 as soon as it came available and am on Zigbee firmware version 20240710 for the base model SLZB-06. Worked well for 3 days, now my devices are not state reporting correctly anymore and push commands from the controller rarely reach devices, even those less than 3 meters from the controller. Literally my entire network map in Z2M is filled with 0s for connection strength.

Zigbee channel 25, lot of wifi around me, but nothing past wifi band >8.

You guys or anyone else seeing this problem too?

[Tarik2142]

This is a zigbee firmware or setup issue.
First, if you have updated your zigbee firmware, roll it back.

[TheDescender]

I mean, it worked perfectly fine for 2 days, then shit bricks on day 3. Firmware version 20240710 is literally recommended by the dev in this post several days ago. I was on Zigbee firmware version 20221226 before and had the same problem prompting me to update to the latest core and zigbee version as recommended. I don't see how rolling back again would solve this issue.

I've now gone back to my Sonoff USB and threw router firmware on the SLZB-06. Ordered a UZG-01 and will see how that works even with ZHA.

My frustrations:
Kinda reaching my limit with Zigbee. Network and coordinator technology is just incredibly immature considering it can just die randomly without any changes in the network or surrounding wifi networks, to the point that coordinators cannot communicate with HUE lights or Tradfri plugs less than 3 meters from them.

I know how to troubleshoot the issue from experience btw. But also learned from experience that it'll then work for maybe a week until it randomly dies.

[Kuchiru]

I understand your frustration, however, please know that this does not have anything to do with zigbee technology as a whole.

The product that isn’t mature is the smlight dongles, and they are working hard to fix the issues people are experiencing.

[TheDescender]

Hence why I'm posting that after 3 days the network went down. Waiting to see if the same happens for others in a week's time. If not then I'll experiment with it later.

[habitats-tech]

CAVEAT EMPTOR!

The hard reality is that, at present, NOTHING beats Wi-Fi is any aspect of local-range-wireless-tech except battery life, which is way shorter on Wi-Fi (6 months compared to 2 years on Zigbee). If your Wi-Fi has been deployed to enterprise or professional standards deploy on Wi-Fi as much infrastructure as possible.

Zigbee on Tuya is very reliable, however not as flexible, configurable or capable as SLZB/UZG. Also Tuya devices outside the Tuya ecosystem can be hit and miss.

The issue with Zigbee is that even after decades quite a bit of the protocol stack is still not standard, rather optional, which manufacturers can implement as they see fit. So on a Zigbee network when issues arise you never know the culprit, as there are so many permutations, most of us do not have the time or skill to address.

Now on the SLZB issue check if you have Tuya devices on your Zigbee network. Frequently they are the source of pain. I do not have any experience with IKEA, but from what I have seen IKEA devices should be avoided if possible.

In my experience SONOFF is the most reliable out there, at present, both from a device and hub point of view. But SONOFF is also not free from issues with devices, for example the same model of device could behave differently in some instances, even when everything is paired from the exact same location.

This is the primary difference with Wi-Fi. If a Wi-Fi device stops working and your Wi-Fi network has no issues, you are certain the device is the problem. With Zigbee you cannot be certain unless you dive deeper into the rabbit hole.

It remains uncertain if, in reality, Thread can address the Zigbee issues, as in theory Thread is superior to Zigbee.

I hope this short post provides some background and warning to newcomers.

[s1n7ax]

Using SLZB-06. SMLight support suggested trying 2.3.6 or 2.6.8.dev16. Non of them last a day.

[janstadt]

I updated to dev16 and all hell broke loose again. Can someone post a link to slzb-06-v2.6.8.dev14.bin? Its no longer listed on the firmware upgrade page. That one seemed to actually work ok with my setup.

[kbonnel]

There’s a link above within this overall thread to dev14 you could try. In the past all I’ve done is copy the link for the latest and then change to the version I want manually and that usually downloads it.

[janstadt]

Yeah i tried that and it showed it wasnt found.

[janstadt]

I was able to find a copy on another machine of mine at home so im good. It seems as though 14 is at least the most stable for my setup.

[s1n7ax]

This coordinator is such a pain. It's a good thing it at least restarts automatically but it has been restarted 16 times within last 5-6 hours

[virtualbitzz]

Same exact symptoms for me. Web UI locks up, devices go offline. Running PoE.

I have two of these, one for Z2M and one for OTBR. Both have the exact same issue and tend to stop responding around the same time, maybe 7 days or so after a restart.

[TheDescender]

Please share your core and radio firmware version, SLZB hardware version, Z2M version, and indicate whether you have the webui disabled on socket connect. Otherwise literally no one here can help you narrow it down whatsoever nor do you help narrow anything down.

All I can say to you now is SAME and unlucky. xD

[habitats-tech]

Same exact symptoms for me. Web UI locks up, devices go offline. Running PoE.

I have two of these, one for Z2M and one for OTBR. Both have the exact same issue and tend to stop responding around the same time, maybe 7 days or so after a restart.

Can you elaborate what hubs/routers/devices you are using on your network. We might be able to assist you understand and fix the issues.

[kbonnel]

FYI, I just did an update to my HA (update Home Assistant from 2024.12.1 to 2024.12.2), and this resulted in my 06P7 crashing and rebooting. I have sent the dump to SMLIGHT.

Please report back if this also happens to you after the update.

[Fulch]

Just had a crash and reboot on my 06M soon after updating Home Assistant from 2024.12.1 to 2024.12.2.
Bug report and dump file sent. Had been stable since install of firmware 2.6.8.dev16 which was about 5 days ago I think.

[Kuchiru]

Just updated to HA Core 2024.12.2 on HA OS 14, running home assistant as a VM and have experienced no issues.

Model: SLZB-06M
Core/FW: v2.6.8.dev16 / 20241127.
Z2M: 1.42.0 - In an LXC, this allows me to make individual backups.

• I am not using the SLZB integration in HA.
• I have websocket disabled.
• I have whitelisting enabled.
• 06M powered by a UniFi PoE Lite Switch with a full copper cable.

[Nico-Hard]

for information, I decided to update mine with Firmware version: | radio 20240330 | Core v2.6.8.dev16 / Coordinator mode on Eth.
Now it's been 4d & 20h online without issue.
On Proxmox, I have a virtual HA running with Z2M, version 1.41.0-1 (I see Z2M is usually making connection issue with devices... but for the moment, no problem)

[kbonnel]

Have you updated to HA 2024.12.2? It appears two of us had their 06's crash doing the update.

My Z2M version 1.42.0-2

[Nico-Hard]

currentlyu, HA core version : 2024.12.1

[drjjr2]

I am not using the Home Assistant SMLIGHT integration. Updated to 2024.12.2 yesterday, no crash. SLZB-06P7, 2.6.8dev16, Zigbee 20240716. Has been up for 3 days.

[s1n7ax]

v2.6.8.dev18 is very unstable.

Green bulb stopped working even when zigbee2mqtt is up and running. Wifi network is not available in USB mode. Even when Ethernet mode on, I had to unplug and plug multiple times to get wifi network to show up. Connecting to wifi network doesn't work either. When I check the network tab, it simply says unable to connect.

They really should use my device for testing cz this doesn't last more than few hours. XD

zigbee2mqtt log with debug level enabled:

[2024-12-11 09:44:31] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/ms kitchen door', payload '{"battery":100,"battery_low":false,"keep_time":30,"linkquality":14,"occupancy":true,"sensitivity":"high","tamper":false,"voltage":2900}'
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: <-- [254,1,100,1,0,100]
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: --- parseNext [254,1,100,1,0,100]
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: --> parsed 1 - 3 - 4 - 1 - [0] - 100
[2024-12-11 09:44:31] debug: 	zh:zstack:znp: <-- SRSP: AF - dataRequest - {"status":0}
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: <-- [254,3,68,128,0,1,113,183]
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: --- parseNext [254,3,68,128,0,1,113,183]
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: --> parsed 3 - 2 - 4 - 128 - [0,1,113] - 183
[2024-12-11 09:44:31] debug: 	zh:zstack:znp: <-- AREQ: AF - dataConfirm - {"status":0,"endpoint":1,"transid":113}
[2024-12-11 09:44:31] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:writer: --> frame [254,5,37,54,15,252,255,254,1,229]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: <-- [254,1,101,54,0,82,254,3,69,182,0,0,0,240]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --- parseNext [254,1,101,54,0,82,254,3,69,182,0,0,0,240]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --> parsed 1 - 3 - 5 - 54 - [0] - 82
[2024-12-11 09:44:33] debug: 	zh:zstack:znp: <-- SRSP: ZDO - mgmtPermitJoinReq
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --- parseNext [254,3,69,182,0,0,0,240]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --> parsed 3 - 2 - 5 - 182 - [0,0,0] - 240
[2024-12-11 09:44:33] debug: 	zh:zstack:znp: <-- AREQ: ZDO - mgmtPermitJoinRsp
[2024-12-11 09:44:33] debug: 	zh:controller: Received ZDO response: clusterId=PERMIT_JOINING_RESPONSE, status=SUCCESS, payload=undefined
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2024-12-11 09:44:33] debug: 	zh:zstack:znp: --> SREQ: AF - dataRequestExt - {"dstaddrmode":2,"dstaddr":"0x000000000000fffd","destendpoint":242,"dstpanid":0,"srcendpoint":242,"clusterid":33,"transid":114,"options":0,"radius":30,"len":6,"data":{"type":"Buffer","data":[25,65,2,11,254,0]}}
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:writer: --> frame [254,26,36,2,2,253,255,0,0,0,0,0,0,242,0,0,242,33,0,114,0,30,6,0,25,65,2,11,254,0,216]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: <-- [254,1,100,2,0,103]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --- parseNext [254,1,100,2,0,103]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --> parsed 1 - 3 - 4 - 2 - [0] - 103
[2024-12-11 09:44:33] debug: 	zh:zstack:znp: <-- SRSP: AF - dataRequestExt - {"status":0}
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: <-- [254,3,68,128,0,242,114,71]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --- parseNext [254,3,68,128,0,242,114,71]
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --> parsed 3 - 2 - 4 - 128 - [0,242,114] - 71
[2024-12-11 09:44:33] debug: 	zh:zstack:znp: <-- AREQ: AF - dataConfirm - {"status":0,"endpoint":242,"transid":114}
[2024-12-11 09:44:33] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2024-12-11 09:44:39] info: 	zh:zstack:znp: Port closed
[2024-12-11 09:44:39] debug: 	zh:controller: Adapter disconnected
[2024-12-11 09:44:39] info: 	zh:zstack:znp: closing
[2024-12-11 09:44:39] error: 	z2m: Adapter disconnected, stopping
[2024-12-11 09:44:39] debug: 	z2m: Saving state to file /app/data/state.json
[2024-12-11 09:44:39] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[2024-12-11 09:44:39] info: 	z2m: Disconnecting from MQTT server
[2024-12-11 09:44:39] info: 	z2m: Stopping zigbee-herdsman...
[2024-12-11 09:44:39] debug: 	zh:controller:database: Writing database to '/app/data/database.db'
[2024-12-11 09:44:39] info: 	z2m: Stopped zigbee-herdsman
[2024-12-11 09:44:39] info: 	z2m: Stopped Zigbee2MQTT

[Davinatorr]

Well for me it works fine since I deactivated the Home Assistant Integration for the SLZB-06 one week ago. I really don't need that integration. Habitats-tech mentioned it in this thread, thank you!

Is there someone who deactivated the Integration and still has problems?

[virtualbitzz]

I actually started speculating that the integration may be part of the problem and disabled mine today on both (I have two, one for Z2M and one for OTBR). Will report back in about a week

[wpformation]

Same here ! Works fine since I deactivated the Home Assistant Integration for the SLZB-06
20240710 | v2.6.8.dev16

[Tarik2142]

dev19 is now available https://smlight.tech/flasher/firmware/bin/slzb06x/core/slzb-06-v2.6.8.dev19-ota.bin

[Tarik2142]

I want to clarify the problem:

Firmwares dev16 and above do not have a memory leak, the webserver has been completely rewritten, which causes crashes in certain situations, but the device does not freeze anymore.

Please note that there is also a known problem of freezing of CC2652P zigbee chips. It often occurs due to SPAM in the zigbee network and in this case, updating the CORE firmware will not help.

How to distinguish a CORE firmware problem from a zigbee firmware problem? To do this, check the device uptime. If the socket uptime has been reset to zero but the device uptime has not been reset, this means that you have a problem with the ZigBee chip firmware or with the ZigBee network setup.

[kbonnel]

@Tarik2142

Please note that there is also a known problem of freezing of CC2652P zigbee chips. It often occurs due to SPAM in the zigbee network and in this case, updating the CORE firmware will not help.

Would this problem be related to this issue being discussed?

#24671

[Tarik2142]

@Tarik2142

Please note that there is also a known problem of freezing of CC2652P zigbee chips. It often occurs due to SPAM in the zigbee network and in this case, updating the CORE firmware will not help.

Would this problem be related to this issue being discussed?

#24671

no. like #17809