There's always this approach, which reverse-engineered the communications between the Nest App and the Nest Server LONG before they had published an API.
It's still more fully-featured than the Nest API (e.g. it allows control over the humidifier).
I can't see this method ceasing -- it may change, but there will always need to be some app-server communication that can be reverse-engineered.
This is how a lot of the other integrations work (reverse engineering). Might as well be this way with Nest now.
Here is another guy who spent some time with the nest api.
The issue with that is that it emulates the Nest iOS Mobile app. Which will be going away and you will use the Google Home App going forward. (At least that's what I was told)
I've heard a few different things on that. Some say it will be the Google Home app. Others say the Google Assistant app. Regardless, from when I last looked at either of these, they've got a long way to go before they have the functionality that is in the Nest app.
Also, I believe it was actually based on the web app -- it's harder to watch traffic between an iOS app and a secure server than it is to just see how Chrome interacts through the Developer Tools window. I can't imagine that they'll be removing the ability to control these devices via the web... though the site and interactions may change.
When I purchased my Google WiFi, I was very surprised to learn that there was no web interface - it can ONLY be configured and interacted with via smartphone app. The Google Home app, specifically.
Won't be to much longer before this isn't even available..... as Google will have enough information on you to automatically know what configurations you're wanting and complete them before you can even type in the web url.....
and that's a prime reason why I'd never buy (nor recommend) that system to anyone.
Would this solution from the original post provide me the capability to use the nest guard sensors for looking at if a door is open or closed?
NST is not offering an api to guard sensors that I'm aware of. That is what would be needed to integrate with hubitat
Thank you.
We have posted an update to the weather driver to use asynchttp
First off, thank you for this app and drivers. I've been using it for a few months, and I greatly appreciate it!
Today, around 12:22p CT I started getting messages in the logs that I've never seen before. Is anyone else getting anything similar? Since this started, I can no longer control any of my Nest devices via Hubitat. (edit: I'm aware that Google is threatening pulling support on August 1, I'm just curious if others are impacted today, 5 weeks early)
Here is a sample. I haven't changed anything in my configuration, Nest userID, password, etc. My account is up to date and I am able to log into, and operate, devices via the Nest app.
app:1952019-06-23 02:35:29.493 pm [info](http://192.168.0.169/installedI can log into, and operate, devices via the Nest appapp/configure/195) schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7752 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:35:29.279 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:57.316 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7660 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:57.135 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:55.671 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7658 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:55.437 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:47.794 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7650 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:47.604 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:09.315 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7612 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:09.110 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:33:06.740 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7609 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:33:06.546 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:32:50.500 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7593 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:32:50.321 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:32:48.059 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7590 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:32:47.872 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:32:03.104 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7546 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:32:02.887 pm tracePolling BLOCKED | Reason: (Sending Cmd)
app:1952019-06-23 02:31:41.486 pm info schedNextWorkQ COMMAND RUNNING │ queue: 0 │ schedTime: 3 │ recentSendCmd: 2 │ last seconds: 7524 │ cmdDelay: 3 | runInActive: false | command proc: true | Api Limited: null
app:1952019-06-23 02:31:41.360 pm tracePolling BLOCKED | Reason: (Sending Cmd)
Thanks!
Probably just an outage
trying going into the nst manager app, and hit done, and see if the logs clear up.
It looks like it stopped on it’s own around 4:22p CT. I’m not looking forward to Aug. 1. 
I also just went into the app and hit Done as you suggested just to be safe. Thank you!
@tonesto7 Apologies if this has been asked before:
I have this integration working in ST at the moment - as we all know, there is no way to sign up to the works with nest program anymore.. but is there a way that I can move over the authentication from the ST app to this Hubitat app?
Keep all your information from Smartthings and use that same information for Hubitat. I moved this from Smartthings to Hubitat and I don't remember it being super hard but I remember it not going flawlessly. I wish I could remember the details but it was too long ago. I don't remember the troubleshooting being difficult though.
NST Manager, NST Automations and device handlers have been updated.
See post 1 in this thread for details.
Download the Hubitat app
