I notice that there’s no mention of ZHA in this thread. I wonder if Z2M is playing a part in this too.
I am running ZHA, and I can confirm this is an issue here as well.
Same here , rollback to 2.3.6 and seems to be ok.
Also noticed that update to 2.5.8 has been removed.
Another failure overnight on 2.3.6 with the HA integration disabled. Only ever seems to happen overnight.
a new firmware dev version is out in the WEBUI v2.6.8.dev16
, I have purchased a spare 06M device, I have flashed it, and WEBUI is now working again in MacOS. I’ll keep an on it over the next few days and report back, before I flash it to my production hardware.
Release notes:
Fixes to prevent device slowdowns.
Fixed an issue where the device would hang indefinitely due to a crash; now the device reboots.
SLZB-06M now supports channel scanning on all ZigBee firmware versions.
SLZB-06M can now change its IEEE address. PLEASE NOTE: The IEEE address on the SLZB-06M can only be changed once! ONCE THE IEEE ADDRESS IS CHANGED ON THE SLZB-06M, IT CANNOT BE CHANGED AGAIN OR REVERTED BACK TO ORIGINAL ONE. Please proceed carefully and make any changes at your own risk.
SLZB-06M can now parse metadata from custom ZigBee firmware (for example, fw version), if available. Both V1 and V2 manifests are supported.
Performance updates for Web server.
Localizations updated.
WPA-3 networks are no longer displayed as open networks.
The "Installed" badge now appears in the core firmware update menu as well.
Added time zone support for Italy.
there also a new Zigbee Firmware 20241127
I’ve been running that firmware for the past couple of days, with theqtesr version of z2m and my network just went down again.
Oddly, I could access the web ui without issue this time and conduct the reboot from there. Once it rebooted, everything came back online.
I have an issue where as soon as I try to access the webui, then Z2M crashes, and the webui fails to load, and the device locks up and crashes, and only a power cycle fixes the issue. reported this the SMLIGHT.
I have been running their latest dev18
firmware for 5 hours now, and so far so good, I’ll keep you guys updated. lets keep our fingers crossed the freezing and crashing bug is under control.
I’m running 2.5.8 and had previously set up an automation to power cycle the PoE port the radio is running on every 24 hours to address a different unrelated issue well before upgrading to 2.5.8, during which I never really hit the slowdown and then dead issue. I turned off the restart automation as per recommended by someone in the Z2M Discord, and so now I’m very much hitting this slow down issue. I’ve setup an uptime monitor poking the web UI on the device, and this is what I saw through the last time it slowly became unresponsive…
I’m going to kill off the HA integration and continue monitoring.
24 hours later after disabling the integration, 2.5.8 hasn’t exhibited any of the symptoms I had before.
Lucky I stumbled on this thread, I was about to buy one. Sounds like it’s unstable.
using dev23 atm seems loads more stable.
Agreed. dev23 and the latest z2m are being kind to me.
And with that, dev25 is out.
It’s been over a week, I haven’t seen any sort of regression under 2.5.8 after removing the HA integration.
Unfortunately I had it happen a couple of times on that version with the integration disabled.
I’ve since re enabled the integration and since using the latest z2m and dev firmware, it’s been stable for over a week.