I see an advertised update to 0.80.1, but it appears that 0.80.2 was released. Clicking update in the UI or doing hassio ha update fails. There is nothing in the logs about it.
I’m having the same problem.
I´m with the same problem since yesterday…Now I´ve just installed a fresh new version of hassbian and I found that Hass.io item is missing
Hassio is missing because you installed hassbian!
For the record, I am still having the same issue. But now it shows that 0.80.2 is available. It still fails.
Yep, but today I´ve done a clean install of hassio 32 bits (64 version has lots of incompatibilities) and when I copy my configuration file, hassio dissapears again
In that case, make sure you have either of the following:
discovery:
hassio:
in config yaml.
You have a new fan!
Thanks David!
uncommenting discovery: was the solution
So I found 2 annoying bugs in the upgrade. As it turns out, I’m running out of disk space to perform the upgrade (see bottom of post for more info). But I was getting steered in the wrong direction by the HASSIO Log. I’ve emphasised the 2 confusing log entries below:
- 18-10-20 23:06:20 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
- 18-10-20 23:06:25 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.80.3
- 18-10-20 23:06:25 INFO (SyncWorker_9) [hassio.docker.interface] Update Docker 0.79.3 with homeassistant/qemux86-64-homeassistant:0.80.3
- 18-10-20 23:06:25 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.80.3.
- 18-10-20 23:07:27 ERROR (SyncWorker_9) [hassio.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:0.80.3 -> 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.80.3: No such image: homeassistant/qemux86-64-homeassistant:0.80.3”).
- 18-10-20 23:07:28 WARNING (MainThread) [hassio.homeassistant] Home Assistant is already running!
- 18-10-20 23:07:28 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.80.3
So the 3 things I noticed about that log:
- It’s throwing a “404” error, but the Docker image was definitely located and downloaded prior to failing. (Strange exit code handling?)
- It’s attempting to start the docker image, even though the download failed and the existing image wasn’t stopped. (Shouldn’t that be conditional on the image download succeeded?).
- The test to see if the service started incorrectly assumes that the version that was started/is running is the version that was queued for download. (Using version variable presumably populated much earlier in the script instead of actually reading it from the container.)
Docker CLI clearly showing the actual issue:
root@HomeAssistant:~# docker pull homeassistant/qemux86-64-homeassistant
Using default tag: latest
latest: Pulling from homeassistant/qemux86-64-homeassistant
4fe2ade4980c: Already exists
50d1dff123a7: Already exists
8cbcc78f9039: Pull complete
57d2d63cdc1e: Pull complete
c458d2948192: Pull complete
4789e49f9c6a: Pull complete
76d77960a962: Pull complete
5c99eb62f59f: Pull complete
6dcbcb52b8bc: Pull complete
eec561124505: Pull complete
2898a4d91aa4: Pull complete
9d27ed263515: Pull complete
48e7b205f7c4: Pull complete
8036cf379a49: Pull complete
a4dc9860ecde: Pull complete
51262be9ade7: Pull complete
44cd5570c230: Pull complete
8d45ca9efc73: Extracting [==================================================>] 152.4MB/152.4MB
f4d83006e9d9: Download complete
33310f69faa8: Download complete
failed to register layer: Error processing tar file(exit status 1): write /usr/local/lib/python3.6/site-packages/passlib/_data/wordsets/eff_long.txt: no space left on device
The 0.80.3 release that showed up today did install for me. Not sure what changed to make it work.
i was facing same issue unable to update from 0.79.3 to 0.81.2… then i rebooted RPI3 now hassio does not boot. i don’t even have my configuration files backup