So how did the nuke the network and start over go?
I have just returned from my trip after 8 weeks. The SLZB-06 worked perfectly for the kids the entire time with no crashes.
So i moved the network again onto SLZB-MR3 after i updated it to latest OS release. It crashed again after about a day.
Now i am thinking should have brought the new sonoff dongle m dongle max…talk about the weird names…
Come to think of it anyone tried the SLZB-MR1 for stability?
Not the SLZB-MR1 but the SLZB-MR2 since a couple of month where Radio 2 [CC2652P] is configured as the Zigbee coordinator and Radio 1 [EFR32MG21] is configured in Zigbee router mode. Connected through LAN and powered through PoE.
I’m very pleased so far: No crashes whatsoever.
I had lots of issues with the MR3 (migrated from zzh!), network crashed every day, powered with the usb-c port
Logs didn’t say anything usefull, it just stopped responding, web gui worked fine and a reboot from that one brought it back
Moved to a POE-port on one of the unifi switches, not a single crash since then, might be worth a try
Which chip/firmware you using for Zigbee vs thread?
If the question was pointed to me, CC2674P10 for zigbee and EFR32MG24 for thread
Yes and which firmware version please?
I am using the CC2674P10 with 20240716 for Z2M and
EFR32MG24 with 20250212 on POE
Firmware version:
EFR: 20250212
CC:20240716
ESP32: v3.1.3
Yeah looks like its the same. thanks. How many devices?
So this thing aint working for me and smlight have offered a refund. So I may have to consider the Sonoff Dongle M or something else.
Any suggestions of any device with similar features or better?
I might still try and re-pair everything but smlight are asking me to remove everything including the z2m folder and start again. So its not just pairing everything again but naming all devices etc. Replacing the SLZB-MR3 with SLZB-06 completely fixes the issue and no drops whatsoever…
Sorry i didn’t notice this.
The nuke and reset has been solid. I have not changed the EFR chip off of the 20240602 from the SLZB-06 FW that support had me change to.
The OS is current “SLZB-OS v3.1.3”
The CC chipset is configured for Matter-over-Thread (but there is nothing connected)
144 devices currently. still need to finish adding light switches but that is a ‘new’ to replace analog switches
Router: 90 & End devices: 54
I did the nuke and reset a few days ago. The CC2674P10 chip again. It was stable for a day and my hopes were dashed as the same 40 odd out of 65 devices dropped or went offline.
This morning I flashed EFR32MG24 for ZigBee and have paired the devices to it. The devices were falling off it as I was pairing them…well a few of them so not very hopeful. I think there i fundamentally an issue with these.
I mean I had no issues with the slzb-06 at all
I have an MR3 newly set up to replace my old Nortek. I have Zigbee on the CC2674P10 and Matter/Thread on the EFR32MG24. The Zigbee firmware is 20240716, the Matter/Thread firmware is 20251218 and the Core ESP32 firmware is v3.2.4. The whole thing is Ethernet connected to a Unifi PoE switch.
I got my Zigbee network migrated over and it seems to work well. The only issue is that every day or so my entire Zigbee installation disappears. It keeps trying to setup and I’m getting errors that it can’t connect. the web UI seems fine and indicates no problems.
I’ve rebooted the Zigbee processor and the core processor and that doesn’t help. I need to power cycle the device to get it back and then it all comes back in seconds. I recall from building a couple of ESP32 devices that I used an external offload chip for the IP stack. I am guessing that this is getting “Wedged” so there’s no way to recover it except power cycle the board.
At ths point I can power cycle the Unifi switch port via HA, which is handy. But I can’t detect when I need to do it. Doing it every day seems good but then, today, it died again within 12 hours and I had to cycle it manually - and it came right back. It’s buggy for sure, but I don’t know if it’s software correctable.
Exactly the same here. Same setup and firmware and I have to power cycle it to recover. It took me a while but the “only” thing to do is to power cycle the MR3. Not statisfying at all.
I have the same device, and after a few months of use it started randomly resetting. Because of that, I decided to update Zigbee2MQTT from version 2.8.x to 2.9.x, and also upgrade the device firmware to version 3.2.4.
The update process itself seemed to go fine, but after a few days the device completely stopped working. I couldn’t access the dashboard anymore, and nothing was responding.
In the end, I had to reflash the firmware using the official SLZB tool from their website. Fortunately, this restored the device and everything started working again.
I’m not entirely sure if the issue was caused by the latest update, but there was no way to reset or recover the device without reflashing. The good news is that I didn’t lose any of my Zigbee pairings.
I gave up on the MR3 frankly.
I read on GitHub somewhere that Ti chips have a flaw but could be wrong. My issue was every 24 hour or so 40 odd devices out of 65 would drop off requiring a restart OS/restart ZigBee and the addon as well.
After the second one had the same problem I asked SMlight to send me a MR2 since SLZB-06 is/was rock solid and it had the same chip. Added MR2 and it swapped out perfectly. I haven’t added any thread devices to my home yet since I wanted to ensure Z2M is working perfectly.
After the last Z2M update weeks ago now I have a device or 2 drop off. Monitoring right now.
How did it work out? Was interested in the MR3U but I guess it doesn’t sound great anymore
Right, you are running your Zigbee coordinator on the EFR32MG24, I (and I think most others with this issue) are running it on the CC2674P10. When I asked the question of SMLight they said there is a problem with the CC2674P10 just choking when there’s a lot of traffic, then proceeded to walk away completely.
I need to find a different device - and certainly one that isn’t built by SMLight!
