Just as a public service announcement, a long-standing bug in Texas Instruments Z-Stack that caused lockups and network shutdown on zigbee2mqtt and ZHA (when using a TI board) has just been fixed.
The bug would be very rare for some or most users, but more common for users with a large (100+) number of devices. The symptoms would be loss of communication with the Zigbee coordinator radio. The serial port would still be present, but nothing would be returned from Z-Stack.
This bug affected:
Electrolama Zig-a-Zig-Ah (ZZH)
Slaesh CC2652 stick
Texas Instruments CC1352P2
Texas Instruments CC26X2R1
Texas Instruments CC2538
Here is the link to the updated ZStack firmware (dated 2021-01-20) that is supposed to fix the issue:
Using Slaesh CC2652 stick as my coordinator, I did the update yesterday !
And it was a pain in the ass to keep 5 small Dupont cables in place with one hand while the other hand was using the mouse to start the firmware flash !!!
But flash was successfull after a few tries.
I’ve been using this coordinator for 3 or 4 months with about 55 zigbee modules without any issue so far.
I don’t use ZHA but Zigbee2MQTT.
Everything is fine for the moment.
Unfortunately I won’t be of any help. I’m just a random user following guides. I have no clue about what Im’ doing !
The only info I can provide is that my CC2652RB with new firmware 20210128 works pretty fine with Zigbee2MQTT HA addon. I did not loose any pairing, and my zigbee network have been stable for 12 hours since the upgrade.
Oh sorry. Confusion ! Disregard what I said ! I ended those firmware udpates at 2AM last night…
For the CC2652RB coordinator though, I did not even had to press any button, just put the coordinator USB stick in the laptop USB port, follow the procedure and use some python command lines : CC2652R stick - slae.sh
It was easy compared to my 2 CC5230 routers that I did just before and required Texas Instrument device and SmartRF Flash software.
Okay, I upgraded my zzh firmware to CC2652R_20210120 sadly I had to repair and redo everything However I’m not sure if that is normal or my fault. What struck me ad odd is, that the name of the former firmware I used was: znp_CC26X2R1_LAUNCHXL_tirtos_ccs so I’m not sure if this is an issue for everyone, or just me because I used an strange firmware beforehand.