Motion Detector

Hawking

@strawberry-3.141
Thanks for your help. Unfortunately I don’t find any information about media access or how to activate it in the Midori browser…

@mongo116
I cant’ help you why the motiondetector does not turn off your screen (it also does not work in my case). However, how does the config.js with the additional time-out section that results in an error look like? At least in my case a section like

{
                   module: 'motiondetector',
                   config: {
                           timeout: 5*60*1000
                   }
           },

gave no complaints about errors in the config file (for a complete config-file see my post above).

mongo116

@Hawking Thank you, that works. Monitor is still not turning off, but that’s one issue off the list :)

mongo116

Just to add to this, I have checked that the camera is working and motion is detected by testing with https://github.com/pageauc/motion-track. All appears to be working as expected. No motion is detected unless I move in front of the camera.

strawberry 3.141

@mongo116 maybe the value that gets returned is different than the value set in the module, so he always tries to activate the monitor?

mongo116

I’ve got the motion detection now working - had to add bcm2835-v4l2 to \etc\modules - restarted and screen now turns off after defined period and on when motion is detected. This is really great, and I’m nearly there - but… Now when the motiondetector is running, the RPi3 temp just goes up and up and up, until it eventually crashes/freezes and I have to pull the power as RPi is completely unresponsive. If I remove motiondetector from MagicMirror, temperature stays stable and no crashing. Is there something I can change in the config to sort out this performance issue?

strawberry 3.141

@mongo116 it looks like https://github.com/alexyak/motiondetector/blob/master/diff-cam-engine.js#L37 it creates 10 images per second and compares it to the previous which is probably the intensive part

mongo116

@strawberry-3.141 Thanks for that. I’ve amended this slightly so will keep an eye on it. Might also have a look at putting on some heatsinks to see if that helps.

One (hopefully!) final question. When the monitor is turned off, is there a way to ‘freeze’ the other modules, so they stop running for the duration that the monitor is off? This would hopefully help with performance, in that the other modules are no longer running.

strawberry 3.141

@mongo116 every module has a suspend and resume function, but nearly none module that I’m aware of has implemented stopping intervals and fetching data in there. so calling those functions wouldn’t make a difference then just hiding it on the display.

Furthermore I doubt that it would really make a difference if you’re not using another cpu intensive task like voice recognition …

reaper81

sorry for my noob-Question but is there an setup or a explaination how to use the three .js files from alexeyak on github? normaly there is an readme-file.

mongo116

@reaper81 I had the following in my config.js:

              {
                module: 'motiondetector',
                config: {
                timeout: 5*60*1000
                   }
               },

You will need to ensure that the 3 files are located in the modules/motiondetector folder.

I ended up using a different method for motion detection though, as tvservice kept stopping working.