Google-Nest Offical Device Access Console Finally Released!

To clarify: Are you saying that updates from the nest app don’t arrive to Home Assistant?
Have a look at the troubleshooting tips at
https://www.home-assistant.io/integrations/nest/#troubleshooting – including making sure you are running the latest home assistant version, and checking for errors in the error log that might indicate a subscriber error.

Hi @allenporter yes it seems that way and it does not always happen. (/sigh)

I did enable the debug logging per suggestion.

I am curious if its related to precision settings. In HA I am using the custom:simple-thermostat’ card with the following settings in lovelace

type: 'custom:simple-thermostat'
entity: climate.upstairs
step_size: 1.0
control:
  hvac:
    auto: true
    heat: true
    cool: true
    off: true
  icon:
    heat: mdi:fire
      cool: mdi:snowflake
      eco: mdi:leaf
      off: mdi:power
      auto: mdi:autorenew
      idle: mdi:power
      away: mdi:leaf

My temperature adjusts in units of 1, so it goes up from 68 to 69 and does down 69 to 68. When I look at the debug logs from HA I see.

image

Notice the heatCelsius: 19.9444 setting, its has a much higher precision and I am wondering if this could be an issue? By the way my Nest and HA is setup for Fahrenheit goes there is always a conversion happening.

Still going …

Great @narsaw I am glad updates are being received. I don’t think there is much additional I can provide, as the integration is passing numbers between the SDM API and home assistant. Maybe others have thoughts.

(Aside: In my home, temperature fluctuations and inaccuracies of 1 degree happen as I just walk from one side of the room to the other so I don’t sweat it, so to speak!)

I’m a non-coder, moderately tenacious, google wielding ‘recipe follower’ trying to get a Nest Thermostat set up. I’ve managed to get pretty far, but am stuck trying to get this command to work…

curl -X GET 'https://smartdevicemanagement.googleapis.com/v1/enterprises/project-id/devices' \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer access-token'

Googling I’ve managed to hack my way through to some extent trying to adjust this instruction so that it actually works (managed to get through previous steps with that method, but am running out of steam :smiley: ) … got as far as replacing single quotes with doubles and deleting backslashes as they’re apparently meant to indicate a connection between lines… but I’m still getting errors in response to the command in my console…

{
  "error": {
    "code": 401,
    "message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
    "status": "UNAUTHENTICATED"
  }
}

figure there’s something obvious to coders that I just don’t get… should there be a space after the double quotes before the -H?

@Gubtug try following this guide.

https://community.home-assistant.io/t/google-nest-offical-device-access-console-finally-released/229146/263

1 Like

Thank you, Narsaw. I actually have the integration installed, it just isn’t showing any devices or entities. After coming across this thread No devices or entities appearing after successful Nest Thermostat Integration I am attempting to follow the instructions here: https://developers.google.com/nest/device-access/authorize and have made my way through to the final step to make the device list call… which gives me the error above. :sob: I’ve found the reference code blocks on the page don’t work very well out of the box. I’ve been able to google and stackoverflow my way through the previous steps editing the curl commands until they work, but haven’t managed to figure out the right format for this curl command.

My struggles seem to be sucking me deeper into the quicksand… in an attempt to “fonzie the jukebox”… I reset the secret, updated configuration.yaml, uninstalled the integration, reinstalled, followed the prompts to give permissions and am now not able to get the integration to take… just comes back to the integration ui and sits at “this step requires you to visit an external website to be completed.”

It sounds like google is not able to access your external URI for the final callback to the integration?

1 Like

@Gubtug make sure you configuring the Nest component while using the external URL for HA

1 Like

@Gubtug I believe that popup comes from home assistant when it creates a new window to redirect to google for auth. Like purely a browser thing at that point. Maybe double check what your browser is doing with like chrome developer tools or make sure it isn’t a popup getting blocked or something odd like that?

1 Like

@allenporter It sounds like he is being taken by the integration to the google page to grant permissions (which he does) but upon completion the page closes and he is returned to the integration which is still waiting for an acknowledgement that perms were granted?

1 Like

Thank you everyone for your help. Some good news! A day later and at least the Nest integration took when I tried again tonight and now appears on my integrations page.

You were correct, @dbrunt . For some reason after completing permissions, the integration didn’t seem to acknowledge yesterday. Not sure what changed, but it did today and I am now back to the issue I initially posted about.

I have what seems to be a successful integration of Nest, but no devices or entities are appearing. Assuming that following the instructions in the link I originally referenced might help… is this the correct formulation…

`curl -X GET “https://smartdevicemanagement.googleapis.com/v1/enterprises/project-id/devices” -H “Content-Type: application/json” -H “Authorization: Bearer access-token”’

of the curl command in this block?

curl -X GET 'https://smartdevicemanagement.googleapis.com/v1/enterprises/project-id/devices' \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer access-token'

I’m using the windows 10 administrator cmd console which has worked for me for previous curl command steps (that I had to similarly modify), but am getting this result…

{
  "error": {
    "code": 401,
    "message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
    "status": "UNAUTHENTICATED"
  }
}

I presume you are replacing access-token with your access token as returned by the previous command?

curl -X GET 'https://smartdevicemanagement.googleapis.com/v1/enterprises/ebff85b2-####-45ea-b794-6e6e76109995/devices' \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer ya29.A0AfH6SMB4p0WCahsdX-2-########-5JusAbJcyUSyl15WVmwXRhqVXT5CDSZLT0zOvL0I6zFhetyLFrPz9d8cZ1sWyM3nbioMEL81QAtvl5DUWv8dVu66Nd_NCcBkxXojn_Qy_AAIrDPKBz1HPV8hMtqj7J8'

Thanks Daniel, Yes, replacing project id and bearer access token. I think I just don’t have the curl command formatted properly, but not sure :man_shrugging:

I can paste the command as-is into an ssh session into my hassio and it works…

curl -X GET 'https://smartdevicemanagement.googleapis.com/v1/enterprises/ebff85b2-####-45ea-b794-6e6e76109995/devices' \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer ya29.A0AfH6SMB4p0WCahsdX-2-########-5JusAbJcyUSyl15WVmwXRhqVXT5CDSZLT0zOvL0I6zFhetyLFrPz9d8cZ1sWyM3nbioMEL81QAtvl5DUWv8dVu66Nd_NCcBkxXojn_Qy_AAIrDPKBz1HPV8hMtqj7J8'

How can I use the ‘image: /api/camera_proxy/camera.front_door’ in the Telegram notification service to send the image? Can you give me an example?
thank you

This integration was working perfectly until around a week ago.

Now the integration card has a red “Reconfigure” button. When I click through and give permissions again I get:

No partner connections found

New partner connections will show up here. If you’re trying to link other services, you can add them from the Home view in the Google Home app.

@tomsr First, check out https://www.home-assistant.io/integrations/nest/#troubleshooting on the “Reauthentication required” part about changing the oauth consent screen settings (updated recently based on figuring out the root cause that was hitting many people). Second, on the no partner connections found first time i’ve seen that one but maybe the discussion on https://stackoverflow.com/questions/64096171/device-access-authentication-no-partner-connections-found is helpful.

Are Nest Cameras able to be used within Home Assistant using DAC?

I am able to see my thermostat, doorbell + camera feed; but not any of my IQ cameras.

Not really wanting to use the actual feed; but to turn them on at night / off in the morning.

@zenko18 yes all nest cameras are supported: https://www.home-assistant.io/integrations/nest/#camera – perhaps there is a bug worth reporting.

There is not support for turning anything on/off in the SDM API, however.