Camera Health

What you can build

• Rank a dead camera by the doors it watches

  A camera_offline event arrives from Verkada. The operator finds the doors that camera is linked to in Brivo and proposes a MaintainX work order with those doors listed first.

  With Verkada, Brivo Access, MaintainX

• Tell a dead port from a dead camera

  Before proposing a ticket for an Eagle Eye camera, it reads ifOperStatus on the switch port through SNMP. A port that is down makes the UpKeep ticket a network ticket, with the port named.

  With Eagle Eye Cloud VMS, SNMP, UpKeep

• Find recorders quietly losing days

  Each morning it compares device retention per camera in Verkada against the days you set and proposes a review list in Slack for the cameras that fall short.

  With Verkada, Slack

• Watch an XProtect estate through one channel

  Item status from the XProtect Events and State API turns into one Fiix work order per recording server or camera that drops, with a Teams notice linking the order.

  With Milestone XProtect, Fiix, Microsoft Teams

Requirements

• One video platform connector: Verkada, Eagle Eye Cloud VMS, Rhombus, Milestone XProtect, or ONVIF devices reached through a gateway
• A door-to-camera map, read from Brivo or Avigilon Alta where cameras are linked to access points, or kept in a sheet
• One maintenance connector for work orders: MaintainX, UpKeep, or Fiix
• Optional: SNMP reach to the switches cameras hang off, or Datadog monitors on them, to tell a dead camera from a dead port

Authentication

Reads video and access platforms through the API keys or service accounts their connectors hold, and files work orders through the maintenance connector's credentials; it holds none of its own.

Limits

• It reports what the platform reports. A camera marked online with a frozen image is caught only if the platform raises tamper or inactivity
• Retention is read only where the API returns it, as Verkada's Get Camera Data does. Other platforms expose recording state, not days kept
• It never reboots, reconfigures, or swaps a camera. Restarts stay with the technician on the work order
• Ranking by doors depends on the camera-to-door links you keep. An unlinked camera ranks last, not first

Questions and answers

What does the approver see before a ticket is filed?

Every work order and notice. You see the camera, the event that triggered the proposal, the doors it covers, and the ticket text. Approve, edit, or dismiss it. Closing an order once the camera is back is a separate proposal.

What is kept after a camera is repaired?

A receipt per proposal: the platform event, the door ranking, who approved, what was written to the maintenance system, and how to undo it. Dismissed proposals are kept, so a camera that flaps every night is visible as a pattern.

Does it ever restart or change a camera on its own?

No. It reads status and events and writes only work orders and notices, each after approval. It never reboots a device, edits camera settings, changes retention, or touches the access platform.