I created a Homey Community Backup & Restore Web App (HCB&RWA). This makes it possible to create and download a Zip file with the Alarms, Logic, Apps, Zones, Devices, Folders and Flows on your Homey.
After that it is possible to Select a previous downloaded Zip backup and restore these objects on this or another Homey. Community Backup & Restore works best from a Desktop browser, pls do not try on a Tablet, it is just to small!
(And up-front apologies for the layout, I am a functional programmer not a Designer )
Although Athom promised a Backup-Restore this is probably something completely different from what Athom will provide. (for what was told cq what the rumors are.)
Differences with the promised Athom Backup, cq characteristics of Community Backup & Restore:
- You download a Zip file with a Fulll Backup! Stor it Locally in a safe place!
- You have the option to select from as many backups (zip files) you keep.
- You can select each object (Alarm, Logic, App, Zone, Device, Folders and Flow) to restore the old state of that object or recreate a deleted object with the same name/characteristics.
- HCB&RWA can’t restore Z-wave and Zigbee devices, it will recreate a App device when that option is selected. Restore of Z-wave and Zigbee will only be possible by the Athom Backup!
- You authorize your Browser to get full Access to your Homey. Just close your browser to stop access.
There are many UIDs used for all objects and these have to be re-linked when restoring/recreating a complete config. I probably have missed some but that will be a matter of time. Pls report what goes wrong and send me fe a description, screenshots of the Developer Console (Inspect in Chrome) a JSON of the Flow and/or a Backup file if you can. (be aware it could contain personal data and/or secrets)
Mapping of UIDs
To keep track of all old and new UIDs you have to let HCB&RWA create a “~ CommunityBackup Restore Info”. It is just a nonfunctional Switch but provides me some place to store settings on your Homey. It does not harm even if you delete it but keeping it will keep track of all IDs on your Homey across restores. If you don’t create the device, a Restore can’t map fe Flows to the re-created devices!
Mapping of Z-Wave and Zigbee devices
HCB&RWA can restore a Z-Wave or zigbee device to a < groups> app device.
it will do this if you enable the option on the first tab and the z- device is not on Homey anymore but you want to restore it from a backup. The created groups device Wil have the same capability as the original z- devices.
After restoring the flows that uses this devices they should work. You can add the real z- device to the group device to let them operate and switch accordingly.
Pls test and report if it works for your devices.
Restore of 433 kind of devices
Restoring a KAKU or some other devices works and automatically pairs with the same 433 code so should work most of the time. Pls also let me know if restoring a Nexa, Telldus or other 433 device works and results in working devices. I expect it to work as it works for other 433 devices.
Tested or reported 433 and other devices that can be restored:
- KlikAanKlikUit (trust/Coco)
- ScreenLine Remote
Devices not able to restore a working version yet:
- Solar panels SolarEdge
These are on my list to get a Restore working, either by fixing the restore process or by adding an option to replace the devices after that in broken flows.
Logon or Authorization
I have to use a workaround for authorizing your browser. This will change once Athom provides me with an Web API Key but for this moment when I asked they stated “They will not give out an API key because we create a Backup option ourself.”. To Authorize YOUR browser : Open https://homeybackup.web.app/login and open the provided link (to https://cli.athom.com…) to log in for an authorization code, Copy it, close the Window and Paste - Submit to log on to your Homey. Have Phun! (Withou /login it halts with an: “redirect_uri does not match” )
Beside many un-known issue’s I give you already one I know:
- in Cards with Text fields with Multiple [Tags] only the first will be repaired (mapped), if more [Tags] exist the mapping fails at this moment.