Hi,
I had a critical error with Supervisor but HA kept working for a few weeks. Today, I tried to update it in the UI but things didn’t really work. Now, I can’t access my HA on my iphone app neither on my desktop. I’m running HA on a raspberry pi 3.
When I try 192.168.2.97:4357, it says that the system is unhealthy : supervisor
When I try to connect on the iphone app, I always get an error message : Could not connect to the server. NSURLErrorDomain -1004
I’d like to be able to run HA supervisor update in the CLI but I don’t know how to access it.
Hi,
i’m also having a similar issue. Observer tells me everything is healthy but i’m stuck with my supervisor version. These are my stats:
Running on Raspi 4
External MariaDB
Home Assistant 2023.10.3
Supervisor 2023.10.1
Operating System 11.1
Frontend 20231005.0 - latest
I can’t get the Core to update from 2023.10.3. In HA directly it tells me about the new update but after starting it stops without any notice after some seconds. Even with “supervisor update” typed directly with Screen and Keyboard connected, it tells me no Update available (which is not true, obviously).
Meaning you have already started the/a core-update-process, i suggest you wait awhile , and if “nothing” happens, you could try to “restart” (through the GUI), if it’s after this is not on “Home Assistant 2023.10.5” , click /Settings/System/Updates# the 3dots-show-skipped ( that is if you dont see the Update, in the usual way)
trying again but that’s what i try for some days now. i wasn’t able to update to 2023.10.4 too. Same for .5 and therefore skipped it after some time thinking the next version might work after a while. since then i had several restarts and even an OS update this morning. even after that i don’t get the core to update.
Maybe there was “something fishy” with " 2023.10.4 too. Same for .5" , it happens sometimes ( depending also upon ones “setup/configurations”) , it’s just give it another try ( However also sometimes, after i.e restart, where the update didn’t go through, one don’t see an “update notification”, as it ends up in “skipped” ( if you i.e manage to restart before the update-process finished )
i see the update under “skipped”. i even manually skipped it because i was annoyed to see it on my wall panel. i’m a bit lost here. is there a way to force jobs in the group home_assistant_core to stop or new ones to get through anyway?
Sometimes it is the backup that hangs the homeassistant core group, especially if the backup is to a place that is not available at the moment, like a shutdown NAS or a network/cloud drive that requires login.
