home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.73k stars 29.98k forks source link

Nest Failed to setup despite previous config working #105810

Closed evan1017 closed 5 months ago

evan1017 commented 9 months ago

The problem

I had a working Nest config but it broke somewhere along the way I got around to fixing it today and unauthenticated it properly (mobile wouldn't work and would throw me a blank HA screen in the app, but browser/PC authentication did) But now the setup fails and passes along this message:

Configuration error: Failed to create subscriber 'projects/annular-beacon-393006/subscriptions/home-assistant-MomYBxzLm8' id was not found

What version of Home Assistant Core has the issue?

2202-12-3

What was the last working version of Home Assistant Core?

No response

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

home-assistant_nest_2023-12-15T16-39-10.766Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Configuration error: Failed to create subscriber 'projects/annular-beacon-393006/subscriptions/home-assistant-MomYBxzLm8' id was not found 

1 min later

climate.upstairs: Received invalid HVAC mode: unavailable

Additional information

I glanced at some forums and noted the change in Oauth to 2.0 I'm not sure if this is what broke it in the first place but if so I can re-setup the integration if needed!

home-assistant[bot] commented 9 months ago

Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration (nest) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `nest` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign nest` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


nest documentation nest source (message by IssueLinks)

allenporter commented 9 months ago

I'm not sure i follow what the problem was and what you did to fix it and what unauthenticating it means? But this definitely looks like things are in an inconsistent state. Home assistant creates a pub/sub subscription in the google cloud API which i t needs to receive updates from the nest API and its saying it can't find it. You can definitely remove the integration and re-add it to get things working again, but i'm also trying to understand if there is a bug in home assistant that it needs to handle this case better or if something you did to fix made it inconsistent.

evan1017 commented 9 months ago

Basically it needed reconfiguring and wanted to reconnect to my google account where it asked for access. The first time i tried this i. my phone and the google portion went fine but then it sent me back to the HA app and gave me a blank screen. The second time i did it from my browser HA the reauthentication worked flawlessly, but then the setup of the device failed. and i couldn’t get anything to fix it

pjatx commented 9 months ago

I actually experienced this as well and saw this so wanted to comment in case helpful.

Noticed my integration was down today. Tried disabling / enabling. Didn't work. Checked logs and saw a bunch of failed requests.

Logged into Google Device console and noticed that the pub/sub topic got disabled in the Google Device cloud dash and potentially changed.

Deleted and reinstalled the integration and now working again.

evan1017 commented 8 months ago

Update Took the time to remove and re-add the integration and It fails upon attempting to add the integration after inputting project IDs its supposed to redirect This redirect worked on mobile but the google side redirect back to HA app results in a blank screen. If you do this on laptop the HA to google redirect fails and nothing happens. I tried setting up a new google device access console and the redirect from HA to google worked but it said that the new Device access console project cant be linked. I cannot proceed and no longer have access to my Thermostat through HA please advise!

allenporter commented 8 months ago

Hi, check the integration docs under troubleshooting instructions for that error and remove existing application credentials.

evan1017 commented 8 months ago

Removed application credentials and re-ran setup, the redirect failed to process on the HA side. So all I saw was a pop-up saying Google Nest with only one button to close; it did not open an additional tab or cause the browser to redirect. I tried with both a new and an old setup of DAC and Google Cloud API both had the same issue both on the browser and on smartphone. EDIT: I tried the new set of DAC and google cloud API and I got through but now my HA side says it has a subscriber error and is asking for the Cloud Project ID again and won't accept it. I'm dumb I missed a step in the setup where I enable the two extra API's my bad! still unsure as to why the old set of DAC and Google Cloud Projects won't accept the HA redirect tho ?

issue-triage-workflows[bot] commented 5 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.