Not sure why, but mine seems to have started working again, but only when I ssh’d into the box and ran hassio homeassistant update.
This command didn’t work before, but it seems to now.
If you don’t have ssh access setup, you need to set up your authorized_keys file using these instructions and ssh using: ssh root@[your_hass_ip]
@xx_Nexus_xx Might want to try this and let us know.
Just a further note, after I do the update (via UI or via SSH), I would not be able to connect to HA. But when I turn off power and turn it back on again, the 0.69.1 instance of HA appears back as normal. Not sure if this is the same as yours or if it is relevant.
Unfortunately for me not… I’m seeing the following error in the hassio panel
18-06-25 08:31:00 INFO (SyncWorker_12) [hassio.docker.interface] Update docker 0.69.1 with homeassistant/raspberrypi3-homeassistant:0.72.0
18-06-25 08:31:00 INFO (SyncWorker_12) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.72.0.
18-06-25 08:37:04 ERROR (SyncWorker_12) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.72.0 → 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.72.0: No such image: homeassistant/raspberrypi3-homeassistant:0.72.0”).
I don’t think so. The home assistant package is not so big. With each update it may be getting some what bigger depending on the functionalities added. Maybe 0.71 was a big update since lot of others have this issue. I believe the add-ons take up much bigger space, or the history component. So if you have a lot of addons installed you can run out of space. If you keep your installation clean and set the history to a few days I don’t think you run out of space. Im not an expert, so correct me if Im wrong