Turn Off Strobe when Alarm Cuts Off

[video321]

I have this rule that works:
WHENEVER ANY ALARM, ANY AREA TURNS ON
THEN TURN Strobe (Out 3) ON

but this rule doesn't work:
WHENEVER ANY ALARM, ANY AREA CUTS OFF
THEN TURN Strobe (Out 3) OFF

Any idea why that won't turn the strobe off? It turns off when I disarm the system. I didn't want to put a set time there as I wanted it to follow the cutoff timers. How can I make this work?

 

[rfdesq]

Are you using two separate rules or trying to combine them into one rule?

 

[video321]

2 rules

 

[rfdesq]

And you are waiting for the alarm to cut off and it still doesn't turn off output 3?

 

[video321]

And you are waiting for the alarm to cut off and it still doesn't turn off output 3?

Correct.

 

[rfdesq]

I'm still pondering. And while I'm pondering, let me tell you what I do. I set my strobes to turn on for 10 hours if any alarm goes off. That way the strobe is a visual reminder that the alarm went off and you should approach the premises with caution. Having the strobe stay on well after the alarm times out also gives the police helicopter a visual clue. When I disarm the area the strobe goes off. Not a solution right now to your problem but it will keep you safer.

 

[video321]

I appreciate the tip, but I use remotes that are programmed to NOT disarm the house and open the garage door, but rather chirp the siren and flash the strobe whenever a burglar alarm condition occured and we didn't get a notice.

What I didn't want to do was have a rule burned for each type of alarm condition to set the strobe time. I want my fire alarm strobe to stay on for a long time following the cutoff timer, but I also want my water alarm strobe that is only a few seconds to cutoff right away as well.


Is this possible?
Does "cuts off" in the rules actually mean "disarm" and NOT the "cutoff timer"?

 

[rfdesq]

I would need to modify my test panel setup to test the scenarios. If Spanky sees this thread I think you'll get your answer faster.

 

[video321]

I would need to modify my test panel setup to test the scenarios.

I'd definitely appreciate that!

 

[wuench]

You could try turning on a phantom output for x minutes when the alarm/strobe is triggered and then a second rule to turn off the strobe when the phantom output turns off.

 

[video321]

You could try turning on a phantom output for x minutes when the alarm/strobe is triggered and then a second rule to turn off the strobe when the phantom output turns off.

True, but that would just mean stacking rules in which case I might as well just use a set time for each type of alarm.

Does nobody use the cutoff rule to know it's true effect?
What rules do you guys use with your strobes?

 

[video321]

Brad from Elk gave me something to try and it works:

whenever (out 2) is turned on
then turn strobe on

whenever (out 2) is turned off
then turn strobe off

something interesting...even though out 2 is on a delay the strobe activates immediately upon alarm.

 

[rfdesq]

Still doesn't answer the question as to why your rule didn't work.

 

[video321]

Still doesn't answer the question as to why your rule didn't work.

My thought exactly :unsure:

 

[gatchel]

I believe there was/is a bug with turning on and off outputs. The issue was related to turning an output on for a "time" and then expecting it to turn off after that time. The fix was to use a phantom (unused) output (100) and have 2 rules to really perform the function of one rule. Maybe it is related, maybe it's not. Only the release notes or ELk can answer this one. Maybe we'll hear from someone in the know as to why your solution didn't work the 1st time. It would be nice...