Core: HA 0.118.0b0 Nest Integration: no updates via the subscriber?

Created on 12 Nov 2020  路  29Comments  路  Source: home-assistant/core

The problem

The thermostat attributes are not updating unless HA is restarted or Nest Integration is reloaded and then only one change is applied.

Environment

  • Home Assistant Core release with the issue: 0.118.0b0
  • Last working Home Assistant Core release (if known): None
  • Operating environment (OS/Container/Supervised/Core):
    ;arch | x86_64
    chassis | desktop
    dev | false
    docker | true
    docker_version | 19.03.13
    hassio | true
    host_os | Debian GNU/Linux 10 (buster)
    installation_type | Home Assistant Supervised
    os_name | Linux
    os_version | 4.19.0-12-amd64
    python_version | 3.8.6
    supervisor | 2020.11.0
    timezone | America/Vancouver
    virtualenv | false

  • Integration causing this issue:
    Nest

  • Link to integration documentation on our website:
    https://www.home-assistant.io/integrations/nest/

Problem-relevant configuration.yaml

N/A

Traceback/Error logs

N/A

Additional information

N/A

nest

Most helpful comment

@danielbrunt57 When you click on the 'Select a Cloud Pub/Sub topic' drop down, the right hand button allows you to manually add your values. Full step by step instructions found here (probably more relevant is A to N for you):
https://community.home-assistant.io/t/google-nest-offical-device-access-console-finally-released/229146/263?u=townsmcp

All 29 comments

Having the same issue. Happy to help by providing some debug logs - How would I go about doing that?

Edit: Should add that it never worked correctly before 118 with just sensor data. Only updated once on restart of HA and never thereafter.

I have made a service account BTW in anticipation of the PR using the subscriber_service_account: config variable - though it looks like this PR hasn't been merged into 118b0 yet.

One approach we have used before is to add extra debug logging to theconfiguration.yaml such as:

logger:
  default: info
  logs:
    homeassistant.components.nest: debug
    homeassistant.components.nest.climate_sdm: debug
    homeassistant.components.nest.camera_sdm: debug
    homeassistant.components.nest.sensor_sdm: debug
    google_nest_sdm: debug
    google_nest_sdm.device: debug
    google_nest_sdm.device_manager: debug
    google_nest_sdm.google_nest_subscriber: debug
    google_nest_sdm.event: debug
    google.cloud.pubsub_v1: debug
    google.cloud.pubsub_v1.subscriber._protocol.leaser: debug
    google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager: debug

Not sure if you can get away with just the top level packages, but that is what I use when I want to debug.

Annecdotally, i just updated my dev instance with the beta and it seems to be receiving updates. The way I test is by changing around the target heater temp and the lovelave climate entity refreshes in near realtime.

nest documentation
nest source
(message by IssueLinks)

Hey there @awarecan, mind taking a look at this issue as its been labeled with an integration (nest) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

