-
Notifications
You must be signed in to change notification settings - Fork 19
Components
Rich edited this page Mar 13, 2025
·
1 revision
DMS3 is organized into the following application components:
Component | Description | |
---|---|---|
DMS3Server | This component acts as the central coordinator for the DMS3 system. It determines whether to enable/disable the overall surveillance system and broadcasts this state to connected DMS3Client devices. DMS3Servers are typically deployed on headless servers or home desktop computers. | |
DMS3Client | These components are client-side services that interact with the DMS3Server. They handle starting and stopping a locally installed motion detection application, such as Motion. Multiple DMS3Client devices can be part of a single DMS3 system. These clients are typically installed on IoT hardware like Raspberry PIs or other SBC devices. | |
DMS3Dashboard (Optional) | This optional component provides a visual interface for displaying real-time status information from connected DMS3Client devices through a web browser. | |
DMS3Libs | This set of shared libraries provides core functionality for managing DMS3 client-server services. DMS3Libs include tools for low-level system and network commands, system logging, and unit testing. |
Optional for DMS3Client devices configured to use the Motion motion detection application:
Component | Description | |
---|---|---|
DMS3Mail | A separate, configurable DMS3 component for generating and sending an email in real-time whenever a client running Motion generates a significant security event |
- Download the DMS3 Project
- Compile the DMS3 Components
- Configure the DMS3 Components
- Install the DMS3 Components
- Run the DMS3 Components
- Configuration Testing & Troubleshooting