Hi,

I asked me the same quastion a view weeks ago but could not find a library for the sensor that is still maintained. I ended up in buying a arduino board and send the signals via USB serial interface to the pi now.

@ejay-ibm you are a genius and saved me a lot of time.
I had the same idea but no time to implement it.
Thank you very mich

@AdnanAhmed97
Hi, i do not have any experience with keypads. A short research showed me, that the pads work with a polling mechanism. You need to check in a endless loop if two signals on different pins happend. In my opinion this is a bad job for the Pi. A better solution would be to do recognition work on a arduino board and only send the result (key x pressed) via serial interface to the Pi.

Hi, i do not now the script youbare using but i wrote two modules which do exactly what you like https://github.com/Tom-Hirschberger/MMM-Screen-Powersave-Notification and https://github.com/Tom-Hirschberger/MMM-GPIO-Notifications

Hi,

i wanted to suggest to use the https://github.com/Trekky12/MMM-ModuleToggle module in combination with in example my https://github.com/Tom-Hirschberger/MMM-Serial-Notifications module.
The problem is that the MMM-RadioDe does not work. There are open issues as from 2017.
I tried to do a quick fix but can’t get it run at the moment.

@ejay-ibm I will take a look as fast as i can. It is deffinitly a problem with the code i added

Edit: Added a pull request which should fix the issue

@sdetweil You are absolutly right. But it is a totally different aproach. Hiding the modules to get the background as dark as possible does not save the same energy as turning off the screen. I am one of the lucky guys that uses a Benq monitor which shuts off in a second after turning off the signal and is back in less than three when turning it on again.
I think your module is the perfect solution for people who are not that lucky

@Stef Hi, yesterday i added two Modules to the Showcase Area. On that monitors GPIO Pins and one which controls the Monitor.
My usecase is exactly like yours. I use an PIR sensor to detect user presence and want the screen to be turned off after a configurable timeout.
If you want to try them:
MMM-Screen-Powersave-Notification
and
MMM-GPIO-Notifications

Hi,
i had the same problem the last weeks.
It looks like pm2 creates the startup script for systemd with wrong parameters.
You should check if there exists a file “/etc/systemd/systemd/pm2-pi.service”
In my case the file existed but contained the following lines:

USER=root which should be USER=pi
Environment=PM2_HOME=/root/.pm2 which should be Environment=PM2_HOME=/home/pi/.pm2
PIDFile=/root/.pm2/pm2.pid which should be PIDFile=/home/pi/.pm2/pm2.pid

If the file does not exist you can create it with:
sudo pm2 startup systemd -u pi

But you need to check the values again after creating it.
In the end you can enable the script with:
sudo systemd enable pm2-pi.service

The parts in described by @Chris are needed as well

@Sean All things i needed are merged now; i archived my repostory and added a hint to yours to the readme