[Support]: Clips not being saved anymore

[filipcoja]

Checklist

• I have updated to the latest available Frigate version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.

Describe the problem you are having

My events and clips are being seen and saved (the snapshots work) since 3 days ago (16.08.2025) frigate suddenly stopped saving my recordings:

Steps to reproduce

Use my config

Version

0.16.0

In which browser(s) are you experiencing the issue with?

No response

Frigate config file

ffmpeg:
  hwaccel_args: preset-vaapi
mqtt:
  host: smart.cool.xyz
  user: testuser
  password: testuser
record:
  enabled: true
  retain:
    days: 7
    mode: motion
  alerts:
    retain:
      days: 30
      mode: all
  detections:
    retain:
      days: 30
      mode: all
snapshots:
  enabled: true
  retain:
    default: 30
cameras:
  door:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://admin@cam.cool.xyz:8554/stream0
          roles:
            - record

    motion:
      threshold: 30
      contour_area: 10
      improve_contrast: true
      mask: 0.023,0.029,0.023,0.073,0.285,0.072,0.284,0.034
    zones: {}
    review:
      alerts: {}
detectors:
  ov:
    type: openvino
    device: AUTO
model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  path: /openvino-model/ssdlite_mobilenet_v2.xml
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt
version: 0.16-0
semantic_search:
  enabled: true
  reindex: false
  model_size: small
go2rtc:
  webrtc:
    candidates:
      - 192.168.0.4:8555
      - stun:8555
  streams:
    door:
      - rtsp://admin@cam.cool.xyz:8554/stream0
      - ffmpeg:back#video=h264#hardware
detect:
  enabled: true

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    stop_grace_period: 30s # allow enough time to shut down the various services
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "256mb" # update for your cameras based on calculation above
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./config:/config
      - /mnt/recordings:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      # - "5000:5000" # Internal unauthenticated access. Expose carefully.
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
      - "1984:1984/udp"
      - "1984:1984"
    environment:
      FRIGATE_RTSP_PASSWORD: "12345!admin12345"

Relevant Frigate log output

there is not output - no errors

Relevant go2rtc log output

-

Operating system

Debian

Install method

Docker Compose

Network connection

Wired

Camera make and model

china off brand

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

This config worked prior to 16.8 without problems, snapshots are created any in my notifications i still see the snapshots, but the recordings are not saved anymore

[inkeep-ai-assistant[bot]]

Looking at your configuration, I can identify the issue. Your camera configuration only has the record role assigned to the RTSP stream, but you don't have the detect role configured for that camera(1).

According to the Frigate documentation, recording requires object detection to be enabled. In your config, you have detect: enabled: true globally, but your camera's ffmpeg input only specifies:

ffmpeg:
  inputs:
    - path: rtsp://admin@cam.cool.xyz:8554/stream0
      roles:
        - record

(1)

To fix this, you need to add the detect role to your camera input. Here's the corrected configuration:

ffmpeg:
  inputs:
    - path: rtsp://admin@cam.cool.xyz:8554/stream0
      roles:
        - record
        - detect

(1)

The documentation shows that both roles can be assigned to the same stream, as demonstrated in the configuration examples(1). Without the detect role, Frigate cannot perform motion detection, which is required for the recording functionality to work properly.

Additionally, make sure your camera has proper detect dimensions configured. You can add:

detect:
  width: 1280
  height: 720
  fps: 5

(1)

This should resolve your recording issue while maintaining your existing snapshot functionality.

📚 Sources:

1. Frigate Configuration

---

Have another question? Just tag @inkeep.

[filipcoja]

"If you only define one stream in your inputs and do not assign a detect role to it, Frigate will automatically assign it the detect role"

[NickM-27]

If recordings are not saved then there should be errors in logs

[filipcoja]

This worked like this in the 0.16.0 like I explained to you. But for your information - I also tried adding all and its still not working.

[hawkeye217]

I don't see anything in the logs of any concern so I'm not sure why it wouldn't be working.

[filipcoja]

its really weird, i tried resetting to a backup back in july and its also not working with new videos, something is odd

[filipcoja]

okay - reversed to a backup with version 0.15.2 - now everything is being recorded how I want.

BUT! it's still not the behaviour as it was since: A recording is only STARTED when there is just a little bit motion at the beginning. (it's enough motion when I open my door or someone rings on my door) but this is still not the behaviour as it was.

Oddly enough, the clips are ALWAYS 20 seconds, even if i specified 15s, also the clip is not limited by motion, it always records the whole 20s even if there is no motion, it just needs motion to start, very very very weird - at this point I'm going to give up and accept that it now only works like this, shouldnt be a big issue since when someone opens the door, there will be enough motion to start triggering the recording

[NickM-27]

What you are describing is always how Frigate has worked. Recordings are done in 10 second segments

[inkeep-ai-assistant[bot]]

Based on the error usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed, this appears to be an Intel GPU hardware acceleration driver issue that could be preventing recordings from being saved properly.

For Intel-based CPUs using hardware acceleration, the documentation shows that you need to ensure the correct driver is being used(1). The default driver is iHD, but you may need to change to the i965 driver by adding the environment variable LIBVA_DRIVER_NAME=i965 to your docker-compose file(1).

Here's how to add this to your docker-compose configuration:

services:
  frigate:
    container_name: frigate
    # ... your existing config ...
    environment:
      FRIGATE_RTSP_PASSWORD: "12345!admin12345"
      LIBVA_DRIVER_NAME: i965  # Add this line

(1)

The documentation also indicates that for Intel CPUs, different generations have different recommended configurations(1):

• gen1 - gen5: Use i965 driver with preset-vaapi
• gen6 - gen7: Use iHD driver with preset-vaapi
• gen8 - gen12: Use iHD driver with preset-vaapi
• gen13+: Use iHD or Xe driver with preset-intel-qsv-*

Since you're getting the iHD_drv_video.so init failed error, try switching to the i965 driver first. If that doesn't work, you could also try changing your hwaccel preset from preset-vaapi to a more specific Intel preset based on your CPU generation(1).

Additionally, ensure your /dev/dri/renderD128 device mapping is correct for your specific hardware setup(1).

📚 Sources:

1. Video Decoding

---

Have another question? Just tag @inkeep.