frigate-configurator
Configure Frigate NVR with optimized YAML, object detection, recording, zones, and hardware acceleration. Use when setting up Frigate cameras, troubleshooting detection issues, configuring Coral TPU/OpenVINO, or integrating with Home Assistant.
What this skill does
# Frigate NVR Configuration Expert
> Comprehensive Frigate NVR configuration assistance with optimized YAML generation, detector setup, and troubleshooting.
## BEFORE YOU START
**This skill prevents 12+ common errors and saves ~60% tokens on Frigate configuration.**
| Metric | Without Skill | With Skill |
|--------|--------------|------------|
| Setup Time | 2-4 hours | 30-45 min |
| Common Errors | 12+ | 0 |
| Token Usage | ~15,000 | ~6,000 |
### Known Issues This Skill Prevents
1. Bus errors from insufficient shared memory allocation
2. Green/distorted video from incorrect resolution configuration
3. Database locked errors when using network storage for SQLite
4. Missing audio in recordings due to default audio stripping
5. MQTT connection failures from using localhost in Docker
6. Coral TPU not detected due to missing device passthrough
7. High CPU usage from missing hardware acceleration
8. False positives from missing motion masks on timestamps
9. No alerts triggered due to misconfigured required_zones
10. Recording corruption from h265 streams without transcoding
11. go2rtc WebRTC failures from missing STUN configuration
12. Object detection misses from wrong detect stream resolution
## Quick Start
### Step 1: Create Minimal Configuration
```yaml
mqtt:
enabled: false
cameras:
front_door:
ffmpeg:
inputs:
- path: rtsp://user:[email protected]:554/stream1
roles:
- detect
detect:
width: 1280
height: 720
fps: 5
```
**Why this matters:** Start with the absolute minimum to verify camera connectivity before adding complexity. Frigate requires explicit detect stream role assignment.
### Step 2: Add Hardware-Accelerated Detector
```yaml
detectors:
coral:
type: edgetpu
device: usb
# OR for Intel with OpenVINO:
detectors:
ov:
type: openvino
device: GPU
```
**Why this matters:** CPU detection is not recommended for production. Even a single USB Coral TPU dramatically reduces CPU usage and improves detection latency.
### Step 3: Enable Recording with Retention
```yaml
record:
enabled: true
retain:
days: 1
mode: motion
alerts:
retain:
days: 14
detections:
retain:
days: 7
cameras:
front_door:
ffmpeg:
inputs:
- path: rtsp://user:[email protected]:554/stream1
roles:
- detect
- path: rtsp://user:[email protected]:554/stream2
roles:
- record
```
**Why this matters:** Use separate streams for detect (low-res) and record (high-res) to optimize performance. Retention modes prevent storage from filling up.
## Critical Rules
### Always Do
- Use `width` and `height` that match your camera's ACTUAL resolution (verify with VLC)
- Set `detect` fps between 5-10 (higher wastes resources, lower misses events)
- Use separate streams for `detect` (sub-stream) and `record` (main stream)
- Allocate adequate `shm-size` in Docker (64MB minimum per camera)
- Create motion masks for timestamp overlays and areas with constant motion
- Use environment variables for credentials: `{FRIGATE_RTSP_PASSWORD}`
- Test RTSP URLs in VLC first before adding to Frigate config
### Never Do
- Never use `localhost` or `127.0.0.1` for MQTT inside Docker containers
- Never set detect resolution higher than 1280x720 (wastes detector capacity)
- Never enable recording without specifying retention policy
- Never mount `/media/frigate` on network storage without relocating database
- Never mix multiple detector types for object detection (e.g., Coral + OpenVINO)
- Never use UDP RTSP transport without explicit configuration (TCP is default)
### Common Mistakes
**Wrong:**
```yaml
cameras:
cam1:
ffmpeg:
inputs:
- path: rtsp://192.168.1.100/stream
roles:
- detect
- record
detect:
width: 1920
height: 1080
fps: 30
```
**Correct:**
```yaml
cameras:
cam1:
ffmpeg:
inputs:
- path: rtsp://192.168.1.100/substream
roles:
- detect
- path: rtsp://192.168.1.100/mainstream
roles:
- record
detect:
width: 1280
height: 720
fps: 5
```
**Why:** Using 1080p@30fps for detection wastes resources. Detection works best at 720p or lower at 5fps. Always use the camera's sub-stream for detection and main stream for recording.
## Known Issues Prevention
| Issue | Root Cause | Solution |
|-------|-----------|----------|
| Bus Error | Insufficient shared memory | Set `shm-size: 256mb` in docker-compose |
| Database Locked | SQLite on network storage | Use `database.path: /config/frigate.db` |
| Green/Distorted Video | Wrong resolution in config | Match camera's actual output resolution |
| No Audio in Recordings | Default audio removal | Use `preset-record-generic-audio-aac` |
| MQTT Connection Failed | localhost in Docker | Use host IP address instead |
| Coral Not Detected | Missing device passthrough | Add `/dev/bus/usb` to Docker devices |
| High CPU Usage | Missing hwaccel | Add appropriate preset (vaapi/qsv/nvidia) |
| Missing Alerts | No required_zones | Configure zones with review.alerts.required_zones |
| UDP Stream Failures | TCP is default in Frigate | Add `preset-rtsp-udp` to input args |
## Configuration Reference
### config.yml Structure
```yaml
# MQTT Configuration (optional but recommended)
mqtt:
enabled: true
host: 192.168.1.50
port: 1883
user: "{FRIGATE_MQTT_USER}"
password: "{FRIGATE_MQTT_PASSWORD}"
# Detector Configuration
detectors:
coral:
type: edgetpu
device: usb # or pci for M.2/PCIe
# Global Object Settings
objects:
track:
- person
- car
- dog
- cat
filters:
person:
min_area: 5000
max_area: 100000
threshold: 0.7
# Recording Settings
record:
enabled: true
retain:
days: 1
mode: motion
alerts:
retain:
days: 14
detections:
retain:
days: 7
# Snapshot Settings
snapshots:
enabled: true
retain:
default: 7
# Camera Configuration
cameras:
front_door:
enabled: true
ffmpeg:
inputs:
- path: "rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.1.100:554/stream1"
input_args: preset-rtsp-restream
roles:
- detect
- path: "rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.1.100:554/stream0"
input_args: preset-rtsp-restream
roles:
- record
output_args:
record: preset-record-generic-audio-aac
detect:
width: 1280
height: 720
fps: 5
motion:
mask:
- 0,0,200,0,200,100,0,100 # Timestamp area
zones:
front_yard:
coordinates: 100,500,400,500,400,720,100,720
objects:
- person
- car
review:
alerts:
required_zones:
- front_yard
```
**Key settings:**
- `detect.fps`: 5 is optimal for most cameras (reduces detector load)
- `detect.width/height`: Must match actual camera sub-stream resolution
- `record.retain.mode`: Use `motion` or `active_objects` to save storage
- `motion.mask`: Define polygons as comma-separated coordinates
- `zones.coordinates`: Bottom-center of bounding box determines zone presence
## Hardware Acceleration Presets
### Intel (6th Gen+)
```yaml
# For Intel gen8+ (prefer QSV)
ffmpeg:
hwaccel_args: preset-intel-qsv-h264 # or preset-intel-qsv-h265
# For Intel gen1-gen7 (use VAAPI)
ffmpeg:
hwaccel_args: preset-vaapi
```
### NVIDIA GPU
```yaml
ffmpeg:
hwaccel_args: preset-nvidia
```
Requires NVIDIA Container Toolkit:
```yaml
# docker-compose.yml
services:
frigate:
runtime: nvidia
environment:
- NVIDIA_VISIBLE_DEVICES=all
```
### AMD GPU
```yaml
ffmpeg:
hwaccel_args: preset-vaapi
# docker-compose.yml
environment:
- LIBVA_DRIVER_NAME=radeonsi
```
### Raspberry Pi
```yaml
# Raspberry Pi 4/5
ffmpeg:
hwaccel_args: preset-rpi-64-h264 # or preset-rpi-64-h26Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.