Quick answer
Create a backup before you update. Read the release notes for breaking changes. Then update from Settings > System > Updates, and check your configuration before any restart. When you need to restart, pick the option that matches the problem: restart Home Assistant Core, or reboot the whole host.
Back up before you update
The update dialog has an option to create a backup before updating. Keep it on. A backup is the real way back if an update breaks something, so the backup should be a copy you can actually restore. A backup on the same disk is not enough, so keep a copy somewhere else. See how to back up and restore Home Assistant.
Read the release notes first
Home Assistant Core versions are numbered by year and month, such as 2025.6.2. A major release comes out about once a month, and patch releases follow during the month. Many people wait for the first patch release before updating. That is a habit rather than a rule.
Read the backward-incompatible changes section first. It lists changes that can break integrations, custom components or your YAML. Skipping several months is allowed, but deprecated features may be gone by then.
Update from Settings
- Open Settings. Updates appear at the top of the page, or go to Settings > System > Updates. If nothing appears, open the menu in the top-right corner and select Check for updates.
- Select the Home Assistant Core update.
- Turn on the backup option and select Update.
- Wait. Home Assistant restarts when the update finishes. Do not interrupt an OS update, which can take more than 10 minutes on slow hardware.
- Afterwards, check Settings > System > Repairs and the logs for new problems.
Update from the command line or a container
On Home Assistant OS, run these in the console or the SSH app:
ha core update --backup
To move to a specific version, use the version number in place of the placeholder:
ha core update --version <version>
For Home Assistant Container (Docker), pull the latest image, then stop and recreate the container with your original settings and volume mounts. Your configuration lives in the mounted folder, so it stays in place:
docker pull ghcr.io/home-assistant/home-assistant:stable
For a Python virtual environment, activate it and run pip install --upgrade homeassistant.
Check your configuration before you restart
A typo in YAML can stop Home Assistant from starting. Before any restart, open Developer tools > YAML and select Check configuration.
You often do not need a restart at all. Automations, scripts, scenes and templates can be reloaded from Developer tools > YAML without one.
Restart, reboot, or shut down?
Home Assistant offers several options, and they do different things. The menu names vary by version, but they are found under Settings > System, behind the power button in the top-right corner.
| Option | What it does | When to use it |
|---|---|---|
| Quick reload | Reloads YAML without restarting Core | After changing automations, scripts or templates |
| Restart Home Assistant | Restarts Core only; the host keeps running and OS updates are not applied | After a Core update, or when Core is stuck |
| Restart in safe mode | Starts Core without custom integrations and custom frontend resources | When a custom integration or card stops Home Assistant from loading |
| Reboot system | Restarts the whole host machine | After an operating system update, or when the host misbehaves |
| Shut down system | Powers off the host | Before you move the device or unplug it |
Restart in safe mode to find the problem
Safe mode is a diagnostic tool. Use it when a custom integration, card or theme stops Home Assistant from loading. Safe mode leaves those out, so you can open the interface, remove or fix the culprit, and then restart normally.
Reboot or shut down the host safely
- On Home Assistant OS, use Reboot system from the restart menu, or run
ha host rebootin the console. - Wait for the reboot to finish before you try to connect. Reboot times vary a lot by hardware and integrations.
- Shut down the system before you unplug it. Do not pull the power to reboot. On a Raspberry Pi with an SD card, a sudden power cut can corrupt the card.
If an update goes wrong
- Check the logs first. Settings > System > Logs often shows the error that points to the cause. See how to find and read Home Assistant logs.
- Roll back Core, with care. You can install an older Core version with
ha core update --version <version>. Rolling back Core does not undo database changes made by the newer version, so it may not fix a problem caused by an upgrade. - Restore your backup. If the update changed data in a way a rollback cannot undo, restoring the backup you made before the update is the safer route. See how to back up and restore Home Assistant.
Can Home Assistant update itself?
Core updates usually start when you choose them in Settings. Some apps have their own automatic-update setting. Check each one before you turn it on, and keep a recent backup in place. If Home Assistant does not come back after a restart, see why you can’t connect to your Home Assistant.