-
-
Notifications
You must be signed in to change notification settings - Fork 32.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
Nest Integration Not Working/Crashing Home Asisstant #117827
Comments
Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) nest documentation |
One of the interesting exceptions is here:
|
Would you be up for enabling debug home in
|
Also, can you try this with custom components disabled in safe mode? https://www.home-assistant.io/docs/troubleshooting_general/#restarting-home-assistant-in-safe-mode |
Here are logs with
home-assistant_2024-05-21T02-49-06.245Z.log I'll try safe mode next |
Still failed in safe mode |
I see a couple merges referencing these issues, but I can't tell if they made it into 2024.5.5 or not. If they have, I'm still having the same issues. If the have not, is there any way to test the changes to see if they help resolve the issue? |
They are in 2025.6 .. beta cut today, releasing next week |
Unfortunately the nest integration still won't start up after upgrading to 2024.6
|
It's no longer causing HA to go temporarily non-responsive at least. But still not working. |
Still can't delete the integration either to try & start over. I got these debug messages, and the subscription in GCP PubSub was deleted, but the integration is still present in HA 30 minutes later
|
Ok progress. That exception trace is the exact code I changed trying to find the issue. This is a much more informative error message about the problem. I'll have a look and suggest further action or add more instrumentation. Thank you for your patience! 🙏 |
I've been following this issue since a while now and hoped that my google integrations (nest and calendar) would work after this update (to core 2024.6.2), but alas. At the integration page I get this error message now (didn't get that one before the update): And in the logs I see this error:
If this aint the same issue as the one above I can remove this comment. |
@TMulderNL does not look like the same issue. That appears to look like an issue i see when folks have ad blockers on that block google from the network, or another kind of ipv6 issue. |
Unfortunately, with it starting to really heat up in these parts, the W.A.F. (wife acceptance factor) has gotten critically low in recent days and I'm spending my afternoon replacing the Nest with an Ecobee now. |
OK i would suggest double checking you don't have an ad blocker or ipv6 misconfiguration that is blocking google. Essentially its timing out opening a connection. I was confused because of how its failing looks like a deadlock or broken subscriber thread but i also realize that an unexpected network issue could be breaking an assumption in the client library. |
I do have AdGuard on the network, and that was the first thing I checked when issues popped up. There were no reported blocks for the IP addresses associated with my HAAS installation. I also use GCP daily for work, so if AdGuard was interfering there, I'd definitely know! |
The logs above look truncated or missing 'info' so its hard to tell exactly what is happening so if you are in fact interested in continuing to diagnose this i might suggest this log setup
|
fwiw I'm also having this issue, with the same error message in the logs. I'm also unable to remove the integration - no error, it just refuses to delete. I have triple checked the setup in both Google Cloud and the Nest/Google Device Console too. Nothing has changed in my setup and this has been happily working for months now. |
Can you please file your own issue report and fill out the bug template? I can dedup if the root cause seems similar. |
My Google Nest Thermostat has stopped working for a number of months now. I have upgrade to the latest HA and still no luck. Error message: Logger: homeassistant.components.nest Configuration error: Failed to create subscriber 'projects/central-embassy-393721/subscriptions/home-assistant-PjK2swRbH0' id was not found |
@mlamport please report a separate issue? it looks like for some reason your subscriber, which is created as part of setup, does not exist. I have heard that there may be an issue where the subscribers will be automatically deleted, so maybe we need to detect this and re-create it. As a workaround in the mean time, deleting the integration and re-adding it should re-create the subscriber. |
Closing since information needed was not provided. Please reopen a new issue when ready to diagnose. |
The problem
I noticed my Nest panels were no longer populated in my dashboard. I started investigation and noticed that the Nest integration completely stopped working recently running on my ODroid M1. Trying to reload the integration causes Home Assistant to completely freeze up & restart. Trying to even delete the integration causes the same to happen. Enabling debug logging doesn't seem to provide any insight into the issue that I can discern.
What version of Home Assistant Core has the issue?
core-2024.5.4
What was the last working version of Home Assistant Core?
core-2024.4.?
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Nest
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nest/
Diagnostics information
This log is starting up with the integration enabled:
home-assistant_2024-05-21T01-16-46.017Z.log
Upon trying to delete the integration, the following line is printed to the log:
HA goes non responsive for several minutes, then we get:
HA then comes back, starts re-initializing everything, including Nest, and fails all over again. Can't get out of this loop
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
This started happening somewhere in the core-2024.05 series, but I'm not sure exactly where.
The text was updated successfully, but these errors were encountered: