Home Assistant install script...Query

Archive HASSbian
1

I upgrade my HA instance on RPi3 with the following command:

sudo hassbian-config upgrade homeassistant

The output I get is shown below with my comments in italics I have always had a couple of errors but my systems ran well, since 0.75.1 its been decidedly dicey so need to have a check to see if there is anything that needs attention:

Home Assistant install script for Hassbian.
Copyright© 2017 Fredrik Lindqvist https://github.com/Landrash.

Checking current version
You are using pip version 10.0.1, however version 18.0 is available. I have installed pip and updated but error remains the same so I assume this is embedded, I am also assuming this is not an issue
You should consider upgrading via the ‘pip install --upgrade pip’ command.
Stopping Home Assistant
Changing to the homeassistant user
Changing to Home Assistant venv
Installing latest version of Home Assistant
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already up-to-date: setuptools in /srv/homeassistant/lib/python3.5/site-packages (40.0.0)
Requirement already up-to-date: wheel in /srv/homeassistant/lib/python3.5/site-packages (0.31.1)
python-jose-cryptodome 1.3.2 has requirement pycryptodome<3.4.0,>=3.3.1, but you’ll have pycryptodome 3.4.11 which is incompatible. Is this something I can resolve or should be concerned about?
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the ‘pip install --upgrade pip’ command.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already up-to-date: homeassistant in /srv/homeassistant/lib/python3.5/site-packages (0.75.2)
Requirement not upgraded as not directly required: pip>=8.0.3 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (10.0.1)
Requirement not upgraded as not directly required: jinja2>=2.10 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (2.10)
Requirement not upgraded as not directly required: astral==1.6.1 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (1.6.1)
Requirement not upgraded as not directly required: voluptuous==0.11.5 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (0.11.5)
Requirement not upgraded as not directly required: pytz>=2018.04 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (2018.5)
Requirement not upgraded as not directly required: attrs==18.1.0 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (18.1.0)
Requirement not upgraded as not directly required: certifi>=2018.04.16 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (2018.4.16)
Requirement not upgraded as not directly required: requests==2.19.1 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (2.19.1)
Requirement not upgraded as not directly required: pyyaml<4,>=3.13 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (3.13)
Requirement not upgraded as not directly required: aiohttp==3.3.2 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (3.3.2)
Requirement not upgraded as not directly required: async-timeout==3.0.0 in /srv/homeassistant/lib/python3.5/site-packages (from homeassistant) (3.0.0)
Requirement not upgraded as not directly required: MarkupSafe>=0.23 in /srv/homeassistant/lib/python3.5/site-packages (from jinja2>=2.10->homeassistant) (1.0)
Requirement not upgraded as not directly required: idna<2.8,>=2.5 in /srv/homeassistant/lib/python3.5/site-packages (from requests==2.19.1->homeassistant) (2.6)
Requirement not upgraded as not directly required: chardet<3.1.0,>=3.0.2 in /srv/homeassistant/lib/python3.5/site-packages (from requests==2.19.1->homeassistant) (3.0.4)
Requirement not upgraded as not directly required: urllib3<1.24,>=1.21.1 in /srv/homeassistant/lib/python3.5/site-packages (from requests==2.19.1->homeassistant) (1.22)
Requirement not upgraded as not directly required: yarl<2.0,>=1.0 in /srv/homeassistant/lib/python3.5/site-packages (from aiohttp==3.3.2->homeassistant) (1.2.5)
Requirement not upgraded as not directly required: multidict<5.0,>=4.0 in /srv/homeassistant/lib/python3.5/site-packages (from aiohttp==3.3.2->homeassistant) (4.3.1)
Requirement not upgraded as not directly required: idna-ssl>=1.0 in /srv/homeassistant/lib/python3.5/site-packages (from aiohttp==3.3.2->homeassistant) (1.0.1)
python-jose-cryptodome 1.3.2 has requirement pycryptodome<3.4.0,>=3.3.1, but you’ll have pycryptodome 3.4.11 which is incompatible. Again I assume this is not an issue but would appreciate confirmation
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the ‘pip install --upgrade pip’ command.
Deactivating virtualenv
Restarting Home Assistant
Checking the installation…

Upgrade complete…
Note that it may take some time to start up after an upgrade.

FYI I am now running 0.75.2 and issues remain the same.
Thanks in advance.

2

You probably have to update pip inside the HA virtual environment to affect this, but it shouldn’t be a problem just running with the existing version

There are few threads about this a couple of months ago, and from that I heard that this wasn’t really a problem to worry about.

Upgrading to 0.75 was my plan for this evening. Is there anything specific that has gone wrong that I should be careful about?

3

I had the pycrytodome error on an upgrade I did a couple of months back. I don’t remember the exact problem but I think it did cause an issue with running my HA. I never could get an answer on what to do about it and everything I tried just seemed to make things worse so I just reverted back to a known good backup of the SD card. Then when everything was working again I did another upgrade and after that everything was good.

4

Thanks @finity

Has anyone else had similar experience?

5

Thanks @gpbenton

Unless I hear otherwise I will not dig too deep into the areas you have commented on.

As for the stability of 0.75.2 I haven’t seen any widely reported issues as I was looking for that as a potential root cause of my issues.