When Google decided to make its Works with Nest API obsolete, there were still many questions about what was going to happen. Some of these responses came when third parties began sending notices to Nest product owners stating that their apps and routines would not work with their cameras, thermostats, and other devices after August 31 (or earlier). At the same time, Nest account holders reluctantly relocate their roots to a Google account, so they wonder if all Works with Nest integrations will be postponed. Google has come back today with answers.

To summarize the supposed positive aspects of the Nest-Google migration, Google could bring all its improvements to the two-step verification and suspicious activity alerts when it's about accessing some controls. This would also require its developer partners to comply with stricter privacy standards regarding how Nest sensors and recordings will be used and permissions management. An example is the ability to allow third parties to process data from external cameras. no camera in the nursery.

For the moment, Google says that existing Integrations of Works with Nest will continue to function normally until third-party developers decide to disapprove of their links. The company announced that its Nest devices would no longer accept new WWN connections on Aug. 31.

Instead of WWN, Google will promote its Works API with Google Assistant, thus preparing more triggers for its routines such as Home / Away status and motion detection. Google Assistant is already associated with more than 3,500 partners (including IFTTT) and 30,000 devices. This means that users will likely find the same Works with Google Assistant library applications and actions as the Works with Nest library for all their Nest devices. . There is no one-touch automatic migration here, so it will be "unplug, replace and play" to the extent of the process.

The company is also working on dedicated Alexa skills for Nest Thermostat and Nest Cam to cover its base using Amazon Echo that will not be able to take advantage of the new WWGA API.

When Scott Scrivens wrote for the first time about the Nest move, he introduced it as a test of Google's reputation as a service provider for customers who did not necessarily buy that name. There is a lot of work to be done to seal Nest's trust.