Google's Nest Thermostat API's

Hey all,

New member to Sharptools and love it - already have 3 dashboards set up that I use everyday!
The 2 things that continue to nag at me or Ring cameras (read enough posts on here to know it’s not worth doing anything with) and nest thermostat.

Almost all of the posts I’ve read on Nest Thermostat are somewhat old, and all refer to Nest being pretty closed down; however, I did see the developer page here: https://developers.google.com/nest/device-access/api/thermostat

based on this info - is it possible to interface with Nest? I’m not really good with API’s so don’t know enough about what I was reading to know if it’s viable… Any response would be very much appreciated.

(start the “one of us” chant)

Bob

Welcome to the community and thanks for posting!

PS. Be sure to scroll up to the top of the post and vote on your own feature request!

Thanks! done!
How about giving me a 2nd vote :slight_smile:

I’m fresh out of votes. :frowning:

image

But I linked to this thread from a few other relevant topics. :smiley:

1 Like

Any chance this is getting some attention now given the voting?

Checking-in again to see if there’s any movement on this?

I just moved to Ecobee. Much better and has a great driver if you use Hubitat.

The increased vote count helps, but there’s still other considerations.

When Google first rolled out their version of the Nest API, they required an annual security audit and implied it was in the 5-6 figure range depending on implementation which would be between hard and impossible to justify.

They are a bit more vague now simply indicating that an annual security audit is required and that the annual cost is on a case-by-case basis.

Unfortunately, it seems like it might be a chicken-and-egg thing were you can’t do the commercial review until you have an implementation in place… but it’s hard to justify building an implementation if you aren’t sure the commercial review would yield a viable result!

Nest w/ Other Hubs

Some companies like Hubitat completely walked back their Nest beta releases and relied on their communities for ‘self install’ methods. Home Assistant also takes a similar approach with a self install. It looks like Hubitat now links you to their Matter integration when trying to connect a Nest thermostat now though.

Matter

The other thing that’s changed between the original sunset of the Works With Nest legacy API and release of the new Google Nest API is the growth of the Matter standard.

Unfortunately, this is a local API so it wouldn’t work with a cloud-to-cloud integration like this. But perhaps if we ever created a ‘bridge’ that could run locally that could pull in Matter devices too.

Workaround

In the meantime, connecting a hub that supports Nest thermostats (eg. through Matter or a self-install method) which would allow you to authorize your Nest thermostat to SharpTools would be a workaround.

Unfortunately, SmartThings implemented a really strict Nest integration where they don’t expose the Nest thermostats via the SmartThings API. I suspect this was a compromise as they had run into several other snags during their initial Nest integration like having to reduce their device history and other things to get the Nest integration.

Thank you for the detailed response Josh. I had a feeling things had evolved and there were new challenges.

I’m on the fence with Nest/Google. I’m fully invested on the Nest camera front and I’ve just accepted those are locked down to the Google Home app, with all it’s issues. For thermostats, I’m still on Nest Gen 2’s and mulling my options. Jumping to Ecobee, or (insert other popular brand here), is not something I’m looking at because I am likely replacing one of my HVAC units with a variable speed system. As far as I know, Nest has nothing that supports that and I’ll need a bespoke thermostat that may or may not have any smart home integration.

Google have locked things down so much due to privacy concerns, it’s crazy. A bit ironic really, when you think about it.

1 Like