-
-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during setup of component hassio #86622
Comments
Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) hassio documentation |
An update to this: after telling Home assistant to restart through the developer options, everything is fully functional again. |
Another update: I suspect it's some sort of race condition when the host (in this case, the aforementioned QEMU VM) first boots up, supervisor doesn't get started in time for HA to recognise it properly. After then telling HA to restart through the dev menu it all works fully again |
I'm still receiving this, even with restarts from the menu. I'm also running this as a QEMU VM under proxmox |
Having the same issue as well. Becoming more frequent now, after the host boots up, home assistant always has to be restarted last. Add-ons and everything else do not show up until I perform this step. Definitely an issue of home assistance starting too fast or too late |
Same issue here, but on a Raspberry Pi 4 (booting from USB SSD). Restarting Home Assistant from Settings -> System -> Restart fixes it and makes addons show up again, but the issue occurs again after each reboot. |
Same issue on all my servers running different versions of Virtualbox. homeassistant.components.hassio.handler.HassioAPIError: System is not ready with state: setup After going into the homeassistant gui i press restart and works again. |
I started getting this in release 2023.3.0b0 This is what is in the logs after system reboot:
Restarting home assistant resolves the issue |
Form e it still happens on all versions of home assistant and don't know whats causting this. 1 server running in VIRTUALBOX windows 11 All of hem i need to restart twice before it works again. |
I have the same issue. |
i even have now 2 instances running on proxmox, same issue. |
It's a reoccurring problem still. Reproducable 100pct of the time. Every reboot of the machine requires a separate 'restart home assistant' action to get it working right. All my raspberry pis have the issue |
Its an issue need to be solved, as how can this system be reliable then ? Indeed you can manual restart HASS and it works, but not if im not at home... And of course this only happens if u do an update or if you do a full system reboot, or you get for example a power issue and your main host goes down, and it restarts. Happening on:
All of them running last version and last HASSOS version besides the windows 11 one. If there is a way to create an automation that triggers on that HASSIO failed to load and will trigger an restart that would be good for the time being. The devs need to fix this asap as this is annoying ! |
Hi I'm having same issue, HA installed in a VM on Proxmox, both on latest version as today. It does not happen on every HA restart.
I'm not able to find any solution. Any suggestion? Thanks |
Error came back with the latest update as well. It's either an issue of updates not applying correctly or they made a change that reverts the fix. The last two weeks of March my boxes have been fine even after restarts (previously had issues all of January and February). After updating to this latest update, restarts bring back the error I'm about to stop updating once everything is stable. The updates, or maybe even how they apply the updates are not stable at all. What's funny is the supervised unsupported installs are actually more reliable than my hassOS boxes for friends. There are a lot of people on other communities having the same issue, they just don't report. |
Does your date time and hassio error go away after you manually restart home assistant once it's half up? |
I've never tried to manually restart home assistant once it's half up. After a normal restart it can happens that I don't get the error (and Settings->Add-ons shows up), I don't know if it's 50-50 of times |
Have the same issue @home-assistant/supervisor please reply |
I have this same issue |
Correction: For me: this only happens if u fully shutdown HASS and start it up again, but manual restart does work normal. |
Not for me, it happens to me when I do a restart (some times). |
True, i corrected my message above. I need to see what happens if tomorrow the new HASS version get released, see if it also happens if we update. |
I seemed to have solved my issue with a weird fix. Based on another suggestion I added a small delay to my docker.service, I used the 'ExecStartPre=' field to sleep for a few seconds. This seems to allow HASS to boot correctly on first startup. Without it I will need to reboot HASS after the VM comes up. |
Im actually having the same issue on hassOS, theregor i double its related
to VM or Docker usage
…On Tue, Apr 4, 2023, 19:00 Michael Weyand ***@***.***> wrote:
Hi
I'm having same issue, HA installed in a VM on Proxmox, both on latest
version as today.
It does not happen on every HA restart. When it happens, in Settings the
item "Add-ons" it's missing
[image: Screenshot 2023-04-01 171049]
<https://user-images.githubusercontent.com/6501444/229297485-242b8405-50ad-4532-b913-355a3fee2354.png>
Logger: homeassistant
Source: components/hassio/__init__.py:320
First occurred: 08:47:06 (1 occurrences)
Last logged: 08:47:06
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 560, in _async_setup_hardware_integration
if (os_info := get_os_info(hass)) is None:
File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 320, in get_os_info
return hass.data.get(DATA_OS_INFO)
AttributeError: 'datetime.datetime' object has no attribute 'data'
I'm not able to find any solution.
Any suggestion?
Thanks
I seemed to have solved my issue with a weird fix. Based on another
suggestion I added a small delay to my docker.service, I used the
'ExecStartPre=' field to sleep for a few seconds. This seems to allow HASS
to boot correctly on first startup. Without it I will need to reboot HASS
after the VM comes up.
—
Reply to this email directly, view it on GitHub
<#86622 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APPENFWVSNFYX7JLKOAHY6DW7RARRANCNFSM6AAAAAAUGMFN6E>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm usinng HA in Proxmox on a VM. |
I can't say for sure this will fix the issue but I am also running HA in a Proxmox VM |
I can verify during the upgrade to 2023.4 on proxmox-windowsVirtualbox i don't get this error anymore. |
Updated to latest version, still having the issue. I'm amazed something as critical of a component as hassio not being reliable hasn't been noticed by any of the repo admins for this long. I wonder which commit caused this. Might finally be time to install visual studio and get back into programming. I've never been that great with asynchronous or parallel algorithms though. |
I've been facing this error for 4 weeks. I continued restarting my home assistant to get things working again. I updated to the last version, but nothing was fixed. |
There will be new supervisor updates this month, they did announce it in the last release update stream. |
I will pray for that. It sucks to reset the home assistant many times a day. |
Same problem for me. This makes my current setup impossible to debug, since my instance crashes and I am unable to find the previous logs (since I don't have access to any add-on like file editor or samba share). I am looking forward a lot for a fix. |
Same here. |
Same here with a PI4 |
See #92569 |
Same issue here running in proxmox |
Definitely something wrong with home assistant. I've asked friends who have home assistant on different machines as well and they experience this issue but they just never report it because their box doesn't reboot as often. Personally experience the same thing on many different host types. HassOS is frequently the most troublesome, the only machine that hasn't given me issues is a random supervised setup. I'd estimate that a third of home assistant users would experience the same issue if they reboot their machine, a majority of them just either don't reboot or havent updated to the latest home assistants |
If the issue is still occuring after |
My logs |
I'm getting this error every time the Unraid VM restarts. A restart from Dev Tools temporarily fixes it. Do you need full logs @epenet? |
Same here with an UnRaid VM. Hopefully there will be a fix soon. Keep up the good work, dear devs! |
Guys, look up a couple of comments. It's being fixed in .3 |
Same issues here core-2023.6.3 see duplicate issue above. Also still exists in 2023.7.1. |
Please stop trying to revive an old issue. What you have now is no longer an unhandled exception and should be a new issue instead. |
The problem
I've recently started having an issue with my HA instillation not starting properly.
The bare basics of the dashboard work but I cant access any of the addon-related pages and the "Supervisor" integration shows there's a fault.
The error first started on 2023.1.1, which i managed to clear by a mix of cli telling the supervisor to repair, reload and restart and also giving the QEMU VM that HA is running in a restart.
I then upgraded to 2023.1.7 (i had missed the intermediate updates as I didn't realise the supervisor wasn't working fully) where it worked for a while, but after a restart last night to solve some unrelated host issues the error has returned.
Any help would be muchly appreciated
What version of Home Assistant Core has the issue?
2023.1.7
What was the last working version of Home Assistant Core?
latest 2022 release or initial 2023 release
What type of installation are you running?
Home Assistant OS
Integration causing the issue
hassio
Link to integration documentation on our website
https://www.home-assistant.io/integrations/hassio
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: