Nest API revokes permissions causing Google Nest entities to be unavailable

[ljhardy]

The problem

All google nest entities have gone unavailable including doorbell, thermostats, and cameras. All still appear in the Google Nest Application.

What version of Home Assistant Core has the issue?

core-2025.4.1

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

Google Nest

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nest/

Diagnostics information

One example:

Logger: homeassistant.helpers.service
Source: helpers/service.py:304
First occurred: 10:24:52 AM (3 occurrences)
Last logged: 10:24:55 AM

Referenced entities climate.master_bedroom are missing or not currently available
Referenced entities climate.downstairs are missing or not currently available

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.helpers.service
Source: helpers/service.py:304
First occurred: 10:24:52 AM (3 occurrences)
Last logged: 10:24:55 AM

Referenced entities climate.master_bedroom are missing or not currently available
Referenced entities climate.downstairs are missing or not currently available

Additional information

No response

[home-assistant]

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)}}

[ljhardy]

I should have noted that I restarted HA and also rebooted the HA machine. Added Debug log:

"integration_manifest": {
"domain": "nest",
"name": "Google Nest",
"after_dependencies": [
"media_source"
],
"codeowners": [
"allenporter"
],
"config_flow": true,
"dependencies": [
"ffmpeg",
"http",
"application_credentials"
],
"dhcp": [
{
"macaddress": "18B430*"
},
{
"macaddress": "641666*"
},
{
"macaddress": "D8EB46*"
}
],
"documentation": "https://www.home-assistant.io/integrations/nest",
"iot_class": "cloud_push",
"loggers": [
"google_nest_sdm"
],
"requirements": [
"google-nest-sdm==7.1.4"
],
"is_built_in": true,
"overwrites_built_in": false
},
"setup_times": {
"null": {
"setup": 0.0007009699999969143
},
"01JJ7NNQ5ENMD19H2SBVXC7NZM": {
"wait_import_platforms": -0.014440387000007604,
"wait_base_component": -0.0004469760000063161,
"config_entry_setup": 3.6573407389999915
}
},
"data": {}
}

[leonverhoeven]

I have the same setup and versioning, also the same errors. My Google Doorbell and Thermostat arent available, with the same errors.
@allenporter are you looking into this?

[JpsCrazy]

Additionally I tried to remove and reconnect the Nest integration. After being asked to sign in with my Google account I get an error:

Something went wrong

Please contact the developer of this app if the issue persists.

[champagj]

I have two Nest Thermostat Gen3 connected to HA using this integration for at least 6 months without issue.
Yesterday automation and controls failed. I did a full restart of HA and now devices show unavailable

"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2025.4.1",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.13.2",
"docker": true,
"arch": "aarch64",
"timezone": "America/Toronto",
"os_name": "Linux",
"os_version": "6.6.74-haos-raspi",
"supervisor": "2025.04.0",
"host_os": "Home Assistant OS 15.0",
"docker_version": "28.0.1",
"chassis": "embedded",
"run_as_root": true

Google Nest API status shows as up and running.

From the log in debug mode. My uneducated guess is a change in the API?

2025-04-10 21:42:44.316 DEBUG (MainThread) [google_nest_sdm.subscriber_client] API error in streaming pull: 503 The service was unable to fulfill your request. Please try again. [code=8a75]
2025-04-10 21:42:44.317 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Disconnected from event stream: API error when streaming iterator: 503 The service was unable to fulfill your request. Please try again. [code=8a75]
2025-04-10 21:42:44.318 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Reconnecting stream in 10.0 seconds
2025-04-10 21:42:54.319 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Connecting with streaming pull
2025-04-10 21:42:54.319 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Credentials refreshed, new expiry 2025-04-10 22:21:59.710561
2025-04-10 21:42:54.322 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Sending streaming pull request for projects/hass-nest-XXXXX/subscriptions/home-assistant-4Y9v9wrzuQ
2025-04-10 21:42:54.517 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Event stream connection established
2025-04-10 21:42:54.517 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Starting streaming iterator
2025-04-10 21:42:54.518 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Sending streaming pull request (acking 0 messages)
2025-04-10 21:43:05.966 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Sending streaming pull request (acking 0 messages)
2025-04-10 21:44:12.350 DEBUG (MainThread) [google_nest_sdm.subscriber_client] API error in streaming pull: 503 The service was unable to fulfill your request. Please try again. [code=8a75]
2025-04-10 21:44:12.350 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Disconnected from event stream: API error when streaming iterator: 503 The service was unable to fulfill your request. Please try again. [code=8a75]

---

Investigating the Cloud Pub/Sub API, showing 100% error in the cloud dashboard..
The Smart Device Management API onl;y started showing error recently

[allenporter]

Additionally I tried to remove and reconnect the Nest integration. After being asked to sign in with my Google account I get an error:

Something went wrong
Please contact the developer of this app if the issue persists.

Please check out the troubleshooting or file a separate issue, this is not related to the discussion here.

[allenporter]

The diagnostics report above is completely empty, which implies the Nest API is returning nothing. This appears to be a nest outage and not a home assistant bug?

[allenporter]

Check out https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging for enabling debug logging. This may help us see some of the requests/replies we're getting from the server.

The 503 subscriber errors are totally normally and not part of the problem. (Those are a detail of how pubsub streaming works, and cannot cause devices to go unavailable. Ignore errors in the pubsub console)

The Smart Device Management API showing errors sounds like a problem.

[champagj]

I have updated the Pub/Sub topic using the integration instructions. The Pub/Sub topic I had was enabled but I guess created a while back. Now updated to the correct format : projects/MYPROJECT/topics/hass-nest.

2025-04-10 22:29:24.525 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Connecting with streaming pull
2025-04-10 22:29:24.526 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Credentials refreshed, new expiry 2025-04-10 23:22:29.372499
2025-04-10 22:29:24.527 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Sending streaming pull request for projects/hass-nest-XXXXXX/subscriptions/home-assistant-4Y9v9wrzuQ
2025-04-10 22:29:24.702 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Event stream connection established
2025-04-10 22:29:24.702 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Starting streaming iterator
2025-04-10 22:29:24.703 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Sending streaming pull request (acking 0 messages)
2025-04-10 22:29:41.883 DEBUG (MainThread) [google_nest_sdm.subscriber_client] Sending streaming pull request (acking 0 messages)
2025-04-10 22:30:41.513 DEBUG (MainThread) [google_nest_sdm.subscriber_client] API error in streaming pull: 503 The service was unable to fulfill your request. Please try again. [code=8a75]
2025-04-10 22:30:41.514 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Disconnected from event stream: API error when streaming iterator: 503 The service was unable to fulfill your request. Please try again. [code=8a75]
2025-04-10 22:30:41.514 DEBUG (MainThread) [google_nest_sdm.streaming_manager] Reconnecting stream in 10.0 seconds

Now looking into the Smart Device Management API.

[allenporter]

The old project format was fine and is not the problem, but it doesn't hurt. Just don't want others to think they need to explore anything related to that since as I said it's not related to what we're discussing here. Pub Sub messages cannot interact with devices being available or not.

[champagj]

All the parameters on Smart Device Management API appeared okay, status was all green checkmarks, Oauth clients etc.

I ended up deleting the integration entry, kept the credentials when asked, re-add my project, device access Project_ID and Pub/sub, went through the app authorization and it all worked.

The detail log shows all proper transactions, no errors.

Google, HA or the integration got confused yesterday I suppose.
I was doing a lot of unrelated work in HA, deploying some custom Esphome devices.

No more issue on my side.

I have been using the Google Nest integration in HA for few years and it is one that we use a lot, is valuable part of HA and has been very stable.

Thank you. ( I did software testing in the past, if you need tester in the future, happy to help if I can)

[ProfsRetroFix]

Just to jump in and confirm I am also experiencing the same issue as original poster. The integration is presenting no errors, but the thermostat is unavailable.

I will add a debug log as soon as I finish work if it helps.

[allenporter]

OK sounds like two other folks may have seen unrelated errors. Thermostats have a special thing when it comes to availability where it will be unavailable if the nest api says it is unavailable.

I've seen this before where the thermostat needs a reset. See https://www.home-assistant.io/integrations/nest/#troubleshooting under the section "Thermostat does not appear or is unavailable" and "How to restart thermostat" and report back anything you find.