Upgrade twice for success?

Archive All-In-One Installer
1

Anyone else having to upgrade twice for HASS to work? My process (for at least the last 3-4 releases) has been as follow:

systemctl stop home-assistant@hass
su -s /bin/bash hass
virtualenv -p python3 /var/opt/home-assistant
source /var/opt/home-assistant/bin/activate
pip3 install --upgrade homeassistant
systemctl start home-assistant@hass
su -s /bin/bash hass
virtualenv -p python3 /var/opt/home-assistant
source /var/opt/home-assistant/bin/activate
pip3 install --upgrade homeassistant
systemctl start home-assistant@hass

After the first upgrade when I start HASS fails to load/find the components:

Jun 20 09:56:20 automation systemd[1]: Started Home Assistant.
Jun 20 09:56:26 automation hass[8563]: INFO:homeassistant.bootstrap:Upgrading config directory from 0.21.2 to 0.22.1
Jun 20 09:56:27 automation hass[8563]: INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_off>
Jun 20 09:56:27 automation hass[8563]: INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_on>
Jun 20 09:56:27 automation hass[8563]: INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeassistant, service=toggle>
Jun 20 09:56:27 automation hass[8563]: INFO:homeassistant.bootstrap:Home Assistant core initialized
Jun 20 09:56:27 automation hass[8563]: ERROR:homeassistant.loader:Unable to find component input_boolean
Jun 20 09:56:27 automation hass[8563]: ERROR:homeassistant.loader:Unable to find component wemo
Jun 20 09:56:27 automation hass[8563]: ERROR:homeassistant.loader:Unable to find component wink
....

After going through the upgrade the process the 2nd time:

Jun 20 09:57:42 automation systemd[1]: Starting Home Assistant...
Jun 20 09:57:42 automation systemd[1]: Started Home Assistant.
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_off>
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_on>
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeassistant, service=toggle>
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.bootstrap:Home Assistant core initialized
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.loader:Loaded input_boolean from homeassistant.components.input_boolean
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.loader:Loaded sun from homeassistant.components.sun
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.loader:Loaded device_tracker from homeassistant.components.device_tracker
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.loader:Loaded zone from homeassistant.components.zone
Jun 20 09:57:48 automation hass[8638]: INFO:homeassistant.loader:Loaded automation from homeassistant.components.automation
2

Have you tried restarting hass a second time after the first upgrade?

3

I’ve been doing my AIO upgrades following the instructions from the main site and simply restarting HA after the upgrade. No problems here except the one time I forgot a step.

4

I have… I think. I’ll certainly try that next time and report back what happens, but again I think I have tried. I know that I tried simply doing the update steps twice and seeing what happened when I started back up again. No joy on that.

5

I’m not using the AIO at this point, but I’m thinking about starting fresh with it. I’m simply using the Linux virtual environment setup: https://home-assistant.io/getting-started/installation-virtualenv/

6

I’m glad I did; it made everything so much easier. Props for doing it manually though!