Replies: 110 comments 222 replies
-
|
I tried flashing SLZB-06P7 on CC1352P2_CC2652P_other_coordinator_20240710.hex but that didn't seem to work, granted It was my first time trying to flash via USB. It just wouldn't verify for me. And the adapter wouldn't start afterwords. I did managed to flash 20240316 over USB again and it works again. I'm not sure I did something wrong or not, as using a different fw image seemed to work fine. |
Beta Was this translation helpful? Give feedback.
-
|
Most likely your SLZB-06P7 uses CC2652P7 chip, so you need to use CC1352P7_coordinator_20240710.hex firmware. |
Beta Was this translation helpful? Give feedback.
-
|
That is probably it, I'll try again later. My bash history showed me using CC1352P7_coordinator when restoring the old version but not when trying the new version. 😭 |
Beta Was this translation helpful? Give feedback.
-
|
deleted since I don't think it's a firmware issue |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @Koenkk, what are the improvements for ZigBee on SDK 7.41? |
Beta Was this translation helpful? Give feedback.
-
Hello my friend, I have received new router boards and I burned your firmware. At first the link quality was 68 when I made the dbm 20. I started to change it randomly to 5 10 19, suddenly the link quality went to 255 _ Unfortunately it doesn't stay like that and sometimes I find the link quality goes down to 50 - 60 again Any ideas? I am using the hi link 5v 5W to power the board but not sure this would be power issue? Does the link quality fluctuates with any body else? |
Beta Was this translation helpful? Give feedback.
-
Hi! I was just passing by while reading your comment and wanted to mention something that may be off-topic to your initial question but seems important to me. Increasing the signal transmission power isn’t necessarily a good thing for two reasons. One reason might explain your LQI fluctuations, though.
In my case, setting the Zigbee coordinator beyond 9dB led to many recurring "MAC network route error" issues. If I stay at 9Db I don't have any issue at all.
By the way, I think a good practice that should be mentioned in Zigbee2MQTT is to pair each device with the coordinator/router without any amplification. Then, if the signal is okay but a bit weak, you can set it to 5 or 9dB to help the coordinator avoid losing the end devices from the network, for example. But don’t go beyond 9dB because, either way, you’ll end up with more interference, or the devices won’t be able to communicate properly with the coordinator if you increase the dB too much. So, having a good LQI in only one direction won't help much. A strong LQI like this might be useful only between the router and coordinator, which both have the ability to boost up to 20dB, but it could negatively affect everything else :(. |
Beta Was this translation helpful? Give feedback.
-
Hi! But as it was mentioned several times in this thread, more TX power brings more signal interference. I can suggest you not much and mostly common:
|
Beta Was this translation helpful? Give feedback.
-
Hello Sorry for late reply, but I was still watching and testing and also waited for newly designed routers to arrive. I want to mention that I was installing this system in a factory with huge interference, crazy thick walls and slabs. Making both routers and coordinator at 20dbm changed the network stability by over 90% Can not tell you how much I was suffering before that, but now it is crazy stable (but only the connection is stable) The zigbee network it self is not, because I am using many Tuya devices +100 and they are reporting like crazy flooding the network with too much information at the same time. Once I find a solution for this problem I will share all that experiment and results with the community... Many thanks for agriadsi for his firmwares additions, it really a life saver .... thanks a lot man... @agriadsi |
Beta Was this translation helpful? Give feedback.
-
@hesham1216 : you can tweak manually the reporting min/max intervals for your tuya devices:
|
Beta Was this translation helpful? Give feedback.
-
|
Coordinator Device: SONOFF Zigbee 3.0 USB Dongle Plus (CC2652P)
After upgrading to version 20240710, two devices showed an error and had to be again paired. Now the device seems to be stabilized. |
Beta Was this translation helpful? Give feedback.
-
|
There was no problem after 4 days of operation. |
Beta Was this translation helpful? Give feedback.
-
|
Hi KoKolaj. Which firmware did you install? I found these two in the zip file |
Beta Was this translation helpful? Give feedback.
-
Flashed it successfully, will post a reply to my own thread for any issues, but didn't see any devices (that I've noticed) not pair correctly after a flash. So will wait and see, so far all looking good. |
Beta Was this translation helpful? Give feedback.
-
|
Had the firmware for 2 weeks, has been rock solid and my network definitely feels overall more responsive! |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 141 all devices work stably |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 132 [End devices: 90 - Router: 42] |
Beta Was this translation helpful? Give feedback.
-
|
Over a month and the coordinator + mesh is rock solid stable with this version (as it was for 20230922). |
Beta Was this translation helpful? Give feedback.
-
|
Would love to know more about your setup. Having a lot of issues w/ the Aqara sensors. |
Beta Was this translation helpful? Give feedback.
-
|
Most of my routers (if not all) are hue, they are working the best. I just have ~15 aqara door/window sensors and 2x P1 motion sensors (modded for faster response times). I am using an: SONOFF Zigbee 3.0 USB Dongle Plus,Zigbee Gateway TI CC2652P + CP2102N Zigbee USB Stick |
Beta Was this translation helpful? Give feedback.
-
|
Can I use the baud rate 460800 on this firmware? |
Beta Was this translation helpful? Give feedback.
-
what effect do you expect from such a port speed? |
Beta Was this translation helpful? Give feedback.
-
|
To my understanding the 460800 version of 20240316 was intended to test if high device count or sensor rich deployments profit due to the then higher bandwidth between z2m and the transceiver. I am running this x4 20240316 firmware currently. Looking at the bindiff, it is a simple 1 byte edit. However I fail to determine the proper place in the 20240710 firmware for that edit. Can you help us out with a 460800 version? Or should all on the x4 version revert back to 115200? |
Beta Was this translation helpful? Give feedback.
-
|
I changed my baud setting back to 115200 to test this. I never attempted to test it with 460800. I was on x4_20240316 and recently most of my devices was offline. I was forced to "test" the 20240710. |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 23 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, no problems here with my SLZB-06. Just updated and then rebooted it. |
Beta Was this translation helpful? Give feedback.
-
|
My also works initially, but then suddenly stop after an hour or so. Requesting mesh map speed up the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Tried requesting a mesh map without any issues. After 8h everything seems to work properly, even aqara devices are reporting properly without touching them. Quite strange. My SLZB-06 is conneted via POE, and no BT proxy anabled. |
Beta Was this translation helpful? Give feedback.
-
|
just updated. Time will tell if there is an issue. updated, rebooted and then waited a few minutes and asked for a map. So far, so good. |
Beta Was this translation helpful? Give feedback.
-
|
I posted a separate response but so far 2 to 3 hours and everything was good the only thing that happened was all 4 of my Ikea tradfri Outlets were offline/not responding. all I did was unplug them and plugged them back in and they came back. |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 79 (End devices: 51 Router: 28) |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 85 (End devices: 45, Router: 40) |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 45 (End devices: 26, Router: 19) |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 89 (End devices: 61 Router: 28) Update: I've tried 20240710 one more time, it worked ok for two days, but on third Buffer full error, restarting RPi4 host repairs the issue, but it works for few minutes and again Buffer full error and nothing is working anymore. Additionally I'm having random network slowdowns with error Read response to (address of the device) failed. |
Beta Was this translation helpful? Give feedback.
-
Where is the router firmware from? Do you have a link? |
Beta Was this translation helpful? Give feedback.
-
|
It's available directly via SLZB-06 coordinator management page, but I've tried also 20240710 and the results were the same. |
Beta Was this translation helpful? Give feedback.
-
That's interesting. As far as I can see, @Koenkk didn't publish a router firmware based on the newest stack. So I really don't know if the firmware you are using is the same as the one we are discussing about, if you flash a firmware which originates from somewhere else. |
Beta Was this translation helpful? Give feedback.
-
|
@SmolikOne I dont see anything newer than below - even the router version disappeared for me. I mentioned that I had to power cycle other routers here
|
Beta Was this translation helpful? Give feedback.
-
|
Now I see and you are right, 20240716 I'ts SMLIGT modification of Koenkk 20240710 firmware (apparently). But as said previoisly, I've tried also Koenkk 20240710 and errors were exactly the same. |
Beta Was this translation helpful? Give feedback.
-
|
Coordinator Device: SONOFF Zigbee 3.0 USB Dongle Plus (CC2652P) Amount of devices in network: 61 (Routers: 31, End devices: 30)
|
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 43 (End devices: 36 Routers: 7) Updated and rebooted the device, and that went well. 2 hours in, and I noticed all 4 of my Ikea Tradfri outlets devices were not responding, so I just unplugged them and plugged them back in, and they came back. Perhaps if I left them, they would have come back by themselves, but considering they are critical to my network, I wanted to make sure they were working first |
Beta Was this translation helpful? Give feedback.
-
|
its been 2 weeks now on 20240710 and overall, this has been really good. There is less lag and more preformance increases. thank you devs and team! |
Beta Was this translation helpful? Give feedback.
-
|
This is new.... Permit join just disables after fiew seconds.... [2024-09-09 12:04:42] error: zh:controller: Failed to keep permit join alive: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms |
Beta Was this translation helpful? Give feedback.
-
Your adapter has crashed unfortunatelly. If 20240315 is working fine for you, I would remain on this firmware for the time. I have some Ikea devices (router and end devices) and they all work fine |
Beta Was this translation helpful? Give feedback.
-
Its not crashed... its working with devices, and afer 3-4 retrys it stayed in pairing mode. |
Beta Was this translation helpful? Give feedback.
-
https://www.zigbee2mqtt.io/guide/faq/#common-error-codes I let you read. Z2M was able to recover but it crashed. What procedure do you follow while flashing your adapter ? It is important to cleanly stop Z2M then you may flash your coordinator. |
Beta Was this translation helpful? Give feedback.
-
|
This was common for me over that last week.
Reflash the firmware to that coordinator
…On Mon, 9 Sept 2024, 8:13 pm dankocrnkovic, ***@***.***> wrote:
This is new....
Permit join just disables after fiew seconds....
[2024-09-09 12:04:42] error: zh:controller: Failed to keep permit join
alive: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms
Error: SRSP - AF - dataRequestExt after 6000ms
at Object.start
(/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:59:23)
at /app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:300:45
at Queue.execute
(/app/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26)
at ZStackAdapter.dataRequestExtended
(/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:1245:9)
at
/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:681:13
at Queue.execute
(/app/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
at GreenPower.permitJoin
(/app/node_modules/zigbee-herdsman/src/controller/greenPower.ts:261:13)
at Controller.permitJoinInternal
(/app/node_modules/zigbee-herdsman/src/controller/controller.ts:311:13)
at Timeout._onTimeout
(/app/node_modules/zigbee-herdsman/src/controller/controller.ts:301:25)
—
Reply to this email directly, view it on GitHub
<#505 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOB2WBF5TMXW43EJ56KO2C3ZVVYGHAVCNFSM6AAAAABK2RNKGCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJYHEZDMMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Normally i would do a git bisect action to find the culprit commit for weird and unknown issues with a software package. For the record i got mentioned issues with zigstar UZG-01 bridge. I tried to update 2 times to 20240710 firmware but everytime i run in weird connection issues. I will roll back to stable 20240316 for the moment |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 26 (End devices: 22 Routers: 4) Sonoff ZBMini worked fine: yes |
Beta Was this translation helpful? Give feedback.
-
|
On 4 occasions I have attempted to access the webUI of UZG-01 the coordinator rebooted - lost and re-established connection within a few seconds. The last time it happened UZG-01 was on 23 hrs uptime. I suggest you take a look at possible issues when coordinator busy a connection over the network for management could cause the connection to reset? I have not tried to setup a continuous ping to test what happens when I try to access the webUI, but this is something I intent doing and will provide feedback. |
Beta Was this translation helpful? Give feedback.
-
Upgraded from 0507 to 0710 and everything stopped working with MAC transaction expired errors in Zigbee2MQTT logs and routers disconnected in map. Tried rebooting routers to no avail. Read some of the comments here, panicked and downgraded to 0315. Restarted Zigbee2MQTT and all back to normal. |
Beta Was this translation helpful? Give feedback.
-
|
experienced the same with 20240710 and a completely fresh HA installation and a z2m network built up from scratch with 20+ devices. After a couple of hours I got lots of "MAC transaction expired errors". |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, However, after upgrading, I observed delays in turning bulbs on/off, groups would be not behaving as groups - only one or two members of a zb group would respond to a on/off command. Did anyone else have similar symptoms?
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hi @chris-1243 ,
This resulted in After just dumping the entire flash/NVRAM contents of the 'old' dongle and uploading that into the 'new' dongle, I was able to have the 'new' dongle behave as the 'old' dongle. From there (starting on the original Sonoff firmware) I was able to upgrade to 20240710. But also there I was faced with Groetjes, |
Beta Was this translation helpful? Give feedback.
-
|
A different, way to change the dongle is like this. Might be easier to do in some situations
All the mains will connect to the new coordinator, as they do not store the IEEE addr during power off. All the battery devices do not store the IEEE addr Super easy and fast to do if you have a laptop as your Z2M machine. |
Beta Was this translation helpful? Give feedback.
-
|
Why do not you use Below how I do:
I do not need more... The main difference is I already use a non-default PanID, extended PanID and network keys |
Beta Was this translation helpful? Give feedback.
-
|
Hi @KHV8, |
Beta Was this translation helpful? Give feedback.
-
Hi @chris-1243 , I figured Sonoff made it not 'too easy' to upgrade the firmware without having to do something to the device itself (e.g. removing the casing and pressing some microswitch like a boss). Groetjes, |
Beta Was this translation helpful? Give feedback.
-
|
Following testing over the last couple of weeks I now have feedback, which I hope might be of some value to some. The physical area where the ZB network has been deployed is divided in 4 quartiles. In every quartile there are 10 routing-devices (Tuya) and 20 end-devices (Tuya). My initial deployment was connecting everything to coordinator (flashed with 20240710 FW). With this deployment the coordinator (UZG-01 or SLZB06P7) was disconnecting every few minutes and I had a lot of communication errors with the routing-devices. What completely solved the communication errors and the coordinator disconnections was the introduction of a dedicated router (UZG-01) in every quartile and connecting all devices in every quartile to the dedicated router for the quartile. I have therefore concluded that the coordinator (UZG-01 and/or SLZB06x) when flashed with FW 20240710 runs stable when it communicates with dedicated routers (using better router-devices might have solved the issue as well, but have not tested this scenario). To stress test the system, all end-devices have been configured to report instantly on every change and they have been running faultless for a few days. No disconnections or errors of any sort. Just to provide an idea of scale, the ZB network has been deployed over a 1150sqm surface area with around 160 devices, one coordinator (UZG-01) and 4 dedicated routers (UZG-01). One last observation is that Tuya devices are definitely not the right way to go, especially on larger ZB networks, for a number of reasons, the primary being stability, configurability and reliability. |
Beta Was this translation helpful? Give feedback.
-
|
From my experience with various Tuya based devices (temp/humidity sensors, presence detection, etc) I have to agree 100% with your conclusion. These devices are cheap for a reason, the base firmware is quickly/poorly developed with no subsequent refinements. Unlike slightly more expensive devices (like Aqara), there is a lack of parameter configurability needed to stabilize one's network or better refine one's automation routines. Cheaper is not always better. |
Beta Was this translation helpful? Give feedback.
-
Will there be router firmware update as well? Are there interesting corrections in the base SDK that router update would benefit from? |
Beta Was this translation helpful? Give feedback.
-
|
Opening the device shouldn't be necessary. At this point I have flashed well over 30 zbdongle-p's multiple times and have never needed to do anything other than use the sonoff command line switch.
…________________________________
From: djurny ***@***.***>
Sent: Thursday, October 3, 2024 5:12:00 PM
To: Koenkk/Z-Stack-firmware ***@***.***>
Cc: jerrm ***@***.***>; Manual ***@***.***>
Subject: Re: [Koenkk/Z-Stack-firmware] Z-Stack_3.x.0 coordinator 20240710 feedback (Discussion #505)
@djurny<https://github.com/djurny>
Why do not you use --bootloader-sonoff-usb while using with cc2538-bsl to access the bootloader ? No need to open your dongle-P.
Hi @chris-1243<https://github.com/chris-1243> ,
The only way how I got cc2538-bsl<https://github.com/git-developer/ti-cc-tool> working is when I put my Sonoff dongle in bootloader mode manually, by holding down the boot button/microswitch on the PCB while powercycling the dongle.
image.png (view on web)<https://github.com/user-attachments/assets/d87f90ad-ac99-484d-bab4-439bb789b1c5>
Entering the bootloader mode without pressing anything only worked for me when I flipped the DIP for hardware flow control on the PCB.
I figured Sonoff made it not 'too easy' to upgrade the firmware without having to do something to the device itself (e.g. removing the casing and pressing some microswitch like a boss).
Groetjes,
—
Reply to this email directly, view it on GitHub<#505 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC4DUIMN4GHTHK53ZXVLZQLZZWXKBAVCNFSM6AAAAABK2RNKGCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBTG42TMMI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
(sorry if this is not the location for this comment. feel free to redirect me to the right location if needed) I upgraded since I was having issues pair some ikea remotes and read that an updated firmware might help. My paired devices still as good as ever. I havent noticed any dropped devices. If i unplug and plug devices they reconnect without issues. I just cannot pair or re-pair anything now. If I try to re-pair devices, they wont and be disconnected. Im kinda new on this. Im not sure if there is any particular logging I can provide. I could not find anything marked as error or evidently problematic on first glance. (I have almost 40 devices so enabling debug logging does print a lot of stuff.). Any tips on how to fix this? is downgrading safe? |
Beta Was this translation helpful? Give feedback.
-
|
General tip is to first be sure to always follow all these best practices regardless of issue or root cause before troubleshooting any deeper -> https://community.home-assistant.io/t/zigbee-network-optimization-a-how-to-guide-for-avoiding-radio-frequency-interference-adding-zigbee-router-devices-repeaters-extenders-to-get-a-stable-zigbee-network-mesh-with-best-possible-range-and-coverage-by-fully-utilizing-zigbee-mesh-networking/515752 |
Beta Was this translation helpful? Give feedback.
-
|
It seems like I have the same issue: Koenkk/zigbee2mqtt#24314 |
Beta Was this translation helpful? Give feedback.
-
|
Unreliable..zha in HA goes into initialisation and then fail retry every now and then. Had to revert back to Firmware: core: v2.5.6 / zigbee: 20240315 |
Beta Was this translation helpful? Give feedback.
-
|
I have a slzb-06p7. There is definitly something wrong with this firmware. After a while it got into a busy cycle, devices responded slowly and the zigbee chip overheated to 65C (seet attached graph). It also corrupted its internal state, after a restart the network would not start (Error: network commissioning timed out). |
Beta Was this translation helpful? Give feedback.
-
|
Check which version of slzb-06 core you are running. I ended up downgrading to 2.3.6 as i found after couple of days / week the interface would be extremely slow. Reboot always fixed it. But also was able to correlate it to SLZB core update |
Beta Was this translation helpful? Give feedback.
-
Fast degrading ZHA - up & down / connect & disconnect - after several restarts of HA / HA VM NAS - mesh with this firmware 20240710. Comms to Sonoff routers (P+E) are A-oke. Return comms to coordinator are showing all 0.
Hardware:1x Sonoff ZBDongle-P as coordinator 3x Sonoff ZBDongle-P as router 3x Sonoff ZBDongle-E as router |
Beta Was this translation helpful? Give feedback.
-
|
Reverted back to fw 20221226 and had a successful restart and full restore of my ZHA in HA Supervised in VM on NAS.
Keep you'll posted on the progress... |
Beta Was this translation helpful? Give feedback.
-
|
Also had problem with my SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P. After updating to 20240710 i got error I would highly recommend to backup data folder before the update! Amount of devices in network: 35 (routers: 26, end devices: 9) |
Beta Was this translation helpful? Give feedback.
and others
-
Update 2024-08-24:
The
20240710firmware has been officially released. Feel free to continue discussing the firmware in this thread. Note that I will not actively monitor this discussion anymore. In case of issues with the firmware, report a new issue here. Make sure to include:Welcome to another firmware testing thread!
After testing a countless amount of different firmwares (many thanks to @nick4275 for all the testing!), we (very likely 🤞) found the root cause of the issues causing the
20230507firmware to crash and managed to fix these (together with help from Texas Instruments).Even more excitingly, this firmware is built on the latest TI SDK (7.41).
This is a continuation of #474, #478, #483 and #496.
Download: 20240710.zip
When providing feedback copy and comment the template below:
If no breaking issues are found, this firmware will be officially released on 24 August.
Beta Was this translation helpful? Give feedback.
All reactions