Help with rules

mwne2nks

Member
I have numerous doors in a commercial property and cant figure out how to have a door held open rule to beep the keypads and scroll a message  that says door  is held open. After 90 seconds  on the doors.
Can this be done.?
 
What kind of panel?
 
I'm implementing that tonight since I have contractors over who keep leaving doors open...
 
I can't test this right now - since the whole family is asleep, but something like this should work - I'd been meaning to add this lately anyway:

' When the door opens, start a timer and increment the number of Open Doors'
WHENEVER Front Door (Zn 49) BECOMES NOT SECURE
THEN TURN Output 180 ON FOR 15 SECS, RESTART TIMER IF RUNNING
THEN ADD 1 TO Doors Open (Counter 2)
WHENEVER Garage Door (Zn 50) BECOMES NOT SECURE
THEN TURN Output 181 ON FOR 20 SECS, RESTART TIMER IF RUNNING
THEN ADD 1 TO Doors Open (Counter 2)
WHENEVER Rear Slider (Zn 51) BECOMES NOT SECURE
THEN TURN Output 182 ON FOR 20 SECS, RESTART TIMER IF RUNNING
THEN ADD 1 TO Doors Open (Counter 2)

' When each door delay timer expires, see if door is still open - if so, start the beeping and send the message'
WHENEVER Output 180 STATE IS TURNED OFF
AND Front Door (Zn 49) IS NOT SECURE
THEN DISPLAY "Front Door Open" IN Area 1 (Area 1) INDEFINITELY, [*] CLEARS, BEEP
WHENEVER Output 181 STATE IS TURNED OFF
AND Garage Door (Zn 50) IS NOT SECURE
THEN DISPLAY "Garage Door Open" IN Area 1 (Area 1) INDEFINITELY, [*] CLEARS, BEEP
WHENEVER Output 182 STATE IS TURNED OFF
AND Rear Slider (Zn 51) IS NOT SECURE
THEN DISPLAY "Rear Slider Open" IN Area 1 (Area 1) INDEFINITELY, [*] CLEARS, BEEP

'As doors close, decrement the counter so you can tell when they are all closed'
WHENEVER Front Door (Zn 49) BECOMES SECURE
THEN SUBTRACT 1 FROM Doors Open (Counter 2)
WHENEVER Garage Door (Zn 50) BECOMES NOT SECURE
THEN SUBTRACT 1 FROM Doors Open (Counter 2)
WHENEVER Rear Slider (Zn 51) BECOMES NOT SECURE
THEN SUBTRACT 1 FROM Doors Open (Counter 2)

'Once all the doors are closed, clear the messages from the keypad'
WHENEVER Doors Open (Counter 2) CHANGES TO 0
THEN CLEAR PREVIOUSLY DISPLAYED MESSAGES ON KEYPADS IN Area 1 (Area 1)

 I'm a little worried that the above would clear alarm or other trouble notifications but it's too late at night for me to think of a better way... the goal is to clear any beeping once all the troubles are resolved - and to only trigger if a particular door goes over the hold-open time and NOT accidentally trigger if somehow multiple doors opening/closing at the same time extending the same output timer.

Theoretically though this could be nice for the fact that, if a door is needed open, you should be able to hit * to silence it - otherwise would need another way to quiet it.
 
Would take a little testing to see if this produces the desired result; I'd love to hear ideas from anyone else who's tried similar - I've never put messages on the keypads before.
 
And with this, if you clear one troubled door while another is open, it'll wait until the other closes before finally clearing the beeping/text - I don't see that as an issue for me but worth pointing out.
 
Work, looking through the rules I may have found something with the counter...
 
When the Garage Door and the Rear Slider are NOT SECURE you are adding 0 to the Doors Open counter. However, when those doors are closed you are subtracting one from that same counter. I'm not sure if that is on purpose, and if so how that works.
 
What I could see happening is... Front Door opens; Doors Open counter is incremented to 1. Garage door opens; Doors Open counter remains the same (you added 0). Garage Door is closed, Doors Open counter is decremented to 0 (subtracted 1)... but the front door is still open. The same could be done with the Rear Slider. Also, do the Elk counters support standard integers (that is, negative numbers as well)? If so, I could see where that counter could get to a -5 by opening and closing your Rear Slider (or Garage Door) 5x.
 
Good catch - simple mistake; I copy/pasted some rules and apparently copied the 0 as well.  I've edited the above so it shows correctly.  I have NOT had a good opportunity to test this yet but would love to hear from the OP if he's seen it.
 
I also missed something else earlier - look at your bottom 2 rules. They say: When X becomes NOT SECURE. Pretty sure you meant for both of those to read SECURE.
 
Back
Top