[Config Support]: No recording for detection events (only preview) and they vanish after an hour #13653
-
Describe the problem you are havingI am opening this as a support question as it’s probably due to a misconfiguration. So have two zones defined on my cameras that restrict the alerts. Those are properly recorded and available. However, detections (so car and persons outside of the required zones) are displayed with their counts in the UI, but:
I looked for other issues and it seems that people can view those detections events similarly to alerts and they are stored as such, which is what make me think the issue is more on my configuration side. Version0.14.1-f4f3cfa Frigate config filemqtt:
host: core-mosquitto
user: REDACTED
password: REDACTED
detectors:
coral:
type: edgetpu
device: usb
# Force correct driver for hw acceleration (it will pick iHD otherwise)
environment_vars:
LIBVA_DRIVER_NAME: i965
ffmpeg:
hwaccel_args: preset-vaapi
detect:
enabled: true
width: 896
height: 672
review:
alerts:
required_zones:
- detection_zone
- car_zone
record:
enabled: true
objects:
track:
- person
- car
filters:
person:
threshold: 0.7
min_score: 0.5
car:
threshold: 0.7
min_score: 0.5
go2rtc:
streams:
mirador1:
- ffmpeg:http://192.168.1.100/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=REDACTED&password=REDACTED#video=copy#audio=copy#audio=opus
mirador1_sub:
- ffmpeg:http://192.168.1.100/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=REDACTED&password=REDACTED
mirador2:
- ffmpeg:http://192.168.1.101/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=REDACTED&password=REDACTED#video=copy#audio=copy#audio=opus
mirador2_sub:
- ffmpeg:http://192.168.1.101/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=REDACTED&password=REDACTED
cameras:
mirador1:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/mirador1
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/mirador1_sub
input_args: preset-rtsp-restream
roles:
- detect
motion:
mask: 0.994,0.982,0.994,0.946,0.577,0.946,0.577,0.982
zones:
detection_zone:
coordinates: 348,210,616,121,896,232,896,672,0,672,0,204
objects:
- person
car_zone:
coordinates: 0.392,0.329,0.633,0.213,0.996,0.412,0.996,1,0.327,0.36
objects: car
inertia: 3
loitering_time: 0
portillon_zone:
coordinates: 0.282,0.385,0.384,0.497,0.552,0.397,0.427,0.293
objects: person
inertia: 3
loitering_time: 0
mqtt:
# Restrict where to publish snapshot via mqtt for camera
required_zones:
- detection_zone
- car_zone
mirador2:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/mirador2
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/mirador2_sub
input_args: preset-rtsp-restream
roles:
- detect
motion:
mask: 0.994,0.982,0.994,0.946,0.577,0.946,0.577,0.982
zones:
detection_zone:
coordinates: 0.152,0.333,0.432,0.121,0.619,0.254,0.866,0.058,1,0.135,1,1,0,1,0,0.348
objects: person
inertia: 3
loitering_time: 0
car_zone:
coordinates: 0.098,0.366,0.402,0.14,0.654,0.345,0.337,0.674
objects: car
inertia: 3
loitering_time: 0
portillon_zone:
coordinates: 0.273,0.394,0.163,0.482,0.095,0.372,0.183,0.299
objects: person
inertia: 3
loitering_time: 0
mqtt:
# Restrict where to publish snapshot via mqtt for camera
required_zones:
- detection_zone
- car_zone
version: 0.14Relevant Frigate log outputI did not have any error/warning logs at this time around. I’m happy to provide further logs in debug if needed.Relevant go2rtc log outputdittoFrigate statsNo response Operating systemHassOS Install methodHassOS Addon Object DetectorCoral Screenshots of the Frigate UI's System metrics pagesAny other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
this is working as expected because, since you added required zones to alerts, only those are considered "events". This is of course confusing, so in the next version of Frigate the recording config will be refactored so you can configure how long to retain alerts and detections specifically. For now, you can enable continuous recording with the mode as active_objects to record detetions |
Beta Was this translation helpful? Give feedback.

this is working as expected because, since you added required zones to alerts, only those are considered "events". This is of course confusing, so in the next version of Frigate the recording config will be refactored so you can configure how long to retain alerts and detections specifically.
For now, you can enable continuous recording with the mode as active_objects to record detetions