Yes this is confusing. The whole “supervisor shows core needs to update but once you click update you have to go somewhere else in the gui to check it worked” is a bit annoying.
2 Likes
I am getting following error updating from Supervisor. Any idea why?
21-01-10 00:30:17 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2021.1.1
21-01-10 00:30:17 INFO (SyncWorker_0) [supervisor.docker.interface] Updating image homeassistant/qemux86-64-homeassistant:2020.12.1 to homeassistant/qemux86-64-homeassistant:2021.1.1
21-01-10 00:30:17 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image homeassistant/qemux86-64-homeassistant with tag 2021.1.1.
21-01-10 00:31:54 ERROR (SyncWorker_0) [supervisor.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:2021.1.1 -> 404 Client Error for http+docker://localhost/v1.40/images/homeassistant/qemux86-64-homeassistant:2021.1.1/json: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:2021.1.1: No such image: homeassistant/qemux86-64-homeassistant:2021.1.1”).
21-01-10 00:31:54 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
Often a sign that your hard drive is too full.
Thanks Tom! Found it.
I do think this should also be on the Supervisor window as an additional line item as this is the page where we look for and accept upgrades / updates. As I update and refress the screen I expected on the same screen to see the version increase as it does on the same page for the “Host System” when on the same screen I accept the update.
1 Like
As addons and the core are just are docker images, the supervisor page seems a logical place to put some version info, along with the addon versions.
1 Like
Unfortunately I’m still facing the same issue with log error:
Error setting up entry Configuration.yaml for neato
AttributeError: 'NoneType' object has no attribute 'encode'
I’ve updated to 2021.1.1, removed my vacuum from my Neato account and re-added it again, rebooted HA several times, but each time it results in the same error. Worse off, deleting the integration and re-adding it results in my Neato integration card showing multiple ‘Configuration.yaml’ forcing me to restore a prior docker container state each time.
Thoughts?
Update: Several reboots fixed my problem
I get a 500 server error:
21-01-10 08:29:12 ERROR (SyncWorker_2) [supervisor.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:2021.1.1 -> 500 Server Error for http+docker://localhost/v1.40/images/create?tag=2021.1.1&fromImage=homeassistant%2Fqemux86-64-homeassistant: Internal Server Error (“Get “https://registry-1.docker.io/v2/”: context deadline exceeded”).
Since the update to 2021.1.0, I get a lot of network specific problems that prevent some components from being set up.
2021-01-10 13:59:07 WARNING (MainThread) [homeassistant.loader] Pastebin.com
I have a Home Assistant Core installation in a Docker container. I have logged into the container via shell and can definitely reach external addresses from it.
I have also tried disabling each component in turn to see if a particular one is causing the problem. But the problem persisted even when I loaded them individually.
Unfortunately, I am currently at a bit of a loss as to what is causing the problem. 
Upgraded to 2021.1.1 from 2020.12.1 with no issues. Also upgraded to HAOS 5.10 with no issues on a Pi 4. New Years resolution is to build more automations in Node Red to take advantage of all the tech I have added.
This is a known bug in pybotvac that has reappeared since we merged the OAuth changes.
I am not quite sure what is the exact reason for this error. As a result, we get incorrect or at least undocumented data from neato, so we run into a parsing error. An upcoming version of pybotvac will work around this problem. For now, please check your account for broken robots at https://neatorobotics.com. We know of users who were able to fix this issue by deleting old or unknown robots from their account.
When instantiating a new OAuth integration in Home Assistant, make sure you start only one configuration flow at a time. Even though you can click “Open Website” several times, press it only once and wait until this flow is complete.
1 Like
Thank you, @Santobert!
I apparently did have a dormant/broken robot hiding in my account online. Removing that allowed the Neato integration to connect without error.
2 Likes
Must be a bug
7 Likes
hahahaha!!!
We love you guys. You all rock
3 Likes
You beta users have all the fun!
Well yeah…
1 Like
Really like this update, working great, no issues for me so far. 
The quick bar thing is really nice also, makes me wonder how I managed without it!
@frenck
Thank you very much for taking the time to explore a way to make a short link to the minor releases! Thanks!
I would like to point out that as soon as I upgraded from 2021.1.1 to 2021.1.3 my ‘weather-card’ card no longer worked correctly instead of showing MON TUE WEDNESDAY THU FRI always shows the day MON
1 Like
Maybe your weather card is vulnerable to cross site attacks or sql injection?
That shit is verboten now.
Take it up with the card developer.