This is awesome!
One suggestion, can you add a configuration setting to specify the png location/name? This way we could use this module for other festive periods :). For example moving snowflake in the winter

@Lipax there you go, nothing wrong with the software code. It’s the PIR sensor giving false positives. Nothing you can really do about that. Perhaps a different brand/quality of PIR sensor if it will help but I doubt.

As mentioned before, due to exact same problem I gave up on PIR sensor completely and moved to the microwave. This works for me now over 3 years. without false positives.

@Lipax you need to be sure that sensor is not the cause.
Measuring it’s sensing, output voltage and duration is a good way of confirming if sensor works ok.

@Lipax try different gpio pin, like a pin 18 which is a GPIO 5. It’s default set to input function. Don’t forget to adjust the python code, change switch to 18.

You might check the GPIO 0 (your pin 11) if it is set to input. Use command: raspi-gpio get 0 or raspi-gpio get to check all GPIO’s.

Also, use a multimeter to measure the voltage coming out from sensor. It should be around 3.3V for few seconds when sensing detected. This way you can monitor if actual detection / voltage is coming from sensor.

Can you share your python code? Perhaps there’s something there

@Lipax this sensor is very sensitive and catches any movement 360 around from several meters away. I had same problem… If you don’t dial down the sensitivity-range you will keep getting false positives.

@Lipax said in UPDATE: Replaced my PIR-Sensor with a Doppler Microwave Sensor.:

hello,
i tried this with the microwave sensor, but im out of ideas. i get wrong positives every minute. (i check every 5 sec).
i added also the ferrite, tried another raspberry, different of these sensors (bought a 5 pack) and placed it in a different room. anyone got any ideas what else i could try?
or maybe similar microwave sensors i could try?

any help would be great, tyvm

Did you try and limit the range as described in beginning of this thread? For me option 2 helped to limit oversensitivity.

@Feedy88 it can be done easy by flipping the GPIO detection.
I use crontab with simple command. During the specified night time my MM does not turn on the screen. In morning the sensor starts to work again. If that’s what you are trying to achieve let me know and I can share details.

It really depends on pir sensor quality and it’s sensitivity setting. I tried several pir sensors and all of them produced too many false triggers.
At the end I switched to using a microwave sensor which never gives me false detection.

@boehmch thanks, this is helpful yes.