Motion Detector

phoenixrising

@Jhonte , see oscarkindberg example. You are missing the config portion to your module config file. Ill dig mine up later when I have a chance.

Jhonte

@phoenixrising That is only an override for the defaults? Or am I missing something here. Working the same way with or without the config part.

WLCD

Hey All,

I’ve followed all the instructions in this topic, and I’ve finally got it to work (RPi 3 + PS EYE camera) everything works well for a while, and then HDMI out stays inactive, moreover, the PS EYE Left LED (the blue one) shuts off, normal operation, both LEDs are ON, so there is definitely an issue with Raspbian itself, is there anyone which resolved this since the previous post ?

My config : https://pastebin.com/j7cKDBy3

pepemujica

Hi @alexyak !
Thanks for the module, it looks awesome!
I was trying to use it, at some point I could make it run, I mean, I can set the timeout and the monitor “wakes up” when the pi camera detects any movement.
But when the timeout reachs the limit time, the monitor get off, but after a few seconds it appears a message that says “not signal, cable disconect”.
Is there any way to avoid that alert?

Kind regards

danielis

Never monitors turn off by themselve as soon as there is no signal or after a few minutes without signal. Mine was a old that did not turn on/off automatically.
I used wiringpi to activate a relais that turns the current of the monitor on and off.

pepemujica

@danielis
Sorry I can’t get your point as English is not my first language.
What I’m saying is that when the camera does not detect any movement, and the timeout setted is out, the monitor does not show the mirror, but after a few seconds appears something like this:
0_1495564666424_upload-299d3f7e-ab18-477b-a821-071edeee684f

danielis

OK
But if there is a movement detected - is then the mirror shown?

Why do you expect to see the mirror after the timeout?

The mirror must be on if there is a movement. And if there is no movement and the timeout is over, then is the mirror off.
That is what you want and what this module is doing.

I think your problem is that as soon as the mirror is off, your monitor should turn off - right?

pepemujica

@danielis said in Motion Detector:

ur problem is that as soon as the mirror is off, your monito

Yes sir, that is my problem, the module seems to be working fine, but it is a bit annoying to see the alert when the mirror is off

danielis

Yes, that was what I tried to say in my first post yesterday.
I had the same problem.
Old monitors do not turn off by themselve if there is no signal. Newer monitor do turn off, and all is fine.

My solution was tu use a relais to turn on/off the current of the monitor. Therefore I used a pin of the GPIOs to control the relais.

For controlling this GPIO pin I used the wiringpi library

I had to add some lines in the node_helper.js - please look at the lines with: exec("gpio -g …

pi@magicmirror:~/MagicMirror/modules/motiondetector $ more node_helper.js

'use strict';

/* Magic Mirror
 * Module: MMM-PIR-Sensor
 *
 * By Paul-Vincent Roll http://paulvincentroll.com
 * MIT Licensed.
 */

const NodeHelper = require('node_helper');
const exec = require('child_process').exec;
var moment = require('moment');

module.exports = NodeHelper.create(
{
  start: function ()
  {
        //this.started = false;
        exec("gpio -g write 4 1", null);
        console.log('motiondetector started ...');
        console.log('monitor relais on');
  },
  activateMonitor: function ()
  {
        exec("gpio -g write 4 1", null);
        console.log(moment().format() + ' monitor relais on');
        //this.started = false;
  },
  deactivateMonitor: function ()
  {
        exec("gpio -g write 4 0", null);
        console.log(moment().format() + ' monitor relais off');
        //this.started = false;
  },
  socketNotificationReceived: function (notification)
  {
      //const self = this;
      if (notification === 'MOTION_DETECTED')
      {
          //const self = this;
          //this.started = true;
          this.activateMonitor();
      }
      if (notification === 'DEACTIVATE_MONITOR')
      {
          //const self = this;
          //this.started = true;
          this.deactivateMonitor();
      }
  }
} );

pepemujica

@danielis Hi! I’ve tried, but still can’t get it. So I was thinking, instead of putting of the monitor, is it possible to show a black image for example?
So when it detects movement, the MM appears, and when not, a black photo is shown.
Is it possible?

yawns

@pepemujica
There is a module called HideAll (or something similar) which simply hides all modules and leaves a black background. Maybe you want to try it

Kimzer

Could someone please write up a working instruction for the motion detector with the rasperry pi camera? Not the pir sensor, need to make use of the camera somehow. :)

mickyas

@alexyak Does this module switch off the pi, i’m only asking since i have Alexa running in the background which requires 3 terminals to be open all the time? If the pi goes into ‘standby’ or goes off i have to re-enter the information into the 3 terminals consecutively to get it up and running again. Thanks
Mick

bhepler

@Kimzer I wrote up a method using a version of Motion for the RasPi. It’s under the tutorials section of the forum. It’s a non-module solution, so there’s some weirdness involved. But I did get it to work with a Raspicam.

@mickyas - This module doesn’t switch off the pi, it just switches off the output to the monitor.

cowboysdude

