Z-Stack_3.x.0 coordinator 20230922/20230923 feedback

[Koenkk]

UPDATE: Let's continue in #483

Since some users are having issues with the 20230507 firmware which they didn't have with 20221226, 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 try 20230922. If 20230923 works fine, there is no need to try 20230922

When providing feedback copy and comment the template below:

- Amount of devices in network:
- Bridge software (Zigbee2MQTT/ZHA):
- 20221226 worked fine: yes/no
- 20230507 worked fine: yes/no
- 20230922 feedback:
- 20230923 feedback:

Changes in these firmwares compared to 20221226:

• 20230922 = 20221226 + fixes for Popp/Danfoss TRVs become unresponsive with CC2652P zigbee2mqtt#13478
• 20230923 = 20221226 + fixes for Popp/Danfoss TRVs become unresponsive with CC2652P zigbee2mqtt#13478 + TI SDK 6.20.00.29

If 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 😄

[KoKolaj]

This time I can't update firmware:

C:>flasher_cc2538.exe -p COM4 -ewv CC1352P2_CC2652P_launchpad_coordinator_20230923.hex
Invoking bootloader by method 1 (default)
Opening port COM4, baud 500000
Reading data from CC1352P2_CC2652P_launchpad_coordinator_20230923.hex
Your firmware looks like an Intel Hex file
Connecting to target...
Traceback (most recent call last):
File "cc2538-bsl.py", line 1247, in
File "cc2538-bsl.py", line 409, in sendSynch
File "cc2538-bsl.py", line 302, in _wait_for_ack
main.CmdException: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "cc2538-bsl.py", line 1362, in
NameError: name 'exit' is not defined
[21032] Failed to execute script cc2538-bsl

[smulle48]

Did you remember to stop Zigbee2MQTT first?

[KoKolaj]

Zigbee2MQTT stopped and USB disconnected.

[Koenkk]

Make sure to put the dongle in BSL mode

[KoKolaj]

I managed to record version 20230923.
All devices (65) online.
So far I am testing about 30 minutes :-)

For previous testing, there was probably a problem with the WiFi network and therefore I had downtime.
Zigbee Channels I have from the beginning at 11
I had a WiFi net on the channel 5.
Now I have a WiFi channel for 13 and there are no problems.
Is it possible for channel 11 and 5 to distract each other?

[KoKolaj]

Amount of devices in network: 65

• Bridge software Zigbee2MQTT
• 20221226 worked fine: yes
• 20230507 worked fine: no
• 20230922 feedback: ---
• 20230923 feedback: yes - 65/65 devices online

[smulle48]

(Update 29/10-2023)

• Amount of devices in network: 57
• Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT
• 20221226 worked fine: yes
• 20230507 worked fine: no
• 20230922 feedback: Testing atm. All devices online. After upgrading, all bindings between buttons and lights are gone. Have to bind, then unbind and then bind again to make it work
• 20230923 feedback: After a few hours, devices started to become offline. Not possible to get them online again.

[snippem]

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.
Slow unresponsive network( routers that do not respond etc), devices that would not pair end devices that stop working. First thing I did was flashing 20221226 but that did not solve the problem. The problem I had was that my WiFi network decided to use channel 3 and my ZigBee channel was 15. After setting a static WiFi channel to 9 all the problems went away. Not saying that this the same situation but it's not always the firmware that is causing problems.

[Koenkk]

@smulle48 is 20230922 still ok?

[smulle48]

@smulle48 is 20230922 still ok?

Unfortunately not. After a few days, it started to get slow, random devices offline, and generally buggy.

[Koenkk]

When now switching back to 20221226, everything keeps working again?

[smulle48]

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.

[cloudbr34k84]

Initial Log.txt

• Amount of devices in network: 124
• Bridge software: Zigbee2MQTT
• 20221226 worked fine: Yes ish
• 20230507 worked fine: Yes ish

- 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:

[Koenkk]

Please also check 20230923

[ahd71]

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!

[Koenkk]

Did you already managed to check 20230923?

[BradleyFord]

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>

[KHV8]

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.

• Amount of devices in network: 52 routers and 66 endpoint
• Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT
• 20221226 worked fine: yes
• 20230507 worked fine: yes
• 20230922: Working fine. Installed on 21oct. Running fully stable for 7 days. Noticeably faster/more responsive than 20230923
• 20230923 feedback: NOT good, running 20230922 now.. I stable network for 14 days and then 1 device lost access. Afterwards stable for 12 days and another device dropped, this time a battery powered switch. The day after one more.

[zen2]

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.

[Koenkk]

@KHV8 20230923 still OK?

[KHV8]

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.
I can try 20230922 if you whan't me to. I will install 20230922 when/if I get next device dropping. Will keep updating with findings.

[KHV8]

Update, look in original post.
Will install 20230922 on Saturday and keep updating any findings here

