Google-Nest Offical Device Access Console Finally Released!

Hello,

I succeeded to integrate my Nest Hello and I see it as a camera entity. However, when I want to display the stream on Lovelace, there are a lot of freezes (as if the image refreshes every 5 seconds).

Is anyone in the same situation as me?

Thank you.

type: picture-entity
entity: camera.porte_d_entree
show_state: false
camera_image: camera.porte_d_entree
camera_view: live

I configured the integration following the steps above, but since I didn’t have a thermostat and that was all that was supported at the time I stopped trying to do anything.

Once I upgraded to .118 it showed up. Could have simply been the reboot of HA, but that’s when it came up. No additional configuration on my part.

I don’t have my nest hello set to live, but auto and when I click the picture entity it buffers after 5 seconds, but doesn’t seem to do it again. I let it go for around 20 seconds and didn’t see any lag.

Thanks for all the hard work on this integration, everyone!

After updating to 0.118.0 and following the extra steps added Nov13 to create a google device subscription within my project, I have my thermostat and cameras working. The thermostat and its sensors update more than just when restarting HA now, too.

If you’re having issues with the sensors or thermostat state not updating, make sure you’ve created a subscription in your Google project as described here : Google-Nest Offical Device Access Console Finally Released!

And if anyone is looking for sensors to track thermostat attributes beyond the default current temp/humidity, here are some I created for mine :

- platform: template  # HVAC Sensors
  sensors:
    thermostat_hvac_action:
      friendly_name: 'HVAC Status'
      value_template: "{{ state_attr('climate.thermostat', 'hvac_action') }}"
      icon_template: mdi:thermostat
    thermostat_fan_mode:
      friendly_name: 'HVAC Fan Mode'
      value_template: "{{ state_attr('climate.thermostat', 'fan_mode') }}"
      icon_template: mdi:fan
    thermostat_preset_mode:
      friendly_name: 'HVAC Eco Mode Status'
      value_template: "{{ state_attr('climate.thermostat', 'preset_mode') }}"
      icon_template: mdi:leaf
    thermostat_set_temperature:
      friendly_name: 'HVAC Set Temperature'
      value_template: "{{ state_attr('climate.thermostat', 'temperature') }}"
      unit_of_measurement: °F
      icon_template: mdi:home-thermometer

2 Likes

I found that you need to add the integration from the external link. So, instead of surfing to your lovelace using your internal IP, use the external address. So, use the duckdns or nabucasa link instead of the ip address.

I was able to add my Nest Thermostat and can initally see the mode it is in after startup. If I change the mode I see that it is changed on nest.com website, but HA does not reflect the mode the thermostat was changed to and it never updates until I restart. Anyone else have this issue?

Started messing around with the Doorbell. If you are interested Reddit - Dive into anything has a great guide (you already have a project and subscription) so just use what you need to get it up and running.

great video on it as well

1 Like

After following the instructions I’m able to see most of my Nest products, unfortunately I’m not seeing my second Nest Thermostat or my temperature sensor. Is anyone else having a similar issue?

1 Like

Yes, I did, but my browser was caching it to antother URL. :slight_smile:

@mostlychris Thanks again for pointing me in the correct direction with your video. I got to the point of Linking my account but when I cut/paste the URL to access nest services I get a:

Can't link to Nest Contact Nest if the issue persists

At first I thought that my Nest account had not migrated, but I can see my thermostat when logging into Nest App’ using my Google Account, as well as in the Google Home App.

Any thoughts ?

Wow finally managed to do this - that was hell …probably took me about 10hrs

Ive created so many different things - talk about confusing - main issue for me was https and the port numbers I think - I didnt need the 8123 - thanks though

Make sure you are using the full path of the subscription id, not just the name.

# Example configuration.yaml entry
nest:
  client_id: CLIENT_ID
  client_secret: CLIENT_SECRET
  project_id: PROJECT_ID    # ("Project ID" in the Device Access Console)
  subscriber_id: projects/.../subscriptions/SUBSCRIBER_ID # ("Subscription ID" in Google Cloud Console. Replace with full path.)

Make sure you are using the same account to integrate that your nest devices belong to. Sometimes an incognito tab is needed to make sure you are not crossing accounts.

My config looks like this, so I think I’m using the full path.

nest:
  project_id: 111111111-11111-1111-1111-1111111111111
  client_id: 1111111111111-1111111111111111111111111111111.apps.googleusercontent.com
  client_secret: 111111111111111111111111
  subscriber_id: projects/sdm-prod/topics/enterprise-111111111-11111-11111-1111-1111111111111

I don’t see any log messages anywhere. The only clue I can find is

I’m not sure what the Pub/Sub is and is at 100% errors as I thought it was using the Smart Device Management API.

1 Like

Your subscriber-id is wrong. Have you followed step A-N on this post?

It looks like you are using the Topic Name and not the Subscription Name. Make sure you are using the sub name:

I see that @RogTP answered this above. Check your sub id.

If you dont mind tinkering around, you can use node red to pull in sdm.devices.traits.CameraPerson

image

just follow this guide

2 Likes

Got the project linked to my devices, thank you for your response!

@RogTP @mostlychris - Thank you guys so much. That did the trick. I must have overlooked the fact you need to use the Subcription Name and not the Topic name.

Thanks yea I saw that.
Depends on my work schedule if I have time to look into that.
I waited this long, what’s another 3 weeks.
(theorizing it’ll be in the next release.)
If not the then, I know there will be a gap in releases due to the holidays, so the I’ll do it.

1 Like