Arm Site For Testing

How long the site's cameras should stay on for testing, in minutes, even though the schedule has them off. 1-120; anything above 120 is a 422 here, so the service's clamp never fires through this API and the response's clamped is always false. The site's disarm_max_minutes deliberately does NOT apply.

The site whose cameras this concerns.

When the test window ends by itself and the cameras go back to their schedule. Ending a test early sets this to the moment it ended rather than nulling it, so the window that really happened stays readable historically — which means a non-null value does NOT mean 'armed for testing'. Read arm_active for that. Expiry is implicit; nothing sweeps this column.

When the current test window began. The resolver's predicate is the window between this and arm_until, so a historical read is not repainted by a test started later. An extend inside a live window keeps the original value.

Who started the test: always 'operator:<uuid>'. The console is the only channel into a test arm, so unlike disarm_by this never carries a customer's phone number. Retained after the window is closed early, alongside the closed window.

Whether this site's cameras are on FOR A TEST right now — the window predicate, resolved server-side. Always false on an end-arm response. Never derive this from arm_until.

Minutes actually applied, after clamping to the 120-minute product ceiling; null on an end-arm.

True when the request asked for longer than the arm's ceiling and was shortened. ALWAYS FALSE THROUGH THIS API TODAY: the request model refuses anything above 120 minutes and the arm clamps to that same ceiling only (never to the site's disarm_max_minutes). Kept for contract symmetry with DisarmStateResponse and so that a later decision to clamp arms to the site cap is not a contract change.

Live View only (site flag or every live camera individually flagged) reads 'live_view_only' and overrides both arm and disarm windows. Otherwise: Whether this site's cameras are being monitored RIGHT NOW, resolved server-side. A live test arm reads 'monitored' — it is not a fifth value; read arm_active to tell a test apart from the schedule doing it. 'disarmed' still wins over a test arm, though a successful arm cannot return it (the route refuses while a disarm is live). On an end-arm response this is what the SCHEDULE leaves behind, which is the whole point: ending a test on an off-schedule site reports 'off_schedule'.

The current schedule-only monitoring state, ignoring Live View only flags, the test arm and the disarm window. Resolved at the same instant as monitoring_now. This is what lets the console say 'on for a test; the schedule has this site off until 7:00 AM'.

The next instant this site's monitored/off state flips BY SCHEDULE ALONE — the test window is deliberately ignored, because you already have arm_until above. Null when nothing changes within 7 days and for an 'unscheduled' site. Aligned to a 15-minute boundary in the site's own timezone.