Skip to content

Appendix B Running DMS3 with Less Smart Device Clients

Rich edited this page Mar 13, 2025 · 1 revision

Less smart device clients (LSDCs), such as IP cameras and webcams require special consideration in DMS3.

While smart device clients (SDCs), such as a Raspberry Pi or similar single board computer (SBC), have both a camera device and a means for running a motion detection application on the same local host, LSDCs typically just have a camera device, with limited means for processing video streams locally.

DMS3 resolves this limitation by allowing any DMS3Client to serve as an SDC proxy for one or more LSDCs.

Operationally, an SDC running as a proxy for one or more LSDCs is viewed no differently than a standalone SDC. However, care must be taken to make sure that all participating LSDCs are correctly enumerated when configuring the locally-installed motion detection application on the SDC proxy.

As an example, using Motion, the configuration file, motion.conf, permits multiple video devices to be managed by a single instance of Motion. These devices can all be managed by one SDC proxy (running the DMS3Client component).

In the example file below, the last few lines of a motion.conf file is listed, showing four separate camera configurations managed by a single SDC proxy (note the last line used by the DMS3Mail component):

##############################################################
# Camera config files - One for each camera.
##############################################################
camera /home/user/security/motion_config/cam_office.conf
camera /home/user/security/motion_config/cam_livingroom.conf
camera /home/user/security/motion_config/cam_garage.conf
camera /home/user/security/motion_config/cam_driveway.conf

##############################################################
# Run DMS3 Mail when image generated
##############################################################
on_picture_save /usr/local/bin/dms3mail -pixels=%D -filename=%f

Once configured, these LSDC devices are now managed directly through a single SDC running the DMS3Client component.

Clone this wiki locally