I am getting a notification to upgrade my supervisor to 209. Now on 212. Is that an error or has 212 been pulled?
Mine shows 213 available.
Just rebooted again and this is what I see:
EDIT: I took the ‘update’ from 212 to 209, rebooted, and then got the upgrade notice to 213 and took that successfully. So all back to normal. Not sure why it had to downgrade to 209.
Maybe there were problems with 212
Well, after updating to 213 I can no longer control my supervisor (through the web UI or through SSH), and I also can’t access any add-ons. So… I’d stick with 209 for now. I can’t restore any snapshots, it seems, so I’ll manually SFTP the backup file to my desktop, re-install Home Assistant, and hope that the latest version still comes with 209 Supervisor… 
Problem is the supervisor updates itself. Sometime you see an update available on the supervisor screen, but even if you don’t press update, it will update.
Yikes! I wasn’t aware of that…
Also forgot to mention above, my Z-Wave network is down as a result of this as well. Luckily, the latest stable Home Assistant build still ships with Supervisor 208, so hopefully I can find a way to stop it from updating to 213?
I had the same issue this morning. If i’m correct, 212 was pulled.
When I ran 212, my addon store broke and it didnt show the addons I had installed under supervisor.
Any reports on that? And are there people running 213 alreadh?
It seems mine updated, now I get
i updated to 213 , the behaviour i am noticing is that now my addons show that they have an update (most of them if not all) and the version of the update is undefined (i suppose that’s why HA believes that there is an update because version undefined is different that the one installed. eg the message i get from adguard is
Update available! 
AdGuard Home undefined is available
You are currently running version 2.3.2
the same applies to most of all my addons
Supervisor 213 HA version 107.7
I am now on 213 supervisor, and all appears fine. Not seeing any issues noted above. On .107.7 Hassio, rpi 3B+. SSD boot drive.
i am using docker on ubuntu 18.04 so that should play a role , although never have seen this problem before.
FWIW Installing Home Assistant (HASSIO) from scratch (which automatically updated Supervisor from 209 to 213), restoring my snapshot that I’d transferred to my desktop via SFTP prior, and then updating Core to 0.107.7, and finally restarting NODE-RED seems to have resolved most of the issues for now. Although, as others have said, NODE-RED is reporting an update is available in the logs with version NULL.
Same error here after updating to 213
I really don’t understand why the Supervisor is required to be forced to update. And for exactly this reason.
Just let the user decide when/if to update the supervisor. That way if things break after the update people have a starting point where to look for the problem instead of people waking up to find their HA broken with no idea what happened.
1 Like
I got everything working again.
systemctl stop docker
systemctl start docker
curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s -- -m raspberrypi3
systemctl start hassio-supervisor.service
Nothing lost, just had to restart the add-ons manually.
I tried that too, critical error is gone. But still no addons
And please people dont copy paste his code unless you run it off a raspberrypi3