Google-Nest Offical Device Access Console Finally Released!

I’ve checked everything several times and it seems to be set correctly.

The “client_id” and “URL” data in configuration.yaml are the same as in the URL

I’m out of my depth sorry, don’t know what the error means.

I enabled debugging but still not sure what to look into. It’s complaining about a resource name somewhere

2020-12-01 14:24:21 DEBUG (MainThread) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Started helper thread Thread-Heartbeater
2020-12-01 14:24:22 INFO (Thread-422) [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-3e16bea5-ba50-4680-b1e8-0959d6b8a092). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-12-01 14:24:22 INFO (Thread-422) [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-3e16bea5-ba50-4680-b1e8-0959d6b8a092). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-12-01 14:24:22 INFO (Thread-422) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] RPC termination has signaled streaming pull manager shutdown.
2020-12-01 14:24:22 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping consumer.
2020-12-01 14:24:22 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-3e16bea5-ba50-4680-b1e8-0959d6b8a092). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-12-01 14:24:22 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-3e16bea5-ba50-4680-b1e8-0959d6b8a092). Refer to https://cloud.google.com/pubsub/docs/admin#resource_names for more information.
2020-12-01 14:24:22 INFO (Thread-ConsumeBidirectionalStream) [google.api_core.bidi] Thread-ConsumeBidirectionalStream exiting
2020-12-01 14:24:22 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping scheduler.
2020-12-01 14:24:22 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping leaser.
2020-12-01 14:24:22 INFO (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Thread-LeaseMaintainer exiting.
2020-12-01 14:24:22 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping dispatcher.
2020-12-01 14:24:22 DEBUG (Thread-CallbackRequestDispatcher) [google.cloud.pubsub_v1.subscriber._protocol.helper_threads] Exiting the QueueCallbackWorker.
2020-12-01 14:24:22 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Stopping heartbeater.
2020-12-01 14:24:22 INFO (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Thread-Heartbeater exiting.
2020-12-01 14:24:22 DEBUG (Thread-OnRpcTerminated) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Finished stopping manager.

The way I’d read that is that the topic behind your subscription is incorrect. Are you sure it is correct? I think the id at the end should be the same as your project id. Worth checking anyway.

You’ve used the topic name for the subscription pull:
[google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager]
projects/sdm-prod/topics/enterprise-3e16bea5-ba50-4680-b1e8-0959d6b8a092


You need to use your subscription name like this:
nest_subscriber_id: projects/home-assistant-295423/subscriptions/nest

Ok I fixed that portion in my configuration.yaml and now have a repeating error

Update: I purged my test messages and now i’m no longer seeing errors. Going to reboot and see if I update

Update 2: I dont think I have anything bad in my logs, but still not getting updates after the initial load.

2020-12-01 16:57:16 DEBUG (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Sent heartbeat.
2020-12-01 16:57:16 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:16 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 6.813943 seconds.
2020-12-01 16:57:23 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:23 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 5.325814 seconds.
2020-12-01 16:57:28 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:28 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 4.017520 seconds.
2020-12-01 16:57:32 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:32 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 1.063543 seconds.
2020-12-01 16:57:33 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:33 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 0.752220 seconds.
2020-12-01 16:57:34 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:34 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 7.811393 seconds.
2020-12-01 16:57:42 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:42 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 3.578538 seconds.
2020-12-01 16:57:45 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:45 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 1.226919 seconds.
2020-12-01 16:57:46 DEBUG (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Sent heartbeat.
2020-12-01 16:57:47 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:47 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 0.470750 seconds.
2020-12-01 16:57:47 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:47 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 6.891481 seconds.
2020-12-01 16:57:54 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:54 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 0.053665 seconds.
2020-12-01 16:57:54 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:54 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 2.644572 seconds.
2020-12-01 16:57:57 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:57:57 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 8.242985 seconds.
2020-12-01 16:58:05 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 16:58:05 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 6.867172 seconds.

Here is what I see in my log when I change the thermostat setpoint:

2020-12-01 14:10:39 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 14:10:39 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 4.210557 seconds.
2020-12-01 14:10:43 DEBUG (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Processing 1 received message(s), currently on hold 0 (bytes 0).
2020-12-01 14:10:43 DEBUG (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Sent request(s) over unary RPC.
2020-12-01 14:10:43 DEBUG (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Released held message, scheduling callback for it, still on hold 0 (bytes 0).
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [google_nest_sdm.event] EventMessage raw_data={'eventId': '4ce26566-33fb-4627-8854-808c35ba5ab0', 'timestamp': '2020-12-01T22:10:41.326Z', 'resourceUpdate': {'name': 'enterprises/ebff85b2-5277-45ea-b794-6e6e76109995/devices/AVPHwEvdLVPCSLrFhZg5VGAbpHlnuFhtOGhZKtjxjTFsCTqRLfTBj49npAdEkfZAik7BkzesHiZ695sDha-5mKbBAzdvYw', 'traits': {'sdm.devices.traits.ThermostatTemperatureSetpoint': {'heatCelsius': 20.9}}}, 'userId': 'AVPHwEtOxuwBVGXBZCDZdVu5DuzSQvjyo2W-ohwvCGcw'}
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [google_nest_sdm.device] Processing update 4ce26566-33fb-4627-8854-808c35ba5ab0 @ 2020-12-01 22:10:41.326000+00:00
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [google_nest_sdm.device] Trait update dict_keys(['sdm.devices.traits.ThermostatTemperatureSetpoint'])
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [homeassistant.components.nest] Update 4ce26566-33fb-4627-8854-808c35ba5ab0 @ 2020-12-01 22:10:41.326000+00:00
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [homeassistant.components.nest] Trait update dict_keys(['sdm.devices.traits.ThermostatTemperatureSetpoint'])
2020-12-01 14:10:43 DEBUG (Thread-CallbackRequestDispatcher) [google.cloud.pubsub_v1.subscriber._protocol.dispatcher] Handling 1 batched requests
2020-12-01 14:10:43 DEBUG (Thread-CallbackRequestDispatcher) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Sent request(s) over unary RPC.
2020-12-01 14:10:43 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] The current deadline value is 10 seconds.
2020-12-01 14:10:43 DEBUG (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Snoozing lease management for 2.148179 seconds.

If you don’t see that, I am thinking your subscription is wrong. i.e. the topic is not for the one from your Nest project.
In your Nest project, your have a Project ID: e.g. ebff85b2-5277-45ea-b794-6e6e76109995

Does it match what you see in google cloud for the Topic ID?

This is what my setup looks like

That looks fine. Kind of stumped.
I presume HA 118??

Yup HA 118

Darn! Was hoping you’d say 117…

So no sign of…

2020-12-01 14:10:43 DEBUG (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Processing 1 received message(s), currently on hold 0 (bytes 0).
2020-12-01 14:10:43 DEBUG (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Sent request(s) over unary RPC.
2020-12-01 14:10:43 DEBUG (Thread-ConsumeBidirectionalStream) [google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager] Released held message, scheduling callback for it, still on hold 0 (bytes 0).
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [google_nest_sdm.event] EventMessage raw_data={'eventId': '4ce26566-33fb-4627-8854-808c35ba5ab0', 'timestamp': '2020-12-01T22:10:41.326Z', 'resourceUpdate': {'name': 'enterprises/ebff85b2-5277-45ea-b794-6e6e76109995/devices/AVPHwEvdLVPCSLrFhZg5VGAbpHlnuFhtOGhZKtjxjTFsCTqRLfTBj49npAdEkfZAik7BkzesHiZ695sDha-5mKbBAzdvYw', 'traits': {'sdm.devices.traits.ThermostatTemperatureSetpoint': {'heatCelsius': 20.9}}}, 'userId': 'AVPHwEtOxuwBVGXBZCDZdVu5DuzSQvjyo2W-ohwvCGcw'}
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [google_nest_sdm.device] Processing update 4ce26566-33fb-4627-8854-808c35ba5ab0 @ 2020-12-01 22:10:41.326000+00:00
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [google_nest_sdm.device] Trait update dict_keys(['sdm.devices.traits.ThermostatTemperatureSetpoint'])
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [homeassistant.components.nest] Update 4ce26566-33fb-4627-8854-808c35ba5ab0 @ 2020-12-01 22:10:41.326000+00:00
2020-12-01 14:10:43 DEBUG (ThreadPoolExecutor-ThreadScheduler_0) [homeassistant.components.nest] Trait update dict_keys(['sdm.devices.traits.ThermostatTemperatureSetpoint'])

in your logs when you change the temperature?

Nope when I set the temperature, nothing in the logs. I also was watching the temp in the nest app and it takes a few tries to even get the temp change to take.

So that is changing the temp from HA and Nest is slow to respond or takes multiple issues of climate.set? Weird…
Mine is virtually instant. Wipe everything and start over??
After 20+ times, it’s eazy-peazy!! LOL

Thanks for all your help. I redid everything and now its working

Got this all up and running after messing with badnest for the last few months, thanks to all! I have one question, I noticed that when you call the set_fan_mode to ‘on’, it only stays on for 15 minutes, how can I get it to stay on until ‘off’ is called? Would an automation be the best way?

The topic looked like it was for the wrong project is. Is that what you changed? (It should have sdm in the topic path)

By the way next HA version will fail loudly if the topic or subscription are not configured properly.

1 Like
alias: Nest Integration Config is FUBAR
description: ''
trigger:
  - platform: state
    entity_id: binary_sensor.nest_integration_failed
    from: 'off'
    to: 'on'
condition: []
action:
  - service: notify.alexa_media
    data:
      data_template:
        target: '{{ states.sensor.last_alexa.state }}'
        message: You bungled the Nest integration setup!
        volume_level: 10
        data:
          type: announce
mode: single

Not sure how he got capable-blend-296116 in there!
Mine is projects/sdm-prod/topics/enterprise-ebff85b2-5277-45ea-b794-6e6e76109995
Would be nice to know what’s there now but at least he’s up and running…