-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Cloud / Nabu Casa Remote not working: "Home Assistant is starting, not everything will be available until it is finished." #41625
Comments
Same issue - needed to revert to 0.115.6 |
cloud documentation |
Hey there @home-assistant/cloud, mind taking a look at this issue as its been labeled with an integration ( |
Just tried to downgrade HA Core to 0.114.4, which seems to have brought back the "Home Assistant Cloud" option in the Configuration menu again. But when I try to log in to Home Assistant Cloud, I now get:
|
@acsands13 is this a vm? Can you share the output of |
I too have this issue, I suspect the Home Assistant cloud starts sooner than My AdGuard addon. Are you guys using AdGuard or Pi-Hole add ons on the same computer ? |
@cogneato Yes, this is running in VirtualBox on a Mac Mini. Pasted the "System Health" info at the bottom of this comment for reference. Here's the output of
And here are my DNS logs under Supervisor → System:
"System Health" info under Configuration → Info:
|
Hm, can you see if in |
@balloob I do not have a file called
I am not logged into Home Assistant Cloud at the moment. Trying to do so fails with the error message "Unable to reach the Home Assistant cloud." |
Right, that's only if you're logged in. Are you on Discord? Could you ping me. I'm balloob#6041 or join us in #cloud channel @ https://www.home-assistant.io/join-chat/ |
Massive thanks to @balloob and @cogneato for the help debugging this. @balloob put in #197 to fix the stack trace for the For others who have this issue, the fix for me was... It turned out to be an ipv6 DNS server that was present, which should not have been. You can remove it by disabling ipv6 on the VM:
|
The problem
After restarting Home Assistant, it hangs on "Home Assistant is starting, not everything will be available until it is finished." permanently. The Nabu Casa Remote UI is unavailable, and the "Cloud" menu option in the Configuration menu is not visible (i.e. http://homeassistant.local:8123/config/cloud/ does not load).
With some debugging, I found that I can bypass the issue by removing
cloud:
from myconfiguration.yaml
. Home Assistant then starts normally and everything works (without remote UI access, obviously), but addingcloud:
back causes this issue once again.This issue started happening suddenly on Oct. 10th, with no known changes between when it was working and when it started failing.
There are others having this same problem on the community forum. Link to that commentary here.
Environment
hass_nabucasa
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: