> **Warning:** This Epic's description is managed as documentation and mirrors a file in the > website repository. Do not edit it directly. See [how we manage the roadmap](https://selorahomes.com/handbook/departments/product/roadmap-management/) > and propose all content changes via a Merge Request. [Source](https://gitlab.com/selorahomes/products/selorahomes.com/-/blob/main/content/docs/roadmap/one-click-restore/index.md) ## Summary Selora OS already makes cloud backups automatically and stores them securely in the Selora Cloud — on every plan, with more storage on paid plans. Restoring is where the flow breaks down today: the homeowner has to download the backup, then upload it and restore it through the Home Assistant UI — and Home Assistant has to be up for any of that to work. One-Click Restore turns that into a button in Connect. ## The homeowner's problem - **Restoring is a procedure, not a click.** Today it means: download the backup from Selora Connect, open Home Assistant, System → Backups, the three-dot menu, Restore backup, upload, confirm — four steps across two products - **Restoring requires HA to be running.** The UI flow only works while Home Assistant is up — which is exactly the moment a backup is least guaranteed - **The moment of stress is when skill is required.** A restore is what you do when something is wrong; asking the homeowner to be fluent in the HA UI at that moment is asking too much ## What's included ### One button in Connect - **Pick a backup, press restore**: the home page in Selora Connect gets a backup picker with a restore action — the same backups Selora OS already creates and stores - **Works even when HA is down**: Selora initiates the restore against the hub itself, not through the Home Assistant UI — the hub has to be reachable, but Home Assistant does not have to be running - **Visible progress and confirmation**: the homeowner sees the restore run and gets a confirmation that the selected backup is the one that was applied ### Behind the scenes - Selora OS pulls the selected backup from the Selora Cloud - The restore is applied by the OS, outside the Home Assistant UI, and the hub comes back up on the restored state - Selora verifies the result and reports it back in Connect ## Why it matters - **Backups are only worth the restore.** A backup nobody can use in the moment that matters is a compliance checkbox, not a product - **Turns a power-user skill into a button.** No download, no file management, no knowledge of the three-dot menu required — the homeowner picks a snapshot and watches it come back - **Closes the worst gap in self-service.** When the hub's own UI is exactly where the homeowner can't get help, the restore path still works from Connect — the one place that is always up ## The complexity - **Restoring outside the HA UI.** Applying a backup while Home Assistant is down means operating at the OS layer — and still verifying cleanly when HA is up, so the two paths cannot diverge - **No half-applied restores.** The operation must be atomic: either the selected backup is fully in place, or the hub returns to the state it was in - **Verification.** After the restore, Selora has to confirm the hub actually came back on the selected snapshot and say so in Connect ## Out of scope (for now) - **Restoring from local storage** (NVR or SD card on the hub) — cloud backups only - **Partial or selective restores** — individual automations, integrations, or config pieces; this is a whole-snapshot restore - **Restoring to a different hub** — a restore brings the selected backup back to the home it was made from