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.
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.
Must be a bug
hahahaha!!!
We love you guys. You all rock
You beta users have all the fun!
Well yeah…
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
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.
OK Thank you
Sensor of netatmo weather not work
not much HA can do when Netatmo’s service is down…in general if no error in your log (after activating Debug for the Netatmo component) then check http://helpcenter.netatmo.com and you’ll get your answers
For me, after updating to 2021.1.3 my ‘weather-card openweather map’ card no longer worked correctly instead of showing MON TUE WEDNESDAY THU FRI always shows the day Monday.
hello i am also in your same situation have you found a solution? At the moment I am back to 2021.1.1, I believe those who developed the weather card have not put their hand on it for some time
