MyFavMirrors/moonfire-nvr
1
0
Fork 0
mirror of https://github.com/scottlamb/moonfire-nvr.git synced 2024-12-26 23:25:55 -05:00
Code Issues Packages Projects Releases Wiki Activity
5e00217784
moonfire-nvr/design/signal.md
Scott Lamb 42fe054d46
make GET /api/ return current permissions 
This is useful for e.g. deciding whether or not to present the user
admin UI in navigation.

As part of this change, I adjusted the casing in Permissions, and then
all the toml stuff for consistency. Noted in changelog.
2022-12-31 12:43:13 -05:00

1.2 KiB
Raw Blame History

Moonfire NVR Signals

Status: draft.

"Signals" are what Moonfire NVR uses to describe non-video timeseries data such as "was motion detected?" or "what mode was my burglar alarm in?" They are intended to be displayed in the UI with the video scrub bar to aid in finding a relevant portion of video.

Objective

Goals:

  • represent simple results of on-camera and on-NVR motion detection, e.g.: true, false, or unknown.
  • represent external signals such as burglar alarm state, e.g.: off, stay, away, alarm, or unknown.

Non-goals:

  • provide meaningful data when the NVR has inaccurate system time.
  • support internal state necessary for on-NVR motion detection. (This will be considered separately.)
  • support fine-grained outputs such as "what are the bounding boxes of all detected faces?", "what cells have motion?", audio volume, or audio spectograms.

Overview

hmm, two ideas:

  • just use timestamps everywhere. allow adding/updating historical data.
  • only allow updating the current open. initially, just support setting current time. then support extending from a previous request. no ability to fill in while NVR is down.