I would suggest something like this:
if motion changes to active
then
send announcement
end if
While motion is active
wait 2 minutes <--never cancel tasks
send announcement
end while
The only issue will be if the motion ca=hanges to inactive and back to active within the two minutes. Blocking that would require more complex logic.
Therein lies the problemā¦ the idea is to prevent multiple announcements, due to the location of the sensor. The Sensor will definitely change from active to inactive to active to inactive multiple times when someone is moving about the garage. It seems like a 2 minute cooldown period would be a simple thing, but so far it isnāt.
As long as someone is moving about, it should never go to inactive. Usually, you need to be still for 30+ seconds for it to go to inactive but it depends on your DTH. If you really want to block no matter what, I would suggest something like:
datetime notifyTimer
if motion changes to active
then
cancel all pending tasks
if $now>notifyTimer
then
send announcement
set variable notifyTime=addMinutes($now,2)
end if
end if
While motion is active
wait 2 minutes <--never cancel tasks
send announcement
set variable notifyTime=addMinutes($now,2)
end whileThe Sensor is located about 7 feet / a little over 2 meters from the south wall of the garage and.points north. Our freezer and my beer fridge sit against the south wall, so the sensor frequently cycles from active to inactive and back to active.
Ahh, we see the source of the problem now. LOL
OK, see if my logic above helps. I think you need a ācancel all pending tasksā in the first if to keep things straight. I edited my post above to show where.
Forgive my ignorance, but how do I insert the ācancel all pending tasksā command? Iām trying to insert an anonymized snapshot, but itās not working. I was able to get the anonymized piston ID, itās ooxzs.
To add a bit to what Ike saidā¦ Notice this command is in the āgenericā section (non-device).
This means this command should be available in nearly all blocks.
(Location, Lightbulb, Motion Sensor, Switch, Thermostat, etc)
Iām beyond frustrated.l appreciate your help, but itās like weāre speaking two different languages. I understand mostlyo when itās in a Piston, but arrows and dashes are frustrating me to no end. .I canāt make sense of it. I havenāt been doing this long.
Sorryā¦ I was referring to this:
ā¦ and this:
I was suggesting to look at the Dashboard from another device, operating system or browserā¦
(It will likely resolve your UI issues)
It looks good, but one small change is required.
On line 17, you can edit the variable up top to say (no value set)
Doing this will allow the body of the piston to write new data to that variable.
Hereās how it looks now:
And the Log:
7/8/2020, 1:40:44 PM +697ms
+1ms āReceived event [227].test = 1594230044697 with a delay of 0ms
+65ms āRunTime Analysis CS > 22ms > PS > 23ms > PE > 20ms > CE
+68ms āRuntime (38298 bytes) successfully initialized in 23ms (v0.3.110.20191009) (66ms)
+69ms āāExecution stage started
+80ms āāCondition #4 evaluated false (6ms)
+82ms āāCondition group #3 evaluated false (state did not change) (8ms)
+84ms āāExecution stage complete. (15ms)
+85ms āEvent processed successfully (85ms)
Iām at work (using my work computer with Windows Vista, meh), so I canāt really test it until I get home. Will let you know how it turns out.
