Replacing a coordinator

Hello, unfortunately I broke my cc1352p-2 while resoldering the condensator, I have now ordered a new one. Do I need to reconnect all my devices now?
Or is it kind of Plug and Play (after i flashed the new coördinator)?

Regards,

If you’re replacing like-for-like, you probably won’t need to re-connect the devices as the device table is not stored on the stick.
I only had to do that when I changed to a totally different coordinator.

1 Like

How did you get on with this? I’ve been trying to swap coordinators on my set up however Z2M won’t start if I do. I’m swapping like for like adapters (CC2530) with the same firmware. The only thing that’s different is the IEEE address. I’ve read this can’t be changed so I hope it’s not this causing the issue.

info  2021-01-04 10:44:15: Logging to console and directory: '/app/data/log/2021-01-04.10-44-15' filename: log.txt
info  2021-01-04 10:44:15: Starting Zigbee2MQTT version 1.16.2-dev (commit #e0fa681)
info  2021-01-04 10:44:15: Starting zigbee-herdsman (0.13.40)
error 2021-01-04 10:44:21: Failed to call 'OnEvent' 'stop' (TypeError: Cannot read property 'getEntries' of null
    at Function.loadFromDatabaseIfNecessary (/app/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55)
    at Function.all (/app/node_modules/zigbee-herdsman/dist/controller/model/device.js:236:16)
    at Controller.getDevices (/app/node_modules/zigbee-herdsman/dist/controller/controller.js:255:31)
    at Zigbee.getClients (/app/lib/zigbee.js:138:30)
    at OnEvent.stop (/app/lib/extension/onEvent.js:23:42)
    at Controller.callExtensionMethod (/app/lib/controller.js:381:44)
    at async Controller.stop (/app/lib/controller.js:189:9))
error 2021-01-04 10:44:21: Not connected to MQTT server!
error 2021-01-04 10:44:21: Cannot send message: topic: 'zb2mqtt/bridge/state', payload: 'offline
info  2021-01-04 10:44:21: Disconnecting from MQTT server

EDIT: One of the cables was disconnected from the CC2530 :see_no_evil: Weird as it still showed up in DMESG, I have another issue now though: Currently 0 devices are joined:
However my devices list in configuration.yaml is still full :roll_eyes:

EDIT2: turns out the database was backed up, not sure if this happened upon changing the coordinator or an upgrade to 117 as I did both this morning. I had another backup anyways… phew.
Think I’ll open a github issue as this isn’t expected behaviour afaik.

EDIT3: So I’ve just tried this again as I’m not sure if so many attempts to start caused the db to be wiped but it’s working now. What the hell backed up my db and wiped it?? Maybe it was because I was on dev and switched back to stable in 117? AKA this