Yes, that makes 110% sense now. I deleted the app, re-installed it (and didn't click the subscribe) and it works perfect. Thanks for the insight!
Now if I fiddle with the temp on my nest display, I see the state variable instantly change in the thermostat device screen.
I think I'm missing something, I think I got it setup correctly and got the correct code but it's not finding any devices still at all.
Excited to get this working, but technically challenged ! When I'm GCP and creating a OAuth client ID, it asks me for an Application Type. What should I be using?
@bfara83 The logs you posted indicate Authorization failed -- hopefully your deleted post is an indication that things are now working?
@karnik.abhijeet You want to select "Web application" for this field.
Thanks. Got past that. What did I miss here
What should the redirect URI be? Is this when we are creating the OAuth?
HI- I know the process is a little confusing, and it seems like there are multiple ways to accomplish this, but I think the simplest way is after you register for device access, go back to Get Started | Device Access | Google Developers and click on the blue "Enable the API and get an OAuth 2.0 Client ID" and follow the directions immediately above that blue button... Get Started | Device Access | Google Developers
Access to the SDM API is provided through GCP. To enable the API and authorize a Google account with a supported Nest device, you'll need a GCP project.
Use the Enable the API and get an OAuth 2.0 Client ID button below to enable the Smart Device Management API and get an OAuth 2.0 Client ID:
Not yet, not too sure what I did wrong still. Won't be home till later to try again.
Got a Bad Request (400) on the token request -- I'm guessing one or more characters got missed in the copy/paste of the authorization code from the google redirect url.
I'm still thinking on how to make this more seamless -- e.g. link from App to Google, allow access, then redirect back to App (providing the code directly) - but haven't found the right sequence/set of attributes to make that work yet.
@jonathan.lorber Thanks a lot this worked out. You were right, this indeed is the easy way of doing it.
@dkilgore90 It would be nice to add the above instruction to your first post for folks like me.
Heads up -- tonight's changes re-worked the Oauth2 workflow to reduce the copy/paste, and manual link construction is no longer required. The README has been updated to document the new workflow.
I don't think this should break any existing installations -- but no warranty or refunds! 
Just had to play with it a little to test it out. FWIW, you have to go back and add Hubitat to the allowed Redirect URI's in order for the authorization to work from the app.
The specific site URI you need is: https://cloud.hubitat.com/oauth/stateredirect
Before I did that, I was getting a 400 error. Afterwards, it discovered my devices.
Another quirk, I had to click done after entering the Project ID and Json. Then I was able to come back into the app and click authorize. So, it was not showing the authorize button until after I clicked done (even though I had filled out the fields. I tried to tab out and clicking on white space. Neither worked)
Forcing the user to click done was intentional -- since we redirect away from HE to do the auth, I wanted to ensure that both the app installation and settings were saved before moving on.
I sort of got that from the read me. (Maybe the wording in the app needs to match the read me? Thinking of users for an app that I had install links with a big red circle around the link and "click here" - but I still had some miss it LOL - Not kidding, I had a call where the guy asked, "It says click here, what should I do??? I literally asked him if he tried clicking there.... 
)
Noted -- I'll update the app display wording to that effect.
Just trying to do it from a beginner user perspective...... (which is not difficult for me on the new platform)
Definitely not complaining.... This is awesome!!!
With the new update, I was able to get it working just fine. I really love the newer flow you created, it's so much simpler than before. The instructions I think is good, at least it was pretty easy for me to follow.
I just have the Nest Thermostat which is the only Nest device I have currently. Obviously this is very early I know into developing this integration, suggestions I came up with so far:
So far it seems to work as intended when testing it out so really great job on this integration. This was the final device I didn't have integrated to Hubitat since Google pulled "Works with Nest" dev program.
This on hpm?
@dkilgore90, I second the idea of setting only 1 decimal point. P.S. - Great job and again, thanks for all of your hard work!
I support the idea of fewer decimals as well. My vote is for 1 decimal.
Hi, great work!
Is there any way of having the Nest Thermostat update it's heating or cooling setpoint automatically, from within HE devices? if the temperature is changed from within the following platforms; Nest app, HE Dashboard, Sharptools,io etc. The thermostat doesn't update within HE - Devices, you have to hit the refresh button every time for the changes to be reflected.
I am using Thermostat scheduler to set the temperature using modes (day, away etc) which works perfectly. It will reflect the changes in the Nest app but not Sharptools, or HE. Since Sharptools pulls the device directly from HE via API. Once you hit the refresh button, the changes appear within Sharptools and HE dashboards.
Download the Hubitat app
