Skip to content

Dashboard and controls

Hemkesh R edited this page Nov 17, 2026 · 3 revisions

Dashboard and controls

This page describes v2.0.0-beta.1, including the scrolling Ask panel, Settings dialog and experimental identity retention. The dashboard GIF and screenshots use synthetic data. The legacy v1 Flask dashboard is a separate application.

Try the interactive dashboard before connecting a device. Explore incidents, ask a question for a scripted response, select a demo scenario, or open Features and use the public demo key. Everything in that demonstration is synthetic; it opens no camera and runs no model. The project website explains the system and the demo's boundaries.

Connect after setup

These commands use the tester package's default directories. Complete the installation guide first; replace <user> and <jetson> with your SSH account and device address.

In a workstation terminal, keep this tunnel running:

ssh -N -o ExitOnForwardFailure=yes -L 18090:127.0.0.1:18090 <user>@<jetson>

In a separate plain SSH shell on the Jetson:

bash ~/sentinel-beta/package/start.sh --device-artifacts ~/sentinel-beta-data/config/device-artifacts.json

The final START prompt is the camera-opening step. Earlier prompts can ask to close competing programs and prepare memory; each action is named before you authorize it. Model loading precedes the live view. The supplied launcher stops after at most 60 minutes once ready. Do not start competing workloads while it runs.

Open http://127.0.0.1:18090/dashboard on the workstation. The v2 server binds to the Jetson's loopback interface; the SSH tunnel provides remote access. It is not v1's Flask server on port 5000.

Panels

Panel What it shows
Live view Frames already captured by the runtime, with freshness and frame time; no second camera connection
Recognition Current matches, retained identity and uncertain/unrecognized states per track; an unknown result is not a stranger verdict
Incidents Recorded events, delivery status and links to details; snapshots appear only if enabled and present
Ask Visual questions answered by LFM3, or supported records questions answered from Sentinel's records
Health and alerts Component availability, monitoring state and notification outcomes
Settings Appearance and runtime feature controls, opened from the sidebar

The tester profile has snapshots and external notifications off. Incident details are read-only. Acknowledgment remains a CLI action while monitoring is stopped: sentinel incident ack --data-dir <runtime-db-directory> <incident-id>. See the incident workflow for the single-writer requirement.

Recognition and identity retention

With --identity-retention, an established identity can remain associated with the same continuously followed track life through degraded or briefly non-matching face evidence. The panel distinguishes a current match from retained identity and shows the basis and age.

Retention is bounded. Track discontinuity, ambiguous ownership, stale/offline video, a new stream epoch, disabling recognition, the time limit, sustained reliable contradiction or a conflicting identity can end it. A reused numeric track ID does not inherit the old identity. Matching thresholds and the underlying face votes are unchanged. The mode is opt-in, experimental and limited to validation runs; multi-person accuracy is unmeasured.

Ask about the live picture

The conversation scrolls inside its own bounded panel. While following the newest exchange it stays at the latest answer as the list resizes; reading earlier messages does not force you back down. The question box stays outside that scrolling list. Hover, focus or activate the ⓘ next to the heading for help.

There are two answer paths:

Example Answer source
“Is the door open?” / “Describe the visible room briefly.” The on-device LFM3 scene model, about the stated frame
“What happened in the last 10 minutes?” Bounded in-memory history and incident records, with coverage stated
“Who is in the room?” The tracker's recognition records, not visual identification by the model
“Were any alerts triggered?” Incidents and notification delivery records; these are reported separately

Only supported records-question patterns take the records path; this is not arbitrary database querying. History starts with each runtime, is bounded, and reports gaps rather than treating missing data as “nothing happened.”

  • Follow-ups carry the relevant question context. Earlier model answers are not treated as verified facts.
  • Analyse again can use the held picture or a new frame; the answer states which.
  • Automatic refresh is opt-in, one cycle at a time, and pauses when the page, camera or chat is unavailable.
  • Zoom crops a selected part of a held frame from its recorded pixels.
  • Scan visible room asks about four overlapping regions of one held frame, sequentially. It does not move the camera or inspect anything outside that picture.
  • Answers state frame provenance and can be historical, shortened or cancelled. Scene monitoring takes priority; memory and time limits still apply. Held pictures expire and are bounded in memory.

Chat is available only when the run's admission or validation configuration permits it. In this beta it remains a validation-run feature, not formally admitted. It cannot acknowledge incidents, change rules, run commands, control the camera or establish someone's identity.

Settings

Appearance changes light/dark theme, palette, density and display choices in the current browser. It does not switch runtime features.

Features pauses or resumes the lanes that this runtime started. Unlock it with the run's operator key. For the default tester installation, read the key privately from another Jetson SSH shell while the run is ready:

cat "$(ls -d ~/sentinel-beta-data/observe/obs-*/ | sort | tail -n 1)db/control-key"

The key is not shown automatically on the page and is deleted when the run stops. Do not share it. Controls keep their same-origin and page-token protections; opening or closing Settings changes no feature. A narrow screen uses a fitted, internally scrolling dialog. Keyboard focus, Escape and the close button are supported; focus returns to the opener. Polling preserves drafts and focused controls. A page reload locks feature controls again. Without JavaScript, settings remain in the page and runtime actions are unavailable.

Freshness and clean stop

If updates stop, the page displays NOT CURRENT. Old frames and answers must not be read as a current view.

  1. Press Ctrl-C once in the Jetson launch terminal.
  2. Wait for OBS_exit (up to about two minutes), then close the tunnel with Ctrl-C.
  3. If the launch terminal was lost, run bash ~/sentinel-beta/package/stop.sh on the Jetson.
  4. If a display manager stopped for the run did not return, use sudo systemctl start display-manager.

A clean observation is not a recognition, answer-quality or resource-validation pass.