Updates and Migration

Updates and Migration

Safe update through HACS

1. Create a native Home Assistant backup.
2. Install the BackupCheckup update in HACS.
3. Restart Home Assistant completely.
4. Reload the browser or Companion App.
5. Check the integration version.
6. Run Refresh backup data.
7. Test notifications and backup protection when appropriate.

The config entry, stable entity IDs, and stored analysis data are migrated. Do not delete the config entry merely because of an update.

Manual update

Replace /config/custom_components/backup_checkup completely. Never copy only selected files over an older version; mixed frontend and backend versions can fail.

Update the runner

The runner is read from runtime_runner on the default branch. After a repository update:

1. refresh the App Store,
2. install the offered runner update,
3. restart the app,
4. check its version line.

The runner version should match the integration.

Release 3.0.12

3.0.12 repairs the sidebar panel delivered by HACS. The published 3.0.11 Git tag still contained the 3.0.10 JavaScript custom-element name, even though the backend registered a 3.0.11 component. Because release tags are immutable installation sources, a corrected file on the default branch could not repair an existing 3.0.11 installation.

The frontend now uses the synchronized component and asset backup-checkup-panel-3.0.12-r1.js. A CI check prevents future releases when the manifest, backend registration, and JavaScript component name disagree. A runtime render probe also loads and renders the panel during validation instead of relying on syntax checks alone. Existing configuration, entities, and stored analysis data remain compatible.

Install the integration from the new v3.0.12 release tag, restart Home Assistant completely, and reload the browser or Companion App. Update the optional runner separately through the App Store and confirm runner initialized version=3.0.12.

Release 3.0.11

3.0.11 fixes a Runtime Runner startup failure that could end with home_assistant_permission_denied. The runner now creates the temporary Home Assistant log for the unprivileged sandbox UID/GID before starting the isolated process. Existing integration configuration, entities, and stored analysis data remain compatible.

The published 3.0.11 tag contains a mismatched frontend component and should be replaced with 3.0.12. The Runtime Runner permission fix itself remains included in all newer versions.

Rollback

1. Download the desired older release.
2. Remove only the old custom_components/backup_checkup directory.
3. Copy the complete older directory into the same location.
4. Restart Home Assistant.

Keep the BackupCheckup config entry to preserve entity IDs and dashboard references. Newer optional stored fields can be ignored by older releases and never modify Home Assistant backups.

Release 3.0.10

3.0.10 is an organizational release based on 3.0.9. User documentation moved from the repository into this Wiki. The README now contains only the product summary, HACS installation, runner note, and canonical Wiki link. Runtime and security fixes from 3.0.9 remain included.

Problem after an update

Check:

• complete restart rather than only reload,
• integration and runner versions,
• browser or Companion App cache,
• complete replacement of the integration directory,
• HACS and App Store updates as separate operations.

See Troubleshooting for further steps.