Replies: 36 comments 69 replies
-
|
This time I can't update firmware: C:>flasher_cc2538.exe -p COM4 -ewv CC1352P2_CC2652P_launchpad_coordinator_20230923.hex During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
-
|
Did you remember to stop Zigbee2MQTT first? |
Beta Was this translation helpful? Give feedback.
-
|
Zigbee2MQTT stopped and USB disconnected. |
Beta Was this translation helpful? Give feedback.
-
|
Make sure to put the dongle in BSL mode |
Beta Was this translation helpful? Give feedback.
-
|
I managed to record version 20230923. For previous testing, there was probably a problem with the WiFi network and therefore I had downtime. |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 65
|
Beta Was this translation helpful? Give feedback.
-
|
(Update 29/10-2023)
|
Beta Was this translation helpful? Give feedback.
-
|
I now am on the 20221226 firmware and was testing 20230901 that started of with no problems. Then suddenly I was starting to have the same problems you discribed. |
Beta Was this translation helpful? Give feedback.
-
|
@smulle48 is 20230922 still ok? |
Beta Was this translation helpful? Give feedback.
-
Unfortunately not. After a few days, it started to get slow, random devices offline, and generally buggy. |
Beta Was this translation helpful? Give feedback.
-
|
When now switching back to |
Beta Was this translation helpful? Give feedback.
-
|
20221226 have always been rock solid. No matter what I do to the network, it simply just work. Atm I'm testing 20230922 once again. So far, after about 24 hours, one Heiman HS2SK has gone offline, and one TuYa TS011F_plug_1 don't report LQI anymore. I've got holiday now, so the family is not 100% dependent on it being reliable, so I will test them both intensively :-) But from what I can remember, 20230922 is more snappy of the two. 20230923 introduce more "popcorn effect" on the lights, then 20230922. But 20221126 is the fastest of them all with "popcorn effect" only one every 20-30 times. |
Beta Was this translation helpful? Give feedback.
-
- 20230922 feedback:-Update: Update firmware. 31 devices did not come online. Had to manually send commands to them while the coordinator is in pairing mode or had to physical try and repair them - 20230923 feedback: |
Beta Was this translation helpful? Give feedback.
-
|
Please also check 20230923 |
Beta Was this translation helpful? Give feedback.
-
|
Just to balance feedback. I've been running 0901 for two weeks almost without issues. Zzh coordinator. Total 202 I had a lot of routers missing in the controller but after making use of the new feature to check coordinator and repair them one by one it has been rather stable. The few issues during these two weeks may also have other causes.
Overall happy with the 20230901 but will give the new ones a go as well. Keep the good work up! |
Beta Was this translation helpful? Give feedback.
-
|
Did you already managed to check 20230923? |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible for that repair feature to be in UI for next release?
…On Sun, Sep 24, 2023, 16:08 Anders ***@***.***> wrote:
Just to balance feedback. I've been running 0901 for two weeks almost
without issues. Zzh coordinator.
Total 202
By device type
Router: 156
End devices: 46
I had a lot of routers missing in the controller but after making use of
the new feature to check coordinator and repair them one by one it has been
rather stable. The few issues during these two weeks may also have other
causes.
- One or two devices went missing the first day or two (restarted them
and they are online since)
- Sometimes it takes 10s for some devices t9 react, likely because
finding alternative routes
- Once when repairing four bulbs at the same time , same ceiling and
breaker, z2m restart without throwing any errors. Have happened with the
same bulbs before a few times On different firmware . If it is relevant
they are physically close to the controller (perhaps massive
rerouting/broadcast storm)
Overall happy with the 20230901 but will give the new ones a go as well.
Keep the good work up!
—
Reply to this email directly, view it on GitHub
<#478 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACOZ7ZZCSTBSBHHRUUMJMLX372BPANCNFSM6AAAAAA5EEM27E>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Agree with adh71, a few comments to balance. I have been running 20221226 and 20230507. Since 20221226 I have had a super stable zigbee network, with no devices losing access. I came from a zigbee network that was having some dropped devices from time to time etc. I installed 20221226, and everything went really bad. I decided to move to channel 25, change the PanID and repaired all devices. Since new year, I have had a super stable zigbee network, running 20221226 and later 20230507. There have been NO dropped devices except some Aqara end-devices due to routers deleted by me. This is expected as the Aqara zigbee 1.2 devices will not roam. I have checked and there is no missing routers in my network as of now.
|
Beta Was this translation helpful? Give feedback.
-
|
Interesting point: I'm fully stable on 20221226 firmware that I'm using since it have been released and I was already using channel 25 since years too. |
Beta Was this translation helpful? Give feedback.
-
|
@KHV8 20230923 still OK? |
Beta Was this translation helpful? Give feedback.
-
|
As mentioned above, I have had one device (a router, a LED controller) dropping of once. System was stable for 2 weeks, and now for 5 days again. |
Beta Was this translation helpful? Give feedback.
-
|
Update, look in original post. |
Beta Was this translation helpful? Give feedback.
-
|
I used the firmwares 20221226 and 20230507. For this test : Thanks for all |
Beta Was this translation helpful? Give feedback.
-
|
With 20230923, what kind of routers where offline? Do they keep dropping off even after repairing them? |
Beta Was this translation helpful? Give feedback.
-
|
Sonoff P version with router firmware, yes droppig off after repairing, after few days.. |
Beta Was this translation helpful? Give feedback.
-
|
I was having issues with 20230507 as routers were going offline after a few days, only solution to have them back online was to restart Z2M. Amount of devices in network: End devices: 52 + Router: 34 |
Beta Was this translation helpful? Give feedback.
-
|
How are the results with 20230922? |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk 20230922 looks good for me but I had to restart my PC on Monday so it is running without interruption only for 3 days, for me not enough to conclude it's working as usually the network is crashing after 5 to 7 days. |
Beta Was this translation helpful? Give feedback.
-
|
After more than 7 days it's still OK even if I saw three of the messages bellow (5 to 7 h interval, each time for the same device)
|
Beta Was this translation helpful? Give feedback.
-
|
After 9 days with FW 20230922, except the exception I got a few days ago and that were without consequence, everything is working fine |
Beta Was this translation helpful? Give feedback.
-
|
After 15days, it's stable with FW 20230922 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Did the 3 devices come back when switching to 20221226? I think it's caused by someone else, so I guess all fws are working fine for you. |
Beta Was this translation helpful? Give feedback.
-
|
After another attempt to test 20230923, my network finally died. I got the following error. That was the last, before it started failed ping
It looks like it failed at this: Friendly name Clever Lader I've tried to look back a few days in the logs, but this is the only error I see |
Beta Was this translation helpful? Give feedback.
-
|
Hello. I'm new to the forum, so sorry for some mistakes if I made them. I've joined as I have a lot of problems with Coordinator/network/Z2M addon stability, I don't know what. I have my environment sitting on Qnap VM and initially when I've installed Sonoff Dongle-P that came with 2021xyz firmware (I don't remember exactly which version), everything worked fine for weeks. Then I wanted to upgrade the firmware to the newest version and from that time everything is a mess. I've tried several different firmware versions, even from 2021, but my network worked fine from 30 minutes, to several hours ending with timeout errors when trying to turn on something. Lately I've tried 20230507, 20230901, now I'm on 20230923 but the issues are still here. What is even stranger, lately I've observed that everytime I update the firmware, not important which one, I need to delete data/coordinator_backup.json and repair all devices as without it every firmware was showing timeout errors almost instantly. I've restarted whole VM, even whole server, HA, Z2M addon, nothing helped. So to conclude after upgrading the firmware, I want now to rip everything form the walls and burn it to the ground... I was even starting from scratch, creating new VM, new HA, and new Z2M with all it's components, changed network channel from 11 to 25, changed PanID, and transmitter power to 14dBm and it helped for a while, but finally still the same problems. Amount of devices in network: 77 (52 routers, 25 end devices)
NWK and No Route errors are even stranger as I don't detect any other devices in this channel, apart from my home. First NWK error I've noticed after 20230923 was loaded to the coordinator and I was half way repairing my devices. With so mamy router devices, network coverage is pretty good, so why no route error?? And additionally errors that I've received today on 20230923 firmware were: SRSP - AF - dataRequest after 6000ms Can enyone help me? I thought that my previous Tuya hub was unstable, but with this, I'm on the edge... UPDATE: After multiple timeout events and NWK table errors later today, I've moved once again to 20221226 for testing, once again deleting backup and repairing all devices... UPDATE 2: 20221226 is tested by me one week, every 1-2 days one random device is having timeout errors, and now NWK table full error apeared, despite no changes in the network or devices from my side. What the hell is going on...? |
Beta Was this translation helpful? Give feedback.
-
|
Version 20230923 is not as good as I originally thought. Every day one to two devices disconnected and had to be paired again. Amount of devices in network: 65 |
Beta Was this translation helpful? Give feedback.
-
|
There has been no problem with version 20230922. |
Beta Was this translation helpful? Give feedback.
-
|
Can you check 20230923 again? If device are disconnected, can you give some more context what actually happens? (what is observed in the log) |
Beta Was this translation helpful? Give feedback.
-
I have had issues with sensors and remotes not being connected for weeks, I have been running on CC1352P2_CC2652P_other_coordinator_20230507 which seemed to indeed have introduced this issue. |
Beta Was this translation helpful? Give feedback.
-
|
Since you repaired deivces, can you try 20230923 once again? |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk I didn't update to 20230923 yet, but I have a number of devices (~10) that just drop their connection and will not come back unless repaired with 20230922 already. |
Beta Was this translation helpful? Give feedback.
-
I will edit my post if firmware 20230923 bugs or works correctly for me in some days. |
Beta Was this translation helpful? Give feedback.
-
|
After some days of testing, 20230923 is working fine for me. I'm going to keep it for further testing |
Beta Was this translation helpful? Give feedback.
-
|
20230923 is still running fine for me after more than 10 days without any errors |
Beta Was this translation helpful? Give feedback.
-
|
I just had https://gist.github.com/deviantintegral/d5980eb26dd0702d9586afefc1292de8 I will try 20230922 later this week.
|
Beta Was this translation helpful? Give feedback.
-
|
On 20230922, I’ve had 2 Tuya door sensors drop offline for many hours, but then come back on their own. This is happening with an Aqara environment sensor as well. But, no crashes or hangs so far, so I think that’s mostly an improvement! |
Beta Was this translation helpful? Give feedback.
-
|
I confirmed 20221226 is not functional, as it completely hung a few hours in. So far, I would say Also, I think it's only the Tuya door contact sensors dropping. The Aqara environment sensor was actually out of battery. |
Beta Was this translation helpful? Give feedback.
-
I guess I was in the minority with 0507 and 0901 working well. I'd have the occasional Ikea blind fall off here or there (not open for the day or closet at night), but it would usually come back online during a checkin. Back to basics, 0923 is working well- up for about 5 days so far. |
Beta Was this translation helpful? Give feedback.
-
|
M'y sisters house : Amount of devices in network: 64 Bridge software Home Assistant (Zigbee2MQTT): 20221226 worked fine: don't know 20230507 worked fine: no, some devices go offline after a few days. 20230922 feedback: no, all routers go offline after a few days. 20230923 feedback: no, some routers offline after 3h. That's strange the same setup as mine, sonoff zigbee 3.0 plus zStack3x0. |
Beta Was this translation helpful? Give feedback.
-
|
Bridge software Home Assistant (Zigbee2MQTT): after a couple of weeks running fine with 0923, tonight started flooding with mem_error. Now I'm moving to 0922. 20221226 worked fine: no, some devices go offline after a few days. 20230507 worked fine: no, some devices go offline after a few days. 20230922 feedback: going to test now 20230923 feedback: no, most of devices goes offline for Mem_error after 2 weeks. |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 74 HW: SLZB-06 Bridge software ioBroker.Zigbee (ZHA): 1.8.24 20221226 worked fine: for some days, then NWK_TABLE_FULL errors 20230507 worked fine: not tested 20230922 feedback: yes, for 13 days now 20230923 feedback: not tested |
Beta Was this translation helpful? Give feedback.
-
|
20230922 feedback: yes, for 17 days now |
Beta Was this translation helpful? Give feedback.
-
|
Bridge Software - Z2M 1.33.1 For my cases, i have Z2M running at 2 different house. House A: SLZB-06:(104 devices) Sonoff P:(48 devices) House B: SLZB-06:(83 devices) |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys. I know it's not asked, but i running 20230901 without major issues since it was released.
@Koenkk when i got the test result's of all others right, the most stable for now is 20230922. thx |
Beta Was this translation helpful? Give feedback.
-
|
I will put all the feedback in an overview sheet soon. Then we can decide what the next step is (probably asking TI for help 😄 ) |
Beta Was this translation helpful? Give feedback.
-
|
Thx for all your efforts |
Beta Was this translation helpful? Give feedback.
-
|
@Koenkk Can we do anything for you? So that the process would be simpler? Maybe some logs? Or anything else? |
Beta Was this translation helpful? Give feedback.
-
|
Nope! I think I have enough info |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 144 |
Beta Was this translation helpful? Give feedback.
-
|
Nope that's not stable.. no idea what is happening.. I have tried so many combinations and nothing seems stable.. might be my coordinator.. |
Beta Was this translation helpful? Give feedback.
-
Flash 0922 back on the coordinator. Do you have updated zigbee2mqtt? |
Beta Was this translation helpful? Give feedback.
-
|
yeah i have now flashed 0922 and its been solid for the last 4 hours, which was not that's case for the last 48 hours |
Beta Was this translation helpful? Give feedback.
-
|
Stay on it, just to see what's going happen. |
Beta Was this translation helpful? Give feedback.
-
|
@cloudbr34k84 Do have also Wifi at you place? If yes on which channel is your zigbee network? recommended channel is 25 to avoid interferences with some wifi channels. Please also check this. |
Beta Was this translation helpful? Give feedback.
-
|
Zigbee2MQTT version 1.33.1-dev commit: d027b852 Every other week I have to unplug the Texas Instruments LAUNCHXL-CC1352P-2 from the Raspberry Pi 4 because it locks the serial port. |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 86 Edit: Flashed 0922 to see if it is any better. |
Beta Was this translation helpful? Give feedback.
-
|
With 0923 I had tons of UART disconnection errors. With 0922 they seems to have gone or at least become very infrequent. |
Beta Was this translation helpful? Give feedback.
-
|
I've made a spreadsheet with all the results. Looks that 20230922 is very good indeed. I've created a thread on the TI forum to figure out what went wrong from 6.20.00.29 and upwards) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Another thought in terms of possible cause.
I have multiple lights that are also Routers and they are joined to my
network.
Currently I am not controlling them via ZigBee, so we just cut the power
via the normal light switch.
Maybe this could be the cause?
…On Tue, Nov 7, 2023, 03:21 chris-1243 ***@***.***> wrote:
I just checked my log and i saw some MAC no ack (233). 4 warnings in 3
weeks.
The devices are connected and the error always happend while pinging the
device.
No idea if it may help you
—
Reply to this email directly, view it on GitHub
<#478 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACOZ73HTM3WZO2BQTEH7IDYDFBF7AVCNFSM6AAAAAA5EEM27GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TIOJRG43TI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Für sure, Routers included in Zigbee should stay online and not cuttet from Power Anytime they will be offline all Routes via them will disappear and need to build from Mesh again |
Beta Was this translation helpful? Give feedback.
-
|
@BradleyFord As stated by @lux73 See here for an good explanation: https://www.blackhillsinfosec.com/understanding-zigbee-and-wireless-mesh-networking/ Just let all your routers power on and see if this improves things. |
Beta Was this translation helpful? Give feedback.
-
|
Amount of devices in network: 93 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Many thanks for all your feedback, based on TI input I've compiled 2 new test firmwares: #483 |
Beta Was this translation helpful? Give feedback.
and others
-
UPDATE: Let's continue in #483
Since some users are having issues with the
20230507firmware which they didn't have with20221226, I've compiled 2 new test firmwares. This is a continuation of #474.Download: 20230922_20230923.zip
First start by testing
20230923, if that doesn't work try20230922. If20230923works fine, there is no need to try20230922When providing feedback copy and comment the template below:
Changes in these firmwares compared to
20221226:20230922=20221226+ fixes for Popp/Danfoss TRVs become unresponsive with CC2652P zigbee2mqtt#1347820230923=20221226+ fixes for Popp/Danfoss TRVs become unresponsive with CC2652P zigbee2mqtt#13478 + TI SDK 6.20.00.29If this firmwares works well, I will provide a similar firmware for the 6.30.00.84 and 6.40.00.13 TI SDK, in this way we narrow down where things break. Happy testing 😄
Beta Was this translation helpful? Give feedback.
All reactions