As far as I know you shouldn’t have to do anything. If you need to move to the new coordinator the z2m backup should just get restored to it (assuming it’s completely blank with no network formed).
Confirmed the process works flawlessly - thanks for the confidence and clarification Tubez !
For those interested … here’s what I did to swap to a new co-ordinator:
Do a HASS backup as well as a Zigbee2MQTT backup.
Stop Zigbee2MQtt add-on and disable ‘start on startup’
replace IP address of new co-ordinator in 2 places - HASS UI for the add-in and the configuration.yaml under the zigbee2mqtt directory
shutdown Hass.
disconnect old co-ordinator and connect the new co-ordinator
restart HASS
check in 2 places that the new ip address of the new co-ordinator is updated - HASS UI for the add-in and the configuration.yaml under the zigbee2mqtt directory
start zigbee2mqtt add-on in hass
wait patiently till all the devices slowly but surely emerge !!
Just rolled out new 2023 design of the TubesZB cc2652 Zigbee coordinator. Stealing a bit from the PoE models form and an increased modular design for upgrades/swap outs of the radio module. Soon with a cc2652p7 variant too!
The efr32 non PoE coordinators will move to this form factor as well. Including new efr32mg24 modules.
New - I set up some addons for doing Firmware updates to TubesZB (or other) coordinators (both efr32 and cc2652!). consider them beta but I’ve tested both successfully. They will work with Network connected coordinators or local USB ones (have not tested). GitHub - tube0013/tubeszb_addons: Home Assistant add-ons for Flashing TubesZB Devices
Hi great add on. I used it yesterday on the older style coordinator.
It kept on doing error 16 I think. It was because it somehow couldn’t turn on the switch for prep for firmware. I had selected it to do this in the config.
Anyway I manually did this, but I unfortunately forgot to turn this off before enabling it in zha, it messed up.
Luckily I had download a backup and restored, all was fine then.
Thanks for the add on.
Ok, I took my chances and upgraded my cc2652p2 coordinator using the add-on and other having to add in the step to toggle the “Prep the cc2652p2 for firmware update” switch it all went great! Thanks for the new tool.
Yep as you guys are finding, if you are not on a recent esphome frimware you’ll need to trigger the bootloader from the coordinator’s esphome web ui. Easy way to tell is if the UI shoes a toggle switch or a button. If a button the addon should be able to trigger it.
Bumped the addon version, as USB flashing was not working. For cc2652 USB coords you will need to enable bootloader mode (push bsl button while plugging into USB) before running the addon.
You should be set to go. I’m shipping the 20221226 z-stack fw as I’ve been tracking an ongoing issues some people have with the 20230507 version so am not yet comfortable with shipping it.
For some reason it ota only gets to 40% and then the webui disconnects, I drop 2 pings and then I can reload the webui. I’m not sure if the update occurred successfully or not.
Is there a way to see what version of your ESP f/w the gateway is running?
Oké great, I will leave it as is for now. As for the newer firmware issue; are you updating progress on this topic or can I subscribe somewhere following progress on the issue?
Thank you sir!
