First of all, should really make sure have a backup before firmware upgrade of a Zigbee Coordinator.
You should not have to pair any devices again, however, if end up having to restore backup then could take up to 24-hours before all devices have connected (especially battery-operated devices like sensors which usually only connect upon sensor changes).
If any device that was connected before is still not connecting after firmware upgrade then should be enough to power-cycle those devices (e.g. unplug and replug mains-power, remove and replace battery).
I assume that is just the assigned serial port in Linux and not the product description value that was written to the product description field in the EEPROM of the CP2102N USB-to-UART chip by ITead.
Not sure on Linux but on Windows can use tools like ex. NirSoft USBDeview or Sieber USBTreeView:
Would having 2 of these as routers and 1 as the coordinator cause interference between them? And would other repeaters and end devices latch on to these routers given their better signal because of their antenna?
I have the previous Sonoff ZigBee 3.0 Dongle plus running the new development branch firmware. I was having problems that seemed to come from inadequate power supply on my USB hub, so I replaced it. Everything started working again, but only for a couple days. While I was re-pairing one of my endpoints, another device of unknown_manufacturer joined the network somehow. It claims that it is a coordinator, and slowly started taking over the network. I think it is my HUSBZB stick that I still have to run my Zwave network! It is metastasizing and destroying my mesh. It has something to do with backing up my HUSBZB and restoring it to my Sonoff stick.
What I saw when I upgraded my CC2530+CC2591, that the new stick somehow got the IEEE-address of the old one (after searching a week why the re-flashed as a router CC2530+CC2591 would not join the mesh)
Maybe that is the case here too.
I just checked and they have different addresses. But the old one does have the same NWK. could that be the problem? Is there a way to erase it? Found it: use zha.remove service. It seems likely that a rogue coordinator could cause lots of problems with pairing and messages.
–EDIT Begin–
Just flashed 20211207 lol I’ll let you guys know if there’s instability. So far so good. All zigbee devices came back.
–EDIT End–
I’m still on CC1352P2_CC2652P_launchpad_coordinator_20211114.hex and this has been working fine on my Sonoff Zigbee 3.0 USB Dongle Plus. Even works with the new E1 sensors along with Zigbee2MQTT.
Only issue I’ve seen is I added a transition delay to all my bulbs to be 1 second. From time to time, the bulbs would come up with a low brightness as if the transition stopped midway. I’ve since just removed the transition and no problems. Not sure where the problem lies exactly.
FYI, ITead posted a blob that should let users themselves update the product description on already shipped dongles to supposedly match that already written in CP2102N EEPROM of the latest batch:
