Here are answers to some common questions about Device Access. You’ll find information about Device Access for Individuals and Commercial developers as well as where to sign up to get the latest updates.
What is Device Access and why are you launching it?
In May, we published a clear set of privacy commitments so Nest customers can understand how our technology works, and explain the safeguards we have in place to protect and secure their sensitive data. With Device Access, we're now offering our third-party ecosystem partners more ways to integrate with Nest products, but doing it built on a foundation of privacy and security.
Device Access lets qualified partners securely access and control your Nest products with their apps and solutions. This gives you more choice in how you control your home. We require Device Access developers to go through an additional security assessment to help keep your data private and secure.
What data security measures are used?
Device Access developers will have to have their proposed use case reviewed, pass an annual security assessment and agree to our Terms of Service before they are approved, so we can make sure each developer has the right data protections and safeguards in place that meet our privacy and security standards.
To learn more about how Google Nest protects user data, read our FAQs on privacy.
How are “Works with Nest”, “Works with Hey Google” and “Nest Device Access” different?
Works with Nest (WWN) was the original way that approved third-party partners could access and control your Nest products. They were fully integrated with a Nest product and could check and change its status. Existing Works with Nest connections will continue to work for those users who have a non-migrated Nest Account in the Nest app.
Works with Hey Google (WWHG) enables Google Assistant to control all your connected products. You can use Google Assistant to create Assistant Routines in the Home or Assistant apps.
Device Access allows partners to integrate Google Nest devices into their smart home ecosystem. With Device Access, third-party partners can directly access and control your Nest products, only after they pass our use case review and an annual security assessment from one of our authorised testers. For example, if you have a security system that offers a Device Access integration, you’ll be able to view and control your Nest camera and other products directly from your security provider’s app. Each year, they’ll be required to update their security assessment to validate that they continue to meet the security requirements.
Which partners are currently on Nest Device Access?
We have a few partners that are already in the process of building their integrations with us through Device Access. Stay tuned for more information once available.
What happens to my Works with Nest connections?
Your existing Works with Nest connections will continue to work without any changes as long as the partner continues to support them, you don’t remove them, and you don't migrate your Nest Account to Google Account
. If we make any changes, we’ll let you know.
What if my Works with Nest partner connection isn't available in Nest Device Access or Routines?
Many of the same companies that are Works with Nest partners are also Nest Device Access partners.
For Routines, check the Google Assistant What it can do page for a full list of routine-based actions available now. This list of actions is constantly being added to, so stay tuned for any additional partner connections through the Device Access program and Routines.
Information for developers
How do I learn more about becoming a Device Access developer?
If you’re a Commercial developer or a Nest customer interested in Device Access, you can find more information on our Device Access site.
Check the page for the latest updates.
Will developers have access to a developer console to manage their integrations?
Yes, we have a console for qualified Commercial developers with approved integrations, as well as for Individuals. To get started, visit the Device Access Console
, accept the Terms of Service and pay a nominal non-refundable fee.
Will developers have to pay for the commercial annual security assessment?
Yes, there is an annual cost on a case-by-case basis. One of our authorised testers determines the scope of work based on your particular use case. Once you apply for commercial development, you will receive more information.
What happens if I fail the annual security assessment?
If you fail the annual security assessment, you have 30 days to fix any issues that were flagged. Once you have fixed these issues, you can schedule a reassessment.
What happens to my Works with Nest developer integrations?
Your existing Works with Nest integrations will continue to work in maintenance mode. If we make any changes, we’ll let you know.
What is Individual access? How is it different from Commercial access?
What is the Device Access Commercial review process?
There’s a qualifying review process that includes an annual security assessment and use case assessment that you have to go through before we accept your application for the Device Access Program. Developers will have to pass this annual security assessment, agree to the applicable Device Access Program terms, which includes our user data policy
, and other additional review requirements before they are approved.
Individual Access is for smart home enthusiasts to participate in Device Access. This allows you to directly control your own Nest devices for your private integrations up to a certain number of users and without a formal review process. It also provides partners with a chance to test their integrations before they submit for Commercial access. Commercial access opens up the integration to a wider audience and requires a complete review process, including an annual security assessment.
Works with Nest had a sandbox for personal integrations. Can I do that with Device Access?
Yes, in the Device Access for Individuals sandbox you can directly control your own Nest devices for your private integrations and automations. These smaller integrations do not require a security audit or review, and have a limited number of allowed users.
If you would like more information, see the Device Access site.