@paulocarrasco That was my bad. The module has been fixed now, do a git pull inside the module dir.

@shgmongohh Ok I’ll take a look at my stuff soon. I’m in the middle of writing another module that takes a photo when this PIR module senses user presence, if you had a camera attached it might be useful to you to see what the pir is detecting, if anything.

Do you experience the same thing with paviro’s original module? https://github.com/paviro/MMM-PIR-Sensor

MMM-Sounds for any mirror/operating system with Alsa support and speakers attached or built in to the monitor. Full setup instructions in the readme.

Currently used in my other MMM-IFTTT module.

To play a sound from another module:

this.sendNotification('PLAY_SOUND', 'wobble.wav');

or also specifying a delay:

this.sendNotification('PLAY_SOUND', {sound: 'wobble.wav', delay: 1000}); // 1 second delay

Update: Added support for my new MMM-Sounds module. Notification integration instructions are in the updated MMM-IFTTT readme.

I agree, a central place for logging info would be ideal but that’s just not possible with MM at this point.

This is a bit out of scope for this topic, however unless you’re across the module system in depth you may not be aware that there are 2 separate “processes” to the MM for lack of a better word

• The UI, electron app that uses console.log and outputs to the chrome dev console if active
• The Server App, express & module node_helpers that uses console.log to output to stdout of the process

With the way MM module system is implemented, using any additional NPM packages required by a module can only be done on the NodeJS App side (as far as I’m aware?), not in the UI where the browser dev console log is available.

That said, for this module particularly, if the UI was started with the dev console option then when motion is detected or no longer detected, the Node JS App will log a USER_PRESENCE socket event where the value will either be true or false respectively. This is the case for both the original github repo and my fork. Unfortunately the dev console event system doesn’t log the value so debugging on/off values is not possible:

calendar received a module notification: USER_PRESENCE from sender: MMM-PIR-Sensor

I don’t use PM2 yet, but to start the MM with dev console on just add the dev argument:

electron js/electron.js dev

When you are running MagicMirror do you see these lines in the console output?

All module helpers loaded.
Starting server op port 8080 ...
Server started ...

@shgmongohh I have forked the original MMM-Pir-Sensor repo and made some mods to debug my own sensor last week.

https://github.com/jc21/MMM-PIR-Sensor

If you add debug: true to the config of my forked code, you’ll get console info about when the sensor detects motion and when it doesn’t. Also note, I’ve renamed the sensorPIN config item to sensorGpio to more accurately indicate the numeric determination.

[MMM-PIR] [2016-10-04 09:31:07] Watching on GPIO #25 ...
[MMM-PIR] [2016-10-04 09:34:15] Motion no longer detected
[MMM-PIR] [2016-10-04 09:34:15] Turning Screen OFF in 30 seconds
[MMM-PIR] [2016-10-04 09:34:18] Motion detected
[MMM-PIR] [2016-10-04 09:34:18] Not turning monitor ON, its already ON

@zydecat74 Thanks for this, I’ve seriously been considering this option over the last week given the supply issues.

A few questions for you:

• Is this the stuff you used? I can’t seem to find any other product on bunnings site
• I guess you applied the film onto the front of the glass, is it just as effective if it were applied to the back instead?

Try:

sudo npm install -g electron

If you get any errors with that command then something needs fixing outside of the MagicMirror package and installation.