Hope this helps…
Project ID:
nest_project_id: x##x#x#x-#xx#-####-x#x#-x#x##x#x#x##
Pub/Sub topic:
nest_subscriber_id: projects/sdm-prod/topics/enterprise-x##x#x#x-#xx#-####-x#x#-x#x##x#x#x##
1 Like
@Xavios the subscriber_id is the one you created at https://console.cloud.google.com/cloudpubsub/subscription with whatever name you wanted:
Like this:
It’s not the Pub/Sub topic name from Device Access Console
1 Like
After rhe integration is added, how can i verify it?
No entity is showing, in my case I have a nest camera.
When will that functionality be added?
1 Like
With my settings shown above, my thermostat finally appeared. Numerous other attempts either failed to complete the integration or, the integration successfully added but no devices appeared plus there was an error in HA logs at HA startup.
I have a pub/sub topic in console.cloud.google.com but it is the one I created in the project called Nest Integration and it did not work. I had to use the pub/sub topic from console.nest.google.com as shown in my previous post. This was after my 3rd time through following the documentation. I created a new project Nest and subsequently deleted my first project named My Nest Thermostat (all in console.nest.google.com). and I do not see it in the google device access console except for the OAuth it created there in my project named Nest Integration (which I think it prompted me to pick since I already had another project over there for another purpose). I subsequently deleted the OAuth I had created. It’s all confusing as hell…
2 Likes
According to HA docs, the Nest Integration SDM API supports Camera in addition to Thermostat but not Binary Sensor or Climate.
Is Canera not implemented yet?
Check your HA logs after startup.
I added the following logger entry in my configuration.yaml as per a post on github:
logger:
default: info
logs:
homeassistant.components.nest: debug
homeassistant.components.nest.sensor_sdm: debug
google.cloud.pubsub_v1: debug
google.cloud.pubsub_v1.subscriber._protocol.leaser: debug
@dbrunt I get a 404 error when browsing to the link of http://console.nest.google.com/ can you confirm that the address you set it on is http://console.nest.google.com/ ?
Try https://console.nest.google.com/device-access/project-list. That’s the page I’m actually on. When I go up a level it redirects me back yo project-list. If I go up 2 levels to the root I get the 404 error. Sorry about that…
1 Like
So sorry, I remember reading that now. What’s that saying? Don’t put the cart before the horse???
My 3rd time through, I followed the steps in https://developers.google.com/nest/device-access/get-started (which is referenced by https://www.home-assistant.io/integrations/nest/). That combined with the many hours I spent learning the first time (when Google made their announcement) and the 2nd time when the integration went live when I tried to get my first setup working with the integration, led me to success. I kept getting lost trying to navigate Google’s cloud…
1 Like
@dbrunt Lol I’m pleased I’m not the only one getting lost in their site.
So is your devices staying updated? Or only updating on a reboot?
On the pub/sub page here https://console.cloud.google.com/cloudpubsub/subscription/list where you can drill into details of messages, I’m finding the Topic page here empty https://console.cloud.google.com/cloudpubsub/topic. Do you have the same?
Google, MS Office 365/Azure and Amazon AWS make my brain hurt!!
Only on reboot. I think that bug is documented on github…
My pub/sub is populated with the entries I created but that is not the sub I specified to get the integration to work. It’s not being used…
If you crank up debug logging for ‘homeassistant.components.nest’ you can see log messages when messages are received.
Glad folks are eager to try this out. The initial version was definitely not ready for prime time! Next release should be much better.
Mine didn’t worked either, but followed this step and updated the config in HA for the subscriber id now it’s working!
https://developers.google.com/nest/device-access/subscribe-to-events#create_a_pull_subscription
Edit: Grmpf, still not able to load the camera’s after a couple of minutes, even though the subscription is working now.
aiohttp.client_exceptions.ClientResponseError: 400, message='Bad Request', url=URL('https://smartdevicemanagement.googleapis.com/v1/enterprises/xxxxxxxx-63f6-46a0-8c2a-7c8890d13546/devices/AVPHwEuLfL1O57JXge-Zwpzf8fXdMsTtpnv_smNTA_8sytnm6xxxxxxxxxxxxxxxxxxxxxxTzwc_HVy4IIkj0hvIgMxe2V:executeCommand')
As I understand it, cameras are not supported yet by the SDM API, only thermostat.
But that error looks suspiciously familiar…
More than willing to help and contribute here. The next release will be? tomorrow??? LOL…
Not critical for me, just a nice to have. Alexa has access to my Nest thermostat and always has so that’s all I really need but would be great to integrate it into HA automations. I just recently have my garage door automatically open when I arrive home if the phone is plugged in & charging in the car, otherwise the front door auto-unlocks when I arrive home and motion is detected. Nice to have that automation turn on the furnace too if ambient temp is low…
1 Like