@bhepler Yup that’s what I did too.

Hawking

I’m trying to use this model on my Raspberry Pi Zero W with the Raspberry Cam. I run
MM in serveronly mode, using the Midori-browser. This setup itself works fine and also the camera is able to make pictures

raspistill -o testpicture.jpg

However, if I try to add the ‘motiondetector’ module to the config I just get an empty (black, but not switched of) screen after reboot. This is even the case for a very small config.js :

var config = {
        port: 8080,
        ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1"],
        language: "en",
        timeFormat: 24,
        units: "metric",

        modules: [
                {
                        module: "clock",
                        position: "top_left"
                },
            {
                    module: 'motiondetector',
                    config: {
                            timeout: 5*60*1000
                    }
            },
        ]

};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {module.exports = config;}

Things I did:

cd ~/MagicMirror/modules
git clone https://github.com/alexyak/motiondetector

Added line bcm2835-v4l2 to /etc/modules and hdmi_blanking=1 to /boot/config.txt

If I omit the motiondetecotor entry in the config.js it loads fine and I can see the loaded modules. If I execute

/opt/vc/bin/tvservice -o

the screen goes off (completely black). I I afterwards run

/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7

the background light of the screen goes on, however the modules that were there previously don’t show up again ( I waited for several minutes).
If I run

/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 2

the modules become visible again. Therefore I changed the line in

~/MagicMirror/modules/motiondetector/node_helper.js

accordingly. However then I got still an empty screen and in the log:

Jul 16 18:59:23 me startMagicMirror.sh[480]: ** Message: console message: [native code] @0: Starting module: motiondetector
Jul 16 18:59:23 me startMagicMirror.sh[480]: ** Message: console message: http://localhost:8080/modules/motiondetector//motiondetector.js @39: TypeError: Attempted to assign to readonly property.
Jul 16 18:59:24 me startMagicMirror.sh[480]: monitor :state 0x12000a [HDMI DMT (82) RGB full 16:9], 1920x1080 @ 60.00Hz, progressive
Jul 16 18:59:24 me startMagicMirror.sh[480]: ** Message: console message: http://localhost:8080/js/main.js @134: TypeError: null is not an object (evaluating 'moduleWrapper.getElementsByClassName')

To me as a beginner it looks like a permission problem. However even making the motiondetector folder and all files therein rw for everybody it didn’t work.

I hope that somebody who has knowledge about JS can comment on this issue. Many thanks in advance.

strawberry 3.141

@Hawking try to change line 39 to:

cameraPreview.style.visibility = "hidden";

Hawking

Thanks for the quick help. I also found the line in motiondetector.js a bit strange (why the semicolon within the parenthesis…) but as I don’t know JS or details about the code, I couldn’t judge.

I still have the same effect (blank screen) but the new error message is

Jul 17 23:16:55 me startMagicMirror.sh[445]: ** Message: console message: [native code] @0: Starting module: motiondetector
Jul 17 23:16:55 me startMagicMirror.sh[445]: ** Message: console message: http://localhost:8080/modules/motiondetector//diff-cam-engine.js @81: TypeError: undefined is not an object (evaluating '(navigator.getUserMedia || navigator.webkitGetUserMedia || navigator.mozGetUserMedia || navigator.msGetUserMedia).call')

Maybe all these things give empty? As a workaround I surrounded the function by

function requestWebcam() {
         var self = this;
         method = (navigator.getUserMedia || navigator.webkitGetUserMedia || navigator.mozGetUserMedia || navigator.msGetUserMedia);
                   if ( !! method ) {
                     ....
                  }
}

Now at least the other modules load successfully.
However, the modules don’t get deactivated after some minutes :-/ I assume that one of these navigator methods is needed for the motiondetector to work? If I look at https://developer.mozilla.org/en/docs/Web/API/Navigator/getUserMedia they seem anyway outdated? How would the user grand permission in a headless setup? Does somebody know if they are supported by the Midori browser?

strawberry 3.141

@Hawking As far as I know electron exposes the audio and video access, but in midori you probably need to allow the access manually

mongo116

Hi, I’m a total noob to all this, but have recently started a project to build a magic mirror. I’ve got MagicMirror setup, and have the modules I want working. Now I’d like to use the motiondetector module, but although it appears to run without any error, the monitor itself is not turning off.

I’ve tested the camera module and that is working, and I can see an image / record video etc. I’ve also tested running the tvservice commands directly and both of these work as expected:

/opt/vc/bin/tvservice -o
/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7

Only change I have made is to the timeout (30000 so I’m not waiting for too long before the screen should turn off).

My config.js has the following entry for motiondetector:

/* Magic Mirror Config Sample
 *
 * By Michael Teeuw http://michaelteeuw.nl
 * MIT Licensed.
 *
 * For more information how you can configurate this file
 * See https://github.com/MichMich/MagicMirror#configuration
 *
 */

