Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup and restore configuration #60

Closed
martonborzak opened this issue Sep 27, 2023 · 3 comments
Closed

Backup and restore configuration #60

martonborzak opened this issue Sep 27, 2023 · 3 comments
Labels
roadmap Planned roadmap feature

Comments

@martonborzak
Copy link
Contributor

No description provided.

@martonborzak martonborzak added the roadmap Planned roadmap feature label Sep 27, 2023
@zehnm
Copy link

zehnm commented Oct 6, 2023

Currently in testing and planned to be released to BETA group either this or next week.

@zehnm
Copy link

zehnm commented Oct 12, 2023

Part of the BETA group release 1.4.0

@zehnm
Copy link

zehnm commented Oct 16, 2023

Included in 1.4.2
Please note that the web-configurator doesn't show a busy indicator yet during the backup archive creation and restore process! This usually takes a few seconds (worst case: up to around a minute).

We'll also add support articles describing more details about the backup & restore feature.

For now, an extract from the API functions:

Backup export

  • The backup archive is only returned to the client and not stored on the device.
  • It is recommended to perform the backup while the remote is in the docking station.
  • Using the remote or the Core-API should be avoided while the backup is running.
  • The backup should only take a few seconds. The backup will take longer:
    • if integration drivers are busy and require more time to shutdown.
    • if many custom resources (icons, background images, etc) are present.

⚠️ Attention:

  • The backup archive may contain personal information and access keys to external systems.
    • The backup archive is not encrypted. Contained information can be extracted with little effort.
    • For example the long-lived access token for Home Assistant is included, if that integration has been configured.
  • All integrations and docks will be disconnected and stopped during backup.
    • They are restarted after the backup is finished. This may take several seconds until all entities are available again.
    • Restart the device, if an integration or entities are no longer working after a backup.
  • The device must have enough free disk space to create the backup archive. At least 100 MB must be free to start the backup process.

The backup does not include:

  • WiFi network configuration and passwords.
  • Administrator pin.
  • Web-configurator pin.
  • Any API-keys created with the Core-API.

Backup restore

  • It is highly recommended to perform the restore while the remote is in the docking station.
  • Using the remote or the Core-API should be avoided while the restore is running.
  • The restore should only take a few seconds. The restore will take longer:
    • if integration drivers are busy and require more time to shutdown.
    • if many custom resources (icons, background images, etc) are present.

⚠️ Attention:

  • The device will not automatically restart after a system restore.
    • The device must be restarted after the restore to activate all changed settings.
    • Certain setting changes like OTA require a system restart.
  • WiFi configuration, administrator pin and web-configurator pin are not overwritten by a system restore.
  • All integrations and docks will be disconnected and stopped during restore.
  • The device must have enough free disk space to restore the backup. At least 100 MB must be free to start the restore process.

@zehnm zehnm closed this as completed Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
roadmap Planned roadmap feature
Projects
None yet
Development

No branches or pull requests

2 participants