Replies: 165 comments 602 replies
-
|
It may be related to #18192 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
After a month of suffering pain of instable/dead Zigbee mesh i have a few things to add:
|
Beta Was this translation helpful? Give feedback.
-
|
I have created a new Zigbee2mqtt container on my Qnap en moved over everything (configuration.yaml, coordinator.json) |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Hi back after a whille, i downgrade Z2M to [1.34.0] it has been running for a week with out issues (sonoff dongle) Hardware @ the moment is a Qnap NAS TVS-H874X, so this should not be a problem i think |
Beta Was this translation helpful? Give feedback.
-
|
Same here, my lan zigbee is down |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem. Every 3/4 hours it freezes |
Beta Was this translation helpful? Give feedback.
-
|
Yes |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
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 ? |
Beta Was this translation helpful? Give feedback.
-
|
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
I am going to try and go back to firmware 20240315 |
Beta Was this translation helpful? Give feedback.
-
|
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 - |
Beta Was this translation helpful? Give feedback.
-
|
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. Edit2: I removed the spammy device (presence sensor), but still the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
I have some update from smlight: There is a known problem with radio modules from Texas Instruments, its radio modules freeze at high load, usually the more load the sooner it will happen. This can happen both in an hour and in a week, depending on the amount of traffic.
|
Beta Was this translation helpful? Give feedback.
-
|
Also, if this thread is a little bit older. I strugled today the whole day. Tried everything (all combinations of plug of stick, reboot, different firmware's and zigbee coordinator fw versions, Zigbee restart in all combinations , recover of backup, of the proxmox machine etc. etc. etc. In the End and that is for all the people who still struggle after what I did above: TRY ALSO RESTARTING THE MQTT BROKER (after you did e.g. "zigbee restart" or unplugging SLZB from power. I would recommend the follwoing:
|
Beta Was this translation helpful? Give feedback.
-
|
OK boys and girls, here is something that might be interesting to specifically SLZB users. Backstory: So I started digging. Turns out that my old instance of Z2M has about 230 devices in coordinator_backup.yaml - considering that originally there were 197 devices MINUS 9 devices moved to the separate instances, this looked fishy. Today over past few days I started something akin of "cleanup". I started removing zombie devices from coordinator_backup.yaml, and for "naughty devices" (one that don't update all the values, or randomly fall off) I started shifting those to new network -> shutdown old Z2M instance -> remove device data from coordinator_backup.yaml -> power OF coordinator -> 10s wait -> power on coordinator -> starts Z2M -> remove device from new instance -> pair it again to the old instance. So far my results are good, values are updating properly, network is becoming more stable. So to me it rakes of Z2M not being to well geared to keep crap out of it's config / internal DB. What I would suggest is if you have a large network: about p10 slzb, dissable everything, dhcp, mdns, auto update check, any funky feature you can. Just leave it as dumb coordinator. |
Beta Was this translation helpful? Give feedback.
-
|
My Zigbee Network is stable since I disabled the smlight integration in Home assistant. With integration enabled it take about one week when it get unstable with device no reaction. And the slzb interface was not reachable. Disabled integration, restart everything and since month it is stable without issues. I use Z2m and a slzb06 |
Beta Was this translation helpful? Give feedback.
-
|
Hi all - so I think I've cracked it, after a week of testing, my Zigbee network hasn't crashed once. Before, it was going down every 24 hours on average - requiring a reboot of the co-ordinator. The change was swapping the slzb06 (Zigbee CC2652P chipset) out for a slzb06m (Zigbee EFR32MG21 chipset) co-ordinator. smlight support (& many above) has said there was a known issue with CC2652P chipset crashing under high Zigbee traffic and they seem to be right. Nothing else on my network has changed - almost 90 devices, about 50% battery powered and the rest mains (routers). Here's how I swapped:
** NOTE: Mine didn't start up first time, saying invalid backup file in the logs, so I renamed coordinator_backup.json to coordinator_backup.save.json and tried again (thanks to these instructions) and it came up fine. Hope that helps someone and gives hope if you're almost giving up - as I was (my family were tearing hair out when the lights were 'broken again' :) |
Beta Was this translation helpful? Give feedback.
-
|
OK boys and girls, have anybody tried THREAD on EFR32MG26 and / or CC2674P10 ? Specifically, looking at how it behaves on SLZB ? |
Beta Was this translation helpful? Give feedback.
-
|
I know you are asking about the MG25 and P10, but in case you were curious,
I am running Matter over Thread on my slzb-06p7 for almost a year and
haven't had any real issues.
I don't have an extensive matter/thread environment, a couple of apple tv
4ks as border routers, and a Aqara hub M2 with a Aqara Smart Lock U100.
Kimo
…On Fri, Feb 6, 2026 at 6:30 PM Tomasz Kusmierz ***@***.***> wrote:
OK boys and girls, have anybody tried THREAD on EFR32MG26 and / or
CC2674P10 ? Specifically, looking at how it behaves on SLZB ?
—
Reply to this email directly, view it on GitHub
<#21157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASASZ7CHTRKT22JRIBX7IAD4KU52DAVCNFSM6AAAAABCWKS5AKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZSGM3DSMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
OK, What is the max baud rate that people run for SLZB-06Mg26 (EFR32MG26) ? I'm pondering going with 460800. But would love some feedback before shifting 200 ish devices over. |
Beta Was this translation helpful? Give feedback.
-
|
I have news from SMLight support regarding this issue: |
Beta Was this translation helpful? Give feedback.
-
|
OK boys and girls ! The SLZB-06Mg26 migration is done, and for 36 hours the network was rock solid as FFFFF !!! even devices that seemed sluggish, are now working perfectly and super fast. My oldest daughter had issues with her light switches being temperamental and slow - now it's instantaneous. She's very happy with the result :) |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I have tried the migration but I see the following error in the log now: I followed the instructions above but additionally also those in the link you shared (copying everything in the coordinator_backup.json except for the first two blocks etc) The list of devices is empty. Any ideas what's going wrong / what I have to do? UPDATE For those of you interested in how to setup Matter-over-Thread on your shiny new dongle, see |
Beta Was this translation helpful? Give feedback.
-
|
I have some news about this issue and solution it this GitHub issue: |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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:
If i now restart Z2M im getting:
On the SLZB-06 side there's nothing suspicious - normal temperatures, everything seems to work except no connected client:
Seems that Z2M is trying to connect but the connection drops.
My Z2M config is as follows:
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
Beta Was this translation helpful? Give feedback.
All reactions