This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1352P: Zigbee Coordinator Replacement

Part Number: CC1352P

I have a general question about how Zigbee works. 

Say we have a network running with a Coordinator and a few dozen Routers and sleeping End Devices. All were commissioned using some BDB method using a fixed channel and panID (example DEFAULT_CHANLIST=11, ZDAPP_CONFIG_PAN_ID=5 respectively). Our Coordinator is also the trust center for the Zigbee network and a gateway to another proprietary system. 

Everything is running fine...then the Coordinator dies with no warning and needs to be replaced.  

How does the Coordinator rejoin this existing Zigbee network?

What we've observed is that the new Coordinator will fail to form the network on the ZDAPP_CONFIG_PAN_ID. I'm assuming its because it sees that there is already a network running on that panID. 

If we shut down the other devices, then the Coordinator will form a new network, but since it derives a new network key, it is not able to communicate with the other devices once they are powered back up.

Its not practical to go personally go to each of the Routers and End Devices and cycle power or manually force them (eg Push Button) to rejoin a new network (via Zstackapi_bdbResetLocalActionReq() + Zstackapi_bdbStartCommissioningReq()).

Does the Zigbee standard have a way to address this use case?  

Thanks,

- Bill