M1Cloud - Not allowing zone bypass - ELK Products

M1Cloud – Not allowing zone bypass

M1 Support Forum M1Cloud – Not allowing zone bypass

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #10031
    Jason Roberts

      In the M1Gold – all zones are checked as Bypassable. All users have bypass privileges. However, the M1Cloud app does not allow any zone to be bypassed.

      Contacted the developer which was not helpful – he said “You normally would need to bypass the zone first before you arm. I think from memory, if you disarm the system it will un-bypass all the zones. What some people do is setup a rule so when a function key (Eg. F1) is pressed to bypass all zones.”

      Doesn’t make sense!

      Suggestions? Thank you.

      #10032
      Michael Burrell

        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

        #10043
        Jason Roberts

          Very helpful – thank you.

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.
        Scroll to Top