Works With Nest Requirements


#1

Hi quick question. Looking at the requirements of Works With Nest, does an integrator have to meet all requirements?

For example: “8.3 Product displays correct camera state”. What if our product/service has nothing to do with cameras?

Or “6.7 Product handles Home and Away transitions and the effects on the thermostat properly”. How would an air freshener pass this requirement?

Or “8.5. Products that do not handle deep linking to home.nest.com properly will be rejected.”. How would a product with no UI meet this criteria?

Thanks for any help in advance!


#2

Hi Charlie -

You only need to meet the requirements that are relevant to your integration. So if you don’t use camera permissions, you don’t need to worry about section 8 at all.

As for how an integration might pass an individual requirement, you’d have to provide details on its Nest API use cases.


#3

Thanks Jeff.

To dive into that…if someone had an application with which they wanted to integrate Nest control:

  • How do we address an item like “6.7 Product handles Home and Away transitions and the effects on the thermostat properly” if we do not plan on having Home and Away transitions at all? Meaning, if we do not plan on supporting that use case, would we typically need to address this criteria? Or does the “properly” mean: “if you do this, you must do it correctly”.
  • Similar question for “8.6 Product handles deep linking to Nest app properly”; our UI has no links. Does that mean that we need to build links that are handled properly or does it mean “if we use links to Nest, it has to be done properly”?

Thanks!


#4

Hi Charlie,

How do we address an item like “6.7 Product handles Home and Away transitions and the effects on the thermostat properly” if we do not plan on having Home and Away transitions at all? Meaning, if we do not plan on supporting that use case, would we typically need to address this criteria? Or does the “properly” mean: “if you do this, you must do it correctly”.

When the structure switches from Home to Away, thermostat automatically goes into Eco. Since you are not supporting the Home/Away use cases, you just need to support Eco.

Similar question for “8.6 Product handles deep linking to Nest app properly”; our UI has no links. Does that mean that we need to build links that are handled properly or does it mean “if we use links to Nest, it has to be done properly”?

Deeplinking here shows up in the context of camera. So if you are planning on having any deeplinking to camera, it just has to be implemented well. That’s all. :slight_smile:


#5

Thanks Luva,

Is there a contact email that you can DM me. We have other questions as we move through this process, and would prefer for competitive reasons not to post everything here. Thanks!

Charlie