MMM-PIR-Sensor tuning

jc21

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

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

shgmongohh

@jc21
Thanks alot for your help. I was on vacation and will try it now.

Sebastian

shgmongohh

@jc21 said in MMM-PIR-Sensor tuning:

debug: true

One stupid question, how is the debug info started?

KirAsh4

As @jc21 suggested, add the line debug: true to the module’s config section, and restart MM, then look at the console log.

shgmongohh

@KirAsh4 said in MMM-PIR-Sensor tuning:

I have add the line to the config section. My question is, how can I look at the console log, when I have start the mm new.
Have I go to a special folder, have I to put something in the consule?

pi@raspberrypi:~ $ pm2 stop mm
[PM2] Applying action stopProcessId on app [mm](ids: 0)
[PM2] [mm](0) ✓
┌──────────┬────┬──────┬─────┬─────────┬─────────┬────────┬────────┬──────────┐
│ App name │ id │ mode │ pid │ status  │ restart │ uptime │ memory │ watching │
├──────────┼────┼──────┼─────┼─────────┼─────────┼────────┼────────┼──────────┤
│ mm       │ 0  │ fork │ 0   │ stopped │ 0       │ 0      │ 0 B    │ disabled │
└──────────┴────┴──────┴─────┴─────────┴─────────┴────────┴────────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@raspberrypi:~ $ pm2 start mm
[PM2] Applying action restartProcessId on app [mm](ids: 0)
[PM2] [mm](0) ✓
[PM2] Process successfully started
┌──────────┬────┬──────┬──────┬────────┬─────────┬────────┬────────────┬────────   ──┐
│ App name │ id │ mode │ pid  │ status │ restart │ uptime │ memory     │ watchin   g │
├──────────┼────┼──────┼──────┼────────┼─────────┼────────┼────────────┼────────   ──┤
│ mm       │ 0  │ fork │ 1246 │ online │ 0       │ 0s     │ 2.262 MB   │ disable   d │
└──────────┴────┴──────┴──────┴────────┴─────────┴────────┴────────────┴────────   ──┘
 Use `pm2 show <id|name>` to get more details about an app
pi@raspberrypi:~ $

So, what next?

Sebastian

KirAsh4

You need the browser’s console log. I forgot how to pull it up in Electron, but a search on the forums should give you an answer. Alternatively, you can open your favorite browser on a different machine (on the same network) and visit the rpi’s ip and MM’s port, like so: http://rpi_ip:8080 (fill in rpi_ip). Then hit F12 on the browser to open the console panel.

Jopyth

@KirAsh4 actually it looks like most of the Debug log will appear on the server side.

You can check this with ‘pm2 logs mm’. Add ‘–lines 100’ to show more off the logs (100) in this case.

KirAsh4

Most being the keyword, not all. And honestly, when I’m developing, I don’t rely on what pm2 is telling me, but rather specifically what the browser sees (or doesn’t) and where the errors lie. pm2 doesn’t do that. I can get all errors and debug messages in one place: the browser’s console log. I don’t need to open yet another window just to look at pm2’s logs.

Jopyth

@KirAsh4 I agree with you, but it also depends on what we are debugging. I looked at the particular way @jc21 implemented it, and it seems all the debug information are shown in the process manager logs only.

KirAsh4

I’m not saying it’s wrong, nor right. I just prefer to use one facility that will show everything, as opposed to one that might only show some things.