Updating Home Assistant

The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install Hass.io, HASSbian, Vagrant, or Virtualenv.

Check what’s new in the latest version and potentially impacts your system in Home Assistant release notes. It is good practice to review these release notes and pay close attention to the Breaking Changes that are listed there. If you haven’t done an update for a while, you should also check previous release notes as they can also contain relevant Breaking Changes. Breaking Changes may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check <config-dir>/home-assistant.log for details about broken components.

The default way to update Home Assistant to the latest release, when available, is:

$ pip3 install --upgrade homeassistant

After updating, you must restart Home Assistant for the changes to take effect. This means that you will have to restart hass itself or the autostarting daemon (if applicable). Startup can take considerable amount of time (i.e. minutes) depending on your device. This is because all requirements are updated as well.

To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install Hass.io, HASSbian, Vagrant, or Virtualenv.

BRUH automation has created a tutorial video explaining how to upgrade Home Assistant.

Run a specific version

In the event that a Home Assistant version doesn’t play well with your hardware setup, you can downgrade to a previous release:

$ pip3 install homeassistant==0.XX.X

Run the development version

If you want to stay on the bleeding-edge Home Assistant development branch, you can upgrade to dev.

The “dev” branch is likely to be unstable. Potential consequences include loss of data and instance corruption.

$ pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@dev