Skip to content
master
Go to file
Code

Latest commit

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.15...4.17.19)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
c12ba19

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 

README.md

MMM-MotionDetector

Installation

Just clone the module into your MagicMirror modules folder:

git clone https://github.com/rejas/MMM-MotionDetector.git

Requirements

Accessing your (web)cam requires to have the client run on localhost or a HTTPS host (due to new requirements in Chrome for getUserMedia). The default value in your MagicMirror config.js is already localhost so most users shouldn't be affected.

Just in case you still have problems (like here) check your config and see if you can solve it by outcommenting the ip-address under

var config = {
    	address : '0.0.0.0',
	...

Configuring MotionDetector with another module that requires MagicMirror address to be 0.0.0.0

You can do this by doing a simple workaround. You need to config the MagicMirror address to localhost (default) and set up a reverse proxy for the other module.

As MagicMirror uses an express server, you can install http-proxy-middleware plugin for express. Then you need to create 2 files:

routes.json

{
  "routes": [
    {
      "route": "/mirror", // any path you like
      "address": "http://localhost:8080" // adrress of MagicMirror
    }
  ]
}

proxyserver.js

// Dependencies
const express = require('express');
const proxy = require('http-proxy-middleware');

// Config
const { routes } = require('./routes.json');

const app = express();

for (route of routes) {
    app.use(route.route,
        proxy({
            target: route.address,
            pathRewrite: (path, req) => {
                return path.split('/').slice(2).join('/'); // Could use replace, but take care of the leading '/'
            }
        })
    );
}

// Start server and listen on port 8081
app.listen(8081, () => {});

Now just start the proxyserver e.g. with PM2 like you may run your MagicMirror.

You can now call http://ipaddress:8081/mirror/modulename and it will be forwarded to http://localhost:8080/modulename.

As you are bypassing browser security with this workaround you may want to add some credentials and/or ip-ranges which can access your proxyserver.

Tested devices

So far I only used a PlayStation3 Eye Webcam for motion-detection at my MagicMirror. If you have successfully used this module with any other webcam, I'd be happy to hear about it.

If you want to use the wired PI-camera follow these steps provided by @rev138:

- Open /etc/modules-load.d/modules.conf
- Add bcm2835-v4l2 to the end of the file and save it.
- Reboot.
- Profit

Another tutorial on how to enable the PI-camera in the browser can be found in this blog post.

Using the module

To use this module, add it to the modules array in the config/config.js file:

modules: [
  {
    module: "MMM-MotionDetector",
    position: "top_left", // Optional. This can be any of the regions. Displays debug informations.
    config: {
      // The config property is optional.
      // See 'Configuration options' for more information.
    }
  }
];

Configuration options

The following properties can be configured:

Option Description
captureIntervalTime Time in ms between capturing images for detection

Default value: 1000
scoreThreshold Threshold minimum for an image to be considered significant

Default value: 20
timeout Time in ms after which monitor is turned off when no motion is detected

Set to -1 to never turn off the monitor

Default value: 120000

Default value:

config: {
    captureIntervalTime: 1000,
    scoreThreshold: 20,
    timeout: 120000
}

Notifications send

Notification Payload Description
MOTION_DETECTED score score calculated by the diff-cam-engine, 0 or greater
DEACTIVATE_MONITOR percentageOff percentage of time the monitor was deactivated since the module started

Changelog

[1.6.0] - 2020-07-05

  • Allow disabling the monitor-functionality and just get the motion detection
  • Use Logger from MM² core
  • Update dependencies

[1.5.0] - 2019-07-14

  • Show error on UI element when something goes wrong during initialization
  • Cleaned up code
  • Update dependencies

[1.4.0] - 2019-03-08

  • Updated code to getUserMedia from browser
  • Cleaned up DOM template

[1.3.0] - 2019-03-06

  • Added time/percentage powered-off to DOM
  • Switched to DOM templating

[1.2.2] - 2019-03-06

  • Switched to MM² codestyle
  • Cleaned up code

[1.2.1] - 2019-03-02

  • Added eslint codestyles

[1.2.0] - 2019-03-01

  • Added DOM for displaying basic debug information on the MagicMirror when a position is specified
  • Updated documentation

[1.1.0] - 2018-11-01

  • Switched from tvservice to vgcencmd. Module can now be used with vc4-kms-v3d and vc4-fkms-v3d drivers.

[1.0.0] - 2018-07-20

  • Initial release

Acknowledgements

Many thanks to

You can’t perform that action at this time.