Nest Detect w/ Nest Thermostat

[btrout11]

I’m trying to set up an automation that would turn my Nest Thermostat off (or to Eco mode) when a door/window with a Nest Detect is opened. We frequently open doors/windows when the temp is favorable. It would be great if these products worked with IFTTT but I haven’t seen where that is an option. Is this type of automation possible or am I totally fantasizing?

[microchips]

I have this requirement too. Support for IFTTT was scheduled to stop.

I want to use Nest camera's alarm zones to turn on outdoor lighting at night

Nest seems to have lots of promises but falls sadly short every time.

Google are one of the driving members behind the Thread networking protocol. Their support team struggle on chat to understand issues. Very dissapointing!

I also have a 3 zone thermostat system in which the zone 2 thermostat sometimes fails to connect to its associated  HeatLink some 25m away - this link uses 'thread network'. There is another (zone 1) midway (12m) between zone 2's thermostat & its HeatLink. According to the 'thread protocol', the zone 2 stat should be capable of acting as a fill-in device to relay thread messages for the zone 2 stat. But this process must be failing.

[FalseProfit]

Unfortunately what you are wanting to do (basically... turn off X device when the state of another device changes) cannot be done - at least at this time. Why GOOGLE/NEST (and for that matter ALEXA, too!) have not implemented simple IF/THEN based actions to be used in or out of routines is beyond me! 

I feel they could - THEY CAN! but can't shake the feeling that they are more focused on pushing (and refining) a complete, seamless and coherent end to end home package since the merger? acquisition? of Nest. And that sucks.

In regards to IFTTT and your GNEST products... even if IFTTT had that capability (they didn't), it wouldn't matter - and I quote:

"...the Works with Nest program was to be discontinued. That meant your IFTTT Applets for Nest Thermostat, Nest Protect, and Nest Cam would cease to function. Now, that is no longer the case."

Wait!!! So I'm telling you that your request either exists or is just right around the corner. Nay, keep reading...

"Please refer to Nest’s post for details, but here is how to keep your Nest Applets working on IFTTT beyond August 31, 2019.

1. Do not migrate your Nest account to a Google account. Migrating your Nest account will cause IFTTT and other Works with Nest integrations to be disconnected. This process is not reversible.

2. Do not disconnect Nest from IFTTT after August 31st as you will not be able to reconnect it. This affects users that do not migrate their Nest accounts to a Google one."

I hate to be the bearer of bad news but, I rather appreciate a clear and concise answer/response such as mine. Hope this helps! 

[microchips]

A lot to digest there, FalseProfit!

You'll need to migrate your Nest to Google, no escape, quite simply they own it now & that's where the Nest product is moving, and where the new developments will be.

In terms of automation, next year will see the launch of new "Matter" home automation products, built on the "Built on Thread" mesh network. This is what IoT has been waiting for, and it means that devices built using Thread should all be able to communicate with one another and participate in the Thread network as a whole. As other manufacturers come on board we should see a range of new & exciting products. 

Big names like Apple, Goole, Amazon, Eve, + many many more are behind Thread & Matter projects, so I for one, am expecting great things. I see a convergence between Google, Apple & Amazon, certainly in terms of networking & device inter-operability. 

The issue I described above with my GNest thermostat not being able to communicate with its HeatLink because of excessive distance / thick walls, has now been fixed. You may be aware this Nest link is in fact, built on Thread, so what I did was to place one "Eve Energy" thread module physically between the thermostat & its heat link. I also enabled my Apple TV as a 'thread boundary device'. Now it seems that these Mesh devices now are talking to each other & the GNest thermostat can control it's HeatLink despite the distance. Since installing we have not had any further drop-outs. 

I think this bodes well for the future of "Built on Thread".

You can Goole the term for yourself & even get the specification - see if you agree.

[GarrettDS]

Hey folks, 
Thanks for visiting the Community. 

Since this thread hasn't had activity in a while, we're going to close it to keep content fresh. 

We hope you were able to get the help you need but if the issue persists feel free to create a new thread, and provide as many details as possible so that others can lend a hand. 

Best regards, 
Garrett DS