TPLink HS110 upgrade stuck on Homeassistant 0.78.0

Archive HASSbian
1

Hi Guys,

Trying to upgrade to HA 0.78.0 from 0.77.3.

While the upgrade itself ran smooth when I restart HA the daemon status gets stuck with the dependency (TPLink switch HS100) below:

[email protected] - Home Assistant for homeassistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-09-19 15:44:21 SAST; 24min ago
Main PID: 847 (hass)
CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
├─847 /srv/homeassistant/bin/python3 /srv/homeassistant/bin/hass
└─889 /srv/homeassistant/bin/python3 -m pip install --quiet pyHS100==0.3.3 --upgrade --constraint /srv/homeassistant/lib/python3.5/site-packages/homeassistant/package_constraints.txt

I tried running the command manually:

pip install pyHS100==0.3.3 --upgrade --constraint /srv/homeassistant/lib/python3.5/site-packages/homeassistant/package_constraints.txt

but it hangs with the following output on the screen:

Looking in indexes: https://pypi.org/simple, https://www.piwheels.hostedpi.com/simple

Funnily, if I run:

pip install pyHS100==0.3.3 --constraint /srv/homeassistant/lib/python3.5/site-packages/homeassistant/package_constraints.txt

It runs fine but once I start HA it still tries to update the dependency as per above.

Any ideas?

Tx

2

That sounds odd, running the same (path-adjusted) command seems to work just fine here, although I’m getting no information about which indexes are checked. Maybe a problem in your network connectivity/DNS?

3

Hi teprrr - no issues with network or DNS.

4

Hmh, okay, are both those domains accessible for you? If yes, then I have no idea what could be the problem :frowning:

5

I even tried a pip uninstall and install and it runs fine (both install & uninstall) but with the same result (when I start HA it hangs with dependency)… tx 4 trying.

6

Further to the above I noticed that the pip constraints file for 0.78.0 shows:

aiohttp == 3…4.4 but running pip list shows I have aiohttp 3.4.0 installed.
When running sudo pip install aiohttp==3.4.4. I get the following:

Looking in indexes: https://pypi.org/simple, https://www.piwheels.hostedpi.com/simple
Collecting aiohttp==3.4.4
Using cached https://www.piwheels.hostedpi.com/simple/aiohttp/aiohttp-3.4.4-cp35-cp35m-linux_armv7l.whl
Requirement already satisfied: yarl<2.0,>=1.0 in /usr/local/lib/python3.5/dist-packages (from aiohttp==3.4.4) (1.2.5)
Requirement already satisfied: async-timeout<4.0,>=3.0 in /usr/local/lib/python3.5/dist-packages (from aiohttp==3.4.4) (3.0.0)
Requirement already satisfied: chardet<4.0,>=2.0 in /usr/local/lib/python3.5/dist-packages (from aiohttp==3.4.4) (3.0.4)
Requirement already satisfied: multidict<5.0,>=4.0 in /usr/local/lib/python3.5/dist-packages (from aiohttp==3.4.4) (4.3.1)
Requirement already satisfied: idna-ssl>=1.0; python_version < “3.7” in /usr/local/lib/python3.5/dist-packages (from aiohttp==3.4.4) (1.0.1)
Requirement already satisfied: attrs>=17.3.0 in /usr/local/lib/python3.5/dist-packages (from aiohttp==3.4.4) (18.2.0)
Requirement already satisfied: idna>=2.0 in /usr/local/lib/python3.5/dist-packages (from yarl<2.0,>=1.0->aiohttp==3.4.4) (2.6)

homeassistant 0.70.1 has requirement aiohttp==3.1.3, but you’ll have aiohttp 3.4.4 which is incompatible.
homeassistant 0.70.1 has requirement async-timeout==2.0.1, but you’ll have async-timeout 3.0.0 which is incompatible.
homeassistant 0.70.1 has requirement attrs==18.1.0, but you’ll have attrs 18.2.0 which is incompatible.
homeassistant 0.70.1 has requirement requests==2.18.4, but you’ll have requests 2.19.1 which is incompatible.
homeassistant 0.70.1 has requirement voluptuous==0.11.1, but you’ll have voluptuous 0.11.5 which is incompatible.

Installing collected packages: aiohttp
Found existing installation: aiohttp 3.4.0
Uninstalling aiohttp-3.4.0:
Successfully uninstalled aiohttp-3.4.0
Successfully installed aiohttp-3.4.4

Do I somehow have leftovers from HA 0.70.1, or is this normal?

7

Moving on, I tried a clean install of now 0.78.3 but still getting stuck on the same spot. From within the venv I then ran pip install with “-v” and get the following before it doesn’t continue any further:

pip install -v pyHS100==0.3.3 --upgrade --constraint /srv/homeassistant/lib/python3.5/site-packages/homeassistant/package_constraints.txt
Created temporary directory: /tmp/pip-ephem-wheel-cache-y9e7u8i4
Created temporary directory: /tmp/pip-install-mbfpb69f
Looking in indexes: https://pypi.python.org/simple, https://www.piwheels.hostedpi.com/simple
Collecting pyHS100==0.3.3
2 location(s) to search for versions of pyHS100:

It looks as if the second source is giving issues? How do I tell pip to use the 1st source?

tx

8

Ok issue solved with a workaround:

With having 2 sources and the 2nd one not behaving I have disabled the 2nd source in /etc/pip.conf to:

[global]
#extra-index-url=https://www.piwheels.org/simple

With now only 1 source everything is updating & working.
I guess someone needs to look into the above source as to why this specific component is not updating.

KR.

9

Piwheels seems to be an unofficial pypi repository for raspberry pi, so I think you could try to report the problem to them. Glad that you got it working though!