eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/reference/services/frigate.md
Erich Blume 5f9b024b4a Add Apple Silicon ZMQ detector for Frigate (#206) 
## Summary

- New `frigate_detector` ansible role deploys the [apple-silicon-detector](https://github.com/frigate-nvr/apple-silicon-detector) as a LaunchAgent on indri
- Switches Frigate from ONNX CPU detector (~117ms) to ZMQ detector backed by CoreML/Neural Engine (~15ms)
- Removes detect FPS cap (no longer needed with fast inference)
- Updates Frigate docs and adds changelog fragment

## Deployment

### Phase 1: Deploy detector on indri (one-time setup + ansible)
```fish
ssh indri 'git clone https://github.com/frigate-nvr/apple-silicon-detector.git ~/code/3rd/apple-silicon-detector'
ssh indri 'cd ~/code/3rd/apple-silicon-detector && make install'
mise run provision-indri -- --tags frigate_detector --check --diff  # dry run
mise run provision-indri -- --tags frigate_detector                 # apply
ssh indri 'launchctl list mcquack.eblume.frigate-detector'          # verify running
ssh indri 'tail ~/Library/Logs/mcquack.frigate-detector.out.log'    # verify bound
```

### Phase 2: Test connectivity
```fish
kubectl --context=minikube-indri -n frigate exec deploy/frigate -- nc -vz host.minikube.internal 5555
```

### Phase 3: Deploy Frigate config (branch workflow)
```fish
argocd app set frigate --revision feature/frigate-zmq-detector && argocd app sync frigate
```

### Phase 4: Post-deploy checks
- [ ] Pod starts, no config errors
- [ ] `/api/stats` shows detector type zmq, inference_speed ~15ms
- [ ] detect_fps uncapped
- [ ] Recordings and MQTT events flowing
- [ ] After merge: `argocd app set frigate --revision main && argocd app sync frigate`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/206
2026-02-17 19:03:28 -08:00

3.1 KiB
Raw Blame History

title modified tags
Frigate 2026-02-17
service
surveillance

Frigate

Open-source network video recorder (NVR) with object detection. Runs cloud-free with all video stored locally on sifaka.

Quick Reference

Property Value
URL https://nvr.ops.eblu.me
Tailscale URL https://nvr.tail8d86e.ts.net
Namespace frigate
Image ghcr.io/blakeblackshear/frigate:0.17.0-rc2-standard-arm64
Upstream https://github.com/blakeblackshear/frigate
Manifests argocd/manifests/frigate/

Architecture

ReoLink Camera (GableCam)
    │ RTSP
    ▼
Frigate pod (minikube)
    ├── go2rtc         — RTSP restream proxy
    ├── FFmpeg          — stream decoding
    ├── ZMQ detector ──tcp://host.minikube.internal:5555──→ apple-silicon-detector
    │                                                        ├── CoreML / Neural Engine
    │                                                        └── LaunchAgent (mcquack.eblume.frigate-detector)
    ├── /media/frigate  — NFS recordings (sifaka)
    └── /db             — SQLite (local PVC)
        │
        └──→ MQTT (Mosquitto) → frigate-notify → ntfy → mobile

Cameras

Camera IP Location Objects Tracked
GableCam 192.168.1.159 Front gable person, car, dog, cat, bird

Camera credentials are stored in 1Password and synced via external-secrets to the frigate-camera Secret.

Detection

Object detection uses the apple-silicon-detector with a YOLOv9-m model (yolo-generic, 320x320), running natively on indri as a LaunchAgent (mcquack.eblume.frigate-detector). It communicates with Frigate via ZMQ over TCP (tcp://host.minikube.internal:5555), using CoreML with partial Neural Engine acceleration (~100-170ms inference). Model ONNX files are stored on the NFS volume at /media/frigate/models/.

Two zones are configured: driveway_entrance (triggers review alerts for person/car) and driveway (triggers review detections).

Retention

Type Duration Mode
Continuous recording 3 days all
Alert clips 30 days active objects
Detection clips 14 days motion
Snapshots 14 days —

Storage

Mount Backend Size
/media/frigate NFS PV on sifaka (/volume1/frigate) 2 Ti
/db Local PVC (frigate-database) SQLite
/dev/shm Memory-backed emptyDir 256 Mi

Alerting (frigate-notify)

A separate frigate-notify pod (ghcr.io/0x2142/frigate-notify:v0.3.5) subscribes to Frigate's MQTT events via Mosquitto and pushes alerts to ntfy on the frigate-alerts topic. Alert messages include action buttons linking back to the Frigate review UI.

Related