[Config Support]: expire_interval is being ignored #10611
-
Describe the problem you are havingI set the expire_interval for all my cameras to 4320 minutes, so 72 hours.
Version0.13.2-6476f8a Frigate config filemqtt:
enabled: True
host: 192.168.0.231
go2rtc:
streams:
reolink_cam:
- "ffmpeg:https://192.168.0.147/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=viewer&password={FRIGATE_RTSP_PASSWORD}#video=copy#audio=copy#audio=opus"
reolink_cam_sub:
- "ffmpeg:https://192.168.0.147/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=viewer&password={FRIGATE_RTSP_PASSWORD}"
reolink_doorbell:
- "ffmpeg:https://192.168.0.215/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=viewer&password={FRIGATE_RTSP_PASSWORD}#video=copy#audio=copy#audio=opus"
reolink_doorbell_sub:
- "ffmpeg:https://192.168.0.215/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=viewer&password={FRIGATE_RTSP_PASSWORD}"
detectors:
coral:
type: edgetpu
device: pci:0
birdseye:
enabled: False
cameras:
doorbell:
objects:
track:
- person
live:
stream_name: reolink_doorbell
record:
enabled: True
expire_interval: 4320
events:
retain:
default: 14
mode: active_objects
detect:
enabled: True
ffmpeg:
hwaccel_args: preset-vaapi
inputs:
- path: rtsp://127.0.0.1:8554/reolink_doorbell?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/reolink_doorbell_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detect
carport:
objects:
track:
- person
live:
stream_name: reolink_cam
record:
enabled: True
expire_interval: 4320
events:
retain:
default: 14
mode: active_objects
detect:
enabled: True
ffmpeg:
hwaccel_args: preset-vaapi
inputs:
- path: rtsp://127.0.0.1:8554/reolink_cam?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/reolink_cam_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detectRelevant log output2024-03-21 09:07:57.750912949 [INFO] Preparing Frigate...
2024-03-21 09:07:57.810285680 [INFO] Starting Frigate..
(...)
Deletion at 2024-03-22 13:09:17, not logged in frigate logs.Frigate statsNo response Operating systemUNRAID Install methodDocker CLI Coral versionPCIe Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 25 replies
-
|
it does not look like the parameter is being ignored, if it was then the default 60 minutes would be used. I also run unraid and using the disk activity plugin can see that my disks are spun down a majority of the time meaning the value does work as expected. if I had to guess, what is happening here is one of two things:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Did you ever get anywhere with this? I'm in the exact same boat, with Frigate regularly deleting clips - I've got a lot of space left on disk, and have configured the |
Beta Was this translation helpful? Give feedback.
-
Is there any benefit to this other than saving power by not spinning up a disk in the array? I have a HDD mounted exclusively for Frigate using Unassigned Devices and write everything other than my database to it. I can't imagine there's any concerns with speed even using HDDs, right? |
Beta Was this translation helpful? Give feedback.
-
|
Power usage, heat, and some wear and tear |
Beta Was this translation helpful? Give feedback.
-
Yea it runs every hour despite my expire-interval setting on 72 hours. |
Beta Was this translation helpful? Give feedback.
-
|
Oh I see the problem, you have it set at the camera level. You should be setting this at the global level |
Beta Was this translation helpful? Give feedback.
-
|
Will try that. |
Beta Was this translation helpful? Give feedback.
-
|
Proper configuration fixed this issue. |
Beta Was this translation helpful? Give feedback.
-
|
Having this same issue. Can you share what the fix was without having to read through the entire thread? Maybe the configuration too? Thanks in advance |
Beta Was this translation helpful? Give feedback.
-
|
The issue was that i didn't set the interval at the global level but at camera level. This was wrong apparently. My current configuration is ``mqtt: logger: go2rtc: detectors: birdseye: record: cameras: |
Beta Was this translation helpful? Give feedback.
-
|
For anyone else who stumbles across this "issue"; it's probably because you have configured It would be great if snapshots had a similar configuration for |
Beta Was this translation helpful? Give feedback.
-
|
I logged an issue for Feature Request: #14002 |
Beta Was this translation helpful? Give feedback.
-
|
Any update on this? |
Beta Was this translation helpful? Give feedback.
Oh I see the problem, you have it set at the camera level. You should be setting this at the global level