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 the log file in the configuration directory, e.g.,
.homeassistant/home-assistant.log, for details about broken components.
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.
The default way to update Home Assistant to the latest release, when available, is:
$ pip3 install --upgrade homeassistant
For a Docker container, simply pull the latest one:
$ sudo docker pull homeassistant/home-assistant:latest
After updating, you must start/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.
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
If you would like to test next release before anyone else, you can install the beta version released every two weeks:
$ pip3 install --pre --upgrade homeassistant
If you want to stay on the bleeding-edge Home Assistant development branch, you can upgrade to
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