Fix frigate live view by capping detect FPS #204

Merged

eblume merged 1 commit from fix/frigate-detect-fps into main

2026-02-17 16:18:03 -08:00

eblume commented

2026-02-17 16:12:07 -08:00

Owner

Summary

Cap detect FPS to 2 to prevent recording segment backlog from ONNX inference bottleneck (~750ms/frame on ARM64 CPU)
Sync motion masks from live config (added second mask area)
Update driveway_entrance zone coordinates from live config
Add explicit alert labels [person, car] while keeping required_zones: [driveway_entrance]

Context

The "No frames have been received" error on the gablecam live view was caused by the detect stream falling behind — ONNX YOLO-NAS-s takes ~750ms per inference on ARM64 CPU, but the sub-stream sends 5 FPS. This caused recording segments to pile up and the ffmpeg watchdog to repeatedly kill/restart the process, creating gaps in the live view.

Test plan

Sync ArgoCD frigate app to branch and verify pod restarts cleanly
Check /api/stats — skipped_fps should drop significantly, process_fps should be close to 2
Verify live view at https://nvr.ops.eblu.me/#gablecam no longer shows "No frames" error
Verify detections and alerts still work in the driveway_entrance zone

🤖 Generated with Claude Code

## Summary - Cap detect FPS to 2 to prevent recording segment backlog from ONNX inference bottleneck (~750ms/frame on ARM64 CPU) - Sync motion masks from live config (added second mask area) - Update driveway_entrance zone coordinates from live config - Add explicit alert labels `[person, car]` while keeping `required_zones: [driveway_entrance]` ## Context The "No frames have been received" error on the gablecam live view was caused by the detect stream falling behind — ONNX YOLO-NAS-s takes ~750ms per inference on ARM64 CPU, but the sub-stream sends 5 FPS. This caused recording segments to pile up and the ffmpeg watchdog to repeatedly kill/restart the process, creating gaps in the live view. ## Test plan - [ ] Sync ArgoCD `frigate` app to branch and verify pod restarts cleanly - [ ] Check `/api/stats` — `skipped_fps` should drop significantly, `process_fps` should be close to 2 - [ ] Verify live view at https://nvr.ops.eblu.me/#gablecam no longer shows "No frames" error - [ ] Verify detections and alerts still work in the driveway_entrance zone 🤖 Generated with [Claude Code](https://claude.com/claude-code)

eblume added 1 commit

2026-02-17 16:12:07 -08:00

Fix frigate live view by capping detect FPS to 2 7d7762b5d5

ONNX inference on ARM64 CPU takes ~750ms/frame, causing the detect
stream to fall behind at 5 FPS. This caps detection at 2 FPS to prevent
recording segment backlog and ffmpeg watchdog restarts. Also syncs
motion masks, zone coordinates, and alert labels from the live config.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>