Beta users impacted by the supervisor 2022.11.0 issues, please see this thread
2 Likes
Same here…
Updated my Odroid system today to a new hassio version available which caused very high CPU usage for more than hour.
Had a stupid idea to restart the whole HassOS but after that it took some time to appear web interface.
I was on Stable, not Beta update channel.
About shows following now:
Home Assistant 2022.11.3
Supervisor 2022.10.2
Operating System 9.3
Frontend 20221108.0 - latest
My Addons seems to be working. Is there some recommended procedure I should follow?
After updating to 2022.11.2 HA seems to run into an infinit loop after 3-4 days uptime, and becomes unavailable with a constant CPU load of 25%. Restarting the container brings HA back up, for another 3-4 days. This reminds me of a memory or buffer overflow situation, but I havn’t beenable tofind any log entry to indicate what actually happened. Never had this problem before, and nothing new has been added and nothing else has been changed.
Anyone else seeing similar issues?
I had to revert to 2022.11.2 as 11.3 caused my Pi 4 to overheat and Home Assistant to be unresponsive. It appears that something was causing the CPU usage to stay high.
1 Like
Looks like I have a similar problem. Can’t connect so I’ve powered down to allow it to cool as just restarting didn’t work. Still seemed to be controlling the lights just couldn’t connect from app.
Currently network doesn’t seem to be coming up as not seen when I scan the network. Need to investigate further.
False alarm, it was the router the HA is connected to had lost the connection!
For comparison, I still can’t get my aging RPi 3B+ up above a few percent CPU utilization. I’m at 2022.11.2. I keep hearing about performance problems, and I always worry that it’s going to affect my little HA box more than most, but it keeps chugging happily along.
I’m only reporting this here so others don’t assume it’s always a problem with the new version.
2 Likes
I had to revert to 2022.11.2 as 2022.11.3 made my system (NUC) unresponsive.
I am running a NUC also so will back out to 11.2 and see how that does.
Thanks, that should fix the problem Not
Logs and submissions to github issues fixes stuff, reversion to a previous version does not.
2 Likes
I don’t recall suggesting that fixed any problem.
I was merely acknowledging the level of support you have shown for the project 
1 Like
Always good to balance the discussion. 
It’s quite frustrating to read all the issue reports that merely say “it’s not working”. Very often, but not always, the issues are with 3rd party stuff and then people still struggle to understand why this is a bad idea: WTH why is HACS not standard part of HA. (Anybody that thinks this is an invitation to rant here about that topic, please go there instead. I’m posting it to substantiate my claim.)
Your typical mass consumer sees HA and everything that comes with it as one product and that’s it. The last x number of posts here proves it.
Please: At least try to investigate an issue and report it properly if valid. Do provide context and details to get help.
7 Likes
my nuc has a hissy fit and stops responding after 2022.11.3 and its hard to get logs etc when system boots and you only have access to logs for 3 mins before it becomes unresponsive.
1 Like
as my previouse post states its hard to investigate and issue when you are plugging in a keyboard mouse and monitor and within a few minutes the system stops responding.
ssh in and the log is at /config/home-assistant.log. The previous log is at /config/home-assistant.log.1
The logs are available even if core is not running.
1 Like
I already tried that, problem is machine was hanging before complete and stopped responding, I just rolled back in the end.
Pardon me but I am very confused, more than likely because of the terminology used.
A few days ago I posted that I was getting this error.
Package rest setup failed. Component rest cannot be merged. Expected a dict.
@Mariusthvdb responded and told me what the problem was that I needed to either upload a file or wait for the fix. I am very weary about uploading a file, because I do not want to wipe my system.
So I have been waiting for a fix.
I am running Home Assistant Core in a Docker Container on an UnRaid server. So going through portainer I recreated the container today, just to see if there had been a fix. Nothing has changed.
As you can see from the following sensor output.
Home assistant still gives me the error from above preventing me from restarting.
I am not sure what to do. To many times I have gone ahead and done things with bad consequences.
Any help is appreciated on how I should proceed.