var config = {
	port: 8080,
	ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1","192.168.7.4"], // Set [] to allow all IP addresses
	                                                       // or add a specific IPv4 of 192.168.1.5 :
	                                                       // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
	                                                       // or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
	                                                       // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],

	language: "en",
	timeFormat: 24,
	units: "metric",

	modules: [
		{
			module: "alert",
		},
		{
			module: "updatenotification",
			position: "top_bar"
		},
		{
			module: "clock",
			position: "top_left"
		},
		{
			module: "calendar",
			header: "UK Holidays",
			position: "top_left",
			config: {
				calendars: [
					{
						symbol: "calendar-check-o ",
						url: "webcal://www.gov.uk/bank-holidays/england-and-wales.ics"
					}
				]
			}
		},
		{
			module: "currentweather",
			position: "top_right",
			config: {
				location: "London",
				locationID: "xxxxxxx",  //ID from http://www.openweathermap.org/help/city_list.txt
				appid: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
			}
		},
		{
			module: "weatherforecast",
			position: "top_right",
			header: "Weather Forecast",
			config: {
				location: "London",
				locationID: "xxxxxxx",  //ID from http://www.openweathermap.org/help/city_list.txt
				appid: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
			}
		},
		{
			module: "newsfeed",
			position: "bottom_bar",
			config: {
				feeds: [
					{
						title: "BBC News",
						url: "http://feeds.bbci.co.uk/news/rss.xml?edition=uk"
					},
					{
						title: "BBC London",
						url: "http://feeds.bbci.co.uk/news/england/london/rss.xml"
					},
				],
				showSourceTitle: true,
				showPublishDate: true
			}
		},
    {
		module: 		'MMM-UKNationalRail',
		position: 		'top_left',
		header:			'Departures',		//Optional - delete this line to turn OFF the header completely
		config: {
			stationCode: 		'xxx', 		// CRS code for station
			app_id: 			'xxxxxxx', 		// TransportAPI App ID
			app_key: 			'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 		// TransportAPI App Key
			maxResults: 		5,  		//Optional - Maximum results to display.
			showOrigin: 		false   	//Optional - Show the origin of the train in the table
		}
	},
	{
    module:		'MMM-Tube-Status',
    position:	'top_left',
    header:		'Tube Status',
    config:		{
                show_all:	 true
                }
},
	    {
		module: 	'MMM-UKLiveBusStopInfo',
		position: 	'top_left',
		header:		'Departures',			//Optional - delete this line to turn OFF the header completely
		config: {
			atcocode: 		'xxxxxxxxxx', 		// ATCO code for specific bus stop
			app_id: 		'xxxxxxx', 				// TransportAPI App ID
			app_key: 		'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 	            // TransportAPI App Key
			limit: 			5, 					// Optional - Maximum results to display.
      		nextBuses: 		'yes',              	// Optional - Use expensive RealTime info from NextBuses
      		showRealTime: 	true,          	// Optional - show realtime departure info
      		showDelay: 		true              	// Optional - show delay in minutes based on Real Time info vs Time table
		}
	},
	{
		module: 'MMM-SystemStats',
		position: 'bottom_right', // This can be any of the regions.
		classes: 'small dimmed', // Add your own styling. Optional.
		config: {
			updateInterval: 10000,
			animationSpeed: 0,
			align: 'left', // align labels
			//header: 'System Stats', // This is optional
		},
	},
		{
			module: "MMM-ip",
			position: "bottom_right"
		},
{
    module: 'MMM-Remote-Control'
    // uncomment the following line to show the URL of the remote control on the mirror
    // , position: 'bottom_left'
    // you can hide this module afterwards from the remote control itself
},
{
    module: 'motiondetector'
},

	]
};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {module.exports = config;}

Weird thing is, if I try to have a config section in the config.js with the timeout, and restart MagicMirror, I get an error that the config.js is corrupt. But if I remove the config part, MagicMirror loads without error. MM log below:

0|mm       | Connecting socket for: MMM-ip
0|mm       | Starting module helper: MMM-ip
0|mm       | Connecting socket for: MMM-Remote-Control
0|mm       | Starting node helper for: MMM-Remote-Control
0|mm       | Connecting socket for: motiondetector
0|mm       | Sockets connected & modules started ...
0|mm       | monitor on: true
0|mm       | monitor :state 0x120006 [DVI DMT (82) RGB full 16:9], 1920x1080 @ 60.00Hz, progressive
0|mm       |
0|mm       | Launching application.
0|mm       | Create new calendar fetcher for url: http://www.gov.uk/bank-holidays/england-and-wales.ics - Interval: 300000
0|mm       | Create new news fetcher for url: http://feeds.bbci.co.uk/news/rss.xml?edition=uk - Interval: 300000
0|mm       | Create new news fetcher for url: http://feeds.bbci.co.uk/news/england/london/rss.xml - Interval: 300000
0|mm       | monitor :state 0x120006 [DVI DMT (82) RGB full 16:9], 1920x1080 @ 60.00Hz, progressive
0|mm       |

Any ideas on what could be the problem?

Thanks…