Alarms
Alarms is the log of every event the tenant's NVRs report: motion, video loss, alarm inputs, analytics, storage problems, and the NVRs going online and offline. It is newest first and updates live. Every role may read it; acknowledging alarms needs the Operator or Tenant admin role (Roles and permissions).
Sphere receives an NVR's events while it is connected to the NVR (NVRs). Events the NVR raises while disconnected, or while its connector is stopped, are not in the log.
The table
| Column | Shows |
|---|---|
| Time | When the NVR says the event happened. |
| Type | The event's name (below). Problems (video loss, tampering, storage, an NVR going offline) are highlighted. |
| State | Started and Ended for events with a duration (motion starts, then ends), Event for single events. |
| Source | The camera (a link that opens it live: Watch {camera} live) or the channel, and the NVR. |
| Status | Not acknowledged, or Acknowledged by who (hover for when). |
Alarms that arrive while the page is open appear at the top with a New badge, if they match the filters. Load older alarms at the bottom loads the next page.
Types
Sphere names the common Dahua event codes; any other code is shown as the NVR sends it.
| Code | Name |
|---|---|
VideoMotion | Motion detected |
VideoLoss | Video loss |
VideoBlind | Camera tampering (video blind) |
AlarmLocal | Alarm input |
CrossLineDetection | Tripwire crossed |
CrossRegionDetection | Intrusion (region crossed) |
StorageFailure | Storage failure |
StorageLowSpace | Storage low on space |
NVROnline | NVR online |
NVROffline | NVR offline |
NVROnline and NVROffline come from the connector: NVROffline when a
connected NVR that was online stops answering or refuses the sign-in,
NVROnline when it is back.
Filters
| Filter | Meaning |
|---|---|
| From, To | A time range. |
| NVR | One NVR, or All NVRs. |
| Camera | One camera, or All cameras. |
| Types | One or more types, or All types. Other code adds a code that is not in the list (for example FaceDetection) with Add. |
| Acknowledged | All, Not acknowledged or Acknowledged. |
Clear filters removes them all. The filters are part of the page's address, so a filtered log can be bookmarked or shared.
Acknowledging alarms
Acknowledging records that someone has seen an alarm: who and when. It does not change anything on the NVR, and alarms are never deleted by it.
- Tick alarms (or the box in the header, for all shown) and choose Acknowledge N alarms (at most 500 at a time).
- Acknowledge all up to now acknowledges every alarm until this moment, whatever the filters show, after a confirmation.
Other users' logs update at once.
From an alarm to the camera
Choose the camera in Source to watch it live, on its own page (Live view). To see what happened, open Playback for that camera and day and click the timeline at the alarm's time.
How long alarms are kept
The alarm log is kept for 365 days by default, the same for every
tenant (the server's setting SPHERE_RETENTION_ALARM_DAYS; alarms are
removed by whole months, so they stay up to a month longer). See
Running Entrosity Sphere → Retention.
The Overview page counts the last 24 hours' alarms and those not acknowledged (Overview); ends of events (Ended) are not counted as unacknowledged.