A typical Home Assistant Core update takes 5 to 15 minutes from start to finish
Most updates complete in under 10 minutes if your system is running smoothly and you have a stable internet connection. The process breaks into three parts: downloading the new version (usually 1 to 3 minutes), stopping the old version and starting the new one (2 to 5 minutes), and Home Assistant checking that everything loaded correctly (1 to 2 minutes). You will see a loading screen during this time, and your smart home devices will not respond until the update finishes.
Some updates take longer. If your system is running on older hardware, or if you have hundreds of automations and integrations loaded, the startup phase can stretch to 10 or 15 minutes. Updates that include database changes — which happen a few times a year — can add another 5 to 10 minutes because Home Assistant has to reorganize how it stores your history and statistics. A few rare updates have required 20 to 30 minutes, but these are announced beforehand in the release notes.
The update will not complete if your internet drops during the read, or if your device loses power. If either happens, Home Assistant rolls back to the previous version automatically and you can try again once the connection is stable.
Key Takeaways
- Standard updates finish in 5 to 15 minutes, with most completing in under 10 minutes on typical hardware.
- Updates that modify the database take longer — usually 5 to 10 minutes extra — and Home Assistant will announce these in advance.
- Older hardware and large numbers of automations or integrations can extend the startup phase to 10 or 15 minutes.
- If your internet drops or power cuts during an update, Home Assistant automatically reverts to the previous version and you can retry once the connection returns.
- You should plan for 20 to 30 minutes of downtime if the release notes mention a database migration or major structural change.
Why updates take different amounts of time
The read speed depends on your internet connection and the size of the new version. Most Home Assistant releases are 50 to 150 megabytes, so on a typical home internet connection this takes 1 to 3 minutes. Slower connections or older routers can stretch this to 5 minutes, but rarely longer.
The startup phase is where most variation happens. When Home Assistant boots, it loads every integration you have set up — your smart bulbs, thermostats, cameras, automations, scripts, and anything else. If you have 20 integrations, startup is fast. If you have 100 integrations or thousands of automations, Home Assistant has to initialize each one, and this can take 10 to 15 minutes. The first boot after an update is always slower than normal operation because Home Assistant is also checking that all your configurations still work with the new code.
Database updates happen when the developers change how Home Assistant stores information internally. These are infrequent — maybe three or four times a year — but when they occur, Home Assistant has to rewrite your entire history and statistics database. On a system with months of data, this can add 10 to 20 minutes to the update. The release notes always mention database migrations before the update is released, so you can plan around them.
What happens during the update process
When you click the update button in Home Assistant, the system first downloads the new version in the background. You will see a progress bar. Once the read finishes, Home Assistant stops all running automations and integrations, then shuts down completely. This takes 30 seconds to 2 minutes depending on how many things need to shut down cleanly.
Next, the new version starts. Home Assistant loads its core code, then initializes every integration in the order they are configured. Each integration connects to your devices and reports back that it is ready. During this phase, your smart home devices are offline — they will not respond to commands or automations. Once all integrations report ready, Home Assistant marks the update as complete and the loading screen disappears.
Finally, Home Assistant runs a check to make sure the database is intact and all your configurations loaded without errors. If it finds a problem, it will show an error message, but this is rare. Most updates finish without any issues.
How to know if an update is taking too long
If the loading screen has been visible for more than 30 minutes, something has gone wrong. Check whether your internet connection is still active — if it dropped during the read, Home Assistant will be stuck waiting. Restart your router and check your device's network connection.
If the connection is stable and the update is still stuck after 30 minutes, restart the device running Home Assistant. This will interrupt the update and Home Assistant will revert to the previous version. Once it boots, check the release notes for that version to see if there were any known issues, then try updating again.
A stuck update is almost always caused by a network interruption or a device that ran out of disk space. If you have less than 500 megabytes of free space on the device, Home Assistant cannot read or install updates. Check your available storage before updating, especially on Raspberry Pi systems, which have limited space.
Preparing your system for a smooth update
Before you update, make sure your device has a stable power supply. If you are running Home Assistant on a Raspberry Pi, use the official power adapter — cheap USB chargers can cause the device to shut down unexpectedly during updates. If you are running it on a computer, make sure the computer is plugged in and will not sleep during the update.
Check your internet connection. Run a speed test or try loading a website to confirm you have a stable connection. If you are on WiFi, move closer to your router or switch to a wired connection if possible. A dropped connection during the read will force Home Assistant to revert.
Give yourself at least 20 to 30 minutes of uninterrupted time. Do not update right before you leave the house or before bed. If something goes wrong, you will want to be present to restart the device or troubleshoot. Check the release notes before updating — if they mention a database migration or major changes, plan for 30 to 45 minutes instead.
What to do if an update fails
If the update fails, Home Assistant automatically reverts to the previous version. You will see an error message on the screen. Write down the error message or take a screenshot — this information helps if you need to ask for help in the Home Assistant forums.
Wait 5 minutes, then try updating again. Many failures are temporary network glitches that will not happen twice. If the update fails a second time with the same error, check the Home Assistant forums or GitHub issues to see if other users have reported the same problem. Sometimes a specific version has a bug that affects certain hardware, and the next release will fix it.
If you cannot wait for the next release, you can manually downgrade to an older version by accessing the Home Assistant files directly, but this requires technical knowledge. For most users, waiting for the next release is the safest option.
Updates on different hardware
Home Assistant runs on many devices, and update speed varies by hardware. On a modern computer or NAS, updates usually take 5 to 10 minutes. On a Raspberry Pi 4, expect 10 to 15 minutes. On older Raspberry Pi models (Pi 3 or earlier), updates can take 20 to 30 minutes because the processor is slower and the startup phase takes longer.
If you are running Home Assistant in Docker or as a virtual machine, update speed depends on how much CPU and memory you have allocated. If your Docker container or VM is limited to one CPU core and 512 megabytes of RAM, startup will be slow. Giving Home Assistant more resources will speed up updates.
The device's storage type also matters. Home Assistant running on a fast SSD will update faster than the same system on a USB drive or SD card. If you are using a Raspberry Pi with a slow SD card, consider upgrading to a faster card or moving to a USB SSD — this will speed up not just updates but everyday operation.
Frequently Asked Questions
Can I use my smart home while an update is running?
No. During the update, all integrations are offline and your devices will not respond to commands or automations. The update usually takes 5 to 15 minutes, so plan updates for a time when you do not need to control anything. Once the loading screen disappears, everything is back online.
Will a power loss during an update break Home Assistant?
No. Home Assistant is designed to handle power loss during updates. When power returns, the system will boot and revert to the previous version automatically. You can then try the update again once the device is stable. However, repeated power loss during updates can eventually damage the storage device, so use a stable power supply.
Why does the first update after I set up Home Assistant take so long?
The first update loads and initializes every integration for the first time, which takes longer than normal startup. Subsequent updates are faster because Home Assistant only needs to load the new code, not discover all your devices again. If the first update takes 20 to 30 minutes, this is normal.
Should I update Home Assistant as soon as a new version is released?
You do not have to update when ready. Most users wait a day or two to see if other users report problems with the new version. If you are running a stable system and do not need new features, waiting a week is fine. Home Assistant releases a new version every week, so there is no rush.
Can I schedule updates to happen automatically at a specific time?
Home Assistant does not have a built-in automatic update scheduler. You have to manually click the update button. Some users create automations that send them a notification when an update is available, so they remember to update during a convenient time. This gives you control over when your system goes offline.