Online manual

Create and use backups

Keep the right copy for your screen or Core, manage encrypted Cloud backups and prepare recovery carefully.

All guides

For: Administrators and users who want to preserve their layout · Updated September 2026

01

Choose the correct backup type

One-Home has different copies for different purposes. A layout backup belongs to the browser display: theme, language, density, Home sections, room order, favourites and One-Views. A Core recovery copy belongs to the installation and its database, configuration and keys. A Cloud backup is encrypted locally before it is sent to Cloud.

First decide what you want to protect. Setting up another tablet differs from recovering a failed Core. A browser file has no resident permissions, current device states, Moments, One-Flows, camera addresses or complete Core data. Name your copy clearly according to its purpose.

02

Keep a layout outside the browser

In the demo or theme version, layout backups are under System > Maintenance. The three latest copies remain available on this device. That local list may disappear when you clear browser data, so also download a file. In the connected v0.37 app, System has different content showing the Core connection and screen preferences.

  1. Open Maintenance in the environment where you created the layout.
  2. Choose Create backup and check the date, version and dashboard count.
  3. Choose Download for the required copy and check that the JSON file was actually saved.
  4. Keep the file somewhere recognisable before clearing the browser or replacing the screen.
03

Restore only the intended layout

Use Restore for a local copy or Open backup file for a downloaded JSON file. The preview gives the date, version and One-Views count. Restoring replaces this device’s display settings and dashboards and first saves the current layout as a recovery copy.

Afterwards, check your starting dashboard and blocks. Missing items receive a notice; a layout file does not recreate those devices. An invalid file is rejected without changing the layout. Do not use a Cloud backup or an arbitrary JSON file for this import.

04

Create an encrypted Core backup

As an administrator, open the Cloud area of the existing Core management interface. It offers Cloud backup settings, Show recovery key and Create backup now. This backup contains the One-Home database and local secret keyring, encrypted before upload. First check that the correct home is linked to Cloud.

  1. Enable Cloud backups if you want to use this service.
  2. Choose Show recovery key and store the key separately in a safe offline location.
  3. Choose Create backup now and wait for confirmation.
  4. Check the new entry, including its date and size, in the backup list.
The backup key is neither your Cloud password nor a 2FA recovery code. Cloud does not know this key; a new installation cannot open the encrypted copy without the matching key.
05

View and download in My One-Home

Open Backups in the account portal and select the correct installation. The list shows each file’s name, date, size and SHA-256. You can download or delete a stored Cloud backup. This portal view has no button to start local system recovery.

  1. Compare the selected installation with the home for which you need the copy.
  2. Download the required copy and keep its name and date with your recovery information.
  3. Delete a Cloud backup only when you deliberately want to remove that stored copy; read the confirmation.
06

Prepare Cloud recovery on Core

Have the administrator choose a suitable recovery time and record the current state. The Cloud backup list on Core offers Restore. A copy from another installation requires its matching recovery key; enter it in the key field in the Core interface.

After confirmation, recovery is staged and One-Home restarts automatically. Wait until Core returns, then check accounts, rooms, connections and real device operation. Having a downloaded file alone does not mean that the correct key and a usable recovery route are available.

07

Review your recovery preparations

When updating Core, also retain the recovery copy made by the update process. In a standard installation, central configuration, database and keys belong together. Do not replace an existing encryption key to make an old copy fit.

Periodically check that you can find the right copy, understand its date and access the required key. A new Cloud identity may affect opening older Cloud backups. Discuss this with the administrator before transfer or recovery, and retain the separately stored recovery key.

One-Home up close