I can’t spot anything wrong from what you’ve posted.
Maybe have a look through this…
I was having trouble getting some of the manual way to work. Strange thing is if I set the redirect uri in my oath to google and follow googles guide verbatim it works well. I’m able to get a token send curl commands and see devices returned etc. then when I setup using my home assistant redirect url if I change all the redirect url in the code from google example to my my redirect url when I copy and paste into browser it fails at the step that you send the browser request to get your access code that you use to send the curl command to get the access token. It goes through most of the steps asking what account you want what devices you want to allow access to etc one pint or flags my https as unsafe and I force it to continue past the warnings and then right at the last step where it normally redirects it sends an error I can’t remember what it is but if try to load the integration in home assistant it seems successful all the way through and finds my thermostat and like I say I can control but not get updated states. The error if I remember right is saying it’s missing parameters and tries to say the callback url of http://xxx.duckdns.org/auth/… isn’t good even though I clearly put https://xxxduckdns.org/auth/… I’m starting to wonder if the problem is somehow related to https as the external access method vs http. Seems lots of people are complaint about similar issues in here. I use nginix with duck dns sets up an https for external access and the. Internally I still acces via http://ip:port I don’t want to get rid of the https as Alexa and other integrations need it to work.
Yes it must match exactly. (Url mismatch of http vs https is a problem. Just add the other one in the redirect url allowed list.)
1 Like
I also have this delay in the Nest Doorbell, can you improve this?
I also use nginx with https and I use the https both internally and externally. When I set up in Google I had redirect URLs for both HA and www.google.com.
1 Like
Does this require one of the new (2019) Nest Aware subscriptions? If not, I’m not sure what I’m doing wrong, I’ve followed the instructions as closely as I can and I’m still not able to get a positive response from the final curl request.
I’m getting the following response.
{
"error": "unsupported_grant_type",
"error_description": "Invalid grant_type: "
}
Works for me, I have no subscription.
Thanks for confirming.
1 Like
I also have this delay in the Nest Doorbell, can you improve this?
In Nest, I have two ‘homes’… one’s actually just a rental.
As you would have it, the rental entities are all that’s showing up. Alphabetically it’s first I suppose…
Is there a way to pick which ‘Home’ is the default?
I’m going to rename them so the one I care more about comes first. We’ll see what that does.
Edit: I deleted the Nest integration and while re-adding it see that I can pick which ‘Home’ i’m granting access to. That seems to be the step I missed.
Okay how do I put multiple redirects for the same oath. The pop up that comes up when you click in the instructions only has a spot for one that I see. And I can’t find where to delete any of the old ones I’ve made either trying to get this to work. Do you have any screenshots or links to what I need to do?
You can edit it afterwards. I can look for the link afterwards but you should be able to find it in the application you set up.
This is great, thank you. I’ve replaced badnest with the official nest and its showing my cameras - great. The camera footage isn’t live footage though, is it still the expectation that we’re getting snapshots?
Also, only my 2 cameras were detected, but nothing was detected for my smoke/co2 protect? Is this not supported yet, do you know?
Thanks again.
Nest Protect is not supported in SDM
Ugh excuse me for the stupid question but I feel like I’m missing something dumb here. I went where you are showing and I don’t see this mine looks different. This is from my phone sorry about that.
Where then did you create the OAuth client credentials that you needed to add to your nest device access console??
I clicked this link in the docs and a pop up came up and I did it there. But I don’t show anything under my actual product page like you showed. I worry this is my problem?!
I think I’m seeing it now it wasn’t putting the oath inside my application when I used that link. I’m thinking this may be the problem fingers crossed