Camera Status
Camera problems surface in the Cameras & tamper section of the Health worklist. Each row is a site, not a single camera: it shows how many of the site's cameras have issues ("3 of 12 cameras with issues"), any streams with an active tamper condition, and the site's arm state.
What lands in Cameras & tamper
- Camera issues — streams whose status reports device offline or issue detected (connectivity loss, stream failure).
- Active tamper — streams with a suspected or confirmed tamper condition: Darkness, Blur, Scene shift, Obstruction or Flashlight. The row names each affected camera and its condition(s), e.g. "Driveway: Obstruction".
Use the Camera and Tamper issue chips in the toolbar to isolate either kind, or combine them with the age and area chips like any other filter.
Reading a row
| Part | Meaning |
|---|---|
| Site name | The affected site — click to open it on the Sites page |
| Description | "N of M cameras with issues", plus tampered cameras and their conditions |
cams metric | Healthy/total camera count, e.g. cams 9/12 |
| Arm pill | The site's current arm state |
Investigating
- Check whether the site's hub is also in an offline section — a hub offline takes every camera at the site down with it, so fix the hub first.
- Multiple cameras with issues at one site usually means the hub or site network, not the cameras.
- Tamper conditions on an armed site deserve priority — an obstructed or darkened camera on an armed site is a blind spot exactly when it matters.
- Report to your field team with the site and camera names.
info
Camera status monitoring is passive — CleverCommand reports what the detection pipeline sees. Fixing a camera needs field or remote configuration work by technicians or administrators.