search

bugsounet / MMM-Pir

Manage your screen with a pir sensor
MIT License
26 stars 7 forks source link

Increase limit for GPIO number #45

Closed outlying closed 4 months ago

outlying commented 4 months ago

In my case, I've done a migration from https://github.com/outlying/MMM-PIR-Sensor (deprecated) to this project. Until now, I have configured my system to use GPIO 23. It really gave me a headache as to why it was not working since it worked with the previous module and when tested from the CLI.

I'm using an RPi3 (which is OK for MM), and for the RPi3, the GPIO pins go as far as 29. For the RPi4 and RPi5, the maximum GPIO is 27.

The artificial limit of 21 used in this project makes no sense at all in any case for past and present RPis.

I also checked the https://github.com/gpiozero/gpiozero/blob/master/gpiozero/input_devices.py#L525 project that is used to get the sensor state, and it also does not limit the GPIO number in any way.

When I changed this restriction, my sensor started working simply because there was no assertion error.

bugsounet commented 4 months ago

humpf... sorry you have right ! Thanks for correct it !

outlying commented 4 months ago

I jumped to conclusions too fast, there is assertion error but screen is not waking up - probably another error

Please accept this correction to assertion and meanwhile I will work on other issue

bugsounet commented 4 months ago

Sure, You can run the python script manually for debuging (without MM²)

inside components folder execute python MotionSensor.py -g <gpio> (replace by your own number) when a motion is detected, you will see Detected