Replies: 101 comments 258 replies
-
|
Great, will try as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
|
By the way, is an updated router firmware also planned? |
Beta Was this translation helpful? Give feedback.
-
|
yes! |
Beta Was this translation helpful? Give feedback.
-
|
hope soon, btw my CC2652P is capable up to 20db? reading below I'm not sure anymore...
|
Beta Was this translation helpful? Give feedback.
-
|
Update done. Wait and see how this one works. |
Beta Was this translation helpful? Give feedback.
-
|
Let's update. My system is up and running since 5 days now. No errors at all!
|
Beta Was this translation helpful? Give feedback.
-
|
A small follow up. My network is fine, no errors at all since late march (first update). I added some devices without any issues as well.
|
Beta Was this translation helpful? Give feedback.
-
|
I just updated my uzg-01 [CC1352P7] from 99250304 to 20250321 |
Beta Was this translation helpful? Give feedback.
-
|
yes only SDK |
Beta Was this translation helpful? Give feedback.
-
|
I am still getting an error for device LYWSD03MMC.
|
Beta Was this translation helpful? Give feedback.
-
|
This has nothing to do with the coordinator firmware, it means the binding table of the device is full. |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 125 I have 8 mmwave presence sensor in another network to avoid their spamming, different channels. There are a lot of errors during start up and the sensors, lights, switchs are not responding, the entire network is down... LOGs |
Beta Was this translation helpful? Give feedback.
-
|
What firmware does work fine for you? |
Beta Was this translation helpful? Give feedback.
-
|
I'm travelling for work, as soon as I arrive home I will answer will, probably Friday. |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk 20250321 is the firmware currently running on coordinator, Zigbee2MQTT version: 2.1.0-1. |
Beta Was this translation helpful? Give feedback.
-
|
Could be some interference maybe, but good to hear it is working |
Beta Was this translation helpful? Give feedback.
-
|
Zigbee2MQTT 2.1.3 |
Beta Was this translation helpful? Give feedback.
-
|
which Coordinator and from which FW upgraded? |
Beta Was this translation helpful? Give feedback.
-
|
Hey i got some issues mine says after update. [2025-03-25 08:33:52] error: z2m: Publish 'set' 'state' to 'slaapkamer licht' failed: 'Error: ZCL command 0x54ef4410000f4a1a/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: AF - dataRequest - {"dstaddr":31686,"destendpoint":1,"srcendpoint":1,"clusterid":6,"transid":26,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,20,1]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))' |
Beta Was this translation helpful? Give feedback.
-
|
Could you provide the debug log of these errors on 20250321? See this on how to enable debug logging. |
Beta Was this translation helpful? Give feedback.
-
|
Update to current firmware revision: 20250321 killed my Z2MQTT
|
Beta Was this translation helpful? Give feedback.
-
|
I did the update thru the interface of the SLZB adapter. Without turning of Zigbee2mqtt in home assistant first. |
Beta Was this translation helpful? Give feedback.
-
|
After a day or 2, devices stoped functioning again. Cant do anything. They do appear online and connected but when i turn a light on or when a state of a device changes when i open a door for example, the state in Zigbee2mqtt stays closed. And the light stays of. So i have just downgraded the zigbee firmware on my SLZB again and now zigbee2mqtt wont connect anymore. Again......... |
Beta Was this translation helpful? Give feedback.
-
|
[11:49:07] INFO: Preparing to start... |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@snhnic How did you upgrade the firmware, can you reproduce it by re-flashing the firmware? |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Sorry for my question but where I can find 20250318 revision? |
Beta Was this translation helpful? Give feedback.
-
|
There is no such revision, only |
Beta Was this translation helpful? Give feedback.
-
|
Sonoff-P and 20250321 running smoothly since yesterday. Currently no BUFFER_FULL errors with that one. |
Beta Was this translation helpful? Give feedback.
-
|
Upgraded from 20240710 to 20250321. |
Beta Was this translation helpful? Give feedback.
-
|
I almost went crazy, downgraded the coordinator firmware, then the add on firmware tried several firmware combinations (add on <> coordinator) and nothing worked. I kinda gave up and was planning to delete everything and repair all devices (125). I left it alone, later that day the network started working again, I changed the coordinator firmware so much that I don't even remember the last firmware installed, it was either the 2024 or 2025 one... I don't know what happened but decide to accepted the unexplained victory 😂 I'm away from home. |
Beta Was this translation helpful? Give feedback.
-
interesting i also have some coordinator and had to roll back to that version which works stable |
Beta Was this translation helpful? Give feedback.
-
|
CC2652RB (slae.sh) upgraded to 20250321 without any issues - Network is up'n'running after Firmware upgrade never experienced any Problem with old 20240710 System up with new FW since ~48h |
Beta Was this translation helpful? Give feedback.
-
|
I flashed my slae.sh stick but now get this z2m: Error: SRSP - SYS - stackTune after 6000ms |
Beta Was this translation helpful? Give feedback.
-
|
OK, After a few hours of troubleshooting, I managed to fix the issue. I had a line: 'disable_led: true' which I removed. I also uninstalled ModemManager, which was preventing zigbee2mqtt from starting after a reboot. |
Beta Was this translation helpful? Give feedback.
-
After the upgrade 1 week ago, my system is still responsive and stable - I have not noticed any problems so far |
Beta Was this translation helpful? Give feedback.
-
Thank you. Commenting |
Beta Was this translation helpful? Give feedback.
-
|
OMG, I had disable_led: false, but removing it seemed to fix mine as well. I don't know for sure, since if I rebooted everything repeatedly it did sometimes work, but once I removed the command it started right up. Let me see if this keeps helping. |
Beta Was this translation helpful? Give feedback.
-
|
I now got almost everything working again with 20250321 on one slzb-07 I changed panid and paired all devices again and on the other slzb-07 I changed the channel and got an empty z2mqqt then moved back to previous channel, got some devices returned by them self, but from the 111 devices still needed to pair most of them. This morning one of the devices disappeared. Still have a lot of repairing to do, mostly automations. But I get it done. It a shame an update can destroy our setup this way! |
Beta Was this translation helpful? Give feedback.
-
|
weird... never had such any issue by upgrading my Coordinator FW |
Beta Was this translation helpful? Give feedback.
-
|
Sonoff-P upgraded from 20240710 to 20250321. |
Beta Was this translation helpful? Give feedback.
-
|
I wanted to add another datapoint to this thread, which seems to overlap with an issue I'm seeing. A few weeks ago all of my Zigbee devices went OFFLINE overnight. I restarted the Zigbee2MQTT Bridge through Home Assistant and everything came back ONLINE eventually. After a bit of head scratching I remembered that I had recently added some repeaters to the network, which I had never used before. I was slightly suspicious of them already because their check in period is sometimes more than 10 minutes, which triggers the default offline alerts in Z2M. I removed them from the network and the problem stopped, but it's hard to be sure because the problem is very intermittent. The smoking gun for me is that although I ejected them from the network, I forgot to unplug one of them and when I permitted join yesterday (for something else) it jumped back on silently and then last night the network went OFFLINE again. Checking the logs in Z2M I saw lots of these messages: Which ultimately led me to this thread. This is how Z2M reports the router: I'm going to remove it from the network for now and on the weekend I will upgrade the coordinator firmware from the current 20240710 to 20250321, add the router back to the network, and report back. Happy to provide more info before and after the upgrade or to send one of these routers to you (I bought four unfortunately). [EDIT] I had misremembered the restart process: I actually turn the PC off and on again 30 seconds later. A soft restart (including a reboot) did not clear the problem originally. Perhaps keeping power going to the Sonoff USB coordinator kept it in the failed state? |
Beta Was this translation helpful? Give feedback.
-
Some computer continues to send voltage to some USB ports even switched off in order to charge devices like smartphone. |
Beta Was this translation helpful? Give feedback.
-
|
A Simple reboot is not a fix when needed at a daily base i think
… I've got the same setup and the same problem it seems. I just updated my
comment below to say a power cycle fixes it. Do you happen to have any
dedicated repeater devices like this in your network?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
--1983143f4cc6ab2283c401ef67
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.=
w3.org/TR/html4/loose.dtd"><html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"></=
head>
<body>
<div dir=3D"auto">
<div dir=3D"auto">A Simple reboot is not a fix when needed at a daily base =
i think =E2=98=BA=EF=B8=8F</div>I have the Exact same issue with the same h=
ardware. And went back to the first available firmware. Now my network is s=
table =F0=9F=98=84. <div id=3D"aqm-original" style=3D"color: black;">
<!-- body start -->
<div class=3D"aqm-original-body">
<div style=3D"color: black;">
<p style=3D"color: black; font-size: 10pt; font-family: sans-serif; margin:=
8pt 0;">Op 22 juli 2025 10:25:17 schreef Rupert Rawnsley <notifications=
@github.com>:</p>
<blockquote type=3D"cite" class=3D"gmail_quote" style=3D"margin: 0 0 0 0.75=
ex; border-left: 1px solid #808080; padding-left: 0.75ex;">
<p></p>
<p dir=3D"auto">I've got the same setup and the same problem it seems. I ju=
st updated my comment below to say a power cycle fixes it. Do you happen to=
have any dedicated repeater devices <a href=3D"https://www.aliexpress.com/=
item/1005006808213878.html" rel=3D"nofollow">like this</a> in your network?=
</p>
<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">=E2=
=80=94<br>Reply to this email directly, <a href=3D"https://github.com/Koenk=
k/Z-Stack-firmware/discussions/545#discussioncomment-13844197">view it on G=
itHub</a>, or <a href=3D"https://github.com/notifications/unsubscribe-auth/=
AM5Y4QDZHUAD6DZKAUSZRW33JXYORAVCNFSM6AAAAABZR7MX4GVHI2DSMVQWIX3LMV43URDJONR=
XK43TNFXW4Q3PNVWWK3TUHMYTGOBUGQYTSNY">unsubscribe</a>.<br>You are receiving=
this because you commented.<img src=3D"https://github.com/notifications/be=
acon/AM5Y4QBOWNLBTKPKUVWIPSD3JXYORA5CNFSM6AAAAABZR7MX4GWGG33NNVSW45C7OR4XAZ=
NRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA2M7OK.gif" height=3D"1" w=
idth=3D"1" alt=3D""><span style=3D"color: transparent; font-size: 0; displa=
y: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height=
: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><Koen=
kk/Z-Stack-firmware/repo-discussions/545/comments/13844197</span><span>@</s=
pan><span>github</span><span>.</span><span>com></span></span></p>
</blockquote>
</div>
</div>
<!-- body end -->
</div><div dir=3D"auto"><br></div>
</div></body>
</html>
--1983143f4cc6ab2283c401ef67--
|
Beta Was this translation helpful? Give feedback.
-
|
I was using stock firmware 20210708 until two weeks ago and I had the same problem. It sometimes takes a few days to fall over; how long have you been running stable? |
Beta Was this translation helpful? Give feedback.
-
|
For those still having the See this on how to enable debug logging. |
Beta Was this translation helpful? Give feedback.
-
Yes, it looks like an env. But where or in which file should i add it. |
Beta Was this translation helpful? Give feedback.
-
|
@raveit65 you can enable it in the addon config when using the edge version |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk it looks like it was not the FW. With the install of 2.6, I also updated the node version. And upgrading from the 20221226 version lead to lost of all devices. I had to switch the channel temporary and restored the db file to make it work again. My setup is now running well:
I will now deactivate the debug log. |
Beta Was this translation helpful? Give feedback.
-
Thanks, that works like a charm. Nice implementation and easy to use. It happens also without |
Beta Was this translation helpful? Give feedback.
-
|
I see new warnings and errors in my logs and i did run the first time in buffer full error when using edge version (2.6.0-dev commit: 2b178087). |
Beta Was this translation helpful? Give feedback.
-
|
I don't know if it has anything to do with the firmware issue, but my Philips GU10 take a long time to update. |
Beta Was this translation helpful? Give feedback.
-
|
I just wanted to chime in on 20250321 and say that this is the most stable firmware I have had. Since I installed it weeks ago, I haven't lost any devices. Usually I would lose routers one by one but so far it just works. I have 12 routers and 1 end device. Using sale.sh Zigbee controller with ha/zigpy. |
Beta Was this translation helpful? Give feedback.
-
|
I also updated last sunday to this version 4 different zigbee networks (aprox 70 devices each) running Zstack CC2652P2 Ethernet coordinator and so far so good. Just to remark I've performed a PoE restart on each oordinator after the update, and also the coordinator_check process (on each process some routers were indentified as out of the net, dont know why) |
Beta Was this translation helpful? Give feedback.
-
|
In this thread I previously reported the Perhaps this is a precursor to the To recap my previous post in this thread: I'm not sure this is a new problem with this firmware particularly as I've seen the same pathology (a dead network) before upgrading. My problems began when I added some dedicated Zigbee routers, but I'm keeping them in place for now to gather more data. |
Beta Was this translation helpful? Give feedback.
-
|
Could you make a new issue report in this repo, if you did not do it already, can you try to disable the Tuya default response (in case you have any Tuya devices)? (#545 (reply in thread)) |
Beta Was this translation helpful? Give feedback.
-
|
@kennymc-c #572 I've added |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Koenkk, I updated my Sonoff Dongle-P coordinator today with a new firmware, but some of my light switches have serious delays. I enabled debug log and saw, e.g.:
Thanks for looking into it! |
Beta Was this translation helpful? Give feedback.
-
|
Does reverting back to the previous fw solve the issue? |
Beta Was this translation helpful? Give feedback.
-
Hi! Haven't checked that yet, I was waiting for your feedback. I will downgrade the dongle and let you know! Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk, I downgraded Z2M to 2.4.0 for now to see if this issue depends on the Z2M version or the FW. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Koenkk,
These are all Tuya branded... 🙄 |
Beta Was this translation helpful? Give feedback.
-
|
I installed the dev version (Edge addon), enabled
The last FW and Z2M version that did not have this problem for me was FW |
Beta Was this translation helpful? Give feedback.
-
|
Which firmware should I use? Launchpad or Other? What is the difference? I run HA together with Z2M. |
Beta Was this translation helpful? Give feedback.
-
Look up your adapter at https://www.zigbee2mqtt.io/guide/adapters/zstack.html#hardware and use the download-link provided. |
Beta Was this translation helpful? Give feedback.
-
|
The Sonoff Zigbee Gateway Pro is not documented, does anyone know what files to use? |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I’m having serious issues with my UZG-01 device running CC2652P7 and firmware 20250321. This device never worked reliably for me. I was trying to switch from a Sonoff USB coordinator to this device, but I cannot get it to operate consistently. The problem is that communication often stops completely. The coordinator stops responding to commands such as SYS_PING. Here’s a sample of what I see in the logs: [1357258945] | Connected client 1 from 192.168.68.203 As you can see, SYS_PING (FE 00 21 01 20) is repeatedly sent, but the device never replies with the expected SRSP or any response. Sometimes a reset helps, other times it requires erasing the NVRAM tables to restore communication. I have been struggling with this for several months, and technical support has no time to assist me. I bought 11 of these devices, intending to use some as routers, but right now I am losing confidence in it. Is there any way to get this device working reliably? Thank you in advance. |
Beta Was this translation helpful? Give feedback.
-
|
I ran exactly into this issue. I had a single UZG-01 w/ CC2652P7 running stable for several months. Then from one day to another after a ZHA restart it completely failed with exactly the communication issue you described. When I tried Z2M it would run into the same issue. Initially I thought the UZG-01 may have failed and ordered a new one, but the issue persisted. Erasing the NVRAM would sometimes get it to work for a short while (minutes to a few hours) before communication would stop again. I tried different firmware versions without success. Then I went on and tried the SMLIGHT SLZB-06p10, which initially seemed to work better, but in the end ran into the same issue. In the meantime I set up a whole new Zigbee mesh but that didn't help either. Also using additional UZG-01 as routers didn't help. My final solution was to split my mesh of about 70 devices, mostly routers, into three separates meshes (one per floor in the house), running three instances of Z2M. Since then everything is pretty stable. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for sharing your experience. I also noticed that the problems start appearing once the network grows to around 70 devices. I tried the SLZB-06p10 as well, but it showed the same behavior. I’ve gone through almost all firmware versions for the UZG ESP and Zigbee chip, but without success. What is frustrating is that the manufacturer officially states support for up to 300 devices (link I really hope the manufacturer can comment on this issue so that we can identify the root cause. I’ve been trying to solve this for half a year already without any clear result. |
Beta Was this translation helpful? Give feedback.
-
|
@PavelVe i'm using HMG-01 clone of UZG-01 with the CC2652P7 and 100+ (50 routers / 50 end) devices, i don't have these problems, but after move from 20240710 to 20250321 i have big LQI degradation. At one point, I tried to significantly reduce the signal level, from +20 to -20, and an inexplicable situation occurred: the average LQI increased significantly, everything looks fine, but sometimes the devices do not work or work with a significant delay. It's kind of mystical. @Koenkk Can you comment on this in any way? |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, i had a major outage in the night (what else). After unplugging and replugging my "SONOFF Zigbee 3.0 USB Dongle Plus,Zigbee Gateway TI CC2652P + CP2102N" without restarting Z2M solved the issue. Never had the issue with "Z-Stack_3.x.0_coordinator_20240710/CC1352P2_CC2652P_launchpad_coordinator_20240710" before, which was really stable for me. Sadly my logs are not complete (hat to try to get it up and running again and restarted Z2M) and i cannot download full logs now (any hint's how todo that on the cli). Anyone of you had the same issue with 20250321? thx |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Iḿ trying to update my Sonoff Zigbee Pro after flashing with Tasmota. However, after uploading the latest hex file, the whole Sonoff seems to crash after some time during the cc.check() command in Berry. Can someone try to help me out here? Thanks. Here is some output from the log:
|
Beta Was this translation helpful? Give feedback.
-
|
After updating my ZBDongle-P I lost all my devices
|
Beta Was this translation helpful? Give feedback.
-
|
hey i have UZG-01 with CC2652P7 , which coordinaor file should i be using? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
When i update from the Tasmota Berry console on a Sonoff Zigbee Bridge pro I get when running the cc.check() command:
Does anyone know whats wrong? |
Beta Was this translation helpful? Give feedback.
-
|
I have tried 20250321 on my UZG-01 device, and have experienced a lot more timeouts in the logs like these: |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Update 2025-07-10: this firmware has now officially been released
Changelog (compared to
20240710)BUFFER_FULLerrorsFirmwares
Beta Was this translation helpful? Give feedback.
All reactions