Elk M1G Delays Immediate Automatic Arm

[TexTech]

A question for you M1G gurus... I've programmed my Elk M1 Gold to arm to night instant when function key F4 is activated on my M1KP2 keypad. I'm using the following rule:

WHENEVER KEY F4 ON KEYPAD1 ACTIVATES
		THEN ARM AREA(S) 1 TO NIGHT INSTANT IMMEDIATELY

This works exactly like I expected: when I press F4 twice, the control arms to night instant.

However, if I change the keypad settings to enable the "Require Code" option for F4, the control waits approximately one minute before arming. I edited the rule so that I could confirm the rule was activating:

WHENEVER KEY F4 ON KEYPAD1 ACTIVATES
		THEN DISPLAY "Arming to   night instant IN Home (Area 1) FOR 60 SECONDS, [*] CLEARS
		THEN ARM AREA(S) 1 TO NIGHT INSTANT IMMEDIATELY

With this modified rule, I confirmed that the rule is firing right away, but the arming is delayed. Here's precisely what happens:

- I press F4
- The keypad buzzes and displays AUTH REQUIRED
- I enter a valid code
- The keypad prompts me to press F4 again; I press F4 a second time
- The keypad displays the "Arming to night instant" message from my rule, but doesn't arm yet. The green READY light stays on
- Up to 60 seconds pass
- Finally, the control arms to night instant with the usual voice announcement and red ARMED light

The timing of the delay is precise: it waits until the start of the next minute.

Obviously, I'd like it to arm immediately when F4 is activated, even when I require a code. Anyone have an idea on this?

Thanks!

-Tex

 

[Del91574]

Your rule is doing exactly as it says, look at the ordering of the events in the rule.

Change the order or fire 2 rules, the first being the arming command, the second being the keypad text.

I'm not sure why I'd code protect an arming command, but to each their own.

 

[TexTech]

Your rule is doing exactly as it says, look at the ordering of the events in the rule.
Change the order or fire 2 rules, the first being the arming command, the second being the keypad text.
I'm not sure why I'd code protect an arming command, but to each their own.

No, that's not the issue. As I said, I only put in the keypad text message to troubleshoot the delay. When I take the display rule out altogether there is still a delay.

And as far as code protecting an arming command... I guess you don't have young kids.

Thanks for the idea anyway...

 

[tmbrown97]

And as far as code protecting an arming command... I guess you don't have young kids.

My youngest recently started climbing things so he could press the police dispatch button - repeatedly... Same reason some of my lighting scene buttons require a quick double-tap to activate, and a normal press or press/hold does nothing.

 

[wuench]

Is your exit timer 60 seconds? Maybe it's somehow using that and just not displaying it on the keypad. What about setting a rule up for "When Exit Timer Expires" And "Armed Night Instant" and have it say something just to test.

 

[TexTech]

Is your exit timer 60 seconds? Maybe it's somehow using that and just not displaying it on the keypad. What about setting a rule up for "When Exit Timer Expires" And "Armed Night Instant" and have it say something just to test.

Wuench:

I thought of that, but the behavior suggests the exit delay isn't involved here:

• When the function key isn't configured to require a code for activation, arming occurs immediately. Pressing F4 twice in this case causes the arming announcement, the red ARMED light illuminates, and the countdown begins and is shown on the keypad.
• When the function key is configured to require a code, the delay I observe isn't fixed to a particular value. Instead, the control waits until the system time rolls over to the next minute. Depending on when during the previous minute I activate F4, this could be anywhere from a few seconds to nearly 60 seconds. If it were a matter of the exit delay, I would expect the delay to be fixed to a particular value. Instead, it's always a delay that ends precisely at the beginning of the next minute. For instance, if I activate F4 at 15 seconds past 5:17 PM, the control doesn't arm until 5:18 PM, a delay of 45 seconds. If I activate F4 at 50 seconds past 7:20 PM, the control arms at 7:21 PM, a delay of 10 seconds.
• After the delay occurs and the control arms, the exit countdown displays on the keypad. My exit delay is set to 60 seconds. After the delay, the exit countdown starts at 60 seconds. So once the system finally arms, it starts the exit delay at that time.

Regards,
Tex