Jason,
Thank you for reaching out and for the detailed description of what you’re seeing.
What you’re experiencing is actually the intended operation of the M1 system.
For security reasons, zones cannot be bypassed while the system is armed. Any zone bypassing must be performed while the system is in the disarmed state. This prevents someone from disabling protection points after the system has already been secured.
It is also correct that when the system is disarmed, any zones that were previously bypassed are automatically restored (un-bypassed). This behavior is intentional and designed to ensure that all protection points return to their normal, active state the next time the system is armed. In other words, bypassing is treated as a temporary condition for a specific arming cycle rather than a persistent configuration change.
Because of this design, the typical workflow is:
- Disarm the system
- Bypass any zones as needed
- Arm the system
If a specific zone needs to be bypassed regularly, installers can create a rule tied to a function key or event to perform a bypass while the system is armed. Since a rule is a custom action created by an installer, it does not adhere to the overall system requirements implemented by ELK. We recommend not having a rule that bypasses a zone when armed, but it is possible to do with rules.
So in short, the M1Cloud app behavior you’re seeing aligns with the panel’s security model and is consistent with how the M1 platform has always handled bypassing.
If you have any questions or concerns we would be happy to assist.
Thanks,
Mike