Nest protect integration

[jfh]

Looks like it dieend of August:

 

As a Works with Nest developer, you and your users will no longer be able to access and control Nest devices once the Works with Nest APIs are turned off on August 31. Because we understand this may impact your users’ experience with our products, we want to notify you well in advance so you can prepare for these changes.

Important dates, information, and resources to help you through the transition:

• Works with Nest API deprecation date. Nest device APIs will be turned off August 31, 2019.
• Nest Account to Google Account migration. Early this summer, we will invite Nest Account holders to migrate to a Google Account to align our systems, accounts, and platforms.

• During account migration, users will be asked to remove their Works with Nest connections.
• Once migration is completed, all of their Works with Nest connections will no longer work. This action is not reversible.
  • Works with Nest badge retirement. We are officially retiring the Works with Nest consumer-facing badge. If you are currently using the Works with Nest badge, we ask that you remove it no later than August 31. For packaging and hard marketing material, please remove it at your next revision.
  • Service Shutdown Reminder. We will notify all Nest Account holders and developers by email at least 2 weeks before the Works with Nest service is turned off.
  • For more detailed information, see our What’s Happening at Nest FAQ 2 page. Please provide this link to customers who want to learn more about these changes.

We appreciate you being a partner of Works with Nest. We encourage you to visit the Actions on Google Smart Home 12developer site to learn how to integrate your devices or services with the Google Assistant.

[jfh]

An update to the last post

 

In a blog post published today, Michele Turner, director of product and smart home ecosystem for Google Nest, says that existing Works with Nest connections will continue to work beyond August 31st, and customers will be able to use those services and connections until they are replicated in the new Works with Google Assistant program. The company will not allow any new Works with Nest integrations after the August 31st shutdown. Once customers migrate their Nest accounts to Google accounts, their Works with Nest connections will cease functioning.

Additionally, Turner says the company is “working with Amazon to migrate the Nest skill that lets you control your Nest thermostat and view your Nest camera livestream via Amazon Alexa.” Google is also claiming that Google Assistant will support the ability to trigger routines based on Nest’s Home / Away status later this year.

 

[Waring192]

My Nest thermostat is still working fine with C4. If I purchased a couple of Nest Protects would they work as the Nest Master driver is still working?

[jfh]

I have Nest Protects working fine on 3.1.0

[RyanE]

Unless you move your account to a Google (not a Nest) account, it should continue to work.

RyanE

[Vercingetorix]

I have three Nest thermostats and three Nest Protects that are fully integrated in my Control4 environment.

Recently, one of my Nest Protects reported a carbon monoxide sensor failure and the entire unit needs to be replaced.

Will I be able to purchase a new Nest Protect, add it to my existing Nest account, and subsequently add it my C4 environment like I was able to do originally?  

[msgreenf]

Yes