Camera's keep recording, instead of record only when motion is detected

[herbkk]

Describe the problem you are having

I want to config Frigate in such a way that:

• recordings are only made/saved when a motion is detected
• objects are not identified
• only recordings with motion are saved for 30 days

Currently the recordings don't stop and are filling my disks with 24/7 recordings. What changes are needed to my config file?

Version

0.16.0-c2f8de9

Frigate config file

mqtt:
  enabled: false  # 

cameras:
  camera_schuur:
    ffmpeg:
      inputs:
        - path: rtsp://admin:xxx@192.168.2.20:88/videoMain
          roles:
            - record
        - path: rtsp://admin:xxx@192.168.2.20:88/videoSub
          roles:
            - detect
    detect:
      enabled: false  
    motion:
      enabled: true   
    record:
      enabled: true
      retain:
        days: 30      
        mode: motion

  camera_deurbel:
    ffmpeg:
      inputs:
        - path: rtsp://admin:xxx@192.168.2.22/Preview_01_main
          roles:
            - record
        - path: rtsp://admin:xxx@192.168.2.22/Preview_01_sub
          roles:
            - detect 
    detect:
      enabled: false
    motion:
      enabled: true
    record:
      enabled: true
      retain:
        days: 30
        mode: motion

  camera_oprit:
    ffmpeg:
      inputs:
        - path: rtsp://admin:xxx@192.168.2.21:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
          roles:
            - record
        - path: rtsp://admin:xxx@192.168.2.21:554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
          roles:
            - detect 
    detect:
      enabled: false
    motion:
      enabled: true
    record:
      enabled: true
      retain:
        days: 30
        mode: motion

snapshots:
  # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
  enabled: true

version: 0.16-0

Relevant Frigate log output

no relevant output available

Relevant go2rtc log output

no relevant output available

Frigate stats

no relevant output available

Operating system

Other

Install method

Docker Compose

docker-compose file or Docker CLI command

name: passionate_atsushi
services:
  frigate:
    cpu_shares: 90
    command: []
    container_name: frigate
    deploy:
      resources:
        limits:
          memory: 11725M
    environment:
      - FRIGATE_RTSP_PASSWORD=xxx
      - TZ=Europe/Berlin
    image: ghcr.io/blakeblackshear/frigate:stable
    labels:
      icon: https://icon.casaos.io/main/all/frigate.png
    ports:
      - target: 5000
        published: "5000"
        protocol: tcp
      - target: 8554
        published: "8554"
        protocol: tcp
      - target: 8555
        published: "8555"
        protocol: tcp
      - target: 8555
        published: "8555"
        protocol: udp
    privileged: true
    restart: unless-stopped
    shm_size: "1073741824"
    volumes:
      - type: bind
        source: /etc/localtime
        target: /etc/localtime:ro
      - type: bind
        source: /DATA/AppData/frigate/config
        target: /config
      - type: bind
        source: /DATA/AppData/frigate/media
        target: /media
    devices: []
    cap_add: []
    network_mode: bridge
x-casaos:
  author: self
  category: self
  hostname: ""
  icon: https://icon.casaos.io/main/all/frigate.png
  index: /
  is_uncontrolled: false
  port_map: "5000"
  scheme: http
  store_app_id: passionate_atsushi
  title:
    custom: ""
    en_us: frigate

Object Detector

CPU (no coral)

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

Your configuration is close, but there are a few important details to address to ensure Frigate only records when motion is detected, does not use object detection, and retains recordings with motion for 30 days:

1. Recording Only on Motion:
   Your use of retain.mode: motion is correct. This means only segments with detected motion are kept(1), (2).

2. Disabling Object Detection:
   Setting detect.enabled: false disables object detection, which matches your goal(1).

3. Motion Detection Must Be Enabled:
   You have motion.enabled: true, which is required for motion-based recording(1).

4. Why Continuous Recording Might Still Happen:
   If you see continuous recordings, verify that:

   • The record.enabled and record.retain.mode: motion are set at the correct level (camera or global) and are not being overridden elsewhere.
   • Motion detection is not overly sensitive (e.g., low threshold or contour_area), which could cause constant motion triggers(3), (1).
   • No other config (such as global record settings) is forcing continuous recording.

5. Suggested Changes and Checks:

   • Double-check that no global record: ... stanza elsewhere in your config (outside the per-camera blocks) is set to mode: all.
   • Review your motion sensitivity settings. Consider tuning the motion section to reduce false positives (e.g., increasing threshold or contour_area):

   motion:
     enabled: true
     threshold: 30        # Increase to reduce sensitivity
     contour_area: 30     # Increase to require larger motion

   Adjust these values in each camera as needed(3).

6. No Object Identification:
   Your current config with detect.enabled: false ensures no object identification takes place(1).

Summary of what to check/change:

• Ensure record.retain.mode: motion is set for every camera and not overridden globally.
• Tune motion.threshold and motion.contour_area upwards to avoid false motion, which could trigger continuous recording.
• Make sure you do not have a global record block with mode: all anywhere in your config.

Reference for recording only on motion:

"mode: motion - save all recordings segments with any detected motion"(1), (2)

Reference for tuning motion detection:

"The threshold value dictates how much of a change in a pixels luminance is required to be considered motion... contour_area: Minimum size in pixels in the resized motion image that counts as motion..."(3)

If you follow the above and still see 24/7 recordings, review the debug motion boxes to confirm if motion is being constantly detected due to environmental factors (e.g., moving trees, shadows). Adjust the motion parameters until only true motion is picked up(3).

📚 Sources:

1. Full Reference Config
2. Recording
3. Tuning Motion Detection

---

Have another question? Just tag @inkeep.