ha-backuplisted

# ha-backup Create a Home Assistant backup through the Supervisor before anything risky, and know how it gets restored. ## When to create a backup Make a **named** backup BEFORE: - Destructive or large config edits (rewriting `configuration.yaml`, bulk automation changes). - Removing an integration or add-on. - A Home Assistant Core / add-on update. - Any change you are not sure you can cleanly undo. - The user explicitly asks to back up. When in doubt, back up. It is cheap; a broken instance is not. ## Create a backup Always give it a descriptive, unambiguous name so it is easy to find later: ```bash ha backups new --name "pre-automation-refactor-2026-07-02" ``` List existing backups (confirm yours was created, note its slug): ```bash ha backups ``` Inspect one: ```bash ha backups info <slug> ``` Full vs partial: - `ha backups new` (as above) creates a **full** backup — all add-ons + HA config/folders. Use this by default before risky changes; it is the safest and needs no decisions. - **Partial** backups (subset of add-ons/folders) are best created from the HA UI (Settings → System → Backups), where you can tick exactly what to include. Prefer a full backup from the CLI unless the user specifically wants a partial one. ## Where backups live - Stored in **`/backup`** as `.tar` archives. - From this add-on, treat `/backup` as **read-only** — do not write, move, or delete files there by hand. Manage backups only through `ha backups ...` or the HA UI. ## Restorin