Issues with MMM-PIR

schris88

@eyesallin yes it´s an “issue” with the pi5 as the os is now using wayland as graphical environment instead of x11 which was used forever, a lot of tools are written for it and now need to be updated to work with wayland. You will find a lot of scenarios where there is no updated tool or alternative for the pi5 atm. The switch was done end of 2023 so it´s very new.

eyesallin

@schris88
Thx for the info, I guess a lot of the modules require reworking for the Pi 5.
Unfortunately I do not have the ability, totally new to the Pi and programming.

ChanceTime

Is anyone able to get MMM-PIR successfully running on Bookworm? Feels like every option I’ve tried to turn my screen on and off after the PIR senses movement has been a struggle with no results. I’ve confirmed with tests that my sensor is working, but all the old ways to trigger the display on-off behaviour seem to not be running. I’m on a Pi4 running 12 with Wayland.

Unfortunately I can’t go back to 11 because 10 worked like a dream, and 11 for some reason i could never successfully troubleshoot would refuse to load a taskbar in. Hardware seems to be working fine again in 12…

I can post my config if it helps. Thanks for the hard work, bugsounet. :)

sdetweil

@ChanceTime bookworm on pi4 or 5 uses a different window manager, Wayland, and requires different commands

you can go back to xorg by using the raspi-config command

diccon

Hi

I have had MMM-Pir module running perfectly for months. When I updated my RPi 3B+ to the latest updates this week the module produce the same error message

Pir Error Detected: EINVAL: invalid argument, write

I have tried reinstalling the module but no luck.

Any help greatly appreciated

Thanks

sdetweil

@diccon which MMM-PIR?

bugsounet

Hi, check pir_mode feature in readme readme

by default pir_mode is on mode 0
With pi 4 and pi 5, you can have EINVAL: invalid argument, write error
In this case
you have to use with pi 4: pir_mode: 1,
with pi 5 pir_mode: 2,

diccon

Hi

I am using Bugsounet’s version

Thanks for the help

diccon

@bugsounet thank you changing to pir_mode 1 fixed the problem. Just for awareness I am running on a RPi 3 B+ Rev 1.3 hence why I didn’t do this sooner.