Not connected with the supervisor / system too busy! / Error during setup of component hassio

I don’t know what’s causing this, but I’ve seen this start to happen more often. I have no idea what’s causing this, and it prevents add-ons from being loaded. I’ve tried cleaning my configuration.yaml to only what’s necessary, and it’s already pretty stripped down.

I also see these errors:
“Can’t read Supervisor data: System is not ready with state: setup”
“Can’t read panel info: System is not ready with state: setup”
“Error during setup of component hassio”

I tried asking for some help on discord but didn’t get much of a response.

Thank you!

Had it as well ystd…restarted… issue gone

I’ve restarted maybe half a dozen times already or more but it’s not working anymore. I’ll keep trying.

It shows this in the logs:

Error during setup of component hassio
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 256, in _async_setup_component
    result = await task
  File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 587, in async_setup
    await repairs.setup()
  File "/usr/src/homeassistant/homeassistant/components/hassio/repairs.py", line 149, in setup
    await self.update()
  File "/usr/src/homeassistant/homeassistant/components/hassio/repairs.py", line 157, in update
    data = await self._client.get_resolution_info()
  File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 51, in _wrapper
    raise HassioAPIError(data["message"])
homeassistant.components.hassio.handler.HassioAPIError: System is not ready with state: setup
1 Like

With me it was on my syno nas who was running many things in paralllel so it seemed. Have you changed anything? HAOS version , hardware. other?

As far as I know I didn’t change anything. I’m trying to think. I was working on my config.yaml file so I removed all the changes I made to that.

I’m going to go over my yaml files and see if there was something else I changed. I did try updating to a newer version of HA core but it wouldn’t let me.

Maybe it was incorrect indentation in my configuration yaml? I deleted some more stuff and then it rebooted. I added the stuff back in and there was one indentation that was wrong. I’m seeing if it will reboot properly now that I fixed the indentation.

Depending on where you come from, recent updates bring database changes and these are slowing things down. I have 2 setups, one docker and one HAOS (for testing) and they both showed issues but it was just a thing being patient with this…cannot say this is the same for you of course. In short, try to verify what you changed and maybe undo it, you hopefully understand it is quite hard to support from afar

can be many reasons. What hardware you use? my raspberry 3b is sometimes also tooo slow and doesnt recover unti lhour later. Reboot wont help mostly then, just patience (or upgrade hardware)

I’ve been having a similar issue for the last couple of months!

I’m running a VirtualBox installation on a Windows laptop set with 2 CPU cores from an old Intel i7-4500U CPU and 2GB of RAM (50% free).

Whenever I restart the virtual machine, the system loads but hassio doesn’t load and shows these errors.
After a VM restart, if I do a HA restart (which doesn’t restart the VM, just the Home Assistant) this doesn’t happen and hassio loads fine.
So any time I restart my computer for other reason, I have to restart HA for a second time after it loads.
Restarting the VM takes about 3min and restarting HA takes about 1:10.

This laptop is almost 100% dedicated to HA, sometimes I use it to copy files between drives but the computer is never busy with something else when I’m restarting HA.

I’m waiting on a Home Assistant Yellow (on its way home!), I was hoping this issue would be solved when I migrate to it but I see that it also happens on a RPi :frowning:

R.

1 Like

I’ve got the same error, but it only occurs after a few days. I’m running HA in a VM with 6GB RAM and two cores.

Because the problem takes time to occur it’s hard to determine the culprit. The only thing I can think of is an update. Maybe Frigate, as I recently updated that add-on. The memory usage shows a slope/spike before the supervisor stops. It could be a memory leak, but I’m just guessing, the memory can be used for caching as well.

Thanks for the hint! Had the same issue and this did the trick to me.