What events trigger alarms

Alarms are tenant-visible incidents. They are not the same as every camera motion event on the NVR. You decide which platform events should open an alarm.

Where to change this

Sign in → Settings → Alarm rules (wording may appear as device health / alarm rules). Owners and admins can edit. Changes apply to the tenant; some unit-level overrides exist for test mode.

Typical triggers

Depending on your plan and hardware, rules can include:

• Unit offline — field agent heartbeat stopped.
• Stale telemetry — the board is online but inverter / Cerbo / Solar Assistant data stopped (for example a stolen board moved to another network).
• Unauthorized movement — a deployed rental trailer’s GPS left the authorized baseline.
• Power / battery — low SOC or other health thresholds you enable.
• NVR / camera signals EyeOut is configured to ingest (not every Protect event by default).

Turn off rules that would page your on-call for noise. Turn on the ones you actually respond to.

Monitoring plans

How far an alarm goes depends on the unit’s monitoring mode:

• Basic — your team only (self-monitor).
• Standard — you first; EyeOut can fail over if you do not handle it.
• Advanced — EyeOut central monitoring (CMS) is in the path.

Dollar amounts and contract terms are set with sales. The dashboard shows the mode, not a public price list.

Test mode

A unit in test mode suppresses customer-facing escalation so you can pin, aim cameras, and pull telemetry without opening a real CMS case. Turn test mode off before the job goes live.

On-call

If you self-monitor, keep On-call current so SMS/voice has a real person. Empty on-call is why teams miss the first week of a job.

Related

• How to create a unit