[Config Support]: New Frigate Setup with Reolink Cameras #22458
-
Config review and general adviceHi, First time setting up frigate- using a compose stack on my truenas server and integrated with HA. Doorbell: Video Doorbell Camera with Chime I couldn't seem to get h265 working at all, it seems like even connecting directly to the camera via webpage or via VLC I had different issues depending on what I tried. Some streams had no audio, some had no video, some didn't load at all etc. Ideally, saving some space on my nas with h265 would be decent. If there is anything else I should look for or tweak, I'm definitely open to any and all feedback. Cheers in advance! Version0.17-0 Frigate config filemqtt:
host: xx.xx.xx.xx # Your HA IP
port: 1883
user: frigate # Same as Mosquitto
password: 'boo'
topic_prefix: frigate
ffmpeg:
hwaccel_args: preset-intel-qsv-h264
input_args: preset-http-reolink
output_args:
record: preset-record-generic-audio-aac
detectors:
onnx:
type: onnx
model:
path: /models/yolox_tiny.onnx
model_type: yolox
width: 416
height: 416
input_tensor: nchw
input_dtype: float_denorm
labelmap_path: /models/labelmap.txt
record:
enabled: true
motion:
days: 7
alerts:
retain:
days: 30
mode: motion
detections:
retain:
days: 30
mode: motion
snapshots:
enabled: true
timestamp: true
bounding_box: true
retain:
default: 30
required_zones: [] # ensure not filtering out
detect:
enabled: true
width: 640
height: 480
fps: 10
objects:
track:
- person
- car
semantic_search:
enabled: true
model_size: small
face_recognition:
enabled: true
model_size: large
min_area: 800
detection_threshold: 0.5
recognition_threshold: 0.7
unknown_score: 0.8
min_faces: 1
blur_confidence_filter: true
lpr:
enabled: false
classification:
bird:
enabled: false
go2rtc:
streams:
Doorbell:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=frigate&password=password#video=copy#audio=copy#audio=opus
Doorbell_sub:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=frigate&password=password
Driveway:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=frigate&password=password#video=copy#audio=copy#audio=opus
Driveway_sub:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=frigate&password=password
Deck:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=frigate&password=password#video=copy#audio=copy#audio=opus
Deck_sub:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=frigate&password=password
Back:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=frigate&password=password#video=copy#audio=copy#audio=opus
Back_sub:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=frigate&password=password
Side:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=frigate&password=password#video=copy#audio=copy#audio=opus
Side_sub:
- ffmpeg:http://xx.xx.xx.xx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=frigate&password=password
cameras:
Doorbell:
audio:
enabled: true
ffmpeg:
inputs:
# High quality stream for recording
- path: rtsp://127.0.0.1:8554/Doorbell?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- record
- audio
# Low resolution stream for object detection
- path: rtsp://127.0.0.1:8554/Doorbell_sub?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- detect
Driveway:
audio:
enabled: true
ffmpeg:
inputs:
# High quality stream for recording
- path: rtsp://127.0.0.1:8554/Driveway?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- record
- audio
# Low resolution stream for object detection
- path: rtsp://127.0.0.1:8554/Driveway_sub?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- detect
Deck:
audio:
enabled: true
ffmpeg:
inputs:
# High quality stream for recording
- path: rtsp://127.0.0.1:8554/Deck?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- record
- audio
# Low resolution stream for object detection
- path: rtsp://127.0.0.1:8554/Deck_sub?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- detect
Back:
audio:
enabled: true
ffmpeg:
inputs:
# High quality stream for recording
- path: rtsp://127.0.0.1:8554/Back?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- record
- audio
# Low resolution stream for object detection
- path: rtsp://127.0.0.1:8554/Back_sub?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- detect
Side:
audio:
enabled: true
ffmpeg:
inputs:
# High quality stream for recording
- path: rtsp://127.0.0.1:8554/Side?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- record
- audio
# Low resolution stream for object detection
- path: rtsp://127.0.0.1:8554/Side_sub?audio&video
input_args: preset-rtsp-restream-low-latency
roles:
- detect
version: 0.17-0Relevant Frigate log outputN/ARelevant go2rtc log outputN/AFrigate statsN/AOperating systemDebian Install methodDocker Compose docker-compose file or Docker CLI commandname: frigate
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
cap_add:
- CAP_PERFMON
restart: unless-stopped
stop_grace_period: 15s # allow enough time to shut down the various services
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "512mb" # update for your cameras based on calculation above
devices:
- /dev/dri:/dev/dri # Intel GPU
volumes:
- /etc/localtime:/etc/localtime:ro
- /mnt/data/containers/frigate/config:/config
- /mnt/data/containers/frigate/storage:/media/frigate
- /mnt/data/containers/frigate/models:/models
- type: tmpfs # 1GB In-memory filesystem for recording segment storage
target: /tmp/cache
tmpfs:
size: 1000000000
networks:
lan:
ipv4_address: xx.xx.xx.xx
networks:
lan:
external: trueObject DetectorOpenVino Screenshots of the Frigate UI's System metrics pagesN/A Any other information that may be helpfulN/A |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
Your config looks solid overall for a first-time setup with Reolink cameras. Here are some observations and recommendations: What Looks Good
RecommendationsCamera Settings: For better performance with Reolink cameras, configure these settings on the camera itself if available:
H.265 Considerations: For cameras 5MP or lower (like your RLC-510A models), the recommended stream type is http-flv with H.264, which you're already using.(1) For 6MP or higher cameras (like your RLC-811A), using H.265 with http-flv requires ffmpeg 8.0 for the new http-flv-enhanced format, or you can use RTSP instead.(1) If you want to try H.265 for storage savings on your RLC-811A (Driveway camera), you would need to ensure you're using ffmpeg 8.0 and change the hwaccel preset accordingly. However, sticking with H.264 is a perfectly valid and stable approach. Input Args: You have Detect Resolution: Your detect settings of 640x480 at 10fps are reasonable. The recommended fps is 5, so you could reduce this to save CPU cycles if detection is working well.(3) detect:
enabled: true
fps: 5Your current configuration should work well as-is. The main decision is whether the storage savings from H.265 are worth the additional complexity of getting it working reliably. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
I've updated my config as per the above. |
Beta Was this translation helpful? Give feedback.
-
H.265 ConfigurationFor 6MP or higher Reolink cameras, using H.265 with http-flv requires ffmpeg 8.0 for the new http-flv-enhanced format, or you can use RTSP instead.(1) To enable ffmpeg 8.0, set the ffmpeg path in your config: ffmpeg:
path: "7.0"You can set this to For H.265 hardware acceleration, you would change the hwaccel preset accordingly (e.g., Two-Way Talk for DoorbellTo enable two-way talk for your Reolink doorbell, you need to add a secondary RTSP stream to your go2rtc config. The http-flv stream should still be used for stability, but a secondary RTSP stream enables two-way audio:(1) go2rtc:
streams:
Doorbell:
- "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=username&password=password#video=copy#audio=copy#audio=opus"
- "rtsp://username:password@reolink_ip/Preview_01_sub"
Doorbell_sub:
- "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=username&password=password"
- "rtsp://username:password@reolink_ip/Preview_01_sub"The RTSP stream cannot be prefixed with Additional requirements for two-way talk:(4)
go2rtc:
streams:
Doorbell: ...
webrtc:
candidates:
- 192.168.1.10:8555
- stun:8555📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'm using a custom ffmpeg 8 version now for h.265 http-flv support. Docker Compose: Frigate Config: |
Beta Was this translation helpful? Give feedback.
-
|
Your updated configuration looks well-structured. Here are some observations: What Looks Good
RecommendationsDocker Compose: Your device mappings look correct for the USB Coral. The standard mapping is: devices:
- /dev/bus/usb:/dev/bus/usbAudio Role Placement: You've moved the Enrichments Note: Since you have semantic search and face recognition enabled, be aware that the Google Coral is a TPU and does not provide acceleration for enrichments like semantic search or face recognition—those run on CPU or GPU. Your Intel GPU (via VAAPI) should automatically be used for enrichments since OpenVINO will be detected in the default Frigate image. shm-size Calculation: With 5 cameras detecting at 640x480 (and one at 640x360), your 512MB shm-size should be sufficient. The formula is based on detect resolution, and the default 128MB is fine for 2 cameras at 720p. The configuration looks solid for your setup with the custom ffmpeg 8, Coral TPU, and VAAPI hardware acceleration. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
Your updated configuration looks well-structured. Here are some observations:
What Looks Good
USB Coral TPU setup is correct with
type: edgetpuanddevice: usb(1)
go2rtc streams are properly configured with the http-flv format and the secondary RTSP stream for two-way talk on the Doorbell
(2)
Audio detection is enabled globally with a custom listen list, which is valid
(3)
WebRTC candidates are configured for two-way talk support
(2)
Using the sub stream for both
detectandaudioroles is a good approach to reduce connections(2)
Recommendations
Docker Compose: Your device mappings look correct for the USB Coral. The standard mapping is:
(…