@schmo90 It should work fine, there is no logic prior to that switch that filters possible values.
What does the server console log report after the text [PiLights] Incoming: ?
req.query.sequence should contain the string name of the sequence you’re requesting.
Hi schmo90, good to see you’re contributing :)
Assuming your tests with curl -X GET "http://yourmagicmirror/PiLights?sequence=blue_pulse" still don’t work, I think I’d need to see all of your changes. If you’ve forked my repo on github can you please link it?
Great stuff. People shouldn’t discount a faulty PIR either. The one I had on the shelf for ages wasn’t detecting quite right so I ordered another one and the difference in detection is huge. I’m not sure if these have a shelf life or what but yeah, that was my recent experience.
Sounds like you’re on top of that then.
Just fyi, the latest code for the original pir sensor module will rebuild the compiled dependencies for you as part of the npm install command in the module. There should be no reason to run npm rebuild manually unless you get those pesky “expected version xx but got xx” errors.
@open_book Very strange, it seems the module is trying to activate/deactive the monitor using the Relay, but you haven’t specified a relay to use.
I have noticed however, that sensorPIN of 3 shouldn’t work. This variable is incorrectly named, it is not actually the pin number of the header, but the GPIO number instead. Refer to this Pi 3 image showing which “pins” correspond to “gpio” numbers. You should be using one of 4, 5, 6, 12, 13, 18, 22, 23, 24, 25, 26 or 27.
For example, a sensorPIN of 4 would require the PIR io cable plugged in to pin header 7.
@open_book Few things,
onoffnpm module has issues with some releases.cat /etc/os-releaseA quick look on that website and I found an API they provide. When you get more advanced you can hook into that.
From the quick googling I’ve done, it may be possible to disable/enable raspberry pi usb power with commands:
Disable
echo 0x0 > /sys/devices/platform/bcm2708_usb/buspower
Enable
echo 0x1 > /sys/devices/platform/bcm2708_usb/buspower
However I haven’t tested. I’d recommend writing a new module that handles this and listens for the USER_PRESENCE event notification that the Pir module triggers.
Depends on your module I guess. If the part you want to debug is in the interface, turning dev console on is the way:
electron js/electron.js dev
But if you want to debug node_helper side, console.log everything.
@paulocarrasco Pull again now.
Made the noob mistake of not testing, I wasn’t near my mirror at the time. All good now.
@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
console.log and outputs to the chrome dev console if activeconsole.log to output to stdout of the processWith 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:
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.