nulledy bb6e889449 Allow API Events to be Detections or Alerts, depending on the Event Label (#21923) ... * - API created events will be alerts OR detections, depending on the event label, defaulting to alerts - Indefinite API events will extend the recording segment until those events are ended - API event start time is the actual start time, instead of having a pre-buffer of record.event_pre_capture * Instead of checking for indefinite events on a camera before deciding if we should end the segment, only update last_detection_time and last_alert_time if frame_time is greater, which should have the same effect * Add the ability to set a pre_capture number of seconds when creating a manual event via the API. Default behavior unchanged * Remove unnecessary _publish_segment_start() call * Formatting * handle last_alert_time or last_detection_time being None when checking them against the frame_time * comment manual_info["label"].split(": ")[0] for clarity		2026-02-26 21:27:56 -07:00
..
__init__.py	Create ReviewSegment table in DB for organizing detections to be reviewed (#9918)	2024-02-20 16:26:09 -07:00
maintainer.py	Allow API Events to be Detections or Alerts, depending on the Event Label (#21923)	2026-02-26 21:27:56 -07:00
review.py	Require setting process priority for FrigateProcess (#19207)	2025-08-16 10:20:33 -05:00
types.py	Refactor event cleanup to consider review severity (#15415)	2024-12-09 08:25:45 -07:00