Uable to update from .92 to .93

notchy · May 16, 2019, 10:27pm

I am using Hassio in a VM on Ubuntu and I am unable to update Home Assistant 0.93.
This is what i get in my log.
Does anyone know why it can not find the image to install?

Blockquote
19-05-16 18:56:36 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-05-16 18:56:36 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-05-16 18:56:36 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-05-16 18:56:36 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running
19-05-16 19:01:23 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.93.0
19-05-16 19:01:23 INFO (SyncWorker_3) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.92.0 to homeassistant/qemux86-64-homeassistant:0.93.0
19-05-16 19:01:23 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.93.0.
19-05-16 19:03:03 ERROR (SyncWorker_3) [hassio.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:0.93.0 → 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.93.0: No such image: homeassistant/qemux86-64-homeassistant:0.93.0”).
19-05-16 19:03:03 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
19-05-16 19:03:49 INFO (MainThread) [hassio.auth] Auth request from core_configurator for hcreight
19-05-16 19:03:51 INFO (MainThread) [hassio.auth] Success login from hcreight
Blockquote

gerdesj · May 16, 2019, 10:53pm

I’ve installed a new HA today at work and I got 0.92.2. I suspect you probably need to wait a little while. I’ve just now run a quick install via pip on my office PC and I got 0.93.

Try it now.

BrianHanifin · May 17, 2019, 12:23am

I’m getting a different error, but I am also not able to update hass.io despite it being available (19 hours ago) according to https://hub.docker.com/r/homeassistant/qemux86-64-homeassistant/tags 0.93 (and “latest”).

19-05-16 14:10:42 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.93.0
19-05-16 14:10:42 INFO (SyncWorker_9) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.92.2 to homeassistant/qemux86-64-homeassistant:0.93.0
19-05-16 14:10:42 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.93.0.
19-05-16 14:10:42 ERROR (SyncWorker_9) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.93.0 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:49955->[::1]:53: read: connection refused").
19-05-16 14:10:42 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

loonysup · May 17, 2019, 10:52am

I’m getting the same error when trying to update to .93. I’m on a fresh Ubuntu VM that I built last week and am currently on Hassio running .92.2

notchy · May 17, 2019, 1:07pm

I am still not able to update Home Assistant. I wonder why a few people are experiencing the update. Is the file corrupt or the correct name as the error says image not found on the server.

joggs · May 17, 2019, 1:10pm

Same here running hassio on HYPER-V

19-05-17 13:05:27 INFO (MainThread) [hassio.core] Hass.io is up and running
19-05-17 13:05:31 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.93.1
19-05-17 13:05:31 INFO (SyncWorker_3) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.92.2 to homeassistant/qemux86-64-homeassistant:0.93.1
19-05-17 13:05:31 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.93.1.
19-05-17 13:05:41 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-05-17 13:05:41 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-05-17 13:05:41 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running
19-05-17 13:06:09 ERROR (SyncWorker_3) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.93.1 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.93.1: No such image: homeassistant/qemux86-64-homeassistant:0.93.1").
19-05-17 13:06:09 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

Gazzah · May 17, 2019, 5:19pm

Same thing here running on Pi, click update, spinny for a few mins then nothing…
homeassistant:0.92.2 to homeassistant/raspberrypi3-homeassistant:0.93.1 19-05-17 17:02:37 INFO (SyncWorker_18) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.93.1. 19-05-17 17:02:59 ERROR (SyncWorker_18) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.93.1 -> 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.93.1: No such image: homeassistant/raspberrypi3-homeassistant:0.93.1”). 19-05-17 17:02:59 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

Also the last update killed my BT home hub integration, so I dont know if Im home or away

Gazzah · May 18, 2019, 10:52am

tried the update again today, and it has all worked…

notchy · May 20, 2019, 1:51pm

I attempted to today to get my version updated and it does not update.

Any other ideas ?

joggs · May 22, 2019, 11:50am

It is a partition space issue.
To solve it, I increased the disk size of hassio in my VM manager and then downloaded and mounted the gparted live disk onto my hassio VM, changed the boot priority so the mounted iso is first in line, started the VM which launched gparted. Gparted then discovers that the partition is smaller than the disk size and asks if I want to increase the partition, which I answer yes to. The partition size is now increased and you can unmount gparted and reboot the VM and the update should work

ConcordGE · May 22, 2019, 8:35pm

I don’t use the Hass.io method install but I assume that all Raspberry Pi users expand the file system once they install Raspbian for the first time

joggs · May 23, 2019, 5:44am

What a stupid assumption.

ConcordGE · May 23, 2019, 10:02am

Stupid assumption ???

It’s part of the standard install after creating the image and before the update/upgrade procedure with sudo raspi-config

joggs · May 23, 2019, 11:14am

Yes, Assuming that ALL Raspberry Pi users expand the file system once they install Raspbian for the first time is stupid and naive. Have you heard about different personalities and personality colors? You are obviously very blue.

ConcordGE · May 23, 2019, 11:33am

I think you maybe expanding your mind as well as your file system.

Haven’t the time for a philosophical discussion here. As long as the user has sorted their issue that’s all that matters.

Home automation does tend to attract all sorts though. They do say if you’ve nothing good to say, say nothing.

joggs · May 23, 2019, 11:52am

That’s the whole point. Your stupid assumption was not helping at all, just annoying.

notchy · May 23, 2019, 12:01pm

@joggs and @ConcordGE - guys lets be nice the community does not need the negative comments. We are all hear to help each other out and have a positive experience with HA. This is bigger then all of us, so lets make this pleasent for new users and not make them afraid to ask questions.

@joggs - thanks for the suggestion and I will give that a try this weekend when i have some free time and hope it works out for me and it should help other users who have had the same issues as us.

Devoraz · September 9, 2019, 7:39pm

joggs, thanks for the tip for enlarging the partition of the VM of Hassos. Finally I can update again. I was running a few versions behind, already.