Hi there -
Thanks for the feedback. There’s really only a few things I can address here, as this site is for the developer API, not product questions or suggestions in general (for those you should try nest.com/support or nest-community.com).
Also, I am not sure if I understand “API does not depend on the Nest Secure alarm system and is not a reflection of the status of that system, nor does it react to state changes in that system. It is completely separate.”
Structure state is not Nest Secure state (that’s how I understand the sentence above) - what is the relations, can these be in different states and what does that mean then?
The Security API that was added has nothing to do with the Nest Secure system. I know it’s confusing to have basically the same name, but it’s focused on deterrence based on events on Nest Cams. It doesn’t influence the alarming state of the home per the Nest Secure, or vice versa. The Nest Secure tracks whether the security system is armed or not, or if it’s been triggered.
With the Security API, a Nest Cam noticing a stranger hanging around your property could trigger the
wwn_security_state to escalate to a
deter state, while your Nest Secure system remains armed and untriggered.
More info here: https://developers.nest.com/documentation/cloud/security-guide
Requires all users to have the app - some people don’t like to be tracked.
Requires cameras - some people don’t like cameras, moreover somewhere you can’t use cameras or it doesn’t make sense to use cameras (apartments) etc.
The Nest Secure is built to interface with the Cloud and be managed from the Nest app or a Google Home. It was also built to work with existing Nest Cams a customer might have. You don’t have to have cameras to use Nest Secure, though. If you’re trying to manage the system entirely offline, however, then our product is probably not the right one for your use case.