I’m new to HA and are trying to learn it better. so I was trying to manipulate configuration.yaml. for that I need to use “File editor” adds-on. for installing it I need to update my supervisor and here is the problem.
I get lots of error from 'AddonManager.install' blocked from execution, system is not healthy - supervisor
to System is not ready with state: setup
and 'AddonManager.install' blocked from execution, supervisor needs to be updated first
I solved two first ones by, performing following commands
banner
su restart
su repair
they usually return again but are manageable. however when I try to solve last one using supervisor update
I encounter following error on HA OS
Error:update of supervisor failed: cant instal ghcr.io/home-assistant/supervisor/pkgs/container/amd64-hassio-supervisor:2024.10.3:
500 server error for http+docer://localhost/v1.47/images/create?tag=2024.10.3&fromImage=ghcr.io%Fhome-assistant%2Famd64-hassio-supervisor&platform
=linux%Famd64: internal server error ("head "https://ghcr.io/v2/home-assistant/amd64-hassio-supervisor/mainfests/2024.10.3":di al tcp 140.82.121.34:443: i/o timeout")
I’m using VM work station on Windows 10 and followed the guide for installation on windows. on https://www.home-assistant.io/installation/windows
I had some problem entering the http://homeassistant.local:8123 because of supervisor errors in update but they went away at some point.
Me too. Some weird things happened after I updated to 11.0, and this is one of them. My question; Is the only way to fix this to reinstall and use an old backup? This might be the perfect time for me to move from Pi4 to a spare NUC I have floating about!
I am busy moving from my VM setup to a NUC and then this lol. Now I can’t configure anything because I can’t install add-ons. It should be fixed quickly I believe but if I just reinstall HA, will that have the latest update already loaded?
Had this problem tonight when trying to add a new add on.
Solved by doing a full shutdown of Home Assistant then restarting it again.
Issue looks to be related to the failed Supervisor update 2024.11.3 that was withdrawn but left the system as ‘not healthy’.