Alarm Types & Groups
Every alarm signal carries a CID code (e.g. E130 burglary, E120 panic, E302 low battery). The CleverCam Brain classifies each code into a behaviour pattern (A–L) that decides how the control room handles it. The Alarm Types & Groups admin lets you:
- name and group alarm codes for your own control room,
- override the behaviour pattern a code maps to — for the whole control room or for a single site, and
- set each code's Handling type, the alarm type an action plan is written against.
This replaces the old way of hand-editing a site's pattern map as raw JSON.
Open it from Settings → Alarm Handling → Alarm types.
The Alarm types sub-tab is only visible to super admins with Super Admin mode switched on (the toggle in the avatar menu, top right). The behaviour patterns it overrides are consumed by the CleverCam Brain, which today runs for a small number of control rooms — so pattern overrides are an advanced tool kept out of the way for everyday operators.
Behaviour patterns (A–L)
| Pattern | Meaning |
|---|---|
| A | Life-safety — panic / duress / fire / medical |
| B | Standard alarm (verified, no photo) |
| C | Alarm with photo (operator reviews the image first) |
| D | Tamper (alarm + service note) |
| E | Comms / power (long-wait, cluster-aware) |
| F | System trouble (tamper-indicator / maintenance) |
| G | Open / close (silent unless out-of-hours business) |
| H | Schedule / fail-to-arm (business-mode nudge) |
| I | Bypass (informational, silent) |
| J | Test / heartbeat (always silent) |
| K | Manual operator event |
| L | Restore pairing (silent closure) |
Each code has a default pattern shown in the table. Some codes (e.g. E130, E138, E139) are marked with * — their effective pattern depends on runtime context such as whether a photo is attached or the event is verified.
Handling type
Alongside the A–L pattern, every code carries a Handling type — the alarm type the Action Plans editor is written against. This is the CID → plan spine: a plan is set per handling type, so a code with — none — reaches no plan at all.
The Handling type column sits in the code table in both scopes and offers — none — plus: Panic, Duress, Fire, Medical, Environmental (leak / temp), Burglary, Tamper, AC mains failure, Comms failure, Hub / device offline, Low battery (system / panel), Low battery (wireless sensor), Sensor / device fault, Supervision / RF loss, Camera issue (video loss), Panel trouble (Ethernet / offline / shutdown), Opening (disarm), Closing (arm), Opening outside hours, Closing outside hours, Fail to arm, Test signal, Informational (log only).
Custom name, group and pattern override are yours alone. A Handling type change is not — it writes straight to the shared code registry and applies to every control room on the platform, whichever scope you happen to have selected. The page header in the app says so. Change one only when the code genuinely means that everywhere.
Opening (disarm) and Closing (arm) are what make the open/close action-plan types fire: E400, E401, E403, E407, E408, E409, E441, E442 and E456 are mapped to opening, and their R counterparts to closing. Opening outside hours and Closing outside hours have no codes mapped to them, so plans written on those two never match a signal — see Open / close.
Panel trouble (E351 Ethernet lost, E369 communicator offline, E414 system shutdown) and Informational (E359, E412, E458, E466, E520, E570, E626, E788, E901) were added on 2 September 2026. Both are Log only by default. Panel trouble is an ordinary technical type — raise it per site or per Mode on Action Plans when a business wants to hear about a lost Ethernet path, and its codes pair with their restores like any other fault. Informational has no routing control at all: those codes stay in the event log and never become an operator card. The same day E361 (communicator supply voltage low) joined Low battery (system / panel) and E323 joined Sensor / device fault. On 15 September 2026 E317 (communicator high temperature) joined Panel trouble. It is what an Olarm's own temperature flag lands as, so it is Log only by default too. Unlike the other Panel trouble codes it does not pair with its restore: if you raise Panel trouble to the Control room, an E317 card stays open until an operator closes it.
One source is special-cased. FinMon sends E466 / R466 when someone signs into or out of the MiAlarm phone app — the FinMon cloud generates it, not the panel — so on FinMon radios that pair is dropped at the door (since 10 September 2026): it shows in the hub's raw signal log as Log only and nowhere else. No event-log entry, no heartbeat credit for the panel, no customer push. Every other protocol's 466 keeps its Informational meaning.
Choosing a scope
At the top of the page, choose what you are editing:
| Scope | What you can edit | Stored on |
|---|---|---|
| VCR defaults | Custom name, group, and pattern override for each code | Your control room |
| Per-site overrides | Pattern override for each code | The selected site |
When the Brain handles an event it merges the two layers: per-site overrides win over VCR overrides, which win over the built-in default.
Handling type sits outside both. Its column is editable in either view, and either way the change is saved to the shared code registry for every control room — see Handling type above.
VCR defaults
- Select VCR defaults.
- For any code, optionally set:
- Custom name — what your control room calls this code.
- Group — a label to organise related codes (e.g. "Maintenance", "Perimeter").
- Pattern override — pick a pattern (A–L) to change how the Brain treats this code, or leave it on — default —.
- Click Save changes.
Custom names and groups are organisational — they help you find and reason about codes. The pattern override is the part that changes Brain behaviour.
Per-site overrides
- Select Per-site overrides and choose a site.
- Set a pattern override for any code you want this site to treat differently.
- Click Save changes.
A common example: promote E380 (sensor trouble, normally maintenance Pattern F) to B (standard alarm) for a high-security site so it surfaces to an operator instead of being logged quietly.
Finding codes
Use the search box (matches code, default name, your custom name, or group), the event-type dropdown, and the Only overridden toggle to narrow the list.
Every change is recorded in the company Audit trail — who changed which alarm-type setting, and when.