Cloud arming and site controls
Decide when a Site's alarm sources raise alarms with arming groups, delays, schedules and alerts; arm, disarm, force-arm, override and command intrusion panels from Monitor; test panel zones; and switch site outputs and speakers.
Contents
Cloud arming decides when a Site's alarm sources raise alarms. It never arms or disarms a physical alarm panel by itself, and safety signals stay active. An administrator sets it up per Site; operators run it, and a Site's panels and outputs, from Monitor.
Permissions
Administrators have every arming and Site control permission. Give Operators and Supervisors the ones they need, such as Operate Site outputs, Arm Sites or Disarm Sites, with a role of your own: Roles and permissions lists them all.
The group for the whole Site
A new Site starts with one armed group, Whole site. Its new cameras, email routes and inputs that follow arming groups join it, never safety or health triggers, unless you clear New cameras, email routes and alarm inputs at this Site join this group in Edit setup > Advanced.
Create an arming group
- Under Sites, open the Site's Arming tab.
- Select + Add group, enter a Group name and select Create armed group.
- Select Edit setup and, under How it arms, choose Kalytera button, Wired input (a Key switch or Push button on an I/O input) or Alarm panel.
- Select Save group.
A new group starts Armed, and saving keeps its state. Sources are affected only once they follow the group.
Choose the sources
Under What it protects, select + Add: the Site's alarm sources are listed under Panel zones, I/O inputs, Camera alarms, Analytic rules and Email inputs. Tick what the group covers and select Save changes. Each source's alarm handling saves as you choose it:
- Not reviewed — stays active: the default; it always raises alarms;
- Always active: for fire, duress, tamper and health signals;
- Follows arming groups: alarms only while one of its groups is armed.
An I/O input must first be an alarm source, set in its device's Settings under Equipment > I/O devices.
Entry and exit delays
Kalytera button and push-button groups can have an Exit delay (seconds) and an Entry delay (seconds), 0 to 300. Alarms during the exit delay don't count. A source with Allow time to disarm when entering here, under Advanced: alarm handling and entry route, starts the entry delay; disarming in time drops its alarms.
Schedules and alerts
In Edit setup > Advanced > Schedule, choose a schedule from Schedules and holidays and select Save; this can arm or disarm at once. A key-switch or panel-area group has Expected arming times instead, which only drive alerts.
Under Alerts about arming, set Failed to arm and Disarmed outside schedule to Off, Notify (the alert's alarm-rule email or webhook only) or Alarm (also in Monitor and to the Site's alarm receiving centres), and select Save alerts. Arming control lost is always an alarm.
Arm and disarm from Monitor
Monitor's Site controls lists the Sites in the view with arming groups, panels or outputs, with operator actions only.
- Each group shows its state, who changed it and when, with Arm or Disarm. Force-arm bypasses unready sources until disarm or expiry; End bypass ends a bypass.
- Override until… sets a schedule group's state for 1 to 168 hours, until the schedule next changes, or until canceled; wired-input and panel groups have their own override. Cancel override ends it.
- Intrusion panels lists each panel's areas, then their zones, each in one state in the panel's words, such as Full set, Unset or Bypassed. Where Cloud may control the panel, an area offers Full set or Disarm and a zone Bypass or Unbypass, whichever changes the state.
Whether a panel command asks for a reason is set per command under Settings > Alarm rules > Panel command reasons: Off (the default), Optional or Required.
Test a panel zone
Test alarm on a zone, on its panel's page or in the Site's Alarm evidence, asks first; Run creates a [TEST] alarm with clips from the zone's saved evidence cameras and no external actions. Where offered, tick Also send it to the ARC as a test signal to have the alarm receiving centre file it as a test, never as a burglary.
Site outputs
Add a device under Equipment > I/O devices > Add device, directly or through a Bridge Agent: see Add an Axis I/O device to a Site. A speaker plays clips either way; talking needs a Bridge.
Use On or Off, whichever changes the output, Pulse or a speaker's clips. A pulse Timed by the device ends even if the connection drops; one Timed by Cloud stays on until it returns. Until a request reaches the Site, Cancel request withdraws it. Lights and sounds that follow arming, in Edit setup > Advanced, links up to four status outputs to a group.
Hold to talk talks through one speaker, one minute per press: hold and release, or click to start and again to stop. Speech is not recorded; each talk is audited.