2020-11-12 11:16:09 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Creating a stream, default ACK deadline set to 10 seconds.
2020-11-12 11:16:09 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.dispatcher] Started helper thread Thread-CallbackRequestDispatcher
2020-11-12 11:16:09 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 11:16:09 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 2.052494 seconds.
2020-11-12 11:16:09 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Started helper thread Thread-LeaseMaintainer
2020-11-12 11:16:09 DEBUG (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Sent heartbeat.
2020-11-12 11:16:09 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Started helper thread Thread-Heartbeater
2020-11-12 11:16:09 INFO (Thread-35) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-terminating stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 11:16:09 INFO (Thread-35) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-recoverable stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 11:16:09 INFO (Thread-35) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] RPC termination has signaled streaming pull manager shutdown.
2020-11-12 11:16:09 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping consumer.
2020-11-12 11:16:09 INFO (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-terminating stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 11:16:09 INFO (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-recoverable stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 11:16:09 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping scheduler.
2020-11-12 11:16:09 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping leaser.
2020-11-12 11:16:09 INFO (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Thread-LeaseMaintainer exiting.
2020-11-12 11:16:09 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping dispatcher.
2020-11-12 11:16:09 DEBUG (Thread-CallbackRequestDispatcher) [google.cloud.pubsub_v1.subscriber._protocol.helper_threads] Exiting the QueueCallbackWorker.
2020-11-12 11:16:09 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping heartbeater.
2020-11-12 11:16:09 INFO (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Thread-Heartbeater exiting.
2020-11-12 11:16:09 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Finished stopping manager.
2020-11-12 11:16:19 DEBUG (MainThread) [google_nest_sdm.google_nest_subscriber] Subscriber shut down; restarting

Sorry, everything works. The instruction here is not entirely correct.
https://community.home-assistant.io/t/google-nest-offical-device-access-console-finally-released/229146/263

@stast1 what is missing/incorrect? I can get the instructions updated

Not specified to create a subscription in https://console.cloud.google.com/cloudpubsub/subscription
image

@stast1 thanks. I will take a look and update the instructions.
Out of curiosity, what iD did you use when creating this? As I recall, it is the project ID?

Subscription ID can be anything. Subscription name must be registered in configuration.yaml as subscriber_id:

As I recall, it is the project ID?
Yes

Ok, thanks. I will retry this again after my ZHA issue in 118.0b0 is fixed.

My ZHA issue is resolved and am back on 118.0b0.
I'm confused by the above comments. There are two places to create projects. One is in the Nest console and the other is in Google console. The purpose of the project in Google console is to be able to create OAuth 2.0 credentials. But as I see it, any subscription created there are unrelated to the Nest project and subscription (aka pub/sub) topic for the nest devices. I tried it your way above using the subscriber ID from Google and it did not work for me. I had to use the pub/sub ID from Nest, but updates are not occurring. I will enable logging and report further...

No errors...

2020-11-12 10:25:51 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Creating a stream, default ACK deadline set to 10 seconds.
2020-11-12 10:25:51 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.dispatcher] Started helper thread Thread-CallbackRequestDispatcher
2020-11-12 10:25:51 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:25:51 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 4.042039 seconds.
2020-11-12 10:25:51 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Started helper thread Thread-LeaseMaintainer
2020-11-12 10:25:51 DEBUG (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Sent heartbeat.
2020-11-12 10:25:51 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Started helper thread Thread-Heartbeater
2020-11-12 10:25:51 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.nest
2020-11-12 10:25:51 INFO (MainThread) [homeassistant.components.camera] Setting up camera.nest
2020-11-12 10:25:51 INFO (MainThread) [homeassistant.components.climate] Setting up climate.nest
2020-11-12 10:25:51 INFO (MainThread) [homeassistant.setup] Setup of domain bhyve took 3.7 seconds

2020-11-12 10:25:55 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:25:55 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 4.076920 seconds.

2020-11-12 10:25:59 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 15.34s
2020-11-12 10:25:59 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2020-11-12 10:25:59 INFO (MainThread) [homeassistant.core] Timer:starting

2020-11-12 10:25:59 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:25:59 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 3.480996 seconds.

2020-11-12 10:26:03 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:26:03 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 4.339464 seconds.

2020-11-12 10:26:07 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:26:07 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 1.295453 seconds.
2020-11-12 10:26:09 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:26:09 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 4.208219 seconds.
2020-11-12 10:26:13 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:26:13 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 0.160343 seconds.
2020-11-12 10:26:13 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:26:13 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 3.494934 seconds.
2020-11-12 10:26:16 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:26:16 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 5.366150 seconds.
.
.
.
2020-11-12 10:39:00 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:39:00 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 5.416167 seconds.
2020-11-12 10:39:05 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:39:05 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 8.614233 seconds.
2020-11-12 10:39:14 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 10:39:14 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 4.118397 seconds.

The nest console enables a pubsub topic. Then you also need to create a pub sub subscriber id in the cloud console, and it is associated with the topic.

(Another approach I may explore is to auto create the subscriber id in code to remove it as an option but I think that may require additional permissions or work better with a service account. Not sure.)

I've never seen the nest console project or pubsub topic in the cloud console.
It says 'sandbox' with an option to apply for commercial development. Is that the missing piece?

Ok, for the 23rd time...
Deleted everything and started over. Now I see these in logs using the pub/sub topic (subscriber ID) from Nest:

2020-11-12 18:02:19 DEBUG (MainThread) [google_nest_sdm.google_nest_subscriber] Starting background watchdog thread
2020-11-12 18:02:19 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Creating a stream, default ACK deadline set to 10 seconds.
2020-11-12 18:02:19 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.dispatcher] Started helper thread Thread-CallbackRequestDispatcher
2020-11-12 18:02:19 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-11-12 18:02:19 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 2.127226 seconds.
2020-11-12 18:02:19 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Started helper thread Thread-LeaseMaintainer
2020-11-12 18:02:19 DEBUG (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Sent heartbeat.
2020-11-12 18:02:19 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Started helper thread Thread-Heartbeater
2020-11-12 18:02:19 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.nest
2020-11-12 18:02:19 INFO (MainThread) [homeassistant.components.camera] Setting up camera.nest
2020-11-12 18:02:19 INFO (MainThread) [homeassistant.components.climate] Setting up climate.nest
2020-11-12 18:02:19 INFO (Thread-107) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-terminating stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 18:02:19 INFO (Thread-107) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-recoverable stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 18:02:19 INFO (Thread-107) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] RPC termination has signaled streaming pull manager shutdown.
2020-11-12 18:02:19 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping consumer.
2020-11-12 18:02:19 INFO (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-terminating stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 18:02:19 INFO (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-recoverable stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-11-12 18:02:19 INFO (Thread-ConsumeBidirectionalStream) [google.api_core.bidi] Thread-ConsumeBidirectionalStream exiting
2020-11-12 18:02:19 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping scheduler.
2020-11-12 18:02:19 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping leaser.
2020-11-12 18:02:19 INFO (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Thread-LeaseMaintainer exiting.
2020-11-12 18:02:19 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping dispatcher.
2020-11-12 18:02:19 DEBUG (Thread-CallbackRequestDispatcher) [google.cloud.pubsub_v1.subscriber._protocol.helper_threads] Exiting the QueueCallbackWorker.
2020-11-12 18:02:19 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping heartbeater.
2020-11-12 18:02:19 INFO (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Thread-Heartbeater exiting.
2020-11-12 18:02:19 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Finished stopping manager.
2020-11-12 18:02:22 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.nest entity: sensor.living_room_temperature
2020-11-12 18:02:22 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.nest entity: sensor.living_room_humidity
2020-11-12 18:02:22 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new climate.nest entity: climate.living_room
2020-11-12 18:02:29 DEBUG (MainThread) [google_nest_sdm.google_nest_subscriber] Subscriber shut down; restarting

I changed to the subscriber ID from my console project:
nest_subscriber_id: projects/home-assistant-1605216166261/subscriptions/nest
and no errors but no updates now again.

The nest console enables a pubsub topic. Then you also need to create a pub sub subscriber id in the cloud console, and it is associated with the topic.

(Another approach I may explore is to auto create the subscriber id in code to remove it as an option but I think that may require additional permissions or work better with a service account. Not sure.)

Agreed, the nest console creates a pubsub topic but I do not ever see that in GCM. I have two projects in GCM. How would it know where to create it? Nor does the Nest console create its project in my GCM. I can create a topic in GCM but I can't link it to the nest topic. I believe they are unrelated and the only purpose for a project in GCM is to establish OAuth credentials that the nest project can utilize. If you feel I'm incorrect, please enlighten me!

My Nest Integration still is not updating. 25 tries at it! Well, maybe not that many but sure feels like it! What's that definition of insanity??? Oh, right....doing the same thing over and over and expecting a different result!

nest_client_id: xxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com
nest_client_secret: xxxxxxxxx-xxxxxxxxxxxxxx
nest_project_id: xxxxdxxxxxxxx-xxxx-xxxx-ea64e1a5a6ef
nest_subscriber_id: projects/sdm-prod/topics/enterprise-3e29d5f2-xxxx-xxxx-xxxx-ea64e1a5a6ef

Nest Project ID: xxxxdxxxxxxxx-xxxx-xxxx-ea64e1a5a6ef
Nest Pub/Sub topic: projects/sdm-prod/topics/enterprise-3e29d5f2-xxxx-xxxx-xxxx-ea64e1a5a6ef

GCM Project ID: home-assistant-295423

As per https://developers.google.com/nest/device-access/get-started...

Upon completion, your (nest) project is assigned a Project ID, in the form of a UUID, such as 32c4c2bc-fe0d-461b-b51c-f3885afff2f0. Make note of this ID, you need it for all SDM API calls.
This Project ID is used in OAuth and API calls. It is specific to your Device Access project, and is not related to a GCP Project ID.

IMO...
If I use the Nest pub/sub subscriber_id I get the '[google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Observed non-terminating stream error 400 Invalid resource name given (name=projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995).' error.
If I use a manually created topic/subscription ID from GCM, there's no error and '[google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager]' happily pulls no info from that subscriber_id since it's not the subscriber_id for Nest events.

HA is able to add the thermostat, set the temperature and turn the thermostat off, etc. because the project_id is the one gleaned from Nest Device Console. But the pub/sub is not working to retrieve temperature setting, current temp & humidity and operating mode....

Also see the simplified instructions in https://github.com/home-assistant/home-assistant.io/pull/15512

I've followed the guide at https://developers.google.com/nest/device-access/get-started and followed it through to a successful completion with the final curl displaying my device. That's not the issue as Nest Initegration is also able to add my device..
I created my first projects as soon as I got the email from Google so I've been at it a while. I also had nest.py successfully working. Today I created this topic in cloud console:
projects/home-assistant-295423/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
and this subscription:
projects/home-assistant-295423/subscriptions/nest
This is the one that generates no errors but also no updating.
As for the instruction:

It may be easiest to create a Pub/Sub subscription from the Google Cloud console. Make sure to use the topic name from the device access console and a unique subscription ID.

The cloud console does not let me change the beginning portion of the topic name to match the device console pub/sub name there I cannot create a subscription ID that works with the integration.
I.e.
projects/home-assistant-295423/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
Am I missing something???

I have the same issue temperature & humidity are not updated in 0.118.0b1 also binary_sensors are not available, probably same cause.

The cloud console does not let me change the beginning portion of the topic name to match the device console pub/sub name there I cannot create a subscription ID that works with the integration.
I.e.
projects/home-assistant-295423/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
Am I missing something???

I think you have to manually enter the topic name using the sdm-prod topic when creating the subscriber. You should not have to create an additional topic in the cloud console, just the subscriber.

The cloud console does not let me change the beginning portion of the topic name to match the device console pub/sub name there I cannot create a subscription ID that works with the integration.
I.e.
projects/home-assistant-295423/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
Am I missing something???

I think you have to manually enter the topic name using the sdm-prod topic when creating the subscriber. You should not have to create an additional topic in the cloud console, just the subscriber.

Not possible...

select cloud pub-sub topic

Got it working!!! I have updated my instructions on HA Community:
https://community.home-assistant.io/t/google-nest-offical-device-access-console-finally-released/229146/263?u=townsmcp

The new additional points are working 100% of the time for me. My message count on Google Cloud Patform is now 0 all the time. I can update the devices in HA and Nest app reflects the changes immediately. VIce versa, if I update form Nest app, HA updates straight away.

Also, as a side note, my Hello and Home Hub Max cameras are also now working perfectly on 0.118.0b0 :)

@danielbrunt57 When you click on the 'Select a Cloud Pub/Sub topic' drop down, the right hand button allows you to manually add your values. Full step by step instructions found here (probably more relevant is A to N for you):
https://community.home-assistant.io/t/google-nest-offical-device-access-console-finally-released/229146/263?u=townsmcp

Man, I don't know how I missed that, or page 4 of the step-by-step at https://developers.google.com/nest/device-access/subscribe-to-events. I just finished those steps utilizing cloud terminal and got the subscription created.
Updated nest secrets, restarted HA and thermostat is working!
Thank you for updating the instructions!

Was this page helpful?
0 / 5 - 0 ratings