Systems, methods, and software for monitoring and controlling a security system for a structure are provided herein. An exemplary method may include receiving sensor data from at least one first peripheral, the sensor data associated with at least one of activity inside and activity outside of a structure; determining a critical event based in part on the sensor data; creating an alert based in part on the critical event; getting user preferences associated with at least one of a user and a base unit; determining a response based in part on the alert and user preferences; and activating at least one of a second peripheral and a service based in part on the response.

Security Monitoring and Control

Systems and Methods disclosed herein relate to providing a message to an application programming interface (API). The message includes a request for data from a data model, a submission of data to the data model, or both; and a host selection between: a representational state transfer (REST) host and a subscription-based application programming interface (API) host, wherein the REST host receives REST-based messages and the subscription-based API host receives messages in accordance with a standard of the subscription-based API host; wherein the request for data, the submission of data, or both are configured to create, delete, modify, or any combination thereof data related to a smart-device environment structure, a thermostat, a hazard detector, or any combination thereof stored in a data model accessible by the API.

Methods and apparatus for using smart environment devices via application program interfaces

A method implemented in a network engine comprising receiving, by a service function (SF) orchestrator in the network engine, a registration request message from a third-party SF manager requesting registration of a SF comprising one or more SF instances in a network, wherein the registration request message comprises vendor identification information identifying a vendor of the SF and SF identification information identifying the SF, receiving a capability information message from the third-party SF manager indicating vendor-specific capability information associated with the SF, receiving a service request message from a service client requesting a network service and one or more policies for the service, generating the network service by utilizing the one or more SF instances according to the one or more policies and the vendor-specific capability information, and sending the one or more policies to the one or more SF instances.

Service function registration mechanism and capability indexing

A site monitoring system may analyze information from sites to determine when a device, a sensor, a controller, or other structure associated with optically switchable devices has a problem. The system may, if appropriate, act on the problem. In certain embodiments, the system learns customer/user preferences and adapts its control logic to meet the customer's goals.

Monitoring sites containing switchable optical devices and controllers

Onboard EC window controllers are described. The controllers are configured in close proximity to the EC window, for example, within the IGU. The controller may be part of a window assembly, which includes an IGU having one or more EC panes, and thus does not have to be matched with the EC window, and installed, in the field. The window controllers described herein have a number of advantages because they are matched to the IGU containing one or more EC devices and their proximity to the EC panes of the window overcomes a number of problems associated with conventional controller configurations. Also described are self-meshing networks for electrochromic windows.

Self-contained EC IGU

In embodiments of a camera system application program interface (API) for third-party integrations, a camera device captures images as a video stream and communicates the video stream to a cloud-based service. The cloud-based service implements a service application that processes video data received as the video stream. The cloud-based service exposes the camera system API that can be invoked by a third-party application running on a client device to request the video data and camera data that is associated with the camera device. The API permits access by the third-party application to the video data and the camera data from the cloud-based service. The API is exposed for the third-party application to communicate with the cloud-based service via a network connection, and the camera device communicates with the cloud-based service via a secure connection to provide the requested camera data and communicate the video stream to the cloud-based service.

Camera System API For Third-Party Integrations

In embodiments of camera data access based on subscription status, a camera device captures and communicates video to a server device that receives the video, and records and maintains the video as remotely recorded video An application implemented by a client computing device provides all access, some access, or no access to the remotely recorded video at the server device based on a subscription level corresponding to the camera device The server device manages subscription levels associated with the user of the camera device, the subscription levels each delineating a level of access to the remotely recorded video A first subscription level provides access to the live video captured by the camera device, and at least a second subscription level provides access to both the live video and the remotely recorded video at the server device

Lev Stesin

Papers

Camera System API For Third-Party Integrations

Camera Data Access based on Subscription Status