I might need to perform Zigbee network reset on v5 but with 61 devices and 300 flows, I’m looking for a simplified “How to”. I was thinking about following way to perform reset and Zones/Flows repair - what do you think, would that be working, any guesses ?
making backup via community tool https://homeybackup.web.app/ and full backup via Cloud backup option
create a checklist marking down existing Zigbee devices names (eg.via devices.json to CSV export - there are several online tools)
re-add all devices, keeping previous names, adding routers first (this would be the most time demanding step)
**** ZONES fix ****
making backup via community tool https://homeybackup.web.app/ and extracting new devices.json
matching newly added devices via those previously based on name and/or “zb_ieee_addr” (not all device types have zb_ieee_addr however in json backup) in related devices.json file and fix zones entries…
re-import “modified” devices with corrected zones via https://homeybackup.web.app/ by “modified” backup ZIP
**** FLOWs fix ****
- search and replace by name and/or “zb_ieee_addr” from previous devices and replace all instances new with new IDs in flows.json
- delete all flows (or just those broken? Via HomeyScript?) - maybe not required at all ?
**** Recovery ****
If all of that fails or get broken, full Athom restore will revert all of this ?
For sure for someone scripting and ReGexp capable, that would be piece of cake yet I’m not that person.
Also I’m not expert, so if this is non-sense, be nice when cometing it
I did a full reset and re-added the devices and fixed the flows by hand. Yes, it’s a pain, but in the end it’s not that hard. What you describe also sounds like a daunting task with high chance on typo’s in names or mistakes when replacing Id’s.
To me, the whole point of the Zigbee reset was to make sure there was no hidden flaw from the upgrade process, besides making sure the mesh was fresh (pun intended). Seems like your approach would keep those problems and maybe add some more.
If you add the devices when the right zone is selected, those devices are in the right zone from the start. You could choose to name devices different if your original name was not perfect in retrospect.
As for flows: flows that referred to the devices directly will get an error mark. These are quite easily found and fixed. I did not encounter flows where I was confused which device was meant while fixing.
The most hard to find are those which tags are used. These don’t get the error mark, just a ? where it was used. I used the online flow editor because that was the fastest to navigate all flows and show all contents of each flow in a single screen. Also this editor allows cut and paste for tags, so that saved me some time too.
All in all it was quite doable with 30+ devices and hundreds of flows, although I did use quite a few tags unfortunately.
Now I know everything is fully V5 compatible, and it really is fully stable for me now. So I have no regrets for taking the long way.
Thank you, I’m well aware of all the aspects when adding and fixing all ZigBees/Flows after reset but my question is related to the idea itself - if anyone would suggest technically against it (eg.such devices would not work after such modifications of json), that’s answer/help I’m looking for.
I don’t think anyone has done what you’re suggesting, so you’re on your own.
Even this is fine unless someone will say - this is total nonsense