Cloud arming and site controls

Decide when a Site's alarm sources raise alarms with arming groups, entry and exit delays, schedules, force-arm, and bypass, and switch site outputs from Monitor.

Last reviewed Print view kalytera-cloud arming site-controls entry-delay exit-delay bypass outputs io
Contents

Cloud arming decides when a Site's alarm sources raise alarms in Kalytera Cloud, for example only at night or while a building is empty. It does not arm or disarm a physical alarm panel, and safety signals stay active. Arming is set up per Site by a tenant administrator and operated from Monitor.

Create an arming group

  1. Open the Site's workspace under Sites and go to Cloud arming.
  2. Set the Site time zone and select Save time zone. Schedules use it.
  3. Select Add group and enter a Group name.
  4. Under What arms this group?, choose one:
    • Operator arm / disarm: operators arm and disarm it in Monitor, and a weekly schedule can do it for them;
    • Key switch or Push button: an I/O input at the Site;
    • Alarm panel areas: the group follows areas of the Site's panels. Part set never counts as armed, and Cloud only reads the panel.

Choose the sources

Select Add or change sources. Sources include I/O inputs, a Camera trigger, Camera analytic rules, an Email input, and a Panel point. For each one, choose:

  • Follows arming groups, for an ordinary door or camera alarm, which then raises alarms only while its group is armed; or
  • Always active — safety or other essential signal, for fire, duress, tamper, and health signals, which must stay always active.

Entry and exit delays

A group that is not controlled by a key switch or panel areas can have an Exit delay (seconds) and an Entry delay (seconds), each from 0 to 300; 0 means none.

  • After arming, the group shows Arming… for the exit delay, and alarms meanwhile don't count.
  • Tick Allow time to disarm when entering here on an entrance source, such as the front-door contact. When it triggers while the group is armed, the group's alarms wait for the entry delay. Disarm before it ends and they are dropped; otherwise they are raised.

Schedules and alerts

A Weekly schedule arms the group during its periods and disarms it outside them. Under Alerts about arming, choose Off, Notify, or Alarm for:

  • Failed to arm: the schedule expects the group armed, and it is still not armed after a grace time of 1 to 240 minutes;
  • Disarmed outside schedule: it was disarmed while its schedule says armed.

Arming control lost is always an alarm: if a controlling switch or panel stops reporting, the group keeps its last confirmed state until it reports again. Arming history lists every change, and Export CSV downloads it.

Lights and sounds that follow arming

A group can drive up to four outputs: On while armed, such as a lamp, or Pulse when armed and Pulse when disarmed, such as a short beep.

Arm and disarm from Monitor

In Monitor, Site controls shows each group's state, such as Armed or Disarmed, and offers:

  • Arm and Disarm. Before arming, Cloud checks the group's sources; an open door or an offline camera stops the arming.
  • Force-arm, to arm anyway: the sources that were not ready are bypassed until the next disarm.
  • Bypass, to leave one source out for a set time or until the next disarm. Its alarms are recorded but don't count. End bypass stops it early.
  • Override…, to set the state against the schedule or key switch until a time you choose, and Cancel override to end it.

Each action needs its permission under People & access > Site controls and arming: Arm or disarm Cloud alarm handling, Disarm panels and Cloud alarm handling, Force-arm Cloud alarm handling, and Bypass Cloud arming sources.

Site outputs

The Site's I/O devices section adds supported Axis inputs, outputs, and speakers, reached directly or through a Bridge Agent at the Site. People with Operate site outputs can turn an output on or off, or pulse it for a set number of seconds, from Site controls. A system rule can also switch outputs; see Alarms and incidents.

Cloud times a pulse. If the server or the site's connection is down when it should end, the output stays on until the connection comes back. For a door strike, use a strike with its own relock timer.