Elk M1 - Invalid or incomplete disarm code entered and system sounds alarm instantly

[mkmcgregor]

Is there a setting that I cannot find that does not instantly activate the burglar alarm state when a single invalid or incomplete code is entered? I originally thought it was just a timeout issue, but last time this happened there were 51 seconds left on the countdown and its repeatable. One of the button presses simply did not register. I waited the typical 2-5 seconds for the system to end the tone of entry detected. Instead, the system then went into Burglar Alarm mode with siren within 2 seconds. There has to be some sort of counter for this, or does this need to manually programmed into a rule keeping count of failures? I've searched the RP settings and none address this.
 
Any help or insight would be appreciated.

 

[mkmcgregor]

Actually, it's not completely repeatable. Just tried to set the alarm and repeat the entry method that has caused it in the past, and I had no success. I will have to get more info on the exact steps; if possible.
 
Still, any suggestions or input would be appreciated!

 

[drvnbysound]

There is a Global setting in ElkRP that is for the number of [incorrect] keystrokes before lockout. I'm not able to access ElkRP at the moment, so I can't provide any additional information regarding where it is found.

 

[mkmcgregor]

Yes, I did find that, but it's set at 99 (disabled, values 13-99). Reading the description it will not trigger an alarm, but prevent further keyboard access for a period of time; one minute. Maybe it does more if anyone knows differently.

 

[drvnbysound]

What version of firmware is your M1G running?

 

[mkmcgregor]

Latest of which I'm aware; just checked this morning for updates:
 
Boot: 3.3.6
Firmware: 5.3.0
 

 

[drvnbysound]

Nothing that I'm aware of... then again, if I've ever mis-keyed an entry, I've never waited. I just re-enter without delay.

 

[Del91574]

The Manual states * to clear any error or miskey. Are we sure that your time didn't expire? What zone generated the alarm (log)?
 
Did you happen to trip a follower or similar instant zone? Something has to be different than a simple miskey.
 
Have you looked at the KP FW? I believe there was a small FPN for a quirk discovered with old FW. though keypads haven't really changed in about 4-5 years.

 

[mkmcgregor]

Found the issue for the alarm tripping. It was NOT a code entry or reentry. Under my old alarm system, when a door was triggered all the motion sensors will no longer be active to trip the alarm. I have an additional motion sensor just beyond the door in a nearby room that can see part of the short entry hall beyond the door. The current configuration on the new ELK system considers those as instant trip; I programmed them as such without thinking. If I went to far into the hall without entering a code (e.g. to put down a bag or package), I would trigger the instant on alarm by my presence in the hall. My bad. Still learning some of the differences in the setup of the Elk and the implications for the different sensors.

 

[Del91574]

Change the ZT to interior follower. Investigate your programming further.