As a relatively new owner of an Elk M1G system, I continue to discover features and behavior of the system that don't appear to be documented.
I noticed that when a zone with wiring type "3" (EOL Supervised with Security Alert on SHORT) or type "4" (EOL Supervised 4 State wiring with Security Alert on OPEN or SHORT) is programmed to be Force Armable, the Security Alert does not work.
For example, I have a motion detector with a tamper circuit wired as type 4 on a zone. In the disarmed state, when motion is detected, the alarm circuit opens and the keypad displays zone not ready. When I remove the cover of the detector or otherwise create a tamper condition, the tamper circuit opens and the keypad beeps with the Security Alert alarm. The event "1350 = Security (Day) Alert" is also logged. (In the armed state, either condition of course will create a burglary alarm.) This all works fine and as expected of this zone type.
However, because this particular motion detector covers an exit/entrance area with a keypad, I have set the zone to be definition 05 - Burglar Interior Follower and Force Armable. This would allow me to pass through this area and arm away while the motion detector sees me, and re-enter this area to disarm without causing a false alarm. Now when the zone is set to force armable, the Security Alert feature does not function when the tamper circuit is tripped; the keypad only displays the zone trouble, and no security alert event is recorded in the log. Furthermore, because this zone is now reporting "trouble" rather than not ready, the system will refuse to arm even though the zone is programmed to be "force armable." (Here I concur with the system not allowing any zone reporting trouble to be overlooked. But why doesn't the Security Alert function?) The manual doesn't seem to document this behavior or effect of force arm on an EOL Supervised Security Alert zone, and I wonder if anyone else is experiencing this too.
Separately, I also notice that when I un-check "Force armable" for a zone in ElkRP (v 2.0.8) and send the change to the control (v 5.2.4), the change does not seem to register, and I must reboot the whole system for the removal of force arm to take effect. Anyone notice this as well?
I noticed that when a zone with wiring type "3" (EOL Supervised with Security Alert on SHORT) or type "4" (EOL Supervised 4 State wiring with Security Alert on OPEN or SHORT) is programmed to be Force Armable, the Security Alert does not work.
For example, I have a motion detector with a tamper circuit wired as type 4 on a zone. In the disarmed state, when motion is detected, the alarm circuit opens and the keypad displays zone not ready. When I remove the cover of the detector or otherwise create a tamper condition, the tamper circuit opens and the keypad beeps with the Security Alert alarm. The event "1350 = Security (Day) Alert" is also logged. (In the armed state, either condition of course will create a burglary alarm.) This all works fine and as expected of this zone type.
However, because this particular motion detector covers an exit/entrance area with a keypad, I have set the zone to be definition 05 - Burglar Interior Follower and Force Armable. This would allow me to pass through this area and arm away while the motion detector sees me, and re-enter this area to disarm without causing a false alarm. Now when the zone is set to force armable, the Security Alert feature does not function when the tamper circuit is tripped; the keypad only displays the zone trouble, and no security alert event is recorded in the log. Furthermore, because this zone is now reporting "trouble" rather than not ready, the system will refuse to arm even though the zone is programmed to be "force armable." (Here I concur with the system not allowing any zone reporting trouble to be overlooked. But why doesn't the Security Alert function?) The manual doesn't seem to document this behavior or effect of force arm on an EOL Supervised Security Alert zone, and I wonder if anyone else is experiencing this too.
Separately, I also notice that when I un-check "Force armable" for a zone in ElkRP (v 2.0.8) and send the change to the control (v 5.2.4), the change does not seem to register, and I must reboot the whole system for the removal of force arm to take effect. Anyone notice this as well?