PIR sensor problem after restart Raspi

[JoeFranz]

Hello,
i restarted my Raspi yesterday, since then the monitor hasn’t gone into standby anymore. I think some Raspian updates have been installed, could it be related to that? Nothing was changed in the MM configuration. Does somebody has any idea?

Greetings Joerg

[kayakbabe]

@JoeFranz have you checked the logs and see whats throwing errors? That is where I would start.

[JoeFranz]

@kayakbabe There are no errors in the logs, nothing was changed in MM. Otherwise the screen was always black when MM started, and the monitor only came on after there was movement in front of the PIR sensor. Now the picture is there right after the start and the monitor no longer goes into standby. So I think it must be something to do with Raspian. Or maybe Electron? I have no idea what happened there… :-(

[sdetweil]

@JoeFranz which pir module are you using?

[JoeFranz]

@sdetweil MMM-PIR-Sensor

[Egnos]

@JoeFranz I can recommend these two modules for the PIR (I just installed them, they also work with the S.O. bullseye):

MMM-GPIO-Notifications: https://github.com/Tom-Hirschberger/MMM-GPIO-Notifications
MMM-Screen-Powersave-Notification: https://github.com/Tom-Hirschberger/MMM-Screen-Powersave-Notification

[JoeFranz]

@Egnos Doesn’t work either, the monitor doesn’t go into standby :-( The Raspbian screensaver function does not seem to work. Can this be reinstalled?

[Egnos]

@JoeFranz have you tried to run the two modules following this guide written by @wishmaster270 ?
https://github.com/Tom-Hirschberger/MMM-GPIO-Notifications/blob/master/examples/HC-SR501/HC-SR501-GPIO4-README-EN.md

Which PIR sensor do you have?

[JoeFranz]

@Egnos I did it according to this guide (in German) have the same pir sensor as in the guide.

[Egnos]

@JoeFranz said in PIR sensor problem after restart Raspi:

I did it according to this guide (in German) have the same pir sensor as in the guide.

Have you checked that the PIR is on the correct pins of the GPIO?

[JoeFranz]

@Egnos The sensor is correctly connected

[sdetweil]

@JoeFranz and does it works correctly outside mm?

there are python scripts that will show it working

[JoeFranz]

@sdetweil How can I test this?

[sdetweil]

@JoeFranz Google search is your friend

https://github.com/raspberrypilearning/physical-computing-guide/blob/master/test-pir-python.md

[JoeFranz]

@sdetweil Ok, that tests the PIR sensor. But since the Raspi doesn’t even let the monitor go into standby, I suspect that it’s due to Raspian. Screen blanking is activated in Raspi-Config, so the monitor should switch off after 10 minutes, right? But that doesn’t work either. Or does that have nothing to do with the PIR function of MM?

[sdetweil]

@JoeFranz well, its shouldn’t go off by itself… as then u would have two things fighting for on or off…

do this, i assume you have pm2 controlling mm at boot

so, do

pm2 status

should only be one thing… defined

[JoeFranz]

@sdetweil ┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.20.0 │ fork │ 12738 │ 64s │ 0 │ online │ 0% │ 2.6mb │ pi │ disabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
pi@raspberrypi:~ $

[sdetweil]

@JoeFranz ok, it’s not a second process getting in the way

next to test the sensor w the python script

stop mm

[JoeFranz]

@sdetweil Nothing happens in the window. :-( PIR sensor broken?

[JoeFranz]

@JoeFranz It is probably because of the current firmware 5.15
With

rpi-update b976c54917e240630c05a9b383010f1492bc61b4 

I installed version 5.10. It now works again with the standby on the HDMI connection.

Greetings Joerg
edited due to wrong quotes outside code block