Read the statement by Michael Teeuw here.
PIR problem
-
@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. -
@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 -
@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
-
@wishmaster270 great!
I will try it as soon as I find time …
Have a nice evening!
Peter -
I was not able to use
vcgencmd
under bullseye and AFAIK they are usingxrandr
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 withxrandr --output HDMI-1 --rotate normal --auto
.xrandr
is also the default ofcommandType
option ofMMM-PIR-Sensor-Lite
(see documentation). -
@karsten13 I tried MMM-Pir-Sensor-Lite: counting down works and is re-activated whenever I move my hand in front of the sensor.
But the screen does not turn off.
Peter -
Just released version 0.0.7 of my MMM-Screen-Powersave-Notification module which supports either
vcgencmd
,tvservice
and now alsoxrandr
. -
@Peter what mode are u trying? xrandr vcgencmd?
only xrandr works on bullseye
-
@sdetweil I used xrandr.
Peter -
@Peter and if you issue the commands yourself(via ssh)
do they work?