-
Notifications
You must be signed in to change notification settings - Fork 19
Features
-
Support for the DMS3Dashboard component, allowing for the easy, visual monitoring of all DMS3Client devices managed by a DMS3Server component
- Mobile first, responsive, web-based design
- Uses Go's HTML templating package to simplify Go/HTML integration
- Easily integrate 3rd-party configurable HTML website templates
-
Automated starting/stopping of any number of motion detection applications installed on smart device clients (e.g., the Motion motion detector software package) based on the presence/absence of user proxy devices
-
Always On feature starts/stops the motion detection application based on time-of-day (e.g., can enable video surveillance during nighttime or specific holiday hours)
-
Device clients can be custom-configured to process and respond to surveillance events independently and uniquely (e.g., an outdoor IR camera device only sends email during nighttime hours)
-
Optionally play separate audio file(s) on surveillance system enable and disable
-
Configurable event logging
- INFO, ERROR, FATAL, and DEBUG log levels
- Persist logs to file or send to STDOUT (terminal)
-
MAC (Layer 2) address sensing
- IPv4 protocol support
- IPv6 protocol support [planned]
-
Bluetooth user proxy sensing (using RSSI, L2CAP, or similar) [planned]
-
Developed for use exclusively with Motion, DMS3Mail is an automated, real-time email notification service triggered by Motion-generated detection events
- Fully configurable email message subject, body, etc. using the excellent Cerberus responsive HTML email template
- Optionally attach an event image or video to an email message
- SMTP-support for compatibility with most web-mail services (e.g., Gmail)
- Configurable event logging
- INFO, ERROR, FATAL, and DEBUG log levels
- Persist logs to file or send to STDOUT (terminal)
While DMS3 is primarily responsible for monitoring user proxies and determining when to enable or disable the surveillance system, it alone does not manage the processing of video stream data. That complex real-time task is left to motion detection libraries/applications which can be integrated directly into DMS3.
-
Support for the Motion motion detector software package
-
Support for the OpenCV Library [planned]
- OpenCV support is highly anticipated, but still experimental, though the current DMS3 codebase cleanly abstracts away any specific motion detection application dependencies so it is anticipated to be a very straightforward integration
DMS3 is designed to utilize intelligent IoT devices, called Smart Device Clients (SDCs), while still supporting less intelligent, single-purpose devices, called Less Smart Device Clients (LSDCs).
-
DMS3 Smart Device Clients (SDCs) are hardware devices capable of processing local video streams for motion detection on-board, with dedicated hardware. Most computers and smaller single board computers (IoT SBCs) would be classed as smart device clients, including:
- Raspberry PIs (DMS3 was tested with the RaspPi Model 2, Model 3, and Pi Zero W) with a configured on-board camera module
- Any IoT single board computer (SBC) capable of running a Unix-like operating system
- Personal computers with a camera and wired or wireless (WiFi) connectivity
-
DMS3 Less Smart Device Clients (LSDCs) are hardware devices--typically purpose-built--unable to process motion detection video streams locally. These devices usually generate raw real-time video data, which is then sent, consumed and processed by an external device(s), oftentimes wirelessly across a network. Some examples of LSDCs include:
- IP cameras (e.g., the Nest Cam), either wired or wireless
- Webcams, typically using USB connections and run from a laptop or desktop computer
- Download the DMS3 Project
- Compile the DMS3 Components
- Configure the DMS3 Components
- Install the DMS3 Components
- Run the DMS3 Components
- Configuration Testing & Troubleshooting