feat: Frigate NVR reverse engineering for edge gateway v2#13
feat: Frigate NVR reverse engineering for edge gateway v2#13Thanukamax wants to merge 1 commit intomainfrom
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closing as part of the CROW-B3 shutdown cleanup. This org is being frozen as a public archive, so unfinished, failing, or conflicted PRs are not being carried forward. |
Summary
Reverse engineer Frigate NVR (MIT licensed) to study and repurpose its architecture for CROW's edge gateway. Frigate's clean separation of stream handling, detection, and event management maps directly to cctv-cli's needs.
Continues from: #10 (
feat/gateway-v1— Edge Ingest Gateway CLI, Phases 0-6)Why Frigate
ffmpeg -i rtsp://callsOnvifMotionWatcherstubfrigate/ptz/onvif.py— integration patterns for our ONVIF motion gatingComponents to study
go2rtc(Go, MIT) — RTSP connection lifecycle, health monitoring, reconnect logicfrigate/detectors/— How detection results feed back into event systemfrigate/events/— Event state machine, cooldowns, zone logicfrigate/config.py— Multi-camera YAML config pattern (compare withstore.example.yaml)frigate/ptz/onvif.py— ONVIF integration for filling inOnvifMotionWatcherPlanned work
Skipped alternatives