-
Notifications
You must be signed in to change notification settings - Fork 19
Use Cases
At its core, DMS3 sensing relies on the concept of a user proxy. In this context:
A user proxy is any device representing a user that can be sensed on a network
A smartphone is an excellent example of a user proxy, assuming that the user's smartphone is a participating device on a home network while the user is "at home," and that smartphone then drops from the network when the user is no longer "at home."
This concept can extend to multiple user proxies, making it possible for DMS3 to keep a surveillance system disabled until everyone in an entire family has left home: once the last registered user proxy is no longer sensed on the home network, DMS3 automatically enables the surveillance system.
The reverse is true as well: DMS3 will keep the surveillance system enabled only until the first user proxy is seen on the home network (e.g., someone pulling into the driveway), at which time DMS3 will automatically disable the surveillance system.
In addition to sensing user proxies, DMS3 can be configured to keep the surveillance system enabled for a specific periods of time. Called Always On, this DMS3 feature works as an override to sensing user proxies: regardless of whether DMS3 senses a user proxy on the network, and as long as the Always On time-of-day policy is met, DMS3 will enable the surveillance system.
This feature is particularly useful for nighttime surveillance, when users may be asleep and/or smartphones may be turned off. For example, DMS3 can be configured to turn a surveillance system on at 2300, and stay on until 0500 the next morning. During this time, DMS3 will remain operational and monitor (and report) surveillance events as they occur.
- Download the DMS3 Project
- Compile the DMS3 Components
- Configure the DMS3 Components
- Install the DMS3 Components
- Run the DMS3 Components
- Configuration Testing & Troubleshooting