[alesoft73]

I used the firmwares 20221226 and 20230507.
As far as I'm concerned the best and most stable 20230507

For this test :
Amount of devices in network: 53 Device 14 router
Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT
20221226 worked fine: yes
20230507 worked fine: yes ( favorite )
20230922: work fine! (update 03/10/23)
20230923 feedback: 2 router off line

Thanks for all

[Koenkk]

With 20230923, what kind of routers where offline? Do they keep dropping off even after repairing them?

[alesoft73]

Sonoff P version with router firmware, yes droppig off after repairing, after few days..

[Fabiancrg]

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
Bridge software : Zigbee2MQTT
Adpater: Sonoff ZDongle-P
20221226 worked fine: yes
20230507 worked fine: no, issues every few days (3 to 5 days I think then restart Z2M to have them back)
20230922 feedback: Upgraded Thursday 5th of October at 05:10 PM, currently running
20230923 feedback: all routers were offline after a week, everything back after Z2M restart. After 6 hours, all routers are offline agian, will switch to 20230922 now

[Koenkk]

How are the results with 20230922?

[Fabiancrg]

@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.
When using 20230507 I noticed that each time I restarted my PC, it was ok for another 5-7 days.

[Fabiancrg]

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)

Exception` while calling fromZigbee converter: Command 0x70ac08fffe3a46ac/1 manuSpecificTuya.mcuGatewayConnectionStatus({"payloadSize":1,"payload":1}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> ZDO - extRouteDisc - {"dstAddr":39755,"options":0,"radius":30}' failed with status '(0xc7: NWK_TABLE_FULL)' (expected '(0x00: SUCCESS)'))}

[Fabiancrg]

After 9 days with FW 20230922, except the exception I got a few days ago and that were without consequence, everything is working fine

[Fabiancrg]

After 15days, it's stable with FW 20230922

[blacknell]

• Amount of devices in network: 26 (18 online, 8 offline) - 3 offline should be online - see my issue
• Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT
• 20221226 worked fine: yes (a long time ago)
• 20230507 worked fine: yes but some light switches are partially joined
• 20230922 feedback: did not try
• 20230923 feedback: no change in behaviour, 3 devices still only partially online

[Koenkk]

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.

[smulle48]

After another attempt to test 20230923, my network finally died.

I got the following error. That was the last, before it started failed ping

error 30-09-2023 22:27:12: Exception while calling fromZigbee converter: CommandResponse 0x00000000e202cc33/242 greenPower.response({"options":0,"tempMaster":57375,"tempMas> debug 30-09-2023 22:27:12: Error: CommandResponse 0x00000000e202cc33/242 greenPower.response({"options":0,"tempMaster":57375,"tempMasterTx":14,"srcID":3791834163,"gpdCmd":2> at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7)

error 30-09-2023 22:27:24: Exception while calling fromZigbee converter: CommandResponse 0x00000000e202cc33/242 greenPower.response({"options":0,"tempMaster":4190,"tempMast> debug 30-09-2023 22:27:24: Error: CommandResponse 0x00000000e202cc33/242 greenPower.response({"options":0,"tempMaster":4190,"tempMasterTx":14,"srcID":3791834163,"gpdCmd":25> at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7) error 30-09-2023 22:27:30: Exception while calling fromZigbee converter: SRSP - ZDO - extNwkInfo after 6000ms} debug 30-09-2023 22:27:30: Error: SRSP - ZDO - extNwkInfo after 6000ms at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7)

It looks like it failed at this:

Friendly name Clever Lader
Description
Last seen N/A
Availability Online
Device type GreenPower
Zigbee Model GreenPower_254
Zigbee Manufacturer
Description PowerTag power sensor
Support status Supported
IEEE Address 0x00000000e202cc33
Network address 0xCC33
Manufacturer Schneider Electric
Model A9MEM1570
Power
Interview completed True

I've tried to look back a few days in the logs, but this is the only error I see

[SmolikOne]

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.
Now to conclude:

Amount of devices in network: 77 (52 routers, 25 end devices)
Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT
20221226 worked fine: only for 1-2 days, after that timeout and NWK table full errors....
20230507 worked fine: no
20230922 feedback: not tested
20230923 feedback: worked fine for one day, now I'm receiving such errors:

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...?

[KoKolaj]

Version 20230923 is not as good as I originally thought. Every day one to two devices disconnected and had to be paired again.
Now I'm testing version 20230922.
After switching on everything OK, time will show if some devices will be disconnected.

Amount of devices in network: 65

Bridge software Zigbee2MQTT
20221226 worked fine: yes
20230507 worked fine: no
20230922 feedback: yes - Tested for now briefly
20230923 feedback: no - Devices were disconnected

[KoKolaj]

There has been no problem with version 20230922.
Everything is fully functional, without errors. Tested a week

[Koenkk]

Can you check 20230923 again? If device are disconnected, can you give some more context what actually happens? (what is observed in the log)

[TimB87]

• Amount of devices in network: 66
• Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT
• 20221226 worked fine: yes
• 20230507 worked fine: no
• 20230922 feedback: made it work again
• 20230923 feedback: didn't seem to have any positive effect on the issue

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.
I haven't had much luck with 20230923, and I eventually got 20230922 to solve my issues.
It took a lot of repairing until it worked, though, but I am glad I was able to avoid having to repair everything 😆

[Koenkk]

Since you repaired deivces, can you try 20230923 once again?

[TimB87]

@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.
So far, nothing I have done have brought those back to life, at least reliably.

[chris-1243]

• Amount of devices in network: 23
• Bridge software (Zigbee2MQTT/ZHA): zigbee2mqtt (1.33.1)
• 20221226 worked fine: no
• 20230507 worked fine: yes
• 20230922 feedback: not tested
• 20230923 feedback: online since 4h and it seems to be fine. No errors at all for the moment. Even based on 20221226, my Ikea styrbar E2001/E2002 (firmware 2.4.5) work fine which was not the case on the original 20221226 i tested those days.

I will edit my post if firmware 20230923 bugs or works correctly for me in some days.

[chris-1243]

After some days of testing, 20230923 is working fine for me. I'm going to keep it for further testing

[chris-1243]

20230923 is still running fine for me after more than 10 days without any errors

[deviantintegral]

I just had 20230923 hang. Here's logs from when the network became unresponsive. I had to power cycle the ZZH! for it to come back.

https://gist.github.com/deviantintegral/d5980eb26dd0702d9586afefc1292de8

I will try 20230922 later this week.

• Amount of devices in network: 109
• Bridge software (Zigbee2MQTT/ZHA): zigbee2mqtt
• 20221226 worked fine: no - hung on me a few hours after
• 20230507 worked fine: no
• 20230922 feedback: No hangs, but 2-3 end devices are having 6-12 hours of dropping before coming back. I believe it was mentioned this was fixed in the 20230507 firmware. I will try repairing them to see if it helps.
• 20230923 feedback: Hangs after days to weeks, requires unplugging or power reset.

[deviantintegral]

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!

[deviantintegral]

I confirmed 20221226 is not functional, as it completely hung a few hours in.

So far, I would say 20230922 is the best, in that there's no hangs, but it's not great given the end devices dropping off. I still need to try re-pairing the end devices as I'd avoided it as they're outside and wrapped in plastidip!

Also, I think it's only the Tuya door contact sensors dropping. The Aqara environment sensor was actually out of battery.

[jasondefuria]

• Amount of devices in network:93
• Bridge software (Zigbee2MQTT/ZHA): ZHA
• 20221226 worked fine: yes
• 20230507 worked fine: yes
• 20230901 worked fine: yes
• 20230922 feedback: N/A
• 20230923 feedback: yes

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.

[tech2mar]

M'y sisters house :

Amount of devices in network: 64

Bridge software Home Assistant (Zigbee2MQTT):
1.33.1

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.

[Claudio1L]

Bridge software Home Assistant (Zigbee2MQTT):
1.33.1
Sonoff Dongle-P

after a couple of weeks running fine with 0923, tonight started flooding with mem_error.

log.txt

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.

[jonnycastaway]

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

[jonnycastaway]

20230922 feedback: yes, for 17 days now

[chewth91]

Bridge Software - Z2M 1.33.1

For my cases, i have Z2M running at 2 different house.

House A:
Was running Sonoff Dongle-P on 20221226 but there's alot nwk table full errors, swapped to SLZB-06, running fine for some time then the same nwk table full error came more often as more devices were added to the network, getting less stable and will crash every few days(SRSP-6000ms) . Upgraded to 20230507 and running fine for awhile then adapter crashed again after few weeks. The team at SMLight said possibly due to the large network(150+) so i moved some devices to Sonoff-P on another Z2M addon(104 devices on SLZB-06 and 48 on Sonoff-P at the moment) . Sonoff P which is on 20230507 has been very stable, no issues.

SLZB-06:(104 devices)
20221226 : Yes but not stable
20230507 : Yes but not stable
20230922 : Running on this for 2 days and still observing
20230923 : No, nwk table full error, many devices were offline.

Sonoff P:(48 devices)
20230507: Fine and stable so no update of firmware.

House B:
Running SLZB-06 relatively fine and stable on 20221226 and 20230507 for very long time. Recently it crashed once(just added the 80th devices to the network).

SLZB-06:(83 devices)
20221226 : Yes
20230507 : Yes
20230922 : Running on this for 3 days and no issue so far
20230923 : No, devices availability shows online but faces delay on turning on the zigbee devices, showing network table full error and timeout error.

[popy2k14]

Hey guys.

I know it's not asked, but i running 20230901 without major issues since it was released.

• Amount of devices in network: 129
• Bridge software (Zigbee2MQTT/ZHA): Z2M 1.33.1
• 20221226 worked fine: yes
• 20230507 worked fine: no
• 20230901 worked fine: yes
• 20230922 feedback: test running since 31.10.2023...
• 20230923 feedback: not tested yet

@Koenkk when i got the test result's of all others right, the most stable for now is 20230922.
Right?
Is it planned to release this as new stable?
Because the last stable here on github Z-Stack_3.x.0_coordinator_20230507 is not stable for most of us :-)

thx

[Koenkk]

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 😄 )

[popy2k14]

Thx for all your efforts

[tech2mar]

@Koenkk Can we do anything for you? So that the process would be simpler? Maybe some logs? Or anything else?

[Koenkk]

Nope! I think I have enough info

[cloudbr34k84]

Amount of devices in network: 144
Bridge software Zigbee2MQTT Edge on Zigstar POE
20221226 worked fine: cant remember
20230507 worked fine: no
20230901 worked fine: yes
20230922 feedback: this has been rock solid since released, until today where I was getting 6000 error.
20230923> im now ging to try this version

[cloudbr34k84]

Nope that's not stable.. no idea what is happening.. I have tried so many combinations and nothing seems stable.. might be my coordinator..

[tech2mar]

Amount of devices in network: 144
Bridge software Zigbee2MQTT Edge on Zigstar POE
20221226 worked fine: cant remember
20230507 worked fine: no
20230901 worked fine: yes
20230922 feedback: this has been rock solid since released, until today where I was getting 6000 error.
20230923> im now ging to try this version

Flash 0922 back on the coordinator. Do you have updated zigbee2mqtt?

[cloudbr34k84]

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

[tech2mar]

Stay on it, just to see what's going happen.

[popy2k14]

@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.

[SargonofAssyria]

Zigbee2MQTT version 1.33.1-dev commit: d027b852
Coordinator type zStack3x0
Coordinator revision 20230923
Frontend version 0.6.137
Stats Total 92
By device type End devices: 50 Router: 42

Every other week I have to unplug the Texas Instruments LAUNCHXL-CC1352P-2 from the Raspberry Pi 4 because it locks the serial port.
Once in a while a device drops of the network for no reason, but can be quickly added.
Going to try 20230922

[alexruffell]

Amount of devices in network: 86
Bridge software (Zigbee2MQTT/ZHA): ZHA
20221226 worked fine: yes
20230507 worked fine: no
20230922 feedback: [TESTING IN PROGRESS]
20230923 feedback: I have been running 0923 for a few weeks and my logs have tons of coordinator UART disconnection errors which are causing devices not to respond. Can this firmware be the cause of this issue or should I be looking elsewhere?

Edit: Flashed 0922 to see if it is any better.

[alexruffell]

With 0923 I had tons of UART disconnection errors. With 0922 they seems to have gone or at least become very infrequent.

[Koenkk]

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)

[tech2mar]

Thank you

[BradleyFord]

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>

[lux73]

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

[popy2k14]

@BradleyFord As stated by @lux73
That's a really bad idea. Zigbee is a mesh system and data is routed over multiple routers (hops).
Each router has an table of nearby end-devices/routers and is sending data over the best route.
Also there is a feature named "source-routing" (which Z2M is using) where the whole routing table is built on the Z2M side,
and used to determined the best route to each device. if you remove an router in between, it takes a while until the network is stabilized again (new routes get's published and picked up by Z2M).

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.

[joschaschultze]

Amount of devices in network: 93
Zigbee2MQTT version 1.33.1
20221226 worked fine: yes
20230507 worked fine: no
20230922 feedback: Yes, absolutely! Even better than 20221216.
20230923 feedback: Not tried

[pdecat]

• Amount of devices in network: 115
• Bridge software (Zigbee2MQTT/ZHA): ZHA from HA 2023.11.1
• 20221226 worked fine: yes (for several months before testing 20230507, and after rolling back in July)
• 20230507 worked fine: no (see Z-Stack_3.x.0 coordinator 20230507 feedback #439 (comment) for the details)
• 20230922 feedback: so far so good as I just installed it, but will update my comment in the coming days as 20230507 seemed fine at first, but then used to freeze after several hours or days. Edit: still ok, 24 hours without issues so far. 🤞
• 20230923 feedback: not tested

[BeFygo]

• Amount of devices in network: 54
• Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT (docker)
• 20221226 worked fine: yes
• 20230507 worked fine: no
• 20230922 feedback: stable for 2 weeks now
• 20230923 feedback: network fail after 3 days, 50% dropouts

[Koenkk]

Many thanks for all your feedback, based on TI input I've compiled 2 new test firmwares: #483