Skip to content
DIY Servers

How to Back Up Home Assistant (and Actually Restore It)

To back up Home Assistant, use the built-in backup tool under Settings > System > Backups, schedule automatic backups, and copy at least one recent backup off the device. A backup you have never test-restored is a hope, not a backup.

The rule that saves you: keep three copies, on two types of media, with one stored away from the machine. For a home server that means one backup on the device, one on a NAS or PC, and one in cloud storage.

What a Home Assistant backup actually contains

A full backup captures your configuration, automations, dashboards, add-ons and their data, and the database of recent history. It does not capture the operating system itself or anything living only in your head, like which Zigbee channel you chose. The backup file is what lets you rebuild on new hardware in minutes instead of days.

Cross-check compatibility, safety and local rules with official sources before you buy. Australian 240 V wiring, RCM labelling and hub protocols change with firmware updates, so confirm details against manufacturer docs and a licensed electrician when mains power is involved.

Step 1: Create a backup the right way

  1. Go to Settings > System > Backups.
  2. Choose Create backup, then Full backup for disaster recovery (a partial backup is fine for quick config snapshots before a risky change).
  3. Give it a clear name that includes the date so you can find the right one later.

Make a manual full backup before every Home Assistant core update or major add-on change. It takes a minute and it is the single habit that prevents most “everything broke after the update” disasters.

Step 2: Automate it so you do not forget

Manual backups fail because humans forget. Set automatic backups on a schedule (weekly is a sensible minimum for most homes, daily if you tinker commonly). Home Assistant can run scheduled backups and prune old ones so they do not fill your storage. Pair this with a notification so you actually know a backup ran, and know quickly when one fails.

Cross-check compatibility, safety and local rules with official sources before you buy. Australian 240 V wiring, RCM labelling and hub protocols change with firmware updates, so confirm details against manufacturer docs and a licensed electrician when mains power is involved.

Step 3: Get a copy off the device

A backup sitting only on the same SD card or SSD that fails is worthless. Move copies somewhere else:

  • To a NAS or PC: use a network-share or Samba add-on so backups land on another machine automatically.
  • To cloud storage: add-ons can push encrypted backups to Google Drive, a Nextcloud server, or S3-compatible storage. Always encrypt cloud copies.
  • Off-site: if your home server matters, one copy should survive theft, fire or flood. Cloud or a drive kept elsewhere covers this.

If you are still running Home Assistant from an SD card, this is also your reminder to move to an SSD. Card wear is the most common cause of sudden Home Assistant death. Our DIY servers hub covers hardware choices, and the Raspberry Pi guide explains storage trade-offs.

Step 4: Test the restore (the part everyone skips)

An untested backup is a gamble. At least once, prove it works:
  1. Flash a fresh Home Assistant install on spare hardware or a virtual machine.
  2. On first boot, choose Restore from backup and upload your latest full backup.
  3. Confirm your dashboards, automations and devices return.

Do this once and you will know exactly what to do on the bad day, instead of learning under pressure.

Cross-check compatibility, safety and local rules with official sources before you buy. Australian 240 V wiring, RCM labelling and hub protocols change with firmware updates, so confirm details against manufacturer docs and a licensed electrician when mains power is involved.

How to restore after a failure

When hardware dies, the recovery path is short if your backups are sound: install Home Assistant on the new device, and on the onboarding screen select Restore from backup. Upload your most recent full backup, wait for it to apply, and the system returns with your configuration intact. Battery and Thread/Zigbee devices can need a moment to reconnect, but you should not be rebuilding automations by hand.

Reality check: the time to set up backups is now, while everything works. The cheapest insurance in self-hosting is a tested restore.

Frequently Asked Questions

How commonly should I back up Home Assistant?

Weekly automatic backups suit most homes, plus a manual full backup before every core update or big change. Daily is better if you change automations commonly.

Where should I store Home Assistant backups?

Keep one on the device, one on a NAS or PC, and one encrypted copy in the cloud or off-site. Never rely on a single copy on the same storage that runs the system.

Does a Home Assistant backup include add-ons?

Onefull backup includes installed add-ons and their data. A partial backup lets you choose specific items, which is handy for quick config snapshots.

Can I restore a backup to different hardware?

Yes. That is the main reason to keep full backups. Install Home Assistant on the new device and restore from backup during onboarding.

Sources: See also www.energy.gov.au for baseline Australian guidance.

How much does smart home gear cost over five years?

Sticker price is only part of the story. Hubs, repeaters, replacement batteries, cloud subscriptions and electrician call-outs can add up quickly on Australian 240 V installs. We compare total ownership cost in our reviews and link to primary references such as the Home Assistant documentation and the Matter specification when protocol compatibility matters. Budget for at least one spare sensor or switch when you standardise on a hub — mixed-vendor kits often need extra repeaters.

Cross-check compatibility, safety and local rules with official sources before you buy. Australian 240 V wiring, RCM labelling and hub protocols change with firmware updates, so confirm details against manufacturer docs and a licensed electrician when mains power is involved.

Which protocol should you standardise on?

Wi-Fi devices are easy to buy but noisy on your network. Zigbee and Thread/Matter devices usually need a compatible hub or border router, yet they tend to behave better when the internet drops. Before you bulk-buy sensors or switches, decide whether Modern Home Tech readers should prioritise local control, Apple Home, Google Home or Home Assistant — then pick products that match that path instead of mixing three ecosystems by accident. Thread border routers in Australia must still meet RCM requirements for radio equipment.

Which smart home news topics matter most for owners?

Protocol changes, security advisories and tariff updates affect real households more than launch-day hype. We prioritise Matter and Thread compatibility notes, recall notices, and energy price shifts that change whether automations still save money. Firmware regressions that break local control also rank above minor app redesigns — those are the updates worth reading before you buy more gear.

Cross-check compatibility, safety and local rules with official sources before you buy. Australian 240 V wiring, RCM labelling and hub protocols change with firmware updates, so confirm details against manufacturer docs and a licensed electrician when mains power is involved.

About Modern Home Tech: We write practical smart home guides for people who want fewer broken automations, clearer product choices and better control over their home network. Our reviews focus on compatibility, setup effort, local-control options, privacy and total cost.

Need Remote Access?

A small VPS can be safer and cleaner than exposing your home network directly.

Check Hostinger VPS