Motion Sensor toggles too quickly for if/then logic

#1

1) Give a description of the problem
I would like to know when someone is driving up our driveway, and have 2 driveway motion sensors. I would get too many false positives if I just looked at the state change of 1 of them, so I look to see if the state changed in one, and then look at the state change of another within 30 seconds to really validate someone is driving up.
After hooking them up, I see that their state changes too quickly.

2) What is the expected behaviour?
The root of the issue is the Motion sensor toggles from “active” to “inactive” within 1 second.

3) What is happening/not happening?
For me to look at the state change of motion sensor 1 and wait 30sec for motion sensor 2, won’t work. Since they toggle on/off so quickly.

4) Post a Green Snapshot of the pistonimage

download
download.png1178×497 88.5 KB

What would the suggestion be if
IF
motion 1 changed (at some-point in in the last 30 seconds)
motion 2 changed (at some-point in the last 30 seconds)
Do
something.

#2

I am walking out the door at the moment, but there is at least one thread on this forum with that exact same goal. (guessing late 2018)

Maybe try the keywords “driveway motion” or another variation.

I have also seen people attempt this with stairwells… (trying to determine direction)

#3

This is way faster than I like to work with…
Some motion sensors let you adjust that delay a bit.
(If possible, I’d probably set it to inactive after 1 minute of inactivity)

It is often marketed as a “battery saving feature”

#4

I’ll take a look, thank you!