PIR problem

wishmaster270

@Peter
There can be a lot of reasons why the PIR modules are not working anymore.
What module did you use in the previous setup?
Did you run “npm install” in the module again? Or did you only copy the directory to the new setup?
Are there any errors during the installation of the module?

You can use my test script to check if the sensor it self triggers an event.

Next step would be to test if the command which controls the screen. Most modules use vcgencmd

If you run the following command to display should be shut off and 20 seconds later it should be shut on again.
Best way is to run the command via ssh shell.

/usr/bin/vcgencmd display_power 0; echo "Display should now be off"; sleep 20; /usr/bin/vcgencmd display_power 1; echo "And now it should be on again"

sdetweil

@wishmaster270 note vcgencmd is sensitive to the pi firmware level

wishmaster270

@sdetweil I saw your post about firmware level in one of the other posts. Additionally i think it is depending of the graphical driver used (vc4-kms-v3d vs vc4-fkms-v3d).
But if it works with the posted command most of the modules should be fine.

sdetweil

@wishmaster270 https://forum.magicmirror.builders/topic/17185/pir-sensor-problem-after-restart-raspi/19?_=1663206370580

Peter

@wishmaster270 said in PIR problem:

@Peter
There can be a lot of reasons why the PIR modules are not working anymore.
What module did you use in the previous setup?
Did you run “npm install” in the module again? Or did you only copy the directory to the new setup?
Are there any errors during the installation of the module?

You can use my test script to check if the sensor it self triggers an event.

Next step would be to test if the command which controls the screen. Most modules use vcgencmd

If you run the following command to display should be shut off and 20 seconds later it should be shut on again.
Best way is to run the command via ssh shell.
/usr/bin/vcgencmd display_power 0; echo "Display should now be off"; sleep 20; /usr/bin/vcgencmd display_power 1; echo "And now it should be on again"

Thanks for your answer.
I used MMM-Pir_Sensor in my previous setup.
I made a complete new install, so I did not copy the directory to the new setup.
I will try your commands in the next days, will keep you informed.
Peter

wishmaster270

@sdetweil
I think it is more a problem of the graphical stack. Just checked my new installation of today.
With “vc4-kms-v3d” my test commands from above result in the screen being unchanged after i changed back to the “vc4-fkms-v3d” driver in the “/boot/config.txt” and a reboot everything is working as before.
I run the kernel 5.15.84-v7l+ at the moment.

Peter

@wishmaster270 sorry for my stupid question, I use Gpio pin 17, do I have to use that number in line 6 of your test script?
Peter

wishmaster270

@Peter
No stupid question more a lack of information/documentation of me ;-)

You can call the script with the GPIO number as first argument. In your case it should be:

./testGPIO.py 17

After some research i am pretty sure the problem is the graphics stack in your case. I am working on a solution for the problem

Peter

@wishmaster270 great!
I will try it as soon as I find time …
Have a nice evening!
Peter

karsten13

I was not able to use vcgencmd under bullseye and AFAIK they are using xrandr under the hood for rotating the screen over the web ui menu.

So beside testing if the sensor works you could test if you can deactivate the sceen with xrandr --output HDMI-1 --off and activate it again with xrandr --output HDMI-1 --rotate normal --auto.

xrandr is also the default of commandType option of MMM-PIR-Sensor-Lite (see documentation).