feat(doors): report selected doors' open time over a range #193

New issue

Open

opened 2026-09-30 15:26:06 +00:00 by gabogg · 0 comments

gabogg commented

2026-09-30 15:26:06 +00:00

Owner

Part of #187 — milestone: Focused operator and supervisor door operations.

Intended outcome

Let a Supervisor select a set of doors and a time interval and see how long those doors were open. The current Open Longest panel ranks doors open now; door_access_cycles and door_hardware_state_transitions provide historical inputs but have different meanings.
Manual status records from #191 appear separately from hardware-derived durations while rules for using them in calculations remain undecided.

Triage questions

Should the report show cumulative open time per door, longest opening, each opening interval, count of openings, or all of these? What is the primary answer the Supervisor needs?
What date/time range and timezone rules apply? How are openings crossing range boundaries, still-open doors, offline periods, missing closing events, and sensorless doors treated?
Should selection support individual doors, labels/groups, or saved lists? Are exports needed in the first release?
Which data source is authoritative for physical open time versus commanded REMAIN_OPEN state? What coverage/quality warning should appear when history is incomplete?
What future evidence and calculation rules, if any, would permit human-entered statuses from #191 to contribute to calculated open time? How should source changes within the interval be shown?

Ready-to-spec outcome

A precise duration formula, inclusion/quality rules, selection contract, and one worked example that can become an integration test.

Part of #187 — milestone: Focused operator and supervisor door operations. ## Intended outcome Let a Supervisor select a set of doors and a time interval and see how long those doors were open. The current Open Longest panel ranks doors open now; `door_access_cycles` and `door_hardware_state_transitions` provide historical inputs but have different meanings. Manual status records from #191 appear separately from hardware-derived durations while rules for using them in calculations remain undecided. ## Triage questions 1. Should the report show cumulative open time per door, longest opening, each opening interval, count of openings, or all of these? What is the primary answer the Supervisor needs? 2. What date/time range and timezone rules apply? How are openings crossing range boundaries, still-open doors, offline periods, missing closing events, and sensorless doors treated? 3. Should selection support individual doors, labels/groups, or saved lists? Are exports needed in the first release? 4. Which data source is authoritative for physical open time versus commanded REMAIN_OPEN state? What coverage/quality warning should appear when history is incomplete? 5. What future evidence and calculation rules, if any, would permit human-entered statuses from #191 to contribute to calculated open time? How should source changes within the interval be shown? ## Ready-to-spec outcome A precise duration formula, inclusion/quality rules, selection contract, and one worked example that can become an integration test.

gabogg added this to the Focused operator and supervisor door operations milestone

2026-09-30 15:26:06 +00:00

gabogg added the

needs-triage

label

2026-09-30 15:26:06 +00:00

gabogg referenced this issue

2026-09-30 15:26:53 +00:00

epic(ui): focus Operator on doors and alarms; introduce Supervisor workspace #187

~~gabogg referenced this issue 2026-09-30 16:03:57 +00:00~~

feat(supervisor): record manual status for existing doors #191