Frigate - NVR With Realtime Object Detection for IP Cameras

Overview

logo

Frigate - NVR With Realtime Object Detection for IP Cameras

A complete and local NVR designed for HomeAssistant with AI object detection. Uses OpenCV and Tensorflow to perform realtime object detection locally for IP cameras.

Use of a Google Coral Accelerator is optional, but highly recommended. The Coral will outperform even the best CPUs and can process 100+ FPS with very little overhead.

  • Tight integration with HomeAssistant via a custom component
  • Designed to minimize resource use and maximize performance by only looking for objects when and where it is necessary
  • Leverages multiprocessing heavily with an emphasis on realtime over processing every frame
  • Uses a very low overhead motion detection to determine where to run object detection
  • Object detection with TensorFlow runs in separate processes for maximum FPS
  • Communicates over MQTT for easy integration into other systems
  • Records video clips of detected objects
  • 24/7 recording
  • Re-streaming via RTMP to reduce the number of connections to your camera

Documentation

View the documentation at https://blakeblackshear.github.io/frigate

Donations

If you would like to make a donation to support development, please use Github Sponsors.

Screenshots

Integration into HomeAssistant

Also comes with a builtin UI:

Events

Comments
  • [Support]: unable to add the ffmpeg hardware acceleration for my Raspberry Pi4

    [Support]: unable to add the ffmpeg hardware acceleration for my Raspberry Pi4

    Describe the problem you are having

    I hope I'm not missing something obvious, I have been looking at this for a while before reaching out ;-)

    I seem unable to add the ffmpeg hardware acceleration for my Raspberry Pi4 using the following lines: ffmpeg: hwaccel_args: - -c:v - h264_v4l2m2m

    I have tried to add globally and under a specific single camera. All I get is a pure green image. Without adding these lines everything works great, although obviously the CPU usage is quite hit.

    In these logs describing the issue, I have only added the acceleration for the camera Living_Room_Low

    I have modified the /boot/config.txt file to 512 - gpu_mem=512 Confirmed this by going to the homeassistant container console: bash-5.1# /opt/vc/bin/vcgencmd get_mem gpu gpu=512M

    Version

    DEBUG 0.9.1-800F33E

    Frigate config file

    mqtt:
      host: 192.168.0.130
      port: 1883
      topic_prefix: frigate
      client_id: frigate
      user: <USERNAME>
      password: <PASSWORD>
      stats_interval: 60
    
    detectors:
      coral:
        type: edgetpu
        device: usb
    
    detect:
      width: 640
      height: 360
      fps: 5
      enabled: True
      max_disappeared: 25
    
    record:
      enabled: True
      retain_days: 0
      events:
        retain:
          default: 10
    
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 10
    
    # Optional: birdseye configuration
    birdseye:
      # Optional: Enable birdseye view (default: shown below)
      enabled: True
      # Optional: Width of the output resolution (default: shown below)
      width: 1280
      # Optional: Height of the output resolution (default: shown below)
      height: 720
      # Optional: Encoding quality of the mpeg1 feed (default: shown below)
      # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
      quality: 31
      # Optional: Mode of the view. Available options are: objects, motion, and continuous
      #   objects - cameras are included if they have had a tracked object within the last 30 seconds
      #   motion - cameras are included if motion was detected in the last 30 seconds
      #   continuous - all cameras are included always
      mode: objects
    
    cameras:
    ## Living Room Low Camera
      Living_Room_Low:
        ffmpeg:
          hwaccel_args:
            - -c:v
            - h264_v4l2m2m
          inputs:
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.206:554/av_stream/ch1
              roles:
                - detect
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.206:554/av_stream/ch0
              roles:
                - record
        objects:
          track:
            - person
            - dog
          filters:
            person:
              threshold: 0.75
              min_score: 0.70
            dog:
              threshold: 0.75
              min_score: 0.70
        motion:
          mask:
            - 0,75,209,61,209,0,0,0
            - 380,74,482,74,487,24,382,21
    ## Living Room High Camera
      Living_Room_High:
        ffmpeg:
          inputs:
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.205:554/av_stream/ch1
              roles:
                - detect
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.205:554/av_stream/ch0
              roles:
                - record
        objects:
          track:
            - person
            - dog
          filters:
            person:
              threshold: 0.75
              min_score: 0.70
            dog:
              threshold: 0.75
              min_score: 0.70
        motion:
          mask:
            - 0,18,155,18,155,0,0,0
      ## Patio camera
      Patio:
        ffmpeg:
          inputs:
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.203:554/av_stream/ch1
              roles:
                - detect
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.203:554/av_stream/ch0
              roles:
                - record
        objects:
          track:
            - person
            - dog
          filters:
            person:
              threshold: 0.75
              min_score: 0.70
            dog:
              threshold: 0.75
              min_score: 0.70
        motion:
          mask:
            - 0,108,640,108,640,0,0,0
      ## Kitchen Camera
      Kitchen:
        ffmpeg:
          inputs:
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.204:554/av_stream/ch1
              roles:
                - detect
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.204:554/av_stream/ch0
              roles:
                - record
        objects:
          track:
            - person
            - dog
          filters:
            person:
              threshold: 0.75
              min_score: 0.70
            dog:
              threshold: 0.65
              min_score: 0.60
        motion:
          mask:
            - 0,18,155,18,155,0,0,0
        zones:
          Cam_Zone_Back_Door:
            coordinates: 365,243,452,257,471,165,388,154
      ## Bedroom Camera
      Bedroom:
        ffmpeg:
          inputs:
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.207:554/av_stream/ch1
              roles:
                - detect
            - path: rtsp://rtsp:<PASSWORD>@192.168.0.207:554/av_stream/ch0
              roles:
                - record
        objects:
          track:
            - person
            - dog
          filters:
            person:
              threshold: 0.75
              min_score: 0.70
            dog:
              threshold: 0.75
              min_score: 0.70
        motion:
          mask:
            - 0,18,155,18,155,0,0,0
    

    Relevant log output

    [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
    [s6-init] ensuring user provided files have correct perms...exited 0.
    [fix-attrs.d] applying ownership & permissions fixes...
    [fix-attrs.d] done.
    [cont-init.d] executing container initialization scripts...
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.
    [2021-10-16 16:28:01] frigate.app                    INFO    : Starting Frigate (0.9.1-800f33e)
    [2021-10-16 16:28:01] frigate.app                    INFO    : Creating directory: /tmp/cache
    [2021-10-16 16:28:01] frigate.app                    WARNING : Camera Living_Room_Low has rtmp enabled, but rtmp is not assigned to an input.
    [2021-10-16 16:28:01] frigate.app                    WARNING : Camera Living_Room_High has rtmp enabled, but rtmp is not assigned to an input.
    [2021-10-16 16:28:01] frigate.app                    WARNING : Camera Patio has rtmp enabled, but rtmp is not assigned to an input.
    [2021-10-16 16:28:01] frigate.app                    WARNING : Camera Kitchen has rtmp enabled, but rtmp is not assigned to an input.
    [2021-10-16 16:28:01] frigate.app                    WARNING : Camera Bedroom has rtmp enabled, but rtmp is not assigned to an input.
    Starting migrations
    [2021-10-16 16:28:01] peewee_migrate                 INFO    : Starting migrations
    There is nothing to migrate
    [2021-10-16 16:28:01] peewee_migrate                 INFO    : There is nothing to migrate
    [2021-10-16 16:28:01] frigate.mqtt                   INFO    : MQTT connected
    [2021-10-16 16:28:01] frigate.app                    INFO    : Output process started: 219
    [2021-10-16 16:28:01] detector.coral                 INFO    : Starting detection process: 217
    [2021-10-16 16:28:01] frigate.edgetpu                INFO    : Attempting to load TPU as usb
    [2021-10-16 16:28:01] frigate.app                    INFO    : Camera processor started for Living_Room_Low: 221
    [2021-10-16 16:28:01] ws4py                          INFO    : Using epoll
    [2021-10-16 16:28:02] frigate.app                    INFO    : Camera processor started for Living_Room_High: 226
    [2021-10-16 16:28:02] frigate.app                    INFO    : Camera processor started for Patio: 230
    [2021-10-16 16:28:02] frigate.app                    INFO    : Camera processor started for Kitchen: 234
    [2021-10-16 16:28:02] frigate.app                    INFO    : Camera processor started for Bedroom: 235
    [2021-10-16 16:28:02] frigate.app                    INFO    : Capture process started for Living_Room_Low: 236
    [2021-10-16 16:28:02] frigate.app                    INFO    : Capture process started for Living_Room_High: 238
    [2021-10-16 16:28:02] frigate.app                    INFO    : Capture process started for Patio: 241
    [2021-10-16 16:28:02] frigate.app                    INFO    : Capture process started for Kitchen: 244
    [2021-10-16 16:28:02] frigate.app                    INFO    : Capture process started for Bedroom: 250
    [2021-10-16 16:28:02] ws4py                          INFO    : Using epoll
    [2021-10-16 16:28:05] frigate.edgetpu                INFO    : TPU found
    [2021-10-16 16:28:22] watchdog.Living_Room_Low       INFO    : No frames received from Living_Room_Low in 20 seconds. Exiting ffmpeg...
    [2021-10-16 16:28:22] watchdog.Living_Room_Low       INFO    : Waiting for ffmpeg to exit gracefully...
    [2021-10-16 16:28:52] watchdog.Living_Room_Low       INFO    : FFmpeg didnt exit. Force killing...
    [2021-10-16 16:28:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    [2021-10-16 16:28:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg process is not running. exiting capture thread...
    [2021-10-16 16:29:02] watchdog.Living_Room_Low       ERROR   : FFMPEG process crashed unexpectedly for Living_Room_Low.
    [2021-10-16 16:29:02] watchdog.Living_Room_Low       ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    [2021-10-16 16:29:02] watchdog.Living_Room_Low       ERROR   : You may have invalid args defined for this camera.
    [2021-10-16 16:29:02] ffmpeg.Living_Room_Low.detect  ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
    [2021-10-16 16:29:22] watchdog.Living_Room_Low       INFO    : No frames received from Living_Room_Low in 20 seconds. Exiting ffmpeg...
    [2021-10-16 16:29:22] watchdog.Living_Room_Low       INFO    : Waiting for ffmpeg to exit gracefully...
    [2021-10-16 16:29:52] watchdog.Living_Room_Low       INFO    : FFmpeg didnt exit. Force killing...
    [2021-10-16 16:29:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    [2021-10-16 16:29:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg process is not running. exiting capture thread...
    [2021-10-16 16:30:02] watchdog.Living_Room_Low       ERROR   : FFMPEG process crashed unexpectedly for Living_Room_Low.
    [2021-10-16 16:30:02] watchdog.Living_Room_Low       ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    [2021-10-16 16:30:02] watchdog.Living_Room_Low       ERROR   : You may have invalid args defined for this camera.
    [2021-10-16 16:30:02] ffmpeg.Living_Room_Low.detect  ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
    [2021-10-16 16:30:22] watchdog.Living_Room_Low       INFO    : No frames received from Living_Room_Low in 20 seconds. Exiting ffmpeg...
    [2021-10-16 16:30:22] watchdog.Living_Room_Low       INFO    : Waiting for ffmpeg to exit gracefully...
    [2021-10-16 16:30:52] watchdog.Living_Room_Low       INFO    : FFmpeg didnt exit. Force killing...
    [2021-10-16 16:30:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    [2021-10-16 16:30:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg process is not running. exiting capture thread...
    [2021-10-16 16:31:02] watchdog.Living_Room_Low       ERROR   : FFMPEG process crashed unexpectedly for Living_Room_Low.
    [2021-10-16 16:31:02] watchdog.Living_Room_Low       ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    [2021-10-16 16:31:02] watchdog.Living_Room_Low       ERROR   : You may have invalid args defined for this camera.
    [2021-10-16 16:31:02] ffmpeg.Living_Room_Low.detect  ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
    [2021-10-16 16:31:22] watchdog.Living_Room_Low       INFO    : No frames received from Living_Room_Low in 20 seconds. Exiting ffmpeg...
    [2021-10-16 16:31:22] watchdog.Living_Room_Low       INFO    : Waiting for ffmpeg to exit gracefully...
    [2021-10-16 16:31:52] watchdog.Living_Room_Low       INFO    : FFmpeg didnt exit. Force killing...
    [2021-10-16 16:31:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    [2021-10-16 16:31:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg sent a broken frame. read of closed file
    [2021-10-16 16:31:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg sent a broken frame. read of closed file
    [2021-10-16 16:31:52] frigate.video                  INFO    : Living_Room_Low: ffmpeg process is not running. exiting capture thread...
    [2021-10-16 16:32:02] watchdog.Living_Room_Low       ERROR   : FFMPEG process crashed unexpectedly for Living_Room_Low.
    [2021-10-16 16:32:02] watchdog.Living_Room_Low       ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    [2021-10-16 16:32:02] watchdog.Living_Room_Low       ERROR   : You may have invalid args defined for this camera.
    [2021-10-16 16:32:02] ffmpeg.Living_Room_Low.detect  ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
    [2021-10-16 16:32:23] watchdog.Living_Room_Low       INFO    : No frames received from Living_Room_Low in 20 seconds. Exiting ffmpeg...
    [2021-10-16 16:32:23] watchdog.Living_Room_Low       INFO    : Waiting for ffmpeg to exit gracefully...
    

    FFprobe output from your camera

    [email protected]:/opt/frigate# ffprobe rtsp://<USERNAME>:<PASSWORD>@192.168.0.206:554/av_stream/ch1
    ffprobe version 4.3.1 Copyright (c) 2007-2020 the FFmpeg developers
      built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04)
      configuration: --disable-debug --disable-doc --disable-ffplay --enable-shared --enable-avresample --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-gpl --enable-libfreetype --enable-libvidstab --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxcb --enable-libx265 --enable-libxvid --enable-libx264 --enable-nonfree --enable-openssl --enable-libfdk_aac --enable-postproc --enable-small --enable-version3 --enable-libzmq --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-libopenjpeg --enable-libkvazaar --enable-libaom --extra-libs=-lpthread --enable-rkmpp --enable-libdrm --enable-v4l2_m2m --enable-neon --extra-cflags=-I/opt/ffmpeg/include --extra-ldflags=-L/opt/ffmpeg/lib
      libavutil      56. 51.100 / 56. 51.100
      libavcodec     58. 91.100 / 58. 91.100
      libavformat    58. 45.100 / 58. 45.100
      libavdevice    58. 10.100 / 58. 10.100
      libavfilter     7. 85.100 /  7. 85.100
      libavresample   4.  0.  0 /  4.  0.  0
      libswscale      5.  7.100 /  5.  7.100
      libswresample   3.  7.100 /  3.  7.100
      libpostproc    55.  7.100 / 55.  7.100
    Input #0, rtsp, from 'rtsp://<USERNAME>:<PASSWORD>@192.168.0.206:554/av_stream/ch1':
      Metadata:
        title           : DYrtpsion
      Duration: N/A, start: 0.356000, bitrate: N/A
        Stream #0:0: Video: h264, yuv420p(progressive), 640x360, 10 fps, 10 tbr, 90k tbn, 20 tbc
        Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
    
    
    [email protected]:/opt/frigate# ffprobe rtsp://<USERNAME>:<PASSWORD>@192.168.0.206:554/av_stream/ch0
    ffprobe version 4.3.1 Copyright (c) 2007-2020 the FFmpeg developers
      built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04)
      configuration: --disable-debug --disable-doc --disable-ffplay --enable-shared --enable-avresample --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-gpl --enable-libfreetype --enable-libvidstab --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxcb --enable-libx265 --enable-libxvid --enable-libx264 --enable-nonfree --enable-openssl --enable-libfdk_aac --enable-postproc --enable-small --enable-version3 --enable-libzmq --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-libopenjpeg --enable-libkvazaar --enable-libaom --extra-libs=-lpthread --enable-rkmpp --enable-libdrm --enable-v4l2_m2m --enable-neon --extra-cflags=-I/opt/ffmpeg/include --extra-ldflags=-L/opt/ffmpeg/lib
      libavutil      56. 51.100 / 56. 51.100
      libavcodec     58. 91.100 / 58. 91.100
      libavformat    58. 45.100 / 58. 45.100
      libavdevice    58. 10.100 / 58. 10.100
      libavfilter     7. 85.100 /  7. 85.100
      libavresample   4.  0.  0 /  4.  0.  0
      libswscale      5.  7.100 /  5.  7.100
      libswresample   3.  7.100 /  3.  7.100
      libpostproc    55.  7.100 / 55.  7.100
    Input #0, rtsp, from 'rtsp://<USERNAME>:<PASSWORD>@192.168.0.206:554/av_stream/ch0':
      Metadata:
        title           : DYrtpsion
      Duration: N/A, start: 1.453000, bitrate: N/A
        Stream #0:0: Video: h264, yuv420p(progressive), 1920x1080, 10 fps, 10 tbr, 90k tbn, 20 tbc
        Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
    

    Frigate stats

    {"Bedroom":{"camera_fps":5.1,"capture_pid":250,"detection_fps":2.4,"pid":235,"process_fps":4.5,"skipped_fps":0.0},"Kitchen":{"camera_fps":4.33,"capture_pid":244,"detection_fps":0.0,"pid":234,"process_fps":2.5,"skipped_fps":0.0},"Living_Room_High":{"camera_fps":5.1,"capture_pid":238,"detection_fps":7.8,"pid":226,"process_fps":3.6,"skipped_fps":0.0},"Living_Room_Low":{"camera_fps":0.0,"capture_pid":236,"detection_fps":0.0,"pid":221,"process_fps":0.0,"skipped_fps":0.0},"Patio":{"camera_fps":5.0,"capture_pid":241,"detection_fps":6.3,"pid":230,"process_fps":5.0,"skipped_fps":0.0},"detection_fps":16.5,"detectors":{"coral":{"detection_start":1634398738.87413,"inference_speed":49.29,"pid":217}},"service":{"storage":{"/dev/shm":{"free":1757.4,"mount_type":"tmpfs","total":1760.4,"used":3.0},"/media/frigate/clips":{"free":187931.6,"mount_type":"ext4","total":235535.3,"used":38003.3},"/media/frigate/recordings":{"free":187931.6,"mount_type":"ext4","total":235535.3,"used":38003.3},"/tmp/cache":{"free":1759.0,"mount_type":"tmpfs","total":1760.4,"used":1.4}},"uptime":656,"version":"0.9.1-800f33e"}}
    

    Operating system

    HassOS

    Install method

    HassOS Addon

    Coral version

    USB

    Network connection

    Wired

    Camera make and model

    Sonoff WiFi IP Camera 1080P

    Any other information that may be helpful

    No response

    support stale triage 
    opened by neildotwilliams 262
  • Nvidia Jetson Nano gstreamer + TensorRT support

    Nvidia Jetson Nano gstreamer + TensorRT support

    The rebased version of the https://github.com/blakeblackshear/frigate/pull/2440

    • [x] make tflite runtime work on CPU and finalize edgetpu refactoring
    • [x] figure out gstreamer + ffmpeg RTMP relay
    • [x] autodetect necessary gstreamer pipeline elements using gst-discoverer-1.0
    • [x] figure out the better way of converting darknet Yolo weights into the TensorRT model
    • [x] optimize docker image
    • [x] make available gstreamer to the other platforms as an alternative to the ffmpeg decoding
    • [x] fix amd64 FFMpeg build
    • [x] gst-discoverer-1.0 hang on discovering stream should not hang up the app
    • [x] try out nvv4l2decoder with (memory:NVMM) specifier
    • [x] figure out recording resolution issue
    • [x] figure out a possibility to write audio stream to the recording
    • [x] resolve 'bufmax >= bufoffs + offset + size assertion message
    • [x] good config defaults for Jetson inference
    • [x] research Presentation Time Stamp values (PTS) for the VBR streams
    • [x] review log messages to avoid FFMpeg / Gstreamer confusion
    • [x] add GStreamer configuration documentation

    I updated the Docker image on the DockerHub, you can test this branch by docker pull yury1sannikov/frigate.l4t:latest More details: https://github.com/blakeblackshear/frigate/pull/2440#issuecomment-1002080620

    stale 
    opened by yury-sannikov 153
  • [Support]: CPU usage near 100% with version 0.11.0 beta 5

    [Support]: CPU usage near 100% with version 0.11.0 beta 5

    Describe the problem you are having

    After upgrading to version 0.11.0 beta 2, 4 & 5, my CPU usage is near 100% when normally it's around 25-30%. I've tried rebooting the Frigate container as well as rebooting my entire mini server (Odyssey X86 Blue J4125) but the issue persists. I did not make any changes to my Frigate config file. Frigate itself appears to be running just fine.

    Version

    0.11.0-D2C3CDC

    Frigate config file

    mqtt:
      host: ip_address
      user: username
      password: password
    
    cameras:
      front:
        ffmpeg:
          inputs:
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
        objects:
          track:
            - person
            - vehicle
            - animal
        record:
          events:
            required_zones:
              - sidewalk
              - driveway
        snapshots:
          required_zones:
            - sidewalk
            - driveway
        zones:
          sidewalk:
            coordinates: 0,741,1533,339,1359,286,921,350,0,561
          driveway:
            coordinates: 468,1080,1920,1080,1920,583,1785,519,1620,646,1121,484,304,701
        motion:
          mask:
            - 1510,354,1920,285,1920,0,1324,0
            - 0,1080,250,1080,147,675,0,703
      side:
        ffmpeg:
          inputs:
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
        objects:
          track:
            - person
            - animal
        motion:
          mask:
            - 244,0,254,285,435,273,430,79,1641,1080,1920,1080,1920,0
          improve_contrast: True
      back:
        ffmpeg:
          inputs:
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
        objects:
          track:
            - person
            - animal
        motion:
          mask:
            - 1357,48,1666,101,1920,201,1920,0,0,0,0,79
      inside:
        ffmpeg:
          inputs:
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://username:[email protected]_address:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
        motion:
          mask:
            - 1920,0,1920,74,633,72,637,0
    
    record:
      enabled: True
      retain:
        days: 6
        mode: all
      events:
        retain:
          default: 12
          mode: active_objects
    
    detect:
      width: 1920
      height: 1080
    
    model:
      labelmap:
        2: vehicle
        3: vehicle
        5: vehicle
        7: vehicle
        15: animal
        16: animal
        17: animal
    
    ffmpeg:
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
    
    detectors:
      coral:
        type: edgetpu
        device: pci
    

    Relevant log output

    From `top` showing the top 4 highest CPU usage (77.8, 76.5, 74.5, 73.5):  
    
       6016 root      20   0  602248  75744  26408 R  77.8   0.9   7:47.10 ffmpeg                                          
       5998 root      20   0  601188  73316  26052 R  76.5   0.9   7:48.00 ffmpeg                                          
       6013 root      20   0  601812  81136  26252 R  74.5   1.0   7:44.76 ffmpeg                                          
       6012 root      20   0  600808  72116  26372 R  73.5   0.9   7:47.56 ffmpeg
    

    FFprobe output from your camera

    ffprobe version 4.2.2 Copyright (c) 2007-2019 the FFmpeg developers
      built with Apple clang version 11.0.0 (clang-1100.0.33.17)
      configuration: --prefix=/usr/local/Cellar/ffmpeg/4.2.2_2 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --disable-libjack --disable-indev=jack
      libavutil      56. 31.100 / 56. 31.100
      libavcodec     58. 54.100 / 58. 54.100
      libavformat    58. 29.100 / 58. 29.100
      libavdevice    58.  8.100 / 58.  8.100
      libavfilter     7. 57.100 /  7. 57.100
      libavresample   4.  0.  0 /  4.  0.  0
      libswscale      5.  5.100 /  5.  5.100
      libswresample   3.  5.100 /  3.  5.100
      libpostproc    55.  5.100 / 55.  5.100
    Input #0, rtsp, from 'rtsp://username:[email protected]_address:port/cam/realmonitor?channel=1&subtype=0':
      Metadata:
        title           : Media Server
      Duration: N/A, start: 0.000000, bitrate: N/A
        Stream #0:0: Video: h264 (Main), yuvj420p(pc, bt470bg/bt470bg/bt709, progressive), 2688x1520, 15 fps, 15 tbr, 90k tbn, 30 tbc
        Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
    

    Frigate stats

    No response

    Operating system

    Debian

    Install method

    Docker Compose

    Coral version

    M.2

    Network connection

    Wired

    Camera make and model

    Loryta (Dahua) IPC-T5442TM-AS

    Any other information that may be helpful

    No response

    support triage 
    opened by shred86 130
  • 0.11.0 release - FFMPEG hardware accelleration not working inside docker container on i7-11th gen RocketLake

    0.11.0 release - FFMPEG hardware accelleration not working inside docker container on i7-11th gen RocketLake

    Describe the problem you are having

    Hardware acceleration works on the host, just not inside the container in the new release 0.11.0.

    If I roll back to v10, all is fine.

    I know the FFMPEG build has now changed, and this HWACCEL issue is a bad nightmare for many projects, ever since the thread bugs to intel's split of i965 vs iHD etc.

    I've spent a few hours on this, just can't seem to get this working, so gone back to v10 for now.

    The error I get when attempting hardware acceleration inside frigate container via the hwaccel_args of '-hwaccel auto': [h264 @ 0x55c00073de80] Failed to end picture decode issue: 23 (internal decoding error). [h264 @ 0x55c00073de80] hardware accelerator failed to decode picture Error while decoding stream #0:0: Input/output error

    The error I get when attempting accel inside frigate container via the hwaccel_args of '-hwaccel_output_format qsv -c:v h264_qsv -hwaccel_device /dev/dri/renderD128': [h264_qsv @ 0x55fe09463f40] Error during QSV decoding.: device failed (-17) Error while decoding stream #0:0: Input/output error

    The output of vainfo inside the container

    error: XDG_RUNTIME_DIR not set in the environment.
    error: can't connect to X server!
    libva info: VA-API version 1.10.0
    libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
    libva info: Found init function __vaDriverInit_1_10
    libva info: va_openDriver() returns 0
    vainfo: VA-API version: 1.10 (libva 2.10.0)
    vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 21.1.1 ()
    vainfo: Supported profile and entrypoints
          VAProfileNone                   :	VAEntrypointVideoProc
          VAProfileNone                   :	VAEntrypointStats
          VAProfileMPEG2Simple            :	VAEntrypointVLD
          VAProfileMPEG2Simple            :	VAEntrypointEncSlice
          VAProfileMPEG2Main              :	VAEntrypointVLD
          VAProfileMPEG2Main              :	VAEntrypointEncSlice
          VAProfileH264Main               :	VAEntrypointVLD
          VAProfileH264Main               :	VAEntrypointEncSlice
          VAProfileH264Main               :	VAEntrypointFEI
          VAProfileH264Main               :	VAEntrypointEncSliceLP
          VAProfileH264High               :	VAEntrypointVLD
          VAProfileH264High               :	VAEntrypointEncSlice
          VAProfileH264High               :	VAEntrypointFEI
          VAProfileH264High               :	VAEntrypointEncSliceLP
          VAProfileVC1Simple              :	VAEntrypointVLD
          VAProfileVC1Main                :	VAEntrypointVLD
          VAProfileVC1Advanced            :	VAEntrypointVLD
          VAProfileJPEGBaseline           :	VAEntrypointVLD
          VAProfileJPEGBaseline           :	VAEntrypointEncPicture
          VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
          VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
          VAProfileH264ConstrainedBaseline:	VAEntrypointFEI
          VAProfileH264ConstrainedBaseline:	VAEntrypointEncSliceLP
          VAProfileHEVCMain               :	VAEntrypointVLD
          VAProfileHEVCMain               :	VAEntrypointEncSlice
          VAProfileHEVCMain               :	VAEntrypointFEI
          VAProfileHEVCMain               :	VAEntrypointEncSliceLP
          VAProfileHEVCMain10             :	VAEntrypointVLD
          VAProfileHEVCMain10             :	VAEntrypointEncSlice
          VAProfileHEVCMain10             :	VAEntrypointEncSliceLP
          VAProfileVP9Profile0            :	VAEntrypointVLD
          VAProfileVP9Profile1            :	VAEntrypointVLD
          VAProfileVP9Profile2            :	VAEntrypointVLD
          VAProfileVP9Profile3            :	VAEntrypointVLD
          VAProfileHEVCMain12             :	VAEntrypointVLD
          VAProfileHEVCMain12             :	VAEntrypointEncSlice
          VAProfileHEVCMain422_10         :	VAEntrypointVLD
          VAProfileHEVCMain422_10         :	VAEntrypointEncSlice
          VAProfileHEVCMain422_12         :	VAEntrypointVLD
          VAProfileHEVCMain422_12         :	VAEntrypointEncSlice
          VAProfileHEVCMain444            :	VAEntrypointVLD
          VAProfileHEVCMain444            :	VAEntrypointEncSliceLP
          VAProfileHEVCMain444_10         :	VAEntrypointVLD
          VAProfileHEVCMain444_10         :	VAEntrypointEncSliceLP
          VAProfileHEVCMain444_12         :	VAEntrypointVLD
          VAProfileHEVCSccMain            :	VAEntrypointVLD
          VAProfileHEVCSccMain            :	VAEntrypointEncSliceLP
          VAProfileHEVCSccMain10          :	VAEntrypointVLD
          VAProfileHEVCSccMain10          :	VAEntrypointEncSliceLP
          VAProfileHEVCSccMain444         :	VAEntrypointVLD
          VAProfileHEVCSccMain444         :	VAEntrypointEncSliceLP
          VAProfileAV1Profile0            :	VAEntrypointVLD
          VAProfileHEVCSccMain444_10      :	VAEntrypointVLD
          VAProfileHEVCSccMain444_10      :	VAEntrypointEncSliceLP
    

    The output of vainfo on the host

    error: can't connect to X server!
    libva info: VA-API version 1.14.0
    libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
    libva info: Found init function __vaDriverInit_1_14
    libva info: va_openDriver() returns 0
    vainfo: VA-API version: 1.14 (libva 2.14.0)
    vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.4.3 (74f40ee)
    vainfo: Supported profile and entrypoints
          VAProfileNone                   :	VAEntrypointVideoProc
          VAProfileNone                   :	VAEntrypointStats
          VAProfileMPEG2Simple            :	VAEntrypointVLD
          VAProfileMPEG2Simple            :	VAEntrypointEncSlice
          VAProfileMPEG2Main              :	VAEntrypointVLD
          VAProfileMPEG2Main              :	VAEntrypointEncSlice
          VAProfileH264Main               :	VAEntrypointVLD
          VAProfileH264Main               :	VAEntrypointEncSlice
          VAProfileH264Main               :	VAEntrypointFEI
          VAProfileH264Main               :	VAEntrypointEncSliceLP
          VAProfileH264High               :	VAEntrypointVLD
          VAProfileH264High               :	VAEntrypointEncSlice
          VAProfileH264High               :	VAEntrypointFEI
          VAProfileH264High               :	VAEntrypointEncSliceLP
          VAProfileVC1Simple              :	VAEntrypointVLD
          VAProfileVC1Main                :	VAEntrypointVLD
          VAProfileVC1Advanced            :	VAEntrypointVLD
          VAProfileJPEGBaseline           :	VAEntrypointVLD
          VAProfileJPEGBaseline           :	VAEntrypointEncPicture
          VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
          VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
          VAProfileH264ConstrainedBaseline:	VAEntrypointFEI
          VAProfileH264ConstrainedBaseline:	VAEntrypointEncSliceLP
          VAProfileHEVCMain               :	VAEntrypointVLD
          VAProfileHEVCMain               :	VAEntrypointEncSlice
          VAProfileHEVCMain               :	VAEntrypointFEI
          VAProfileHEVCMain               :	VAEntrypointEncSliceLP
          VAProfileHEVCMain10             :	VAEntrypointVLD
          VAProfileHEVCMain10             :	VAEntrypointEncSlice
          VAProfileHEVCMain10             :	VAEntrypointEncSliceLP
          VAProfileVP9Profile0            :	VAEntrypointVLD
          VAProfileVP9Profile1            :	VAEntrypointVLD
          VAProfileVP9Profile2            :	VAEntrypointVLD
          VAProfileVP9Profile3            :	VAEntrypointVLD
          VAProfileHEVCMain12             :	VAEntrypointVLD
          VAProfileHEVCMain12             :	VAEntrypointEncSlice
          VAProfileHEVCMain422_10         :	VAEntrypointVLD
          VAProfileHEVCMain422_10         :	VAEntrypointEncSlice
          VAProfileHEVCMain422_12         :	VAEntrypointVLD
          VAProfileHEVCMain422_12         :	VAEntrypointEncSlice
          VAProfileHEVCMain444            :	VAEntrypointVLD
          VAProfileHEVCMain444            :	VAEntrypointEncSliceLP
          VAProfileHEVCMain444_10         :	VAEntrypointVLD
          VAProfileHEVCMain444_10         :	VAEntrypointEncSliceLP
          VAProfileHEVCMain444_12         :	VAEntrypointVLD
          VAProfileHEVCSccMain            :	VAEntrypointVLD
          VAProfileHEVCSccMain            :	VAEntrypointEncSliceLP
          VAProfileHEVCSccMain10          :	VAEntrypointVLD
          VAProfileHEVCSccMain10          :	VAEntrypointEncSliceLP
          VAProfileHEVCSccMain444         :	VAEntrypointVLD
          VAProfileHEVCSccMain444         :	VAEntrypointEncSliceLP
          VAProfileAV1Profile0            :	VAEntrypointVLD
          VAProfileHEVCSccMain444_10      :	VAEntrypointVLD
          VAProfileHEVCSccMain444_10      :	VAEntrypointEncSliceLP
    

    inte_gpu_top works fine and shows the card as active inside the container, and when running ffmpeg with accel on the host, the gpu_top tool shows the appropriate hardware acceleration activity.

    It seems like the FFMPEG build included in the 0.11.0 release of Frigate doesn't want to use Intel's Media iHD driver for hardware acceleration, though this is just a guess...

    Version

    0.11.0

    Frigate config file

    hwaccel_args: -hwaccel_output_format qsv -c:v h264_qsv -qsv_device /dev/dri/renderD128
    

    Relevant log output

    FFMPEG hardware acceleration failures.
    

    FFprobe output from your camera

    n/a
    

    Frigate stats

    n/a
    

    Operating system

    Other Linux

    Install method

    Docker Compose

    Coral version

    PCIe

    Network connection

    Wired

    Camera make and model

    n/a

    Any other information that may be helpful

    No response

    support pinned triage 
    opened by Sarah-Connelli 117
  • H.265/H.265+ Input - Streaming Works, Clip/Recording Viewing Does Not

    H.265/H.265+ Input - Streaming Works, Clip/Recording Viewing Does Not

    Describe the bug Cannot play clips or recordings of camera footage on mobile app (Android) or desktop browser. Can (somehow?) view streams, however, at full 4K resolution on Frigate web portal. But in Home Assistant at very low resolution only, even when feed has been clicked on. Can view recorded .mp4 files on PC through file browser just fine (via SMB share on networked Windows PCs). Clips (sidenote - these do not always record?) just give a blank window.

    I understand that H.265 is the culprit here, and that viewing clips/recordings of H.264 footage is preferable. However, not my scenario, so I've been trying to figure out real-time conversion from H.265 to H.264 (or if there's some other preferred codec to convert to, I'm not opposed!).

    Camera footage is from two identical Annke C800 cameras with ONLY a choice between H.265 or H.265+ main streams (the substream can be H.265 or MJPEG). I have Frigate running as a Docker container (on a secondary UnRAID server with the Google Coral TPU and an Intel Core i5-6600K CPU - integrated, but no dedicated GPU).

    I have Home Assistant running in HASSIO via VM (on my primary UnRAID Server). Frigate is (successfully!) tied into a Home Assistant integration.

    However, at my wit's end of figuring out how to get Frigate to convert the H.265 footage on-the-fly for viewing clips/recordings through browsers or phones (I'm doing detect, clip, record, and have currently disabled rtmp as that almost-always causes a "green" image for me).

    I have tried all kinds of random ffmpeg arguments (as you can see in my code, some previous things I've tried are commented out - but there's other stuff I've tried thats not in the commented out code).

    The Frigate-hosting server with the Intel Core i5-6600K - in theory - should be capable of QSV hardware encoding (I think?) and seemed to do so perfectly when I previously used it for Plex hardware transcoding, but for Frigate I've had better luck with the "h264_vaapi" ffmpeg setting, at least so far as CPU-load is concerned. The Google Coral TPU works perfectly with a 6.52 inference speed at this exact moment.

    What am I missing here, and how did I manage to get the live stream working, given that the other stuff doesn't?

    NOTE: I know that the hardware acceleration settings are currently different for both cameras. I also did notice a slight difference (two characters - ":v") in the clip ffmpeg arguments for both cameras (in my mess of experimenting with one at a time), but both of them are operating similarly and neither have accessible clips/recordings nonetheless: clips: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy clips: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy

    Version of frigate 0.8.4-5043040

    Config file

    detectors:
      coral_pci:
        type: edgetpu
        device: pci
    # Required: mqtt configuration
    mqtt:
      # Required: host name
      host: 192.168.0.115
      # Optional: port (default: shown below)
      port: 1883
      # Optional: topic prefix (default: shown below)
      # WARNING: must be unique if you are running multiple instances
      topic_prefix: frigate
      # Optional: client id (default: shown below)
      # WARNING: must be unique if you are running multiple instances
      client_id: frigate
      # Optional: user
      user: username
      # Optional: password
      # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}. 
      #       eg. password: '{FRIGATE_MQTT_PASSWORD}'
      password: password
      stats_interval: 60
    
    # Required: configuration section for cameras
    cameras:
      # Required: name of the camera
      garage:
        # Required: ffmpeg settings for the camera
        ffmpeg:
          input_args:
            - -avoid_negative_ts
            - make_zero
            - -fflags
            - +genpts
            - -r
            - '5'  # <---- adjust depending on your desired frame rate from the mjpeg image
            - -use_wallclock_as_timestamps
            - '1'    
          hwaccel_args:
            - -hwaccel
            - vaapi
            - -hwaccel_device
            - /dev/dri/renderD128
            - -hwaccel_output_format
            - yuv420p
          output_args:
              detect: -f rawvideo -pix_fmt yuv420p
              record: -f segment -segment_time 300 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
              clips: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy
              #record: -f segment -segment_time 300 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v h264_vaapi -pix_fmt yuv420p
              #clips: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v h264_vaapi -pix_fmt yuv420p                             
              #rtmp: -c:v h264_vaapi -c:a copy -vf format=nv12|vaapi,hwupload -f flv                          
              #rtmp: -c:v h264_qsv -c:a copy -f flv
          inputs:
            - path: rtsp://username:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1
              roles:
                - detect
                - record
                - clips
                #- rtmp
        width: 3840
        height: 2160
        fps: 5                                                                       
        best_image_timeout: 15                                                        
        detect:                                                                       
          enabled: True                                                               
          max_disappeared: 15   
        
        # Optional: 24/7 recording configuration
        record:
          # Optional: Enable recording (default: global setting)
          enabled: true
          # Optional: Number of days to retain (default: global setting)
          retain_days: 28
            
        rtmp:
          # Required: Enable the live stream (default: True)
          enabled: false
        clips:
          # Required: enables clips for the camera (default: shown below)
          # This value can be set via MQTT and will be updated in startup based on retained value
          enabled: true
          # Optional: Number of seconds before the event to include in the clips (default: shown below)
          pre_capture: 5
          # Optional: Number of seconds after the event to include in the clips (default: shown below)
          post_capture: 30
          # Optional: Objects to save clips for. (default: all tracked objects)
          # Notice: If you have mounted a tmpfs volume through docker, this value should not be set in your config
          objects:
            - person
            - cat
            - dog
            - bird
            - car
            - truck
            - bicycle
            - motorcycle
          # Optional: Camera override for retention settings (default: global values)
          retain:
            # Required: Default retention days (default: shown below)
            default: 28
            # Optional: Per object retention days
            objects:
              person: 28
              cat: 28
              dog: 28
              bird: 28
              car: 28
              truck: 28
              bicycle: 28
              motorcycle: 28
        # Optional: Configuration for the jpg snapshots written to the clips directory for each event
        snapshots:
          # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
          # This value can be set via MQTT and will be updated in startup based on retained value
          enabled: true
          # Optional: print a timestamp on the snapshots (default: shown below)
          timestamp: false
          # Optional: draw bounding box on the snapshots (default: shown below)
          bounding_box: true
          # Optional: crop the snapshot (default: shown below)
          crop: false
    #      # Optional: height to resize the snapshot to (default: original size)
    #      height: 175
          # Optional: Camera override for retention settings (default: global values)
          retain:
            # Required: Default retention days (default: shown below)
            default: 28
            # Optional: Per object retention days
            objects:
              person: 28
              cat: 28
              dog: 28
              bird: 28
              car: 28
              truck: 28
              bicycle: 28
              motorcycle: 28
        objects:
          track:
            - person
            - cat
            - dog
            - bird
            - car
            - truck
            - bicycle
            - motorcycle
      patio:
        zones:
          # Required: name of the zone
          # NOTE: This must be different than any camera names, but can match with another zone on another camera.
          patio_interior:
            # Required: List of x,y coordinates to define the polygon of the zone.
            # NOTE: Coordinates can be generated at https://www.image-map.net/
            coordinates: 2744,2160,2694,1299,2609,711,1992,426,1789,743,934,770,855,497,288,638,0,1134,0,2160
          front_steps:
            # Required: List of x,y coordinates to define the polygon of the zone.
            # NOTE: Coordinates can be generated at https://www.image-map.net/    
            coordinates: 3006,1657,3611,1607,3840,1263,3840,2160,3029,2160
        # Required: ffmpeg settings for the camera
        # Optional: camera level motion config
        motion:
          # Optional: motion mask
          # NOTE: see docs for more detailed info on creating masks
          mask: 1496,1558,1495,1690,1573,1859,1645,1923,1828,2009,1985,2024,2187,1962,2372,1830,2465,1619,2441,1434,2375,1325,2269,1234,2118,1175,1943,1173,1711,1258,1560,1396
        ffmpeg:
          input_args:
            - -avoid_negative_ts
            - make_zero
            - -fflags
            - +genpts
            - -r
            - '5'  # <---- adjust depending on your desired frame rate from the mjpeg image
            - -use_wallclock_as_timestamps
            - '1'    
          hwaccel_args:
            - -hwaccel
            - vaapi
            - -hwaccel_device
            - /dev/dri/renderD128
            #- -hwaccel_output_format
            #- yuv420p
          output_args:
              # Optional: output args for detect streams (default: shown below)
              detect: -f rawvideo -pix_fmt yuv420p
              # Optional: output args for record streams (default: shown below)
              record: -f segment -segment_time 300 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
              # Optional: output args for clips streams (default: shown below)
              clips: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
              # Optional: output args for rtmp streams (default: shown below)
              #record: -f segment -segment_time 300 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v h264_vaapi -pix_fmt yuv420p
              #clips: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v h264_vaapi -pix_fmt yuv420p                             
              #rtmp: -c:v h264_vaapi -c:a copy -vf format=nv12|vaapi,hwupload -f flv
              
          inputs:
            - path: rtsp://username:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1
              roles:
                - detect
                - record
                - clips
               #- rtmp
    
        width: 3840
        height: 2160
        fps: 5                                                                        
        best_image_timeout: 15                                                        
        detect:                                                                       
          enabled: True                                                               
          max_disappeared: 15   
        # Optional: 24/7 recording configuration
        record:
          # Optional: Enable recording (default: global setting)
          enabled: true
          # Optional: Number of days to retain (default: global setting)
          retain_days: 28
        
        rtmp:
          # Required: Enable the live stream (default: True)
          enabled: false
        clips:
          # Required: enables clips for the camera (default: shown below)
          # This value can be set via MQTT and will be updated in startup based on retained value
          enabled: true
          # Optional: Number of seconds before the event to include in the clips (default: shown below)
          pre_capture: 5
          # Optional: Number of seconds after the event to include in the clips (default: shown below)
          post_capture: 30
          # Optional: Objects to save clips for. (default: all tracked objects)
          objects:
            - person
            - cat
            - dog
            - bird
            - bicycle
          # Optional: Camera override for retention settings (default: global values)
          retain:
            # Required: Default retention days (default: shown below)
            default: 28
            # Optional: Per object retention days
            objects:
              person: 28
              cat: 28
              dog: 28
              bird: 28
              bicycle: 28
        # Optional: Configuration for the jpg snapshots written to the clips directory for each event
        snapshots:
          # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
          # This value can be set via MQTT and will be updated in startup based on retained value
          enabled: true
          # Optional: print a timestamp on the snapshots (default: shown below)
          timestamp: false
          # Optional: draw bounding box on the snapshots (default: shown below)
          bounding_box: true
          # Optional: crop the snapshot (default: shown below)
          crop: false
    #      # Optional: height to resize the snapshot to (default: original size)
    #      height: 175
          # Optional: Camera override for retention settings (default: global values)
          retain:
            # Required: Default retention days (default: shown below)
            default: 28
            # Optional: Per object retention days
            objects:
              person: 28
              cat: 28
              dog: 28
              bird: 28
              bicycle: 28
        objects:
          track:
            - person
            - cat
            - dog
            - bird
            - bicycle
    

    Frigate container logs

    * Starting nginx nginx
    ...done.
    Starting migrations
    peewee_migrate INFO : Starting migrations
    There is nothing to migrate
    peewee_migrate INFO : There is nothing to migrate
    frigate.mqtt INFO : MQTT connected
    detector.coral_pci INFO : Starting detection process: 34
    frigate.edgetpu INFO : Attempting to load TPU as pci
    frigate.app INFO : Camera processor started for garage: 37
    frigate.app INFO : Camera processor started for patio: 42
    frigate.app INFO : Capture process started for garage: 43
    frigate.app INFO : Capture process started for patio: 48
    frigate.edgetpu INFO : TPU found
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x561ccdf44140] moov atom not found
    /tmp/cache/garage-20210604032034.mp4: Invalid data found when processing input
    frigate.events INFO : bad file: garage-20210604032034.mp4
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55e559f2f140] moov atom not found
    /media/frigate/recordings/garage-20210604032034.mp4: Invalid data found when processing input
    frigate.record INFO : bad file: garage-20210604032034.mp4
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x563e96e20140] moov atom not found
    /tmp/cache/patio-20210604032034.mp4: Invalid data found when processing input
    frigate.events INFO : bad file: patio-20210604032034.mp4
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55f2ecab0140] moov atom not found
    /media/frigate/recordings/patio-20210604032034.mp4: Invalid data found when processing input
    frigate.record INFO : bad file: patio-20210604032034.mp4
    frigate.events WARNING : Unable to create clip for garage and event 1622802130.68389-al3z1u. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622802153.36347-wdwbd1. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622803783.822933-0g7mvn. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622803971.304239-ttsd0u. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622806468.274713-d9ldul. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622807117.957606-iw6c20. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622807123.357425-0qpxz4. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622808762.174949-sj43le. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622812768.352098-2ye58u. There were no cache files for this event.
    frigate.mqtt INFO : MQTT connected
    frigate.events WARNING : Unable to create clip for patio and event 1622814252.938436-uw0per. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622815311.75895-gezo2s. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622815312.29653-qjtlv4. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622815311.821276-lywhng. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622816228.822682-udjxih. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622816237.023143-sn01py. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622816597.650224-avgjsf. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622816617.067812-qn54kk. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622816746.399308-dr4vin. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622816752.137597-gmsjnt. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622816747.743455-xjoh2f. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622819925.901527-fsxnf5. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821574.790685-swmtw4. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821575.136792-8jd1mx. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821603.495505-w7jq8x. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821615.9878-zeejqa. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821661.153113-k3ad2i. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821667.292972-vzk5zx. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821742.851961-kw8gwx. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622821710.027854-b3srbw. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622822385.299786-iq0siz. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622822390.824511-zt70jl. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622822539.907096-t322vj. There were no cache files for this event.
    frigate.mqtt INFO : MQTT connected
    frigate.events WARNING : Unable to create clip for patio and event 1622825310.27496-fhijfo. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622826181.68446-395z3b. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622828240.677298-oxgsgi. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622828893.830872-s6nseo. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622829176.35348-ry21qm. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622829342.770291-syxgpj. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622829920.088727-mf6vqz. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622829987.841575-11eyqx. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622830023.338597-etkjoi. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622831155.057975-wxgc4r. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622831160.119702-nur742. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622831206.047522-ifcark. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622831636.2801-gp1phd. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622832538.78718-l20mok. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622832554.866569-jfz3sv. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622832773.44799-i0idri. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622832774.330443-iasdjx. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622832780.066681-hu06oi. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622834895.042775-6wrg3e. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622835530.32922-xj20tu. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622835797.430096-nf7cgp. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622835908.503294-8ku77f. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622835912.300151-inb9dm. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622836040.371498-f9x4zr. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622836081.036489-hoib8i. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622837206.721741-35g23r. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622837207.660586-ccv7eo. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622837209.402653-tz676f. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622842132.121597-8ui141. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622844321.762195-97cev8. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622844322.306303-dq17wx. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622848380.86077-65w0ec. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622849253.745187-dx9r9w. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622849268.83767-p3rt2g. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622849274.380077-j100lv. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622849632.79096-2mxui1. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622849718.964755-as3a9l. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622849718.339-kdg27y. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622849993.99836-knh7um. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622850193.642327-n3727h. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622850532.221807-oa0igc. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622851347.495611-q5ovvu. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622851362.929145-pc824h. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622851374.010079-x8jh3e. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622852315.68379-w3pl0q. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622852328.960694-g4esy9. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622852348.805504-vavups. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622852568.324141-62gukx. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622854080.788556-lmjl5c. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622854088.532009-mv44uv. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622854289.578867-z6o8ko. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622857799.159086-6hx3dy. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622857796.033671-wamyyz. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622857795.355121-5bs9c2. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622860008.522527-skgjpi. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622860012.654567-kxt7ly. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622861255.734256-sqp0zt. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622861256.536406-gzw2ww. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622861276.025416-z8nd84. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622861258.676553-ky189i. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622861328.885643-xjzlm9. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622861365.465755-lrghar. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622861387.557007-ofsyrk. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622863920.628907-ta4je0. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622863938.441934-10g0a7. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622863964.934348-f5nfia. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622863955.585607-wz6yn9. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622864041.908044-cklncs. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for patio and event 1622864047.792371-0q0ezo. There were no cache files for this event.
    frigate.events WARNING : Unable to create clip for garage and event 1622864214.033175-49xcon. There were no cache files for this event.
    

    Frigate stats

    {
      "detection_fps": 0.0, 
      "detectors": {
        "coral_pci": {
          "detection_start": 0.0, 
          "inference_speed": 6.51, 
          "pid": 34
        }
      }, 
      "garage": {
        "camera_fps": 15.1, 
        "capture_pid": 43, 
        "detection_fps": 0.0, 
        "pid": 37, 
        "process_fps": 15.1, 
        "skipped_fps": 0.0
      }, 
      "patio": {
        "camera_fps": 15.0, 
        "capture_pid": 48, 
        "detection_fps": 0.0, 
        "pid": 42, 
        "process_fps": 15.0, 
        "skipped_fps": 0.0
      }, 
      "service": {
        "storage": {
          "/dev/shm": {
            "free": 5334.7, 
            "mount_type": "tmpfs", 
            "total": 5368.7, 
            "used": 34.0
          }, 
          "/media/frigate/clips": {
            "free": 2803689.5, 
            "mount_type": "xfs", 
            "total": 2999111.0, 
            "used": 195421.5
          }, 
          "/media/frigate/recordings": {
            "free": 2803689.5, 
            "mount_type": "xfs", 
            "total": 2999111.0, 
            "used": 195421.5
          }, 
          "/tmp/cache": {
            "free": 15172.8, 
            "mount_type": "rootfs", 
            "total": 16563.4, 
            "used": 1390.6
          }
        }, 
        "uptime": 72962, 
        "version": "0.8.4-5043040"
      }
    }
    
    

    FFprobe from your camera (Virtually identical for both cameras.)

    # ffprobe rtsp://username:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1
    # ffprobe version 4.3.1 Copyright (c) 2007-2020 the FFmpeg developers
      built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04)
      configuration: --disable-debug --disable-doc --disable-ffplay --enable-shared --enable-avresample --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-gpl --enable-libfreetype --enable-libvidstab --enable-libmfx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxcb --enable-libx265 --enable-libxvid --enable-libx264 --enable-nonfree --enable-openssl --enable-libfdk_aac --enable-postproc --enable-small --enable-version3 --enable-libzmq --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-libopenjpeg --enable-libkvazaar --enable-libaom --extra-libs=-lpthread --enable-vaapi --extra-cflags=-I/opt/ffmpeg/include --extra-ldflags=-L/opt/ffmpeg/lib
      libavutil      56. 51.100 / 56. 51.100
      libavcodec     58. 91.100 / 58. 91.100
      libavformat    58. 45.100 / 58. 45.100
      libavdevice    58. 10.100 / 58. 10.100
      libavfilter     7. 85.100 /  7. 85.100
      libavresample   4.  0.  0 /  4.  0.  0
      libswscale      5.  7.100 /  5.  7.100
      libswresample   3.  7.100 /  3.  7.100
      libpostproc    55.  7.100 / 55.  7.100
    Input #0, rtsp, from 'rtsp://username:[email protected]:554/Streaming/Channels/101?transportmode=unicast':
      Metadata:
        title           : Media Presentation
      Duration: N/A, start: 0.000000, bitrate: N/A
        Stream #0:0: Video: hevc, yuvj420p(pc), 3840x2160 [SAR 1:1 DAR 16:9], 14.99 tbr, 90k tbn, 90k tbc
        Stream #0:1: Audio: aac, 16000 Hz, mono, fltp
    

    Screenshots image image image

    Computer Hardware

    • OS: UnRAID (Linux)
    • Install method: HASSIO - VM (On UnRAID Server 1); Frigate - Docker Container (On UnRAID Server 2)
    • Virtualization: HASSIO VM
    • Coral Version: PCIe (On UnRAID Server 2)
    • Network Setup: Wired

    Camera Info:

    • Manufacturer: Annke
    • Model: C800
    • Resolution: 2160p
    • FPS: 15
    stale 
    opened by pr0927 91
  • [Support]: 0.11.0 Release Candidate 2 Memory Leak

    [Support]: 0.11.0 Release Candidate 2 Memory Leak

    Describe the problem you are having

    seems to be another memory leak in 0.11.0 Release Candidate 2. Anyone else seeing this?

    Version

    0.11.0 Release Candidate 2

    Frigate config file

    mqtt:
      host: 192.168.**.**
      user: *******
      password: *******
    
    #detectors:
    #  coral:
    #    type: edgetpu
    #    device: usb
    
    detectors:
      cpu1:
        type: cpu
        num_threads: 2
      cpu2:
        type: cpu
        num_threads: 2
      cpu3:
        type: cpu
        num_threads: 2
    
    birdseye:
      enabled: true
      width: 640
      height: 360
      quality: 1
      mode: motion
    
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      crop: false
      retain:
        default: 14
    
    # Optional: logger verbosity settings
    logger:
      # Optional: Default log verbosity (default: shown below)
      default: info
      # Optional: Component specific logger overrides
    #  logs:
    #    frigate.event: debug
    record:
      # Optional: Enable recording (default: shown below)
      enabled: true
      # Optional: Number of days to retain recordings regardless of events (default: shown below)
      # NOTE: This should be set to 0 and retention should be defined in events section below
      #       if you only want to retain recordings of events.
      retain:
        days: 7
        mode: motion
      # Optional: Event recording settings
      events:
        # Optional: Maximum length of time to retain video during long events. (default: shown below)
        # NOTE: If an object is being tracked for longer than this amount of time, the retained recordings
        #       will be the last x seconds of the event unless retain_days under record is > 0.
    #    max_seconds: 300
        # Optional: Number of seconds before the event to include (default: shown below)
        pre_capture: 60
        # Optional: Number of seconds after the event to include (default: shown below)
        post_capture: 60
        # Optional: Objects to save recordings for. (default: all tracked objects)
        objects:
          - person
        # Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones)
        required_zones: []
        # Optional: Retention settings for recordings of events
        retain:
          # Required: Default retention days (default: shown below)
    #      default: 10
          # Optional: Per object retention days
          default: 14
          mode: active_objects
          objects:
            person: 14
    rtmp:
      enabled: true
    
    #objects:
    #  track:
    #    - person
    #  filters:
    #    person:
    #      min_score: 0.4
    #      threshold: 0.6
    
    cameras:
      front_camera: # <------ Name the camera
        ffmpeg:
          hwaccel_args:
            - -hwaccel
            - vaapi
            - -hwaccel_device
            - /dev/dri/renderD128
            - -hwaccel_output_format
            - yuv420p
          inputs:
            - path: rtsp://user:[email protected]:port/Streaming/channels/102 # <----- Update for your camera
              roles:
                - detect
                - rtmp
    #            - record
            - path: rtsp://user:[email protected]:port/Streaming/channels/101 # <----- Update for your camera
              roles:
                - record
        detect:
          width: 640 # <---- update for your camera's resolution
          height: 360 # <---- update for your camera's resolution
          fps: 6
          max_disappeared: 25
          stationary:
            interval: 0
            threshold: 50
            max_frames: 
              default: 3000
              objects:
                person: 1000
        best_image_timeout: 30
        objects:
          track:
            - person
          filters:
            person:
              min_score: 0.4
              threshold: 0.5
              mask: 
                - 96,80,109,110,76,123,56,95 # Tree
                - 65,120,111,106,95,82,67,90 # Small Shrub by porch/driveway
                - 150,106,166,95,155,69,139,74 # mailbox
                - 25,35,212,37,210,22,26,22 # date and time
        zones:
          front_porch:
            coordinates: 640,131,640,0,412,0,431,128
    #        filters:
    #          person:
    #            min_score: 0.3
    #            threshold: 0.4
          house:
            coordinates: 0,212,315,0,0,0
    #        filters:
    #          person:
    #            min_area: 200
    #            max_area: 1000
    ##            min_score: 0.4
    #            threshold: 0.6
          driveway:
            coordinates: 134,193,0,311,51,360,640,360,640,240
    #        filters:
    #          person:
    #            min_score: 0.3
    #            threshold: 0.4
        motion:
          contour_area: 50
    #      threshold: 35
          mask:
            - 25,35,212,37,210,22,26,22 # date and time
            - 546,332,542,308,463,307,463,331 # camera name
          improve_contrast: true
    
      front_camera_2: # <------ Name the camera
        ffmpeg:
          hwaccel_args:
            - -hwaccel
            - vaapi
            - -hwaccel_device
            - /dev/dri/renderD128
            - -hwaccel_output_format
            - yuv420p
          inputs:
            - path: rtsp://user:[email protected]:port/Streaming/channels/102 # <----- Update for your camera
              roles:
                - detect
                - rtmp
    #            - record
            - path: rtsp://user:[email protected]:port/Streaming/channels/101 # <----- Update for your camera
              roles:
                - record
        detect:
          width: 640 # <---- update for your camera's resolution
          height: 360 # <---- update for your camera's resolution
          fps: 6
          max_disappeared: 25
          stationary:
            interval: 0
            threshold: 50
            max_frames: 
              default: 3000
              objects:
                person: 1000
        best_image_timeout: 30
        objects:
          track:
            - person
          filters:
            person:
              max_area: 5000
              min_score: 0.4
              threshold: 0.55 # Raised from .55 to .58 on 12/25
              mask: 
                - 371,53,370,79,357,77,356,57 # mailbox
                - 26,43,221,39,210,22,26,22 # Date and Time
                - 165,149,174,177,143,179,141,156 # Small bush is front of walkway ( added 12/25 )
                - 218,200,217,235,157,253,155,211 # Large bush in Side Yard (added 12/25)
                - 465,306,563,308,559,334,457,331 # Camera Name
                - 88,0,90,67,0,65,0,0 # Top Left Corner
        zones:
          side_yard:
            coordinates: 0,0,73,0,85,93,376,214,244,306,325,360,0,360
    #        filters:
    #          person:
    #            max_area: 3200
    ##            min_score: 0.5
    #            threshold: 0.7
          driveway:
            coordinates: 523,360,326,360,245,307,432,174,596,223
    #        filters:
    #          person:
    #            min_score: 0.3
    #            threshold: 0.4
          m_and_d:
            coordinates: 640,0,424,0,418,21,285,68,640,146
    #        filter:
    #          person:
    #            min_area: 253
    ##            min_score: 0.4
    #            threshold: 0.6
        motion:
          contour_area: 50
    #      threshold: 35 #changed from 45
    #      frame_alpha: 0.3
          mask:
            - 26,43,221,39,210,22,26,22 # Date and Time
            - 465,306,563,308,559,334,457,331 # Camera Name
          improve_contrast: true
    
      back_camera: # <------ Name the camera
        ffmpeg:
          hwaccel_args:
            - -hwaccel
            - vaapi
            - -hwaccel_device
            - /dev/dri/renderD128
            - -hwaccel_output_format
            - yuv420p
          inputs:
            - path: rtsp://user:[email protected]:port/Streaming/channels/102 # <----- Update for your camera
              roles:
                - detect
                - rtmp
    #            - record
            - path: rtsp://user:[email protected]:port/Streaming/channels/101 # <----- Update for your camera
              roles:
                - record
        detect:
          width: 640 # <---- update for your camera's resolution
          height: 360 # <---- update for your camera's resolution
          fps: 6
          max_disappeared: 25
          stationary:
            interval: 0
            threshold: 50
            max_frames: 
              default: 3000
              objects:
                person: 1000
        best_image_timeout: 30
        objects:
          track:
            - person
          filters:
            person:
              min_area: 675
              max_area: 15000
              min_score: 0.3
              threshold: 0.5
              mask: 
                - 214,147,243,145,239,120,215,122 # small shrub in front of patio
                - 546,332,542,308,463,307,463,331 # camera name
        zones:
          patio:
            coordinates: 80,360,320,243,92,77,0,104
    #        filters:
    #          person:
    #            min_score: 0.3
    #            threshold: 0.4
          yard:
            coordinates: 321,244,93,78,0,103,0,0,640,0,640,360,81,361
    #        filters:
    #          person:
    ##            min_score: 0.4
    #            threshold: 0.6
        motion:
    #      contour_area: 40
          mask:
            - 25,35,212,37,210,22,26,22 # Date and Time
            - 546,332,542,308,463,307,463,331 # Camera Name
          improve_contrast: true
    

    Relevant log output

    none
    

    FFprobe output from your camera

    will work on this if needed
    

    Frigate stats

    No response

    Operating system

    Debian

    Install method

    Docker Compose

    Coral version

    CPU (no coral)

    Network connection

    Wired

    Camera make and model

    Hiks DS-2CD2142FWD-IS

    Any other information that may be helpful

    none

    support triage 
    opened by pdobrien3 74
  • [Support]: No space left on device

    [Support]: No space left on device

    Describe the problem you are having

    My "docker host" slowly dies. Then it crashes frigate. I have added extra disk space but that also is filled with something but I can't detect what is causing this. I have this issue after recently updating frigate container.

    Version

    0.9.1-800f33e

    Frigate config file

    birdseye:
      enabled: True
      width: 1280
      height: 720
      quality: 8
      mode: objects
    
    database:
      path: /media/frigate/db/frigate.db
    
    ffmpeg:
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p
    
    record:
      enabled: true
      retain_days: 10
      events:
        retain:
          default: 14
    
    
    # MQTT Config ##########################################################################################################
    mqtt:
      host: 192.168.1.142
      port: 1883
      topic_prefix: frigate112
      client_id: frigate112
      user: mqtt
      password: mqtt
      stats_interval: 60
    
    # Cameras Config ######################################################################################################
    cameras:
    # FRONT Camera ########################################################################################################
      front:
        ffmpeg:
          inputs:
            - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
              roles:
                - detect
                - record
        detect:
          enabled: True
          max_disappeared: 2
          width: 2560
          height: 1440
          fps: 6
        snapshots:
          enabled: true
          crop: false
          bounding_box: True
        objects:
          track:
            - person
            - dog
            - cat
        motion:
          mask:
            - '1090,81,1216,0,1382,34,1532,99,1518,259,1426,363,1123,247'
            - '1766,498,1753,669,1778,722,1829,773,1863,825,1906,884,1924,955,1953,1065,2237,1169,2255,1128,2295,1046,2338,946,2378,841,2410,743,2215,647,2190,582,2138,512,2010,402,1859,351'
    
    # Back Camera ########################################################################################################
      back:
        ffmpeg:
          inputs:
            - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
              roles:
                - detect
                - record
        detect:
          enabled: True
          max_disappeared: 2
          width: 2048
          height: 1536
          fps: 4
        snapshots:
          enabled: true
          crop: false
          bounding_box: True
        objects:
          track:
            - person
            - car
            - dog
            - bicycle
            - cat
          filters:
            car:
              min_score: 0.5
              threshold: 0.7
              mask:
                - '276,374,440,126,467,0,808,0,781,103,697,367'
                - '1723,199,2048,354,2048,585,1128,396,1086,128,1115,27'
    
    # PARKING Camera ########################################################################################################
      parkeing:
        ffmpeg:
          inputs:
            - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
              roles:
                - detect
                - record
        detect:
          enabled: True
          max_disappeared: 2
          width: 3840
          height: 2160
          fps: 6
        snapshots:
          enabled: true
          crop: false
          bounding_box: True
        objects:
          track:
            - person
            - car
            - dog
            - bicycle
        motion:
          mask:
            - '2868,0,2839,240,2812,276,2775,329,2740,783,3840,1037,3840,0'
            - '2261,174,2190,154,2140,142,2096,133,2053,124,2002,122,1968,101,1914,71,1868,58,1817,56,1768,58,1716,69,1689,99,1642,100,1596,117,1566,137,1471,135,1419,162,1378,217,1364,278,1402,344,1474,393,1582,391,1652,347,1710,350,1786,361,1879,347,1991,328,2022,307,2046,289,2046,205,2074,189,2157,201,2154,330,2249,282'
            - '0,1896,153,2081,298,2049,403,1941,436,1839,439,1685,326,1492,142,1419,0,1531'
            - '1130,217,1265,271,519,597,1122,744,1104,990,1016,1049,464,838,426,620,415,564,412,494'
            - '398,490,483,455,605,416,730,372,754,339,751,233,744,167,695,122,645,105,569,99,497,110,441,119,365,189'
        zones:  
            parkeerplaats_voortuin_zone:
                coordinates: 297,2160,3840,2160,3840,1074,2754,786,2768,451,2128,325,1298,258,428,614,515,1002,620,1335,372,1573
    
    # FRONT2 Camera ########################################################################################################
      front2:
        ffmpeg:
          inputs:
            - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
              roles:
                - detect
                - record
    
        detect:
          enabled: True
          max_disappeared: 25
          width: 3840
          height: 2160
          fps: 6
        
        snapshots:
          enabled: true
          crop: false
          bounding_box: True
        objects:
          track:
            - person
            - car
            - dog
            - bicycle
            - cat
            - truck
        motion:
          mask:
            - '3840,751,3840,386,3560,283,3482,341,3275,293,3150,302,3102,481,2948,460,2937,541,2978,714,3306,1422,3714,1413,3840,1647'
            - '1961,892,1907,871,1876,878,1844,867,1787,874,1689,914,1569,896,1486,881,1417,829,1413,736,1374,606,1345,415,1456,293,2344,337,2319,507,2199,499,2194,610,2244,655,2249,786,2213,881,2160,900,2111,921,2024,928'
            - '553,1714,670,1791,726,1866,747,1950,1879,2160,548,2160,466,1880'
            - '265,1437,428,1486,496,1568,426,1728,351,1672,190,1571,222,1502'
            - '1508,0,1586,77,1587,194,1561,229,1493,268,1416,312,1342,304,1225,276,1182,201,1196,86,1274,0'
            - '560,1410,658,1426,739,1490,832,1590,872,1716,879,1823,839,1901,726,1889,661,1816,588,1744,510,1691,506,1539'
            - '499,1508,584,1357,683,1222,682,1155,665,1066,627,987,566,889,491,821,389,803,270,829,176,872,64,966,0,1055,21,1190,63,1323,151,1413,194,1449'
    
    # TERRAS Camera ########################################################################################################
      terras:
        ffmpeg:
          inputs:
            - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
              roles:
                - detect
                - record
        detect:
          enabled: True
          max_disappeared: 25
          width: 3840
          height: 2160
          fps: 4
        snapshots:
          timestamp: False
          bounding_box: True
          enabled: true
          crop: false
        objects:
          track:
            - bird
            - dog
            - cat
        motion:
          mask:    
            - '3840,0,3840,1295,3138,1412,3034,769,2958,382,2622,0'
            - '0,652,178,384,444,137,598,303,416,496,104,819,25,777'
            - '0,161,64,242,180,248,248,264,354,178,455,92,532,0,0,0'
          threshold: 25
    
    detectors:
      coral:
        type: edgetpu
        device: usb
    

    Relevant log output

    "no space left on device"
    

    FFprobe output from your camera

    NA
    

    Frigate stats

    NA
    

    Operating system

    Proxmox

    Install method

    Docker CLI

    Coral version

    USB

    Network connection

    Wired

    Camera make and model

    NA

    Any other information that may be helpful

    [email protected] /tmp# df -h
    Filesystem                        Size  Used Avail Use% Mounted on
    /dev/mapper/pve-vm--108--disk--0   47G   39G  6.7G  86% /
    none                              492K  4.0K  488K   1% /dev
    udev                              7.8G     0  7.8G   0% /dev/bus/usb/002
    tmpfs                             7.8G     0  7.8G   0% /dev/shm
    tmpfs                             7.8G  743M  7.1G  10% /run
    tmpfs                             5.0M     0  5.0M   0% /run/lock
    tmpfs                             7.8G     0  7.8G   0% /sys/fs/cgroup
    shm                               256M     0  256M   0% /var/lib/docker/containers/1eb1f0039cdf20412515def8d06b6580d49939a9a852a3af4e9ed625f62eec7b/mounts/shm
    //192.168.3.99/frigate/clips       28T  6.7T   22T  24% /shared/frigate/clips
    shm                               256M     0  256M   0% /var/lib/docker/containers/d581a1b12406181e8f52cfc6cef3f66a7cf0c8edf2382cd35f3c9f170c35e983/mounts/shm
    shm                               1.0G   47M  978M   5% /var/lib/docker/containers/400149611d5daa0d983f2863065ba9b7325daee5f7e2c1a38921d4ccf7e23d40/mounts/shm
    
    support stale triage 
    opened by sanderlv 74
  • [Support]: Unable to playback h265 recordings in modern interface.

    [Support]: Unable to playback h265 recordings in modern interface.

    Describe the problem you are having

    Unable to playback h265 clips and recordings in the updated viewer. Works fine with older (0.8.4) version. Browsers throws an error, and has to be refeshed to select anything else on the page. "Playback cannot continue. No available working or supported playlists."

    Tested on version 0.8.4 the file plays - Section information is:

    The home / non working one shows:

    The video URL allows the file to playback with no problems. http://192.168.12.207:5000/api/events/1642372025.240855-6tjtap/clip.mp4

    streaming is working fine in the browser, and i can see a live view.

    Version

    Tested on 0.9.4 and 0.10.0

    Frigate config file

    mqtt:
      host: 192.168.12.201
      port: 1883
    detectors:
      coral1:
        type: edgetpu
        device: pci
      coral2:
        type: edgetpu
        device: pci:1
    snapshots:
      retain:
        default: 1
    database:
      path: /media/frigate/clips/database/frigate.db
    objects:
      track:
        - person
    record:
      enabled: true
      retain_days: 0
      events:
        max_seconds: 300
        pre_capture: 5
        post_capture: 20
        retain:
          default: 1
    logger:
      default: warning
    cameras:
      porch:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:554/Streaming/Channels/102
              roles:
                - detect
            - path: rtsp://USER:[email protected]:554/Streaming/Channels/101
              roles:
                - record
        detect:        
          width: 640
          height: 480
          fps: 8
        record:
          enabled: true
          retain_days: 1
          events:
            max_seconds: 300
            pre_capture: 15
            post_capture: 45
            retain:
              default: 1
        rtmp:
          enabled: False
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
        motion:
          mask:
          - 545,480,640,480,640,420,578,448
      diningroom:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:8554/live1.264
              roles:
                - detect
            - path: rtsp://USER:[email protected]:8554/live0.264
              roles:
                - record
        rtmp:
          enabled: False
        detect:        
          width: 768
          height: 432
          fps: 8
        record:
          enabled: true
          retain_days: 0
          events:
            retain:
              default: 1
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
      bedroom:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:8554/live1.264
              roles:
                - detect
            - path: rtsp://USER:[email protected]:8554/live0.264
              roles:
                - record
        detect:        
          width: 768
          height: 432
          fps: 8
        record:
          enabled: true
          retain_days: 0
          events:
            retain:
              default: 1
        rtmp:
          enabled: False
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
      livingroom:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:8554/live1.264
              roles:
                - detect
            - path: rtsp://USER:[email protected]:8554/live0.264
              roles:
                - record
        detect:        
          width: 768
          height: 432
          fps: 8
        record:
          enabled: true
          retain_days: 0
          events:
            retain:
              default: 1
        rtmp:
          enabled: False
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
      landing:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:8554/live1.264
              roles:
                - detect
            - path: rtsp://USER:[email protected]:8554/live0.264
              roles:
                - record
        detect:        
          width: 768
          height: 432
          fps: 8
        record:
          enabled: true
          retain_days: 0
          events:
            retain:
              default: 1
        rtmp:
          enabled: False
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
      kitchen:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:8554/unicast
              roles:
                - detect
                - record 
        detect:        
          width: 1280
          height: 720
          fps: 8
        record:
          enabled: true
          retain_days: 0
          events:
            retain:
              default: 1
        rtmp:
          enabled: False
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
      backdoor:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:8554/unicast
              roles:
                - detect
                - record 
        detect:        
          width: 1280
          height: 720
          fps: 8
        record:
          enabled: true
          retain_days: 0
          events:
            retain:
              default: 1
        rtmp:
          enabled: False
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
      babycam:
        ffmpeg:
          inputs:
            - path: rtsp://USER:[email protected]:8554/unicast
              roles:
                - detect
                - record 
        detect:        
          width: 1280
          height: 720
          fps: 8
        zones:
          cot:
            coordinates: 361,669,956,660,949,376,368,382
        objects:
          filters:
            person:
              min_score: 0.4
              threshold: 0.5
        record:
          enabled: true
          retain_days: 1
          events:
            retain:
              default: 1
        rtmp:
          enabled: False
        snapshots:
          enabled: True
        mqtt:
          enabled: True
          timestamp: True
          crop: True
    

    Relevant log output

    access.log:
    192.168.10.123 - - [16/Jan/2022:23:26:49 +0000] "GET /api/events/1642372025.240855-6tjtap HTTP/1.1" 200 5604 "http://192.168.12.207:5000/events?camera=porch" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36 Edg/97.0.1072.55" "-"
    192.168.10.123 - - [16/Jan/2022:23:26:49 +0000] "GET /api/events/1642372025.240855-6tjtap/snapshot.jpg HTTP/1.1" 200 27832 "http://192.168.12.207:5000/events?camera=porch" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36 Edg/97.0.1072.55" "-"
    192.168.12.202 - - [16/Jan/2022:23:27:26 +0000] "GET /api/stats HTTP/1.1" 200 1556 "-" "HomeAssistant/2021.12.8 aiohttp/3.8.1 Python/3.9" "-"
    
    error.log:
    2022/01/16 22:18:30 [error] 202#202: *7 no live upstreams while connecting to upstream, client: 192.168.10.123, server: , request: "GET /api/config HTTP/1.1", upstream: "http://frigate_api/config", host: "192.168.12.207:5000", referrer: "http://192.168.12.207:5000/events?camera=porch"
    

    FFprobe output from your camera

    ffprobe version 4.3.1 Copyright (c) 2007-2020 the FFmpeg developers
      built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04)
      configuration: --disable-debug --disable-doc --disable-ffplay --enable-shared --enable-avresample --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-gpl --enable-libfreetype --enable-libvidstab --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxcb --enable-libx265 --enable-libxvid --enable-libx264 --enable-nonfree --enable-openssl --enable-libfdk_aac --enable-postproc --enable-small --enable-version3 --enable-libzmq --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-libopenjpeg --enable-libkvazaar --enable-libaom --extra-libs=-lpthread --enable-libsrt --enable-libaribb24 --enable-nvenc --enable-cuda --enable-cuvid --enable-libnpp --extra-cflags='-I/opt/ffmpeg/include -I/opt/ffmpeg/include/ffnvcodec -I/usr/local/cuda/include/' --extra-ldflags='-L/opt/ffmpeg/lib -L/usr/local/cuda/lib64 -L/usr/local/cuda/lib32/'
      libavutil      56. 51.100 / 56. 51.100
      libavcodec     58. 91.100 / 58. 91.100
      libavformat    58. 45.100 / 58. 45.100
      libavdevice    58. 10.100 / 58. 10.100
      libavfilter     7. 85.100 /  7. 85.100
      libavresample   4.  0.  0 /  4.  0.  0
      libswscale      5.  7.100 /  5.  7.100
      libswresample   3.  7.100 /  3.  7.100
      libpostproc    55.  7.100 / 55.  7.100
    Input #0, rtsp, from 'rtsp://USER:[email protected]:554/Streaming/Channels/101':
      Metadata:
        title           : Media Presentation
      Duration: N/A, start: 0.000000, bitrate: N/A
        Stream #0:0: Video: hevc, yuvj420p(pc), 3840x2160 [SAR 1:1 DAR 16:9], 12.50 tbr, 90k tbn, 90k tbc
        Stream #0:1: Audio: pcm_mulaw, 8000 Hz, 1 channels, s16, 64 kb/s
    

    Frigate stats

    No response

    Operating system

    UNRAID

    Install method

    Docker CLI

    Coral version

    PCIe

    Network connection

    Wired

    Camera make and model

    hikvision I91BM

    Any other information that may be helpful

    No response

    support stale triage 
    opened by karldonteljames 67
  • 'No space left on device' errors because tmpfs full

    'No space left on device' errors because tmpfs full

    Describe the bug Frigate has crashed again after a couple days running, throwing these errors for all cameras every 10 seconds.

    [2021-09-10 16:17:52] ffmpeg.Deck.record             ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device,
    [2021-09-10 16:17:52] ffmpeg.Deck.record             ERROR   : ,
    [2021-09-10 16:17:52] watchdog.Deck                  INFO    : Terminating the existing ffmpeg process...,
    [2021-09-10 16:17:52] watchdog.Deck                  INFO    : Waiting for ffmpeg to exit gracefully...,
    [2021-09-10 16:17:52] ffmpeg.Laundry.record          ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device,
    [2021-09-10 16:17:52] ffmpeg.Laundry.record          ERROR   : ,
    [2021-09-10 16:17:52] watchdog.Laundry               INFO    : Terminating the existing ffmpeg process...,
    [2021-09-10 16:17:52] watchdog.Laundry               INFO    : Waiting for ffmpeg to exit gracefully...,
    [2021-09-10 16:18:02] ffmpeg.Entrance.record         ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device,
    [2021-09-10 16:18:02] ffmpeg.Entrance.record         ERROR   : ,
    [2021-09-10 16:18:02] watchdog.Entrance              INFO    : Terminating the existing ffmpeg process...,
    [2021-09-10 16:18:02] watchdog.Entrance              INFO    : Waiting for ffmpeg to exit gracefully...,
    [2021-09-10 16:18:02] ffmpeg.Driveway.record         ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device,
    [2021-09-10 16:18:02] ffmpeg.Driveway.record         ERROR   : ,
    [2021-09-10 16:18:02] watchdog.Driveway              INFO    : Terminating the existing ffmpeg process...,
    [2021-09-10 16:18:02] watchdog.Driveway              INFO    : Waiting for ffmpeg to exit gracefully...,
    [2021-09-10 16:18:02] ffmpeg.Rumpus.record           ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device,
    [2021-09-10 16:18:02] ffmpeg.Rumpus.record           ERROR   : ,
    [2021-09-10 16:18:02] watchdog.Rumpus                INFO    : Terminating the existing ffmpeg process...,
    [2021-09-10 16:18:02] watchdog.Rumpus                INFO    : Waiting for ffmpeg to exit gracefully...,
    [2021-09-10 16:18:02] ffmpeg.Balcony.record          ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device,
    [2021-09-10 16:18:02] ffmpeg.Balcony.record          ERROR   : ,
    [2021-09-10 16:18:02] watchdog.Balcony               INFO    : Terminating the existing ffmpeg process...,
    [2021-09-10 16:18:02] watchdog.Balcony               INFO    : Waiting for ffmpeg to exit gracefully...,
    [2021-09-10 16:18:02] ffmpeg.Deck.record             ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device,
    [2021-09-10 16:18:02] ffmpeg.Deck.record             ERROR   : ,
    [2021-09-10 16:18:02] watchdog.Deck                  INFO    : Terminating the existing ffmpeg process...,
    [2021-09-10 16:18:02] watchdog.Deck                  INFO    : Waiting for ffmpeg to exit gracefully...,
    
    [email protected]:/opt/frigate# df -h
    Filesystem                     Size  Used Avail Use% Mounted on
    overlay                        233G   20G  201G   9% /
    tmpfs                           64M     0   64M   0% /dev
    shm                            300M   26M  275M   9% /dev/shm
    /dev/sda2                      233G   20G  201G   9% /labelmap.txt
    192.168.30.8:/storage/frigate  1.8T  449G  1.4T  26% /media/frigate
    tmpfs                          2.0G  2.0G     0 100% /tmp/cache
    tmpfs                          7.7G     0  7.7G   0% /proc/asound
    tmpfs                          7.7G     0  7.7G   0% /proc/acpi
    tmpfs                          7.7G     0  7.7G   0% /sys/firmware
    

    Version of frigate 0.9.0-6c28613

    Config file

    database:
      path: /media/frigate/database/frigate.db
    
    detectors:
      coral:
        type: edgetpu
        device: usb
    
    mqtt:
      host: 192.168.1.5
      port: 1883
      user: mqtt
      password: "{FRIGATE_MQTT_PASSWORD}"
    
    birdseye:
      mode: continuous
      width: 1792
      height: 1344
    
    detect:
      width: 896
      height: 672
      fps: 5
    
    ffmpeg:
      hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
      input_args: -avoid_negative_ts make_zero -flags low_delay -fflags nobuffer -fflags +genpts+discardcorrupt -rw_timeout 5000000 -strict experimental -use_wallclock_as_timestamps 1 -f live_flv
      output_args:
        record: -f segment -segment_time 30 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy # -an
    
    motion:
      mask:
        - 265,650,265,625,630,625,630,650
    
    record:
      enabled: true
      retain_days: 1
      events:
        enabled: true
        pre_capture: 3
        retain:
          default: 15
    
    snapshots:
      enabled: true
      clean_copy: false
      bounding_box: true
      retain:
        default: 15
    
    cameras:
      Driveway:
        ffmpeg:
          inputs:
            - path: http://192.168.1.71/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - detect
            - path: http://192.168.1.71/flv?port=1935&app=bcs&stream=channel0_main.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - record
        objects:
          filters:
            person:
              mask: 510,120,540,120,540,160,510,160
          track:
            - person
            - vehicle
            - dog
        rtmp:
          enabled: false
        timestamp_style:
          format: "%d/%m/%Y %H:%M:%S"
    
      Entrance:
        ffmpeg:
          inputs:
            - path: http://192.168.1.72/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - detect
            - path: http://192.168.1.72/flv?port=1935&app=bcs&stream=channel0_main.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - record
        objects:
          track:
            - person
            - dog
        rtmp:
          enabled: false
        timestamp_style:
          format: "%d/%m/%Y %H:%M:%S"
    
      Rumpus:
        ffmpeg:
          inputs:
            - path: http://192.168.1.73/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - detect
            - path: http://192.168.1.73/flv?port=1935&app=bcs&stream=channel0_main.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - record
        objects:
          track:
            - person
            - dog
        rtmp:
          enabled: false
        timestamp_style:
          format: "%d/%m/%Y %H:%M:%S"
    
      Deck:
        ffmpeg:
          inputs:
            - path: http://192.168.1.74/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - detect
            - path: http://192.168.1.74/flv?port=1935&app=bcs&stream=channel0_main.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - record
        objects:
          mask: 
            - 265,650,265,625,630,625,630,650
            - 0,585,29,592,60,617,74,672,0,672
          track:
            - person
        rtmp:
          enabled: false
        timestamp_style:
          format: "%d/%m/%Y %H:%M:%S"
    
      Laundry:
        ffmpeg:
          inputs:
            - path: http://192.168.1.75/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - detect
            - path: http://192.168.1.75/flv?port=1935&app=bcs&stream=channel0_main.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - record
        objects:
          track:
            - person
        rtmp:
          enabled: false
        timestamp_style:
          format: "%d/%m/%Y %H:%M:%S"
    
      Balcony:
        ffmpeg:
          inputs:
            - path: http://192.168.1.76/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - detect
            - path: http://192.168.1.76/flv?port=1935&app=bcs&stream=channel0_main.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
              roles:
                - record
        objects:
          track:
            - person
            - vehicle
        rtmp:
          enabled: false
        timestamp_style:
          format: "%d/%m/%Y %H:%M:%S"
    

    Frigate stats (After restart, as Frigate's web ui was not responding)

    {"Balcony":{"camera_fps":5.1,"capture_pid":256,"detection_fps":0.0,"pid":235,"process_fps":5.1,"skipped_fps":0.0},"Deck":{"camera_fps":5.1,"capture_pid":247,"detection_fps":3.2,"pid":233,"process_fps":5.1,"skipped_fps":0.0},"Driveway":{"camera_fps":5.1,"capture_pid":237,"detection_fps":0.0,"pid":228,"process_fps":5.1,"skipped_fps":0.0},"Entrance":{"camera_fps":5.1,"capture_pid":241,"detection_fps":0.0,"pid":230,"process_fps":5.1,"skipped_fps":0.0},"Laundry":{"camera_fps":5.1,"capture_pid":252,"detection_fps":0.0,"pid":234,"process_fps":5.1,"skipped_fps":0.0},"Rumpus":{"camera_fps":5.0,"capture_pid":243,"detection_fps":0.0,"pid":231,"process_fps":5.0,"skipped_fps":0.0},"detection_fps":3.2,"detectors":{"coral":{"detection_start":0.0,"inference_speed":13.15,"pid":219}},"service":{"storage":{"/dev/shm":{"free":306.5,"mount_type":"tmpfs","total":314.6,"used":8.1},"/media/frigate/clips":{"free":1447499.7,"mount_type":"nfs4","total":1921292.6,"used":473256.0},"/media/frigate/recordings":{"free":1447499.8,"mount_type":"nfs4","total":1921292.6,"used":473256.0},"/tmp/cache":{"free":1993.8,"mount_type":"tmpfs","total":2147.5,"used":153.6}},"uptime":98,"version":"0.9.0-6c28613"}}
    

    Computer Hardware

    • OS: Debian 11
    • Install method: Docker Compose
    • Coral Version: USB
    • Network Setup: Wired

    Camera Info:

    • Manufacturer: Reolink
    • Model: RLC-520A
    • Resolution: 5Mp
    • FPS: 5

    docker-compose.yml

    services:
      frigate:
        container_name: frigate-0.9
        image: blakeblackshear/frigate:0.9.0-6c28613-amd64
        hostname: frigate
        restart: always
        shm_size: '300m'
        devices:
          - /dev/dri/renderD128:/dev/dri/renderD128
          - /dev/bus/usb:/dev/bus/usb
        volumes:
          - /etc/localtime:/etc/localtime:ro
          - /usr/docker/frigate-0.9/config.yml:/config/config.yml:ro
          - /usr/docker/frigate-0.9/labelmap.txt:/labelmap.txt:ro
          - /usr/docker/frigate-0.9/database:/media/frigate/database
          - /mnt/nas/frigate:/media/frigate
          - type: tmpfs
            target: /tmp/cache
            tmpfs:
              size: '2gb'
        network_mode: bridge
        ports:
          - 0.0.0.0:5000:5000
        environment:
          FRIGATE_MQTT_PASSWORD: ""
          FRIGATE_USER: ""
          FRIGATE_PASSWORD: ""
          LIBVA_DRIVER_NAME: "radeonsi"
    
    opened by jasonpstokes 66
  • [Support]: Car/person detection during the day and only people at night?

    [Support]: Car/person detection during the day and only people at night?

    Describe the problem you are having

    I am only opening this as an issue because with the upcoming launch of Frigate+, I suspect this to be something people may request or want to achieve.

    I noticed that the way my camera is pointed is my driveway always gives me false alerts with parked cars so along with the power of Home Assistant, I configured my detectors to only be on when we are away and know that the cars are not there. I achieved that using location and a simple automation. The issue now is at night, I would like to turn on the detector but only allow the detector to pick up people, no cars as I know the cars will be there in the zone causing false alerts.

    Is this possible? For some reason, I can't think it through.

    Version

    0.10.0

    Frigate config file

    cameras:
      driveway_cam:
        rtmp:
          enabled: False
    
        ffmpeg:
          inputs:
            - path: rtsp://ha:[email protected]:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - detect
                - record
    
        detect:
          width: 3840
          height: 2160
          fps: 5
          enabled: True
    
        zones:
          driveway:
            coordinates: 2876,2160,2083,1823,1928,1413,2175,1308,3840,1746,3840,2160
            objects:
              - person
              - dog
              - car
    
        objects:
          track:
            - person
            - dog
            - car
          filters:
            person:
              # Optional: minimum width*height of the bounding box for the detected object (default: 0)
              min_area: 5000
              # Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
              max_area: 100000
              mask:
                - 0,0,0,2160,2098,2160,1928,1374,2690,948,3840,1130,3840,0
            car:
              # Optional: minimum width*height of the bounding box for the detected object (default: 0)
              min_area: 5000
              # Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
              max_area: 200000
              mask:
                - 0,0,0,2160,2098,2160,1928,1374,2690,948,3840,1130,3840,0
            dog:
              mask:
                - 0,0,0,2160,2098,2160,1928,1374,2690,948,3840,1130,3840,0
    
        motion:
          # Increasing this value will make motion detection less sensitive
          # threshold: 30
          # default 25
    
          # Minimum size in pixels in the resized motion image that counts as motion.
          # Increasing this value will prevent smaller areas of motion from being detected. Decreasing will
          # make motion detection more sensitive to smaller moving objects.
          # As a rule of thumb:
          #  - 15 - high sensitivity
          #  - 30 - medium sensitivity
          #  - 50 - low sensitivity
          contour_area: 35
          # default: 30
    
          mask:
           - 0,0,0,2160,2098,2160,1928,1374,2690,948,3840,1130,3840,0
    
        record:
          enabled: True
          retain:
            days: 7
            mode: motion
          events:
            max_seconds: 240
            pre_capture: 5
            post_capture: 5
            retain:
              default: 7
              mode: active_objects
            objects:
              - person
              - car
              - dog
            required_zones:
              - driveway
    
        snapshots:
          enabled: True
          timestamp: True
          bounding_box: True
          crop: False
          required_zones:
            - driveway
          retain:
            default: 7
    #####
    
    mqtt:
      host: 192.168.141.21
      user: REDACTED
      password: REDACTED
    
    detectors:
      coral:
        type: edgetpu
        device: usb
    
    database:
      path: /db/frigate.db
    
    snapshots:
      enabled: True
      timestamp: True
      bounding_box: True
      crop: False
      required_zones: []
      retain:
        default: 7
    
    model:
      labelmap:
        15: animal
        16: animal
        17: animal
        18: animal
        19: animal
        20: animal
        21: animal
        22: animal
        23: animal
        24: animal
    
    birdseye:
      enabled: False
      # width: 1920
      # height: 1080
      # quality: 8
      # mode: motion
    

    Relevant log output

    NA
    

    FFprobe output from your camera

    NA
    

    Frigate stats

    No response

    Operating system

    Debian

    Install method

    Docker Compose

    Coral version

    USB

    Network connection

    Wired

    Camera make and model

    Amcrest 4K

    Any other information that may be helpful

    No response

    support stale triage 
    opened by junior466 64
  • [Support]: It was working fine until Oct 30th and suddenly stopped

    [Support]: It was working fine until Oct 30th and suddenly stopped

    Describe the problem you are having

    Frigate was recording perfectly fine on Oct 30th 2021 but since then, it keeps throwing errors. Yesterday there was an error about there being no space left on device, I restarted and this went away, I went to bed, woke up now to Frigate throwing other errors. Please help!

    Version

    0.9.4-26AE608

    Frigate config file

    {
      "birdseye": {
        "enabled": true,
        "height": 720,
        "mode": "continuous",
        "quality": 8,
        "width": 1280
      },
      "cameras": {
        "frigate_backyard": {
          "best_image_timeout": 60,
          "detect": {
            "enabled": true,
            "fps": 5,
            "height": 972,
            "max_disappeared": 25,
            "width": 1296
          },
          "ffmpeg": {
            "global_args": "-hide_banner -loglevel warning",
            "hwaccel_args": [],
            "input_args": "-avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1",
            "inputs": [
              {
                "global_args": [],
                "hwaccel_args": [],
                "input_args": [],
                "path": "rtsp://x.x.x.x:8554/cam4_ch1",
                "roles": [
                  "record",
                  "rtmp",
                  "detect"
                ]
              }
            ],
            "output_args": {
              "detect": "-f rawvideo -pix_fmt yuv420p",
              "record": "-f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an",
              "rtmp": "-c copy -f flv"
            }
          },
          "ffmpeg_cmds": [
            {
              "cmd": "ffmpeg -hide_banner -loglevel warning -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 -i rtsp://x.x.x.x:8554/cam4_ch1 -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an /tmp/cache/frigate_backyard-%Y%m%d%H%M%S.mp4 -r 5 -s 1296x972 -f rawvideo -pix_fmt yuv420p pipe:",
              "roles": [
                "record",
                "rtmp",
                "detect"
              ]
            }
          ],
          "live": {
            "height": 720,
            "quality": 8
          },
          "motion": {
            "contour_area": 100,
            "delta_alpha": 0.2,
            "frame_alpha": 0.2,
            "frame_height": 180,
            "mask": "",
            "threshold": 25
          },
          "mqtt": {
            "bounding_box": false,
            "crop": true,
            "enabled": true,
            "height": 500,
            "quality": 100,
            "required_zones": [],
            "timestamp": true
          },
          "name": "frigate_backyard",
          "objects": {
            "filters": {
              "cat": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "dog": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "knife": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "person": {
                "mask": null,
                "max_area": 100000,
                "min_area": 5000,
                "min_score": 0.5,
                "threshold": 0.7
              }
            },
            "mask": "",
            "track": [
              "person",
              "dog",
              "cat",
              "knife"
            ]
          },
          "record": {
            "enabled": true,
            "events": {
              "max_seconds": 300,
              "objects": null,
              "post_capture": 5,
              "pre_capture": 5,
              "required_zones": [],
              "retain": {
                "default": 10,
                "objects": {}
              }
            },
            "retain_days": 1
          },
          "rtmp": {
            "enabled": false
          },
          "snapshots": {
            "bounding_box": false,
            "clean_copy": true,
            "crop": false,
            "enabled": false,
            "height": null,
            "quality": 70,
            "required_zones": [],
            "retain": {
              "default": 7,
              "objects": {
                "person": 7
              }
            },
            "timestamp": true
          },
          "timestamp_style": {
            "color": {
              "blue": 0,
              "green": 255,
              "red": 255
            },
            "effect": "shadow",
            "format": "%m/%d/%Y %H:%M:%S",
            "position": "tl",
            "thickness": 1
          },
          "zones": {}
        },
        "frigate_street_front": {
          "best_image_timeout": 60,
          "detect": {
            "enabled": true,
            "fps": 5,
            "height": 972,
            "max_disappeared": 25,
            "width": 1296
          },
          "ffmpeg": {
            "global_args": "-hide_banner -loglevel warning",
            "hwaccel_args": [],
            "input_args": "-avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1",
            "inputs": [
              {
                "global_args": [],
                "hwaccel_args": [],
                "input_args": [],
                "path": "rtsp://x.x.x.x:8554/cam2_ch1",
                "roles": [
                  "record",
                  "rtmp",
                  "detect"
                ]
              }
            ],
            "output_args": {
              "detect": "-f rawvideo -pix_fmt yuv420p",
              "record": "-f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an",
              "rtmp": "-c copy -f flv"
            }
          },
          "ffmpeg_cmds": [
            {
              "cmd": "ffmpeg -hide_banner -loglevel warning -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 -i rtsp://x.x.x.x:8554/cam2_ch1 -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an /tmp/cache/frigate_street_front-%Y%m%d%H%M%S.mp4 -r 5 -s 1296x972 -f rawvideo -pix_fmt yuv420p pipe:",
              "roles": [
                "record",
                "rtmp",
                "detect"
              ]
            }
          ],
          "live": {
            "height": 720,
            "quality": 8
          },
          "motion": {
            "contour_area": 100,
            "delta_alpha": 0.2,
            "frame_alpha": 0.2,
            "frame_height": 180,
            "mask": "",
            "threshold": 25
          },
          "mqtt": {
            "bounding_box": false,
            "crop": true,
            "enabled": true,
            "height": 500,
            "quality": 100,
            "required_zones": [],
            "timestamp": true
          },
          "name": "frigate_street_front",
          "objects": {
            "filters": {
              "cat": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "dog": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "knife": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "person": {
                "mask": null,
                "max_area": 100000,
                "min_area": 5000,
                "min_score": 0.5,
                "threshold": 0.7
              }
            },
            "mask": "",
            "track": [
              "person",
              "dog",
              "cat",
              "knife"
            ]
          },
          "record": {
            "enabled": true,
            "events": {
              "max_seconds": 300,
              "objects": null,
              "post_capture": 5,
              "pre_capture": 5,
              "required_zones": [],
              "retain": {
                "default": 10,
                "objects": {}
              }
            },
            "retain_days": 1
          },
          "rtmp": {
            "enabled": false
          },
          "snapshots": {
            "bounding_box": false,
            "clean_copy": true,
            "crop": false,
            "enabled": false,
            "height": null,
            "quality": 70,
            "required_zones": [],
            "retain": {
              "default": 7,
              "objects": {
                "person": 7
              }
            },
            "timestamp": true
          },
          "timestamp_style": {
            "color": {
              "blue": 0,
              "green": 255,
              "red": 255
            },
            "effect": "shadow",
            "format": "%m/%d/%Y %H:%M:%S",
            "position": "tl",
            "thickness": 1
          },
          "zones": {}
        },
        "frigate_street_nw": {
          "best_image_timeout": 60,
          "detect": {
            "enabled": true,
            "fps": 5,
            "height": 972,
            "max_disappeared": 25,
            "width": 1296
          },
          "ffmpeg": {
            "global_args": "-hide_banner -loglevel warning",
            "hwaccel_args": [],
            "input_args": "-avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1",
            "inputs": [
              {
                "global_args": [],
                "hwaccel_args": [],
                "input_args": [],
                "path": "rtsp://x.x.x.x:8554/cam3_ch1",
                "roles": [
                  "record",
                  "rtmp",
                  "detect"
                ]
              }
            ],
            "output_args": {
              "detect": "-f rawvideo -pix_fmt yuv420p",
              "record": "-f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an",
              "rtmp": "-c copy -f flv"
            }
          },
          "ffmpeg_cmds": [
            {
              "cmd": "ffmpeg -hide_banner -loglevel warning -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 -i rtsp://x.x.x.x:8554/cam3_ch1 -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an /tmp/cache/frigate_street_nw-%Y%m%d%H%M%S.mp4 -r 5 -s 1296x972 -f rawvideo -pix_fmt yuv420p pipe:",
              "roles": [
                "record",
                "rtmp",
                "detect"
              ]
            }
          ],
          "live": {
            "height": 720,
            "quality": 8
          },
          "motion": {
            "contour_area": 100,
            "delta_alpha": 0.2,
            "frame_alpha": 0.2,
            "frame_height": 180,
            "mask": "",
            "threshold": 25
          },
          "mqtt": {
            "bounding_box": false,
            "crop": true,
            "enabled": true,
            "height": 500,
            "quality": 100,
            "required_zones": [],
            "timestamp": true
          },
          "name": "frigate_street_nw",
          "objects": {
            "filters": {
              "cat": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "dog": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "knife": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "person": {
                "mask": null,
                "max_area": 100000,
                "min_area": 5000,
                "min_score": 0.5,
                "threshold": 0.7
              }
            },
            "mask": "",
            "track": [
              "person",
              "dog",
              "cat",
              "knife"
            ]
          },
          "record": {
            "enabled": true,
            "events": {
              "max_seconds": 300,
              "objects": null,
              "post_capture": 5,
              "pre_capture": 5,
              "required_zones": [],
              "retain": {
                "default": 10,
                "objects": {}
              }
            },
            "retain_days": 1
          },
          "rtmp": {
            "enabled": false
          },
          "snapshots": {
            "bounding_box": false,
            "clean_copy": true,
            "crop": false,
            "enabled": false,
            "height": null,
            "quality": 70,
            "required_zones": [],
            "retain": {
              "default": 7,
              "objects": {
                "person": 7
              }
            },
            "timestamp": true
          },
          "timestamp_style": {
            "color": {
              "blue": 0,
              "green": 255,
              "red": 255
            },
            "effect": "shadow",
            "format": "%m/%d/%Y %H:%M:%S",
            "position": "tl",
            "thickness": 1
          },
          "zones": {}
        },
        "frigate_street_se": {
          "best_image_timeout": 60,
          "detect": {
            "enabled": true,
            "fps": 5,
            "height": 972,
            "max_disappeared": 25,
            "width": 1296
          },
          "ffmpeg": {
            "global_args": "-hide_banner -loglevel warning",
            "hwaccel_args": [],
            "input_args": "-avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1",
            "inputs": [
              {
                "global_args": [],
                "hwaccel_args": [],
                "input_args": [],
                "path": "rtsp://x.x.x.x:8554/cam1_ch1",
                "roles": [
                  "record",
                  "rtmp",
                  "detect"
                ]
              }
            ],
            "output_args": {
              "detect": "-f rawvideo -pix_fmt yuv420p",
              "record": "-f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an",
              "rtmp": "-c copy -f flv"
            }
          },
          "ffmpeg_cmds": [
            {
              "cmd": "ffmpeg -hide_banner -loglevel warning -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 -i rtsp://x.x.x.x:8554/cam1_ch1 -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an /tmp/cache/frigate_street_se-%Y%m%d%H%M%S.mp4 -r 5 -s 1296x972 -f rawvideo -pix_fmt yuv420p pipe:",
              "roles": [
                "record",
                "rtmp",
                "detect"
              ]
            }
          ],
          "live": {
            "height": 720,
            "quality": 8
          },
          "motion": {
            "contour_area": 100,
            "delta_alpha": 0.2,
            "frame_alpha": 0.2,
            "frame_height": 180,
            "mask": "",
            "threshold": 25
          },
          "mqtt": {
            "bounding_box": false,
            "crop": true,
            "enabled": true,
            "height": 500,
            "quality": 100,
            "required_zones": [],
            "timestamp": true
          },
          "name": "frigate_street_se",
          "objects": {
            "filters": {
              "cat": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "dog": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "knife": {
                "mask": null,
                "max_area": 24000000,
                "min_area": 0,
                "min_score": 0.5,
                "threshold": 0.7
              },
              "person": {
                "mask": null,
                "max_area": 100000,
                "min_area": 5000,
                "min_score": 0.5,
                "threshold": 0.7
              }
            },
            "mask": "",
            "track": [
              "person",
              "dog",
              "cat",
              "knife"
            ]
          },
          "record": {
            "enabled": true,
            "events": {
              "max_seconds": 300,
              "objects": null,
              "post_capture": 5,
              "pre_capture": 5,
              "required_zones": [],
              "retain": {
                "default": 10,
                "objects": {}
              }
            },
            "retain_days": 1
          },
          "rtmp": {
            "enabled": false
          },
          "snapshots": {
            "bounding_box": false,
            "clean_copy": true,
            "crop": false,
            "enabled": false,
            "height": null,
            "quality": 70,
            "required_zones": [],
            "retain": {
              "default": 7,
              "objects": {
                "person": 7
              }
            },
            "timestamp": true
          },
          "timestamp_style": {
            "color": {
              "blue": 0,
              "green": 255,
              "red": 255
            },
            "effect": "shadow",
            "format": "%m/%d/%Y %H:%M:%S",
            "position": "tl",
            "thickness": 1
          },
          "zones": {}
        }
      },
      "database": {
        "path": "/media/frigate/frigate.db"
      },
      "detect": {
        "enabled": true,
        "fps": 5,
        "height": 972,
        "max_disappeared": 25,
        "width": 1296
      },
      "detectors": {
        "cpu": {
          "device": "usb",
          "num_threads": 3,
          "type": "cpu"
        }
      },
      "environment_vars": {},
      "ffmpeg": {
        "global_args": "-hide_banner -loglevel warning",
        "hwaccel_args": [],
        "input_args": "-avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1",
        "output_args": {
          "detect": "-f rawvideo -pix_fmt yuv420p",
          "record": "-f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an",
          "rtmp": "-c copy -f flv"
        }
      },
      "live": {
        "height": 720,
        "quality": 8
      },
      "logger": {
        "default": "info",
        "logs": {
          "frigate.event": "debug"
        }
      },
      "model": {
        "height": 320,
        "labelmap": {},
        "labelmap_path": null,
        "path": null,
        "width": 320
      },
      "motion": {
        "contour_area": 100,
        "delta_alpha": 0.2,
        "frame_alpha": 0.2,
        "frame_height": 180,
        "mask": "",
        "threshold": 25
      },
      "mqtt": {
        "client_id": "frigate",
        "host": "x.x.x.x redacted",
        "password": null,
        "port": 1883,
        "stats_interval": 60,
        "tls_ca_certs": null,
        "tls_client_cert": null,
        "tls_client_key": null,
        "tls_insecure": null,
        "topic_prefix": "frigate",
        "user": null
      },
      "objects": {
        "filters": {
          "person": {
            "mask": null,
            "max_area": 100000,
            "min_area": 5000,
            "min_score": 0.5,
            "threshold": 0.7
          }
        },
        "mask": "",
        "track": [
          "person",
          "dog",
          "cat",
          "knife"
        ]
      },
      "record": {
        "enabled": true,
        "events": {
          "max_seconds": 300,
          "objects": null,
          "post_capture": 5,
          "pre_capture": 5,
          "required_zones": [],
          "retain": {
            "default": 10,
            "objects": {}
          }
        },
        "retain_days": 1
      },
      "rtmp": {
        "enabled": false
      },
      "snapshots": {
        "bounding_box": false,
        "clean_copy": true,
        "crop": false,
        "enabled": false,
        "height": null,
        "quality": 70,
        "required_zones": [],
        "retain": {
          "default": 7,
          "objects": {
            "person": 7
          }
        },
        "timestamp": true
      },
      "timestamp_style": {
        "color": {
          "blue": 0,
          "green": 255,
          "red": 255
        },
        "effect": "shadow",
        "format": "%m/%d/%Y %H:%M:%S",
        "position": "tl",
        "thickness": 1
      }
    }
    

    Relevant log output

    [2021-11-04 22:03:17] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:03:17] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:03:17] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:17] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:22] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:27] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:03:27] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:03:27] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:27] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:27] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:27] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x5616db63bb80] Error parsing AU headers
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55d7d37a8b80] Error parsing AU headers
    
    [2021-11-04 22:03:27] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 86 times
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:27] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:03:27] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:27] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:03:27] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x563421925b80] Error parsing AU headers
    
    [2021-11-04 22:03:27] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 82 times
    
    [2021-11-04 22:03:27] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:27] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:27] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:27] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x559a95c42b80] Error parsing AU headers
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 30 times
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:27] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:03:32] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:32] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:32] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:32] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:32] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:32] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:34] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:34] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:37] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:03:37] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:37] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x55abcc945b80] Error parsing AU headers
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 51 times
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:03:37] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:03:37] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:37] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:37] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:03:37] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:37] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:37] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x55a777767b80] Error parsing AU headers
    
    [2021-11-04 22:03:37] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:03:37] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:37] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55d65a433b80] Error parsing AU headers
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:03:37] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:03:37] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:37] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x55815c0beb80] Error parsing AU headers
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 82 times
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:37] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:03:42] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:42] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:42] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:42] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:42] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:42] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:43] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:43] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:47] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:03:47] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:47] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x558508734b80] Error parsing AU headers
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 34 times
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:03:47] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:03:47] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:47] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:47] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x55f0b271ab80] Error parsing AU headers
    
    [2021-11-04 22:03:47] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:03:47] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:47] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:03:47] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:03:47] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:47] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x55dfd610ab80] Error parsing AU headers
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:03:47] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:03:47] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:47] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55a6e4b50b80] Error parsing AU headers
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:47] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:03:52] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:52] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:52] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:52] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:52] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:52] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:55] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:03:55] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:03:57] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:03:57] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:57] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x563f7ca77b80] Error parsing AU headers
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 52 times
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:03:57] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:03:57] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:03:57] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:57] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:57] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:57] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:03:57] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:03:57] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:57] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x556944cb8b80] Error parsing AU headers
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:03:57] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5563f75e4b80] Error parsing AU headers
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:57] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:03:57] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:57] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x55fffca75b80] Error parsing AU headers
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 82 times
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:03:57] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:04:02] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:02] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:02] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:02] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:02] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:02] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:03] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:03] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:07] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:04:07] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:07] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x55779c09fb80] Error parsing AU headers
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 35 times
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:04:07] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:04:07] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:07] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:07] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x55f3f35b2b80] Error parsing AU headers
    
    [2021-11-04 22:04:07] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:07] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:07] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x56503beeeb80] Error parsing AU headers
    
    [2021-11-04 22:04:07] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:07] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:04:07] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x55d5dce44b80] Error parsing AU headers
    
    [2021-11-04 22:04:07] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:07] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:07] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 85 times
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:07] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:04:12] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:12] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:12] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:12] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:12] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:12] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:16] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:16] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:17] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:04:17] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:17] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:04:17] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:17] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x5576a4f70b80] Error parsing AU headers
    
    [2021-11-04 22:04:17] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:04:17] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x562c4ab3db80] Error parsing AU headers
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:17] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 82 times
    
    [2021-11-04 22:04:17] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:04:17] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:17] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:04:17] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:04:17] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:17] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x561817ff3b80] Error parsing AU headers
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 61 times
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:17] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:04:17] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x55adc7135b80] Error parsing AU headers
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 81 times
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:17] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:04:22] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:22] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:22] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:22] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:22] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:22] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:25] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:25] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:27] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:04:27] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:27] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x5642e62bab80] Error parsing AU headers
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 62 times
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:04:27] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:04:27] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:27] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x559bc67e8b80] Error parsing AU headers
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:27] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:04:27] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:04:27] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:27] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:27] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:27] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:27] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x562c0d82eb80] Error parsing AU headers
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x563bc6d4ab80] Error parsing AU headers
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:27] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:04:27] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:04:27] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:27] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:04:32] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:32] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:32] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:32] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:32] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:32] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:34] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:34] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:37] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:04:37] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:04:37] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:37] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:37] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:37] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:37] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x55e88e1a7b80] Error parsing AU headers
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x558085c25b80] Error parsing AU headers
    
    [2021-11-04 22:04:37] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 82 times
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:04:37] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:04:37] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:37] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:37] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x564171315b80] Error parsing AU headers
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 43 times
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:37] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:04:37] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:37] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:04:37] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x560f7190cb80] Error parsing AU headers
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:37] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:04:42] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:42] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:42] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:42] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:42] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:42] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:44] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:44] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:47] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-04 22:04:47] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:47] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x5586935e6b80] Error parsing AU headers
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 83 times
    
    [2021-11-04 22:04:47] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_se.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:47] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_se.detect ERROR   : 
    
    [2021-11-04 22:04:47] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:47] watchdog.frigate_street_nw     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_nw.
    
    [2021-11-04 22:04:47] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55f0f0b5eb80] Error parsing AU headers
    
    [2021-11-04 22:04:47] watchdog.frigate_street_nw     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:47] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-04 22:04:47] watchdog.frigate_street_nw     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 82 times
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_nw.detect ERROR   : [rtsp @ 0x559e453b0b80] Error parsing AU headers
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_front.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_nw.detect ERROR   :     Last message repeated 43 times
    
    [2021-11-04 22:04:47] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_front.detect ERROR   : 
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_nw.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:47] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x55e335d3cb80] Error parsing AU headers
    
    [2021-11-04 22:04:47] ffmpeg.frigate_street_nw.detect ERROR   : 
    
    [2021-11-04 22:04:47] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-04 22:04:47] ffmpeg.frigate_backyard.detect ERROR   : Could not write header for output file #0 (incorrect codec parameters ?): No space left on device
    
    [2021-11-04 22:04:47] ffmpeg.frigate_backyard.detect ERROR   : 
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_street_nw: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_street_nw: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-04 22:04:48] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [cont-finish.d] executing container finish scripts...
    
    [cont-finish.d] done.
    
    [s6-finish] waiting for services.
    
    [s6-finish] sending all processes the TERM signal.
    
    [s6-finish] sending all processes the KILL signal and exiting.
    
    [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
    
    [s6-init] ensuring user provided files have correct perms...exited 0.
    
    [fix-attrs.d] applying ownership & permissions fixes...
    
    [fix-attrs.d] done.
    
    [cont-init.d] executing container initialization scripts...
    
    [cont-init.d] done.
    
    [services.d] starting services
    
    [services.d] done.
    
    [2021-11-04 22:05:50] frigate.app                    INFO    : Starting Frigate (0.9.4-26ae608)
    
    Starting migrations
    
    [2021-11-04 22:05:51] peewee_migrate                 INFO    : Starting migrations
    
    There is nothing to migrate
    
    [2021-11-04 22:05:51] peewee_migrate                 INFO    : There is nothing to migrate
    
    [2021-11-04 22:05:51] frigate.mqtt                   INFO    : MQTT connected
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Output process started: 227
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Camera processor started for frigate_street_front: 229
    
    [2021-11-04 22:05:51] ws4py                          INFO    : Using epoll
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Camera processor started for frigate_street_nw: 232
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Camera processor started for frigate_street_se: 235
    
    [2021-11-04 22:05:51] detector.cpu                   INFO    : Starting detection process: 226
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Camera processor started for frigate_backyard: 236
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Capture process started for frigate_street_front: 237
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Capture process started for frigate_street_nw: 241
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Capture process started for frigate_street_se: 247
    
    [2021-11-04 22:05:51] frigate.app                    INFO    : Capture process started for frigate_backyard: 249
    
    [2021-11-04 22:05:51] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
    
    [2021-11-04 22:05:51] ws4py                          INFO    : Using epoll
    
    [2021-11-04 22:06:16] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:54220]
    
    [2021-11-04 22:06:20] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:38768]
    
    [2021-11-04 22:07:50] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:38768]
    
    [2021-11-04 22:08:02] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:54220]
    
    [2021-11-04 22:48:27] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42096]
    
    [2021-11-04 22:48:33] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42096]
    
    [2021-11-04 22:48:34] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42120]
    
    [2021-11-04 22:48:38] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42120]
    
    [2021-11-04 22:48:39] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42142]
    
    [2021-11-04 22:48:41] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42142]
    
    [2021-11-04 22:48:42] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42160]
    
    [2021-11-04 22:48:43] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42160]
    
    [2021-11-04 22:48:44] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42182]
    
    [2021-11-04 22:48:45] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42182]
    
    [2021-11-04 22:48:46] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42202]
    
    [2021-11-04 22:48:48] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42202]
    
    [2021-11-05 05:00:04] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:04] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:04] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:04] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:05] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:05] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:12] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-05 05:00:12] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:12] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x558d97786b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 80 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [swscaler @ 0x558d97917c40] deprecated pixel format used, make sure you did set range correctly
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x558d97786b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 161289 times
    
    [2021-11-05 05:00:12] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [h264 @ 0x558d978aca00] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:12] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x558d97786b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:12] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 1125 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5622d508cb80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 84 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 85 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [swscaler @ 0x55818b02e800] deprecated pixel format used, make sure you did set range correctly
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [swscaler @ 0x5622d5477a40] deprecated pixel format used, make sure you did set range correctly
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5622d508cb80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 8139 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 8601 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [h264 @ 0x55818b49de40] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [h264 @ 0x5622d5426a40] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5622d508cb80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 9388 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [h264 @ 0x558d977a7780] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [h264 @ 0x5622d5206600] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x558d97786b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5622d508cb80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 30628 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 21645 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [h264 @ 0x558d978d96c0] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [h264 @ 0x5622d50c4b80] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   : [rtsp @ 0x558d97786b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5622d508cb80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_se.detect ERROR   :     Last message repeated 194989 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 106525 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [h264 @ 0x5622d50e31c0] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 24123 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5622d508cb80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [h264 @ 0x55818b499c80] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 195139 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [h264 @ 0x5622d54a0d80] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 18337 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   : [rtsp @ 0x5622d508cb80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [h264 @ 0x55818b0eb1c0] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_backyard.detect ERROR   :     Last message repeated 46406 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 18829 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [h264 @ 0x55818b12da80] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 55405 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [h264 @ 0x55818b0eb1c0] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 10793 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [h264 @ 0x55818afdd200] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 191245 times
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [h264 @ 0x55818b499c80] SEI type 240 size 360 truncated at 352
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   : [rtsp @ 0x55818afc7b80] Error parsing AU headers
    
    [2021-11-05 05:00:12] ffmpeg.frigate_street_front.detect ERROR   :     Last message repeated 61020 times
    
    [2021-11-05 05:00:17] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:17] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:17] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:17] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:17] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:17] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:22] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-05 05:00:22] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-05 05:00:22] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:22] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:22] ffmpeg.frigate_backyard.detect ERROR   : rtsp://x.x.x.x:8554/cam4_ch1: Invalid data found when processing input
    
    [2021-11-05 05:00:22] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:22] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:22] ffmpeg.frigate_street_se.detect ERROR   : rtsp://x.x.x.x:8554/cam1_ch1: Invalid data found when processing input
    
    [2021-11-05 05:00:22] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-05 05:00:22] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:22] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:22] ffmpeg.frigate_street_front.detect ERROR   : rtsp://x.x.x.x:8554/cam2_ch1: Invalid data found when processing input
    
    [2021-11-05 05:00:27] frigate.video                  INFO    : frigate_backyard: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:27] frigate.video                  INFO    : frigate_backyard: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:27] frigate.video                  INFO    : frigate_street_front: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:27] frigate.video                  INFO    : frigate_street_front: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:27] frigate.video                  INFO    : frigate_street_se: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
    
    [2021-11-05 05:00:27] frigate.video                  INFO    : frigate_street_se: ffmpeg process is not running. exiting capture thread...
    
    [2021-11-05 05:00:32] watchdog.frigate_backyard      ERROR   : FFMPEG process crashed unexpectedly for frigate_backyard.
    
    [2021-11-05 05:00:32] watchdog.frigate_backyard      ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:32] watchdog.frigate_street_front  ERROR   : FFMPEG process crashed unexpectedly for frigate_street_front.
    
    [2021-11-05 05:00:32] watchdog.frigate_backyard      ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:32] watchdog.frigate_street_front  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:32] watchdog.frigate_street_se     ERROR   : FFMPEG process crashed unexpectedly for frigate_street_se.
    
    [2021-11-05 05:00:32] ffmpeg.frigate_backyard.detect ERROR   : rtsp://x.x.x.x:8554/cam4_ch1: Invalid data found when processing input
    
    [2021-11-05 05:00:32] watchdog.frigate_street_front  ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:32] watchdog.frigate_street_se     ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    
    [2021-11-05 05:00:32] watchdog.frigate_street_se     ERROR   : You may have invalid args defined for this camera.
    
    [2021-11-05 05:00:32] ffmpeg.frigate_street_front.detect ERROR   : rtsp://x.x.x.x:8554/cam2_ch1: Invalid data found when processing input
    
    [2021-11-05 05:00:32] ffmpeg.frigate_street_se.detect ERROR   : rtsp://x.x.x.x:8554/cam1_ch1: Invalid data found when processing input
    
    [2021-11-05 08:59:24] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:58426]
    
    [2021-11-05 08:59:24] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42950]
    
    [2021-11-05 08:59:24] frigate.output                 WARNING : Unable to copy frame frigate_backyard1636063669.896263 to birdseye.
    
    [2021-11-05 08:59:25] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42950]
    
    [2021-11-05 09:03:04] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:58426]
    

    FFprobe output from your camera

    ffprobe version 4.3.3-0+deb11u1 Copyright (c) 2007-2021 the FFmpeg developers
      built with gcc 10 (Debian 10.2.1-6)
      configuration: --prefix=/usr --extra-version=0+deb11u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
      libavutil      56. 51.100 / 56. 51.100
      libavcodec     58. 91.100 / 58. 91.100
      libavformat    58. 45.100 / 58. 45.100
      libavdevice    58. 10.100 / 58. 10.100
      libavfilter     7. 85.100 /  7. 85.100
      libavresample   4.  0.  0 /  4.  0.  0
      libswscale      5.  7.100 /  5.  7.100
      libswresample   3.  7.100 /  3.  7.100
      libpostproc    55.  7.100 / 55.  7.100
    [rtsp @ 0x560439d5fa00] method SETUP failed: 461 Unsupported Transport
    [rtsp @ 0x560439d5fa00] Error parsing AU headers
        Last message repeated 94 times
    Input #0, rtsp, from 'rtsp://x.x.x.x:8554/cam2_ch1':
      Metadata:
        title           : Stream
      Duration: N/A, start: -0.013044, bitrate: N/A
        Stream #0:0: Video: h264 (Main), yuvj420p(pc, progressive), 2592x1944, 10 tbr, 90k tbn, 180k tbc
        Stream #0:1: Audio: aac, 16000 Hz, mono, fltp
    

    Frigate stats

    {
      "detection_fps": 8.8,
      "detectors": {
        "cpu": {
          "detection_start": 1636103221.110705,
          "inference_speed": 122.91,
          "pid": 226
        }
      },
      "frigate_backyard": {
        "camera_fps": 5.1,
        "capture_pid": 249,
        "detection_fps": 0.0,
        "pid": 236,
        "process_fps": 5.1,
        "skipped_fps": 0.0
      },
      "frigate_street_front": {
        "camera_fps": 5.0,
        "capture_pid": 237,
        "detection_fps": 2.4,
        "pid": 229,
        "process_fps": 3.5,
        "skipped_fps": 0.0
      },
      "frigate_street_nw": {
        "camera_fps": 5.1,
        "capture_pid": 241,
        "detection_fps": 3.1,
        "pid": 232,
        "process_fps": 1.4,
        "skipped_fps": 0.0
      },
      "frigate_street_se": {
        "camera_fps": 5.1,
        "capture_pid": 247,
        "detection_fps": 3.3,
        "pid": 235,
        "process_fps": 2.2,
        "skipped_fps": 0.0
      },
      "service": {
        "storage": {
          "/dev/shm": {
            "free": 42.5,
            "mount_type": "tmpfs",
            "total": 67.1,
            "used": 24.6
          },
          "/media/frigate/clips": {
            "free": 1646575.4,
            "mount_type": "ext4",
            "total": 1967902.2,
            "used": 221291.9
          },
          "/media/frigate/recordings": {
            "free": 1646575.4,
            "mount_type": "ext4",
            "total": 1967902.2,
            "used": 221291.9
          },
          "/tmp/cache": {
            "free": 977.4,
            "mount_type": "tmpfs",
            "total": 1000.0,
            "used": 22.6
          }
        },
        "uptime": 39670,
        "version": "0.9.4-26ae608"
      }
    }
    

    Operating system

    Debian

    Install method

    Docker CLI

    Coral version

    CPU (no coral)

    Network connection

    Wired

    Camera make and model

    AnpViz IPC-D250G-S-4X (YM500L)

    Any other information that may be helpful

    I am using rtsp-simple-server, cameras feed into it, and then I pull video from it. If I put the URL into VNC it plays just fine, either directly from the camera or from rtsp-simple-server.

    support stale triage 
    opened by user897943 60
  • [Camera Support]: Reolink 510A

    [Camera Support]: Reolink 510A

    Describe the problem you are having

    Hi.

    I'm using the Reolink 510A, and I currently receive no frame from FFmpeg, so it's displayed as a green camera right now. My configuration seems correct when I compare it to the documentation.

    I verified that my RTMP link is functional on VLC and others apps. I verified that my RTMP is enabled in the config. I tried with and without input_args. I also try to use the-stimeout trick described in this issue, but it seems that -stimeout is not not recognized (ffmpeg.camera_un.detect ERROR : Unrecognized option 'stimeout'.)

    Version

    0.11.1-2EADA21

    Frigate config file

    mqtt:
      host: 192.168.1.37
      user: HA
      password: HA
    
    cameras:
      camera_un: # <------ Name the camera
        ffmpeg:
          inputs:
            - path: <my valid RTMP link here>
              roles:
                - detect
                - rtmp
        rtmp:
          enabled: True # <-- RTMP should be disabled if your stream is not H264
        detect:
          enabled: True
          width: 1920 # <---- update for your camera's resolution
          height: 1080 # <---- update for your camera's resolution
        record:
          enabled: True
        objects:
          track:
            - person
            - cat
            - dog
          filters:
            person:
              min_score: 0.25
            cat:
              min_score: 0.25
            dog:
              min_score: 0.25
    

    Relevant log output

    [2023-01-06 08:41:40] ffmpeg.camera_un.detect        ERROR   : Error splitting the argument list: Option not found
    [2023-01-06 08:41:40] frigate.video                  ERROR   : camera_un: Unable to read frames from ffmpeg process.
    [2023-01-06 08:41:40] frigate.video                  ERROR   : camera_un: ffmpeg process is not running. exiting capture thread...
    [2023-01-06 08:41:50] watchdog.camera_un             ERROR   : Ffmpeg process crashed unexpectedly for camera_un.
    [2023-01-06 08:41:50] watchdog.camera_un             ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    [2023-01-06 08:41:50] ffmpeg.camera_un.detect        ERROR   : Unrecognized option 'stimeout'.
    

    FFprobe output from your camera

    ffprobe version n5.1-2-g915ef932a3-20220731 Copyright (c) 2007-2022 the FFmpeg developers
      built with gcc 12.1.0 (crosstool-NG 1.25.0.55_3defb7b)
      configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-mbedtls --enable-librist --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags=-pie --extra-libs='-ldl -lgomp' --extra-version=20220731
      libavutil      57. 28.100 / 57. 28.100
      libavcodec     59. 37.100 / 59. 37.100
      libavformat    59. 27.100 / 59. 27.100
      libavdevice    59.  7.100 / 59.  7.100
      libavfilter     8. 44.100 /  8. 44.100
      libswscale      6.  7.100 /  6.  7.100
      libswresample   4.  7.100 /  4.  7.100
      libpostproc    56.  6.100 / 56.  6.100
    rtmp://XXXXX:[email protected]/bcs/channel0_main.bcs?token=sdasdasd: Input/output error
    

    Frigate stats

    No response

    Operating system

    UNRAID

    Install method

    Docker CLI

    Coral version

    CPU (no coral)

    Network connection

    Wired

    Camera make and model

    Reolink 510A

    Any other information that may be helpful

    Unraid version: 6.11.1

    support triage 
    opened by BLKKKBVSIK 0
  • [Support]: Frigate crashes randomly on Ubuntu microk8s

    [Support]: Frigate crashes randomly on Ubuntu microk8s

    Describe the problem you are having

    I thought this was related to hardware acceleration but removed this from the container and it still crashes randomly now.

    Not sure what is happening but hopefully you can tell from the logs

    Version

    0.11.1-2EADA21

    Frigate config file

    mqtt:
      host: hass.cjhx.net
      user: frigate
      password: ${FRIGATE_MQTT_PASSWORD}
    logger:
        # Optional: default log level (default: shown below)
      default: debug
    detectors:
      cpu1:
        type: cpu
        num_threads: 2
      cpu2:
        type: cpu
        num_threads: 2
      cpu3:
        type: cpu
        num_threads: 2
      cpu4:
        type: cpu
        num_threads: 2
    rtmp:
      # Required: Enable the live stream (default: True)
      enabled: True
    record:
      enabled: True
      retain:
        days: 30
        mode: all
    snapshots:
      # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
      # This value can be set via MQTT and will be updated in startup based on retained value
      enabled: true
      # Optional: print a timestamp on the snapshots (default: shown below)
      timestamp: false
      # Optional: draw bounding box on the snapshots (default: shown below)
      bounding_box: true
      # Optional: crop the snapshot (default: shown below)
      crop: false
    #      # Optional: height to resize the snapshot to (default: original size)
    #      height: 175
      # Optional: Camera override for retention settings (default: global values)
      retain:
        # Required: Default retention days (default: shown below)
        default: 120
        # Optional: Per object retention days
        #objects:
        #  person: 60
    ffmpeg:
      #hwaccel_args: -hwaccel qsv -hwaccel_output_format nv12 -c:v h264_qsv
      #hwaccel_args: -c:v h264_qsv
      #hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
      
      # Optional: global input args (default: shown below)
      #input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -timeout 5000000 -use_wallclock_as_timestamps 1
      input_args: -avoid_negative_ts make_zero -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -rtsp_transport tcp -timeout 5000000 -use_wallclock_as_timestamps 1
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an
    cameras:
      CAM001-Nursery:
        ffmpeg:
          inputs:
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@cam1.cjhx.net:554/videoMain
              roles:
                - detect
                - record
                - rtmp
          output_args:
            record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
        detect:
          enabled: False
          width: 1280
          height: 720
        motion:
          mask:
            - 240,55,0,55,0,0,240,0
        zones:
          crib:
            coordinates: 379,480,468,55,320,0,209,396
            #objects:
            #  - person
      CAM002-XXXX:
        ffmpeg:
          inputs:
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:88/videoSub
              roles:
                - detect
                - rtmp
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:88/videoMain
              roles:
                - record
          output_args:
            record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
        detect:
          enabled: False
          width: 1024
          height: 768
        motion:
          mask:
            - 400,55,0,55,0,0,400,0 # Timestamp
            #- 0,596,505,422,163,0,0,0 # XXXX Bed
            - 380,0,375,237,208,221,196,0 # XXXX Mobile
        objects:
          filters:
            person:
              mask: 0,596,505,422,163,0,0,0
      CAM003-LivingRoom:
        ffmpeg:
          inputs:
            - path: http://XXXX:[email protected]/video.cgi?resolution=VGA
              roles:
                - detect
                - record
          #hwaccel_args: -c:v mjpeg_vaapi
          input_args: -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1
          output_args:
            record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an
            #rtmp: -c:v h264_qsv -an -f flv
        detect:
          enabled: false
          width: 640
          height: 480
          fps: 5
        record:
          enabled: false
          events:
            retain:
              default: 30
            post_capture: 10
        rtmp:
          enabled: false
      #CAM004-ServiceEntrance:
      #  ffmpeg:
      #    inputs:
      #      - path: http://XXX:[email protected]/video.cgi?resolution=VGA
      #        roles:
      #          - detect
      #          - record
      #    hwaccel_args: []
      #    input_args: -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1
      #    output_args:
      #      record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an
      #      rtmp: -c:v h264_qsv -an -f flv
      #  detect:
      #    enabled: false
      #    width: 640
      #    height: 480
      #    fps: 5
      #  record:
      #    enabled: false
      #    days: 0
      #    events:
      #      retain:
      #        default: 30
      #      post_capture: 10
      #  rtmp:
      #    enabled: true
      CAM101-Driveway:
        ffmpeg:
          inputs:
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
        detect:
          width: 1280
          height: 720
        zones:
          driveway:
            coordinates: 1225,720,1053,398,826,233,403,210,0,432,0,720
          street:
            coordinates: 627,196,1280,294,1280,92,0,64,0,213
          yard2:
            coordinates: 0,220,0,438,477,193
            objects:
              - person
              - bicycle
              - bird
              - cat
              - dog
          yard:
            coordinates: 1159,720,1280,720,1280,319,794,239
            objects:
              - person
              - bicycle
              - bird
              - cat
              - dog
        objects:
          track:
            - person
            - bicycle
            - car
            - motorcycle
            - bus
            - cat
            - dog
          filters:
            car:
              mask:
                - 786,720,1186,635,981,255,733,455  
            bus:
              mask:
                - 786,720,1186,635,981,255,733,455
        motion:
          #threshold: 20
          #contour_area: 15
          mask:
            - 0,40,450,40,450,0,0,0 # Overlay
        rtmp:
          # Required: Enable the live stream (default: True)
          enabled: true
      CAM102-Porch:
        ffmpeg:
          inputs:
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@cam7.cjhx.net:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@cam7.cjhx.net:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
        detect:
          width: 1280
          height: 720
        motion:
          mask:
            - 0,40,450,40,450,0,0,0
            - 934,720,1087,720,1091,495,987,335,894,516,736,611
        rtmp:
          # Required: Enable the live stream (default: True)
          enabled: True
      CAM111-Deck:
        ffmpeg:
          inputs:
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
          #input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport udp -stimeout 5000000 -use_wallclock_as_timestamps 1
        detect:
          width: 1280
          height: 720
        motion:
          mask:
            - 0,40,450,40,450,0,0,0 # Overlay
        rtmp:
          # Required: Enable the live stream (default: True)
          enabled: true
      CAM112-Pool:
        ffmpeg:
          inputs:
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@cam6.cjhx.net:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@cam6.cjhx.net:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
            #input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport udp -stimeout 5000000 -use_wallclock_as_timestamps 1
        detect:
          width: 1280
          height: 720
        motion:
          mask:
            - 0,40,450,40,450,0,0,0 # Timestamp
            - 0,720,530,720,225,499,428,293,410,0,0,0 # Tree left side
            - 1280,327,1280,720,833,720,1031,454,994,301 # Grasses right side
        zones:
          pool:
              coordinates: 979,432,954,328,884,291,787,261,692,229,636,204,510,200,448,202,355,248,346,341,375,407,418,429,738,422,916,462
              #objects:
            #  - person
        rtmp:
          # Required: Enable the live stream (default: True)
          enabled: true
      CAM113-SideYard:
        ffmpeg:
          inputs:
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:554/cam/realmonitor?channel=1&subtype=2
              roles:
                - detect
                - rtmp
            - path: rtsp://{FRIGATE_RSTP_USERNAME}:{FRIGATE_RTSP_PASSWORD}@XXX.XXX.XXX.XXX:554/cam/realmonitor?channel=1&subtype=0
              roles:
                - record
          #input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport udp -stimeout 5000000 -use_wallclock_as_timestamps 1
        detect:
          width: 1280
          height: 720
        zones:
          street:
            coordinates: 767,206,771,140,186,141,192,204
            #filters:
              #person:
                #threshold: 0.2
                #min_score: 0.20
              #car:
                #threshold: 0.2
                #min_score: 0.20
          yard:
            coordinates: 1280,720,1280,0,777,0,754,206,0,205,0,720
            filters:
              person:
                threshold: 0.70
                #min_score: 0.70
        objects:
          track:
            - person
            - bicycle
            - car
            - motorcycle
            - bus
            - bird
            - cat
            - dog
            - horse
            - sheep
            - cow
            - bear
            - zebra
            - giraffe
          filters:
            person:
              #threshold: 0.75
              #min_score: 0.70
              mask:
                - 86,291,100,332,33,325,36,289
        motion:
          #threshold: 20
          #contour_area: 15
          #mask:
            #- 0,40,450,40,450,0,0,0 # Overlay
        rtmp:
          # Required: Enable the live stream (default: True)
          enabled: true
      zTEST:
        ffmpeg:
          inputs:
            - path: rtsp://XXX.XXX.XXX.XXX/frigate-test
              roles:
                - detect
                - record
          hwaccel_args: []
          #input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport udp -stimeout 5000000 -use_wallclock_as_timestamps 1
        detect:
          width: 1280
          height: 720
        zones:
          street:
            coordinates: 767,206,771,140,186,141,192,204
            #filters:
              #person:
                #threshold: 0.2
                #min_score: 0.20
              #car:
                #threshold: 0.2
                #min_score: 0.20
          yard:
            coordinates: 1280,720,1280,0,777,0,754,206,0,205,0,720
            filters:
              person:
                threshold: 0.75
                min_score: 0.70
        objects:
          track:
            - person
            - bicycle
            - car
            - motorcycle
            - bus
            - bird
            - cat
            - dog
            - horse
            - sheep
            - cow
            - bear
            - zebra
            - giraffe
          filters:
            person:
              #threshold: 0.75
              #min_score: 0.70
              mask:
                - 86,291,100,332,33,325,36,289
        motion:
          #threshold: 20
          #contour_area: 15
          #mask:
            #- 0,40,450,40,450,0,0,0 # Overlay
        rtmp:
          enabled: false
        record:
          enabled: false
    # Optional: birdseye configuration
    birdseye:
      # Optional: Enable birdseye view (default: shown below)
      enabled: True
      # Optional: Width of the output resolution (default: shown below)
      width: 1280
      # Optional: Height of the output resolution (default: shown below)
      height: 720
      # Optional: Encoding quality of the mpeg1 feed (default: shown below)
      # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
      quality: 10
      # Optional: Mode of the view. Available options are: objects, motion, and continuous
      #   objects - cameras are included if they have had a tracked object within the last 30 seconds
        #   motion - cameras are included if motion was detected in the last 30 seconds
        #   continuous - all cameras are included always
      mode: motion
    

    Relevant log output

    "timestamp","source","message"
    "2023-01-05T10:00:08.261-05:00","docker3","2023-01-05T10:00:08.244486854-05:00 stderr F [2023-01-05 10:00:08] ws4py                          INFO    : Managing websocket [Local => XXX.XXX.XXX.XXX:8082 | Remote => XXX.XXX.XXX.XXX:41076]"
    "2023-01-05T10:01:08.257-05:00","docker3","2023-01-05T10:01:08.246316104-05:00 stderr F [2023-01-05 10:01:08] ws4py                          INFO    : Terminating websocket [Local => XXX.XXX.XXX.XXX:8082 | Remote => XXX.XXX.XXX.XXX:41076]"
    "2023-01-05T10:01:57.605-05:00","docker3","2023-01-05T10:01:57.604945605-05:00 stdout F [cont-finish.d] executing container finish scripts..."
    "2023-01-05T10:01:57.617-05:00","docker3","2023-01-05T10:01:57.607140369-05:00 stdout F [cont-finish.d] done."
    "2023-01-05T10:01:57.617-05:00","docker3","2023-01-05T10:01:57.607845151-05:00 stdout F [s6-finish] waiting for services."
    "2023-01-05T10:01:57.628-05:00","docker3","2023-01-05T10:01:57.627357642-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM002-xxxx: ffmpeg process is not running. exiting capture thread..."
    "2023-01-05T10:01:57.628-05:00","docker3","2023-01-05T10:01:57.627164562-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM002-xxxx: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.651-05:00","docker3","2023-01-05T10:01:57.65084017-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM112-Pool: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659647147-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : [flv @ 0x55d18cea6c80] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly"
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659866332-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : [flv @ 0x55d18cea6c80] Failed to update header with correct filesize."
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659957009-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : Error closing file rtmp://XXX.XXX.XXX.XXX/live/CAM002-xxxx: Broken pipe"
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659713665-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : [flv @ 0x55d18cea6c80] Non-monotonous DTS in output stream 0:0; previous: 91, current: 67; changing to 91. This may result in incorrect timestamps in the output file."
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659899541-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : Error writing trailer of rtmp://XXX.XXX.XXX.XXX/live/CAM002-xxxx: Connection reset by peer"
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.651032396-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM112-Pool: ffmpeg process is not running. exiting capture thread..."
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659773647-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : av_interleaved_write_frame(): Connection reset by peer"
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659459951-05:00 stderr F [2023-01-05 10:01:57] watchdog.CAM002-xxxx          ERROR   : Ffmpeg process crashed unexpectedly for CAM002-xxxx."
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.659589162-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono"
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.65951965-05:00 stderr F [2023-01-05 10:01:57] watchdog.CAM002-xxxx          ERROR   : The following ffmpeg logs include the last 100 lines prior to exit."
    "2023-01-05T10:01:57.669-05:00","docker3","2023-01-05T10:01:57.6598291-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM002-xxxx.detect     ERROR   : [flv @ 0x55d18cea6c80] Failed to update header with correct duration."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741873041-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.74187459-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.74188536-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741891438-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741915959-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741914387-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741879119-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741886846-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.74189291-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741895928-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741911417-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741918994-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.74192758-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741868664-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741882376-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741889906-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741897476-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.74184322-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741877611-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741880682-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741883883-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741894456-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741929618-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: ffmpeg process is not running. exiting capture thread..."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741917447-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741871305-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741912914-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.741909912-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.74188842-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.744-05:00","docker3","2023-01-05T10:01:57.74190823-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM111-Deck: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.780-05:00","docker3","2023-01-05T10:01:57.770268101-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM113-SideYard: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.780-05:00","docker3","2023-01-05T10:01:57.77045599-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM113-SideYard: ffmpeg process is not running. exiting capture thread..."
    "2023-01-05T10:01:57.780-05:00","docker3","2023-01-05T10:01:57.762084582-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM102-Porch: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.780-05:00","docker3","2023-01-05T10:01:57.762165348-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM102-Porch: ffmpeg process is not running. exiting capture thread..."
    "2023-01-05T10:01:57.799-05:00","docker3","2023-01-05T10:01:57.788207922-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM101-Driveway: ffmpeg process is not running. exiting capture thread..."
    "2023-01-05T10:01:57.799-05:00","docker3","2023-01-05T10:01:57.788146195-05:00 stderr F [2023-01-05 10:01:57] frigate.video                  ERROR   : CAM101-Driveway: Unable to read frames from ffmpeg process."
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.841214022-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : [flv @ 0x55b459f3fcc0] Failed to update header with correct duration."
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.841373519-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : Error closing file rtmp://XXX.XXX.XXX.XXX/live/CAM102-Porch: Broken pipe"
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.841319337-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : Error writing trailer of rtmp://XXX.XXX.XXX.XXX/live/CAM102-Porch: Connection reset by peer"
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.840935947-05:00 stderr F [2023-01-05 10:01:57] watchdog.CAM102-Porch          ERROR   : The following ffmpeg logs include the last 100 lines prior to exit."
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.841119515-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : More than 1000 frames duplicated"
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.841178934-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : av_interleaved_write_frame(): Connection reset by peer"
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.841241594-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : [flv @ 0x55b459f3fcc0] Failed to update header with correct filesize."
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.842734419-05:00 stdout F [s6-finish] sending all processes the TERM signal."
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.84079546-05:00 stderr F [2023-01-05 10:01:57] watchdog.CAM102-Porch          ERROR   : Ffmpeg process crashed unexpectedly for CAM102-Porch."
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.840993307-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : [flv @ 0x55b459f3fcc0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly"
    "2023-01-05T10:01:57.843-05:00","docker3","2023-01-05T10:01:57.841042283-05:00 stderr F [2023-01-05 10:01:57] ffmpeg.CAM102-Porch.detect     ERROR   : [flv @ 0x55b459f3fcc0] Non-monotonous DTS in output stream 0:0; previous: 200, current: 0; changing to 200. This may result in incorrect timestamps in the output file."
    "2023-01-05T10:02:00.880-05:00","docker3","2023-01-05T10:02:00.880085633-05:00 stdout F [s6-finish] sending all processes the KILL signal and exiting."
    
    
    [Frigate was unresponsive after this point, redeployment in k8s the pod hangs on "terminating" and a full system reboot is required. It comes up normally after a reboot]
    
    
    
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.949061027-05:00 stdout F [cont-init.d] done."
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.953556128-05:00 stdout F [services.d] done."
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:35.216712849-05:00 stderr F [2023-01-05 10:50:35] frigate.app                    INFO    : Creating directory: /tmp/cache"
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:35.218643666-05:00 stderr F [2023-01-05 10:50:35] peewee                         DEBUG   : ('CREATE TABLE IF NOT EXISTS ""migratehistory"" (""id"" INTEGER NOT NULL PRIMARY KEY, ""name"" VARCHAR(255) NOT NULL, ""migrated_at"" DATETIME NOT NULL)', [])"
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.904086299-05:00 stdout F [s6-init] making user provided files available at /var/run/s6/etc...exited 0."
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:35.218537971-05:00 stderr F [2023-01-05 10:50:35] peewee_migrate                 INFO    : Starting migrations"
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.947205816-05:00 stdout F [s6-init] ensuring user provided files have correct perms...exited 0."
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.949426428-05:00 stdout F [services.d] starting services"
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:35.218528781-05:00 stderr F Starting migrations"
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.948018468-05:00 stdout F [fix-attrs.d] applying ownership & permissions fixes..."
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.948768874-05:00 stdout F [cont-init.d] executing container initialization scripts..."
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:35.307373317-05:00 stderr F [2023-01-05 10:50:35] peewee                         DEBUG   : ('SELECT ""t1"".""id"", ""t1"".""name"", ""t1"".""migrated_at"" FROM ""migratehistory"" AS ""t1"" ORDER BY ""t1"".""id""', [])"
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:32.948370204-05:00 stdout F [fix-attrs.d] done."
    "2023-01-05T10:50:35.998-05:00","docker3","2023-01-05T10:50:35.159834774-05:00 stderr F [2023-01-05 10:50:35] frigate.app                    INFO    : Starting Frigate (0.11.1-2eada21)"
    "2023-01-05T10:50:44.638-05:00","docker3","2023-01-05T10:50:44.638223041-05:00 stderr F [2023-01-05 10:50:44] peewee_migrate                 INFO    : There is nothing to migrate"
    "2023-01-05T10:50:44.638-05:00","docker3","2023-01-05T10:50:44.638187169-05:00 stderr F There is nothing to migrate"
    "2023-01-05T10:50:44.657-05:00","docker3","2023-01-05T10:50:44.656599406-05:00 stderr F [2023-01-05 10:50:44] frigate.mqtt                   DEBUG   : MQTT connected"
    "2023-01-05T10:50:44.683-05:00","docker3","2023-01-05T10:50:44.680554543-05:00 stderr F [2023-01-05 10:50:44] detector.cpu1                  INFO    : Starting detection process: 215"
    "2023-01-05T10:50:44.740-05:00","docker3","2023-01-05T10:50:44.739794116-05:00 stderr F [2023-01-05 10:50:44] detector.cpu2                  INFO    : Starting detection process: 217"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.739950706-05:00 stderr F [2023-01-05 10:50:44] detector.cpu3                  INFO    : Starting detection process: 219"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.74333992-05:00 stderr F [2023-01-05 10:50:44] ws4py                          INFO    : Using epoll"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.743256144-05:00 stderr F [2023-01-05 10:50:44] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes."
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.742734654-05:00 stderr F [2023-01-05 10:50:44] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes."
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.743094033-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM113-SideYard: 238"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.74287566-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM111-Deck: 235"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.740022645-05:00 stderr F [2023-01-05 10:50:44] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes."
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.742215031-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Output process started: 223"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.742962905-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM112-Pool: 237"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.742781572-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM102-Porch: 233"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.742760872-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM002-xxxx: 229"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.74276504-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM101-Driveway: 232"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.7486343-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM002-xxxx: 246"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.743153449-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for zTEST: 240"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.741373774-05:00 stderr F [2023-01-05 10:50:44] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes."
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.740068018-05:00 stderr F [2023-01-05 10:50:44] detector.cpu4                  INFO    : Starting detection process: 221"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.742757432-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM001-Nursery: 227"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.753730605-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM003-LivingRoom: 250"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.7427631-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Camera processor started for CAM003-LivingRoom: 230"
    "2023-01-05T10:50:44.765-05:00","docker3","2023-01-05T10:50:44.743204334-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM001-Nursery: 242"
    "2023-01-05T10:50:44.792-05:00","docker3","2023-01-05T10:50:44.792192242-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM101-Driveway: 256"
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.797731742-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM102-Porch: 263"
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.91363996-05:00 stderr F [2023-01-05 10:50:44] urllib3.connectionpool         DEBUG   : Starting new HTTPS connection (1): api.github.com:443"
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.919350675-05:00 stderr F [2023-01-05 10:50:44] frigate.video                  ERROR   : zTEST: Unable to read frames from ffmpeg process."
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.913550276-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM111-Deck: 275"
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.913611546-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM112-Pool: 279"
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.913623073-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for zTEST: 300"
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.919391693-05:00 stderr F [2023-01-05 10:50:44] frigate.video                  ERROR   : zTEST: ffmpeg process is not running. exiting capture thread..."
    "2023-01-05T10:50:44.921-05:00","docker3","2023-01-05T10:50:44.913616005-05:00 stderr F [2023-01-05 10:50:44] frigate.app                    INFO    : Capture process started for CAM113-SideYard: 285"
    "2023-01-05T10:50:44.935-05:00","docker3","2023-01-05T10:50:44.935328094-05:00 stderr F [2023-01-05 10:50:44] urllib3.connectionpool         DEBUG   : https://api.github.com:443 ""GET /repos/blakeblackshear/frigate/releases/latest HTTP/1.1"" 200 1217"
    "2023-01-05T10:50:44.951-05:00","docker3","2023-01-05T10:50:44.95075702-05:00 stderr F [2023-01-05 10:50:44] ws4py                          INFO    : Using epoll"
    "2023-01-05T10:50:44.960-05:00","docker3","2023-01-05T10:50:44.952830876-05:00 stderr F [2023-01-05 10:50:44] peewee.sqliteq                 DEBUG   : received query UPDATE ""event"" SET ""end_time"" = (""event"".""start_time"" + ?) WHERE (""event"".""end_time"" IS ?)"
    "2023-01-05T10:50:44.960-05:00","docker3","2023-01-05T10:50:44.952843186-05:00 stderr F [2023-01-05 10:50:44] peewee                         DEBUG   : ('UPDATE ""event"" SET ""end_time"" = (""event"".""start_time"" + ?) WHERE (""event"".""end_time"" IS ?)', [30, None])"
    "2023-01-05T10:50:45.339-05:00","docker3","2023-01-05T10:50:45.338929626-05:00 stderr F [2023-01-05 10:50:45] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM003-LivingRoom/all."
    "2023-01-05T10:50:47.299-05:00","docker3","2023-01-05T10:50:47.298834508-05:00 stderr F [2023-01-05 10:50:47] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM002-xxxx/all."
    "2023-01-05T10:50:50.313-05:00","docker3","2023-01-05T10:50:50.297661339-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM102-Porch/all."
    "2023-01-05T10:50:50.339-05:00","docker3","2023-01-05T10:50:50.33692259-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM101-Driveway/all."
    "2023-01-05T10:50:50.392-05:00","docker3","2023-01-05T10:50:50.390576328-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/driveway/all."
    "2023-01-05T10:50:50.392-05:00","docker3","2023-01-05T10:50:50.390731822-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/street/all."
    "2023-01-05T10:50:50.412-05:00","docker3","2023-01-05T10:50:50.392585226-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/yard2/all."
    "2023-01-05T10:50:50.412-05:00","docker3","2023-01-05T10:50:50.392689965-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/yard/all."
    "2023-01-05T10:50:50.445-05:00","docker3","2023-01-05T10:50:50.436701032-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/crib/all."
    "2023-01-05T10:50:50.445-05:00","docker3","2023-01-05T10:50:50.411933619-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM111-Deck/all."
    "2023-01-05T10:50:50.445-05:00","docker3","2023-01-05T10:50:50.43453361-05:00 stderr F [2023-01-05 10:50:50] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM001-Nursery/all."
    "2023-01-05T10:50:51.294-05:00","docker3","2023-01-05T10:50:51.29406923-05:00 stderr F [2023-01-05 10:50:51] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM112-Pool/all."
    "2023-01-05T10:50:51.712-05:00","docker3","2023-01-05T10:50:51.294733328-05:00 stderr F [2023-01-05 10:50:51] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/pool/all."
    "2023-01-05T10:50:51.734-05:00","docker3","2023-01-05T10:50:51.733582334-05:00 stderr F [2023-01-05 10:50:51] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM113-SideYard/all."
    "2023-01-05T10:50:51.757-05:00","docker3","2023-01-05T10:50:51.738191855-05:00 stderr F [2023-01-05 10:50:51] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/street/all."
    "2023-01-05T10:50:51.757-05:00","docker3","2023-01-05T10:50:51.738293854-05:00 stderr F [2023-01-05 10:50:51] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/yard/all."
    "2023-01-05T10:50:54.843-05:00","docker3","2023-01-05T10:50:54.835625114-05:00 stderr F [2023-01-05 10:50:54] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/events."
    "2023-01-05T10:50:54.903-05:00","docker3","2023-01-05T10:50:54.900847239-05:00 stderr F [2023-01-05 10:50:54] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM112-Pool/person."
    "2023-01-05T10:50:54.903-05:00","docker3","2023-01-05T10:50:54.900849184-05:00 stderr F [2023-01-05 10:50:54] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM112-Pool/all."
    "2023-01-05T10:50:54.903-05:00","docker3","2023-01-05T10:50:54.900822037-05:00 stderr F [2023-01-05 10:50:54] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM112-Pool/person/snapshot."
    "2023-01-05T10:50:54.903-05:00","docker3","2023-01-05T10:50:54.900844659-05:00 stderr F [2023-01-05 10:50:54] frigate.mqtt                   DEBUG   : MQTT payload for frigate/CAM112-Pool/person/snapshot wasn't text. Skipping..."
    "2023-01-05T10:50:55.530-05:00","docker3","2023-01-05T10:50:55.529832587-05:00 stderr F [2023-01-05 10:50:55] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM111-Deck/person/snapshot."
    "2023-01-05T10:50:55.530-05:00","docker3","2023-01-05T10:50:55.529795817-05:00 stderr F [2023-01-05 10:50:55] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/events."
    "2023-01-05T10:50:55.547-05:00","docker3","2023-01-05T10:50:55.530778232-05:00 stderr F [2023-01-05 10:50:55] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM111-Deck/person."
    "2023-01-05T10:50:55.547-05:00","docker3","2023-01-05T10:50:55.53112165-05:00 stderr F [2023-01-05 10:50:55] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM111-Deck/all."
    "2023-01-05T10:50:55.547-05:00","docker3","2023-01-05T10:50:55.529943086-05:00 stderr F [2023-01-05 10:50:55] frigate.mqtt                   DEBUG   : MQTT payload for frigate/CAM111-Deck/person/snapshot wasn't text. Skipping..."
    "2023-01-05T10:50:56.832-05:00","docker3","2023-01-05T10:50:56.832140277-05:00 stderr F [2023-01-05 10:50:56] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/events."
    "2023-01-05T10:50:56.850-05:00","docker3","2023-01-05T10:50:56.833247809-05:00 stderr F [2023-01-05 10:50:56] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM111-Deck/all."
    "2023-01-05T10:50:56.850-05:00","docker3","2023-01-05T10:50:56.833230084-05:00 stderr F [2023-01-05 10:50:56] frigate.mqtt                   DEBUG   : Received mqtt message on frigate/CAM111-Deck/person."
    

    FFprobe output from your camera

    N/A can be provided if needed
    

    Frigate stats

    {"CAM001-Nursery":{"camera_fps":5.0,"capture_pid":242,"detection_fps":0.0,"pid":227,"process_fps":5.0,"skipped_fps":0.0},"CAM002-XXXX":{"camera_fps":5.1,"capture_pid":246,"detection_fps":0.0,"pid":229,"process_fps":5.1,"skipped_fps":0.0},"CAM003-LivingRoom":{"camera_fps":5.1,"capture_pid":250,"detection_fps":0.0,"pid":230,"process_fps":5.1,"skipped_fps":0.0},"CAM101-Driveway":{"camera_fps":5.1,"capture_pid":256,"detection_fps":1.2,"pid":232,"process_fps":5.2,"skipped_fps":0.0},"CAM102-Porch":{"camera_fps":5.1,"capture_pid":263,"detection_fps":0.0,"pid":233,"process_fps":5.1,"skipped_fps":0.0},"CAM111-Deck":{"camera_fps":5.1,"capture_pid":275,"detection_fps":0.0,"pid":235,"process_fps":5.1,"skipped_fps":0.0},"CAM112-Pool":{"camera_fps":5.1,"capture_pid":279,"detection_fps":0.0,"pid":237,"process_fps":5.1,"skipped_fps":0.0},"CAM113-SideYard":{"camera_fps":5.1,"capture_pid":285,"detection_fps":0.5,"pid":238,"process_fps":5.0,"skipped_fps":0.0},"detection_fps":1.7,"detectors":{"cpu1":{"detection_start":0.0,"inference_speed":185.3,"pid":215},"cpu2":{"detection_start":0.0,"inference_speed":141.71,"pid":217},"cpu3":{"detection_start":0.0,"inference_speed":186.71,"pid":219},"cpu4":{"detection_start":0.0,"inference_speed":189.56,"pid":221}},"service":{"latest_version":"0.11.1","storage":{"/dev/shm":{"free":1059.1,"mount_type":"tmpfs","total":1073.7,"used":14.6},"/media/frigate/clips":{"free":11306937.2,"mount_type":"nfs","total":18441705.1,"used":7134767.9},"/media/frigate/recordings":{"free":11306937.2,"mount_type":"nfs","total":18441705.1,"used":7134767.9},"/tmp/cache":{"free":76630.4,"mount_type":"overlay","total":103240.1,"used":21858.2}},"temperatures":{},"uptime":16003,"version":"0.11.1-2eada21"},"zTEST":{"camera_fps":5.4,"capture_pid":300,"detection_fps":0.0,"pid":240,"process_fps":5.4,"skipped_fps":0.0}}
    

    Operating system

    HassOS

    Install method

    HassOS Addon

    Coral version

    USB

    Network connection

    Wired

    Camera make and model

    Amcrest multiple

    Any other information that may be helpful

    kubernetes deployment generated by helm

    kind: Deployment apiVersion: apps/v1 metadata: name: my-release-frigate namespace: default selfLink: /apis/apps/v1/namespaces/default/deployments/my-release-frigate uid: bb82515d-48e2-43c2-b0da-00025052c1da resourceVersion: '49063077' generation: 238 creationTimestamp: '2022-05-16T18:17:31Z' labels: app.kubernetes.io/instance: my-release app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: frigate app.kubernetes.io/version: 0.11.0 helm.sh/chart: frigate-7.0.0 annotations: deployment.kubernetes.io/revision: '195' meta.helm.sh/release-name: my-release meta.helm.sh/release-namespace: default managedFields: - manager: helm operation: Update apiVersion: apps/v1 time: '2022-12-19T22:23:48Z' fieldsType: FieldsV1 fieldsV1: f:metadata: f:annotations: .: {} f:meta.helm.sh/release-name: {} f:meta.helm.sh/release-namespace: {} f:labels: .: {} f:app.kubernetes.io/instance: {} f:app.kubernetes.io/managed-by: {} f:app.kubernetes.io/name: {} f:app.kubernetes.io/version: {} f:helm.sh/chart: {} f:spec: f:progressDeadlineSeconds: {} f:revisionHistoryLimit: {} f:selector: {} f:strategy: f:type: {} f:template: f:metadata: f:annotations: .: {} f:checksum/configmap: {} f:labels: .: {} f:app.kubernetes.io/instance: {} f:app.kubernetes.io/name: {} f:spec: f:containers: k:{"name":"frigate"}: .: {} f:env: .: {} k:{"name":"FRIGATE_MQTT_PASSWORD"}: .: {} f:name: {} f:value: {} k:{"name":"FRIGATE_RSTP_USERNAME"}: .: {} f:name: {} f:value: {} k:{"name":"FRIGATE_RTSP_PASSWORD"}: .: {} f:name: {} f:value: {} k:{"name":"TZ"}: .: {} f:name: {} f:value: {} f:image: {} f:imagePullPolicy: {} f:livenessProbe: .: {} f:failureThreshold: {} f:httpGet: .: {} f:port: {} f:scheme: {} f:periodSeconds: {} f:successThreshold: {} f:timeoutSeconds: {} f:name: {} f:ports: .: {} k:{"containerPort":1935,"protocol":"TCP"}: .: {} f:containerPort: {} f:name: {} f:protocol: {} k:{"containerPort":5000,"protocol":"TCP"}: .: {} f:containerPort: {} f:name: {} f:protocol: {} f:readinessProbe: .: {} f:failureThreshold: {} f:httpGet: .: {} f:port: {} f:scheme: {} f:periodSeconds: {} f:successThreshold: {} f:timeoutSeconds: {} f:resources: .: {} f:limits: .: {} f:cpu: {} f:memory: {} f:requests: .: {} f:cpu: {} f:memory: {} f:securityContext: {} f:terminationMessagePath: {} f:terminationMessagePolicy: {} f:volumeMounts: .: {} k:{"mountPath":"/config"}: .: {} f:mountPath: {} f:name: {} k:{"mountPath":"/data"}: .: {} f:mountPath: {} f:name: {} k:{"mountPath":"/dev/shm"}: .: {} f:mountPath: {} f:name: {} f:dnsPolicy: {} f:restartPolicy: {} f:schedulerName: {} f:securityContext: {} f:terminationGracePeriodSeconds: {} f:volumes: .: {} k:{"name":"config"}: .: {} f:configMap: .: {} f:defaultMode: {} f:name: {} f:name: {} k:{"name":"data"}: .: {} f:emptyDir: {} f:name: {} k:{"name":"dshm"}: .: {} f:emptyDir: .: {} f:medium: {} f:sizeLimit: {} f:name: {} - manager: dashboard operation: Update apiVersion: apps/v1 time: '2023-01-02T15:39:16Z' fieldsType: FieldsV1 fieldsV1: f:spec: f:template: f:metadata: f:annotations: f:kubectl.kubernetes.io/restartedAt: {} f:spec: f:containers: k:{"name":"frigate"}: f:env: k:{"name":"PLUS_API_KEY"}: .: {} f:name: {} f:value: {} f:livenessProbe: f:httpGet: f:path: {} f:initialDelaySeconds: {} f:readinessProbe: f:httpGet: f:path: {} f:initialDelaySeconds: {} f:volumeMounts: k:{"mountPath":"/media/frigate"}: .: {} f:mountPath: {} f:name: {} f:volumes: k:{"name":"frigate-data"}: .: {} f:name: {} f:persistentVolumeClaim: .: {} f:claimName: {} - manager: kubelite operation: Update apiVersion: apps/v1 time: '2023-01-05T15:55:32Z' fieldsType: FieldsV1 fieldsV1: f:metadata: f:annotations: f:deployment.kubernetes.io/revision: {} f:status: f:availableReplicas: {} f:conditions: k:{"type":"Available"}: f:lastTransitionTime: {} f:lastUpdateTime: {} f:message: {} f:reason: {} f:status: {} k:{"type":"Progressing"}: f:lastUpdateTime: {} f:message: {} f:reason: {} f:observedGeneration: {} f:readyReplicas: {} f:replicas: {} f:updatedReplicas: {} subresource: status spec: replicas: 1 selector: matchLabels: app.kubernetes.io/instance: my-release app.kubernetes.io/name: frigate template: metadata: creationTimestamp: null labels: app.kubernetes.io/instance: my-release app.kubernetes.io/name: frigate annotations: checksum/configmap: 561d1ea8e8f7ae9de9123c8f6db49f27ad6c8d2711fd7601d4ae4de84cd9c2ef kubectl.kubernetes.io/restartedAt: '2023-01-05T15:34:10Z' spec: volumes: - name: config configMap: name: my-release-frigate defaultMode: 420 - name: data emptyDir: {} - name: frigate-data persistentVolumeClaim: claimName: frigate-nas3-pvc - name: dshm emptyDir: medium: Memory sizeLimit: 1Gi containers: - name: frigate image: blakeblackshear/frigate:0.11.1 ports: - name: http containerPort: 5000 protocol: TCP - name: rtmp containerPort: 1935 protocol: TCP env: - name: FRIGATE_MQTT_PASSWORD value: xxxxx - name: FRIGATE_RSTP_USERNAME value: xxxx - name: FRIGATE_RTSP_PASSWORD value: xxxxx - name: TZ value: America/New_York - name: PLUS_API_KEY value: >- xxxxxx resources: limits: cpu: '2' memory: 4Gi requests: cpu: 100m memory: 128Mi volumeMounts: - name: config mountPath: /config - name: data mountPath: /data - name: frigate-data mountPath: /media/frigate - name: dshm mountPath: /dev/shm livenessProbe: httpGet: path: / port: http scheme: HTTP initialDelaySeconds: 300 timeoutSeconds: 10 periodSeconds: 10 successThreshold: 1 failureThreshold: 5 readinessProbe: httpGet: path: / port: http scheme: HTTP initialDelaySeconds: 300 timeoutSeconds: 10 periodSeconds: 10 successThreshold: 1 failureThreshold: 5 terminationMessagePath: /dev/termination-log terminationMessagePolicy: File imagePullPolicy: IfNotPresent securityContext: {} restartPolicy: Always terminationGracePeriodSeconds: 30 dnsPolicy: ClusterFirst securityContext: {} schedulerName: default-scheduler strategy: type: Recreate revisionHistoryLimit: 3 progressDeadlineSeconds: 600 status: observedGeneration: 238 replicas: 1 updatedReplicas: 1 readyReplicas: 1 availableReplicas: 1 conditions: - type: Available status: 'True' lastUpdateTime: '2023-01-05T15:55:32Z' lastTransitionTime: '2023-01-05T15:55:32Z' reason: MinimumReplicasAvailable message: Deployment has minimum availability. - type: Progressing status: 'True' lastUpdateTime: '2023-01-05T15:55:32Z' lastTransitionTime: '2022-10-16T16:09:16Z' reason: NewReplicaSetAvailable message: ReplicaSet "my-release-frigate-64f8859ddb" has successfully progressed.

    support triage 
    opened by k1n6b0b 3
  • [HW Accel Support]: Crash with using present hwaccel_args: preset-intel-qsv-h264

    [HW Accel Support]: Crash with using present hwaccel_args: preset-intel-qsv-h264

    Describe the problem you are having

    Moved from 0.11 and was using

    hwaccel_args: -c:v h264_qsv

    now using

    hwaccel_args: preset-intel-qsv-h264

    Unclear how to debug this as the debug page no longer shows the ffmpeg command that is being run so I can manually run it to see the error.

    I have one cameras using hwaccel_args: preset-intel-vaapi which seems to work and one camera using no hwaccel and that also works ( the first two below).

    If I disable hardware hwaccel in the global settings everything works fine

    Version

    0.12.0-53D39A1

    Frigate config file

    database:
      path: /db/frigate.db
    
    mqtt:
      host: XXX
      user: mqtt
      password: XXX
    
    ffmpeg:
    #  hwaccel_args: -c:v h264_qsv
      hwaccel_args: preset-intel-qsv-h264
    
    detectors:
      coral:
        type: edgetpu
        device: usb
    
    timestamp_style:
      # Optional: Position of the timestamp (default: shown below)
      #           "tl" (top left), "tr" (top right), "bl" (bottom left), "br" (bottom right)
      position: "tl"
      # Optional: Format specifier conform to the Python package "datetime" (default: shown below)
      #           Additional Examples:
      #             german: "%d.%m.%Y %H:%M:%S"
      format: "%m/%d/%Y %H:%M:%S"
      # Optional: Color of font
      color:
        # All Required when color is specified (default: shown below)
        red: 255
        green: 255
        blue: 255
      # Optional: Line thickness of font (default: shown below)
      thickness: 1
      # Optional: Effect of lettering (default: shown below)
      #           None (No effect),
      #           "solid" (solid background in inverse color of font)
      #           "shadow" (shadow for font)
      effect: solid
    
    
    birdseye:
      # Optional: Enable birdseye view (default: shown below)
      enabled: True
      # Optional: Width of the output resolution (default: shown below)
      width: 1280
      # Optional: Height of the output resolution (default: shown below)
      height: 720
      # Optional: Encoding quality of the mpeg1 feed (default: shown below)
      # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
      quality: 8
      # Optional: Mode of the view. Available options are: objects, motion, and continuous
      #   objects - cameras are included if they have had a tracked object within the last 30 seconds
      #   motion - cameras are included if motion was detected in the last 30 seconds
      #   continuous - all cameras are included always
      mode: objects
    
    objects:
      track:
        - person
        - dog
        - cat
        - car
        - bear
    
    record:
      enabled: True
      events:
        retain:
          default: 10
        pre_capture: 5
        post_capture: 5
    
    
    cameras:
    
      attic1: # <------ Name the camera
        ffmpeg:
          hwaccel_args: preset-intel-vaapi
    #      hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
          inputs:
            - path: rtsp://XXX:554/cam/realmonitor?channel=1&subtype=0 # <----- Update for your camera
              roles:
                - detect
                - record
        record:
          enabled: True
          retain:
            days: 30
            mode: motion
    
        objects:
          track:
            - person
            - cat
            - bird
    
        motion:
          threshold: 5
    
      attic2: # <------ Name the camera
        ffmpeg:
          hwaccel_args: []
    #      hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
          inputs:
            - path: rtsp://XXX:554/cam1/mpeg4  # <----- Update for your camera
              roles:
                - detect
                - record
        record:
          enabled: True
          retain:
            days: 30
            mode: motion
    
        objects:
          track:
            - person
            - cat
            - bird
    
        motion:
          threshold: 5
    
      catgenie1: # <------ Name the camera
        ffmpeg:
    #      hwaccel_args: []
    #      hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
          inputs:
            - path: rtsp://XXX:554/live/0/h264.sdp # <----- Update for your camera
              roles:
                - detect
                - record
        objects:
          track:
            - person
            - cat
    
        motion:
          threshold: 5
    
      catgenie2: # <------ Name the camera
        ffmpeg:
    #      hwaccel_args: []
    #      hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
          inputs:
            - path: rtsp://XXX:554/live/0/h264.sdp # <----- Update for your camera
              roles:
                - detect
                - record
        objects:
          track:
            - person
            - cat
    
        motion:
          threshold: 5
    
      driveway1: # <------ Name the camera
        ffmpeg:
          inputs:
            - path: rtsp://XXX:554/cam/realmonitor?channel=1&subtype=0 # <----- Update for your camera
              roles:
                - detect
        detect:
          enabled: True
        record:
          enabled: True
    
    
      driveway2: # <------ Name the camera
        ffmpeg:
          inputs:
            - path: rtsp://XXX:554/cam/realmonitor?channel=1&subtype=0 # <----- Update for your camera
              roles:
                - detect
        detect:
          enabled: True
        record:
          enabled: True
    
    
    --TRUNCATED AS MORE CAMERAS ALL CONFIGURED THE SAME---
    

    docker-compose file or Docker CLI command

    version: "3"
    services:
      frigate:
    #    image: blakeblackshear/frigate:stable
    #    image: crzynik/frigate:testing-driver
        image: blakeblackshear/frigate:0.12.0-beta1
        shm_size: "1024mb"
        container_name: frigate
        privileged: true
        devices:
          - /dev/dri:/dev/dri
        volumes:
          - /disk1/docker/frigate/config:/config
          - /disk1/docker/frigate/db:/db
    #      - /disk1/docker/frigate/media:/media/frigate
          - frigate-media:/media/frigate
          - /etc/localtime:/etc/localtime:ro
          - /dev/bus/usb:/dev/bus/usb
    

    Relevant log output

    023-01-05 10:38:36.733070865  [2023-01-05 10:38:36] ffmpeg.frontyard2.detect       ERROR   : [AVHWDeviceContext @ 0x557928b93280] Error setting child device handle: -17
    2023-01-05 10:38:36.733074625  [2023-01-05 10:38:36] frigate.video                  ERROR   : driveway1: Unable to read frames from ffmpeg process.
    2023-01-05 10:38:36.733076363  [2023-01-05 10:38:36] frigate.video                  ERROR   : driveway1: ffmpeg process is not running. exiting capture thread...
    2023-01-05 10:38:36.736829250  [2023-01-05 10:38:36] watchdog.garage                ERROR   : Ffmpeg process crashed unexpectedly for garage.
    2023-01-05 10:38:36.737094975  [2023-01-05 10:38:36] watchdog.garage                ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    2023-01-05 10:38:36.737099123  [2023-01-05 10:38:36] ffmpeg.garage.detect           ERROR   : [AVHWDeviceContext @ 0x561ebb8a3280] Error setting child device handle: -17
    2023-01-05 10:38:36.737963398  [2023-01-05 10:38:36] watchdog.ch-garage             ERROR   : Ffmpeg process crashed unexpectedly for ch-garage.
    2023-01-05 10:38:36.738239223  [2023-01-05 10:38:36] watchdog.ch-garage             ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
    2023-01-05 10:38:36.738242430  [2023-01-05 10:38:36] ffmpeg.ch-garage.detect        ERROR   : [AVHWDeviceContext @ 0x560cc43b4280] Error setting child device handle: -17
    2023-01-05 10:38:36.756873209  [2023-01-05 10:38:36] frigate.video                  ERROR   : backyardandpool1: Unable to read frames from ffmpeg process.
    2023-01-05 10:38:36.756954064  [2023-01-05 10:38:36] frigate.video                  ERROR   : backyardandpool1: ffmpeg process is not running. exiting capture thread...
    2023-01-05 10:38:36.766415164  [2023-01-05 10:38:36] frigate.video                  ERROR   : garage: Unable to read frames from ffmpeg process.
    2023-01-05 10:38:36.766493212  [2023-01-05 10:38:36] frigate.video                  ERROR   : garage: ffmpeg process is not running. exiting capture thread...
    2023-01-05 10:38:36.771099462  [2023-01-05 10:38:36] frigate.video                  ERROR   : catgenie1: Unable to read frames from ffmpeg process.
    2023-01-05 10:38:36.771210512  [2023-01-05 10:38:36] frigate.video                  ERROR   : catgenie1: ffmpeg process is not running. exiting capture thread...
    2023-01-05 10:38:36.784321477  [2023-01-05 10:38:36] frigate.video                  ERROR   : carriagehouseback: Unable to read frames from ffmpeg process.
    2023-01-05 10:38:36.784402270  [2023-01-05 10:38:36] frigate.video                  ERROR   : carriagehouseback: ffmpeg process is not running. exiting capture thread...
    2023-01-05 10:38:36.796788396  [2023-01-05 10:38:36] frigate.video                  ERROR   : sideyard: Unable to read frames from ffmpeg process.
    2023-01-05 10:38:36.796862139  [2023-01-05 10:38:36] frigate.video                  ERROR   : sideyard: ffmpeg process is not running. exiting capture thread...
    2023-01-05 10:38:36.811204251  [2023-01-05 10:38:36] frigate.video                  ERROR   : carriagehousefront: Unable to read frames from ffmpeg process.
    2023-01-05 10:38:36.811293031  [2023-01-05 10:38:36] frigate.video                  ERROR   : carriagehousefront: ffmpeg process is not running. exiting capture thread...
    

    FFprobe output from your camera

    From Driveway1
    
    [ { "return_code": 0, "stderr": {}, "stdout": { "programs": [], "streams": [ { "avg_frame_rate": "10/1", "codec_long_name": "H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10", "display_aspect_ratio": "16:9", "height": 2160, "width": 3840 }, { "avg_frame_rate": "0/0", "bit_rate": "64000", "codec_long_name": "PCM A-law / G.711 A-law" } ] } } ]
    

    Operating system

    Other Linux

    Install method

    Docker Compose

    Network connection

    Wired

    Camera make and model

    Amcrest IP8M mostly

    Any other information that may be helpful

    No response

    support triage 
    opened by madasus 14
  • [Support]:

    [Support]: "In Progress" events go on forever because phantom objects detected after real objects have left

    Describe the problem you are having

    I've been having an issue for quite some time where I have "in progress" events go on for hours upon hours after a real object detection takes place. For example a car pulls in my driveway, then leaves, but Frigate is still detecting the object is there even when it's gone. Please see the attached 1 4 5

    Version

    0.11.1-2EADA21

    Frigate config file

    mqtt:
      host: 10.4.110.70
      port: 1883
      topic_prefix: frigate
      client_id: frigate
      user: '{FRIGATE_MQTT_USERNAME}'
      password: '{FRIGATE_MQTT_PASSWORD}'
      stats_interval: 60
    
    detectors:
      coral_pci:
        type: edgetpu
        device: pci
    
    birdseye:
    
      enabled: True
      width: 1280
      height: 720
      quality: 8
      mode: motion
    
    cameras:
      
      01-garage-driveway:
        ffmpeg:
          inputs:
            - path: rtsp://10.4.130.72:554/ch01/1
              roles:
                - detect
                - rtmp
            - path: rtsp://10.4.130.72:554/ch01/0
              roles:
                - record
        detect:
          width: 1280 # <---- update for your camera's resolution
          height: 720 # <---- update for your camera's resolution
    
        zones:
          driveway_entry:
            coordinates: 1118,46,1239,58,1228,158,959,120,999,36
          driverway_main:
            coordinates: 1133,720,1280,331,1280,149,945,128,433,417,701,720
        
        motion:
          mask:
            - 0,0,1280,0,1280,64,1004,47,633,79,0,462
    
        rtmp:
          enabled: true
        snapshots:
          enabled: true
          timestamp: false
          bounding_box: true
          crop: false
          retain:
            default: 30
            objects:
              person: 45
        objects:
          track:
            - person
            - cat
            - dog
            - car
          filters:
            person:
              min_score: 0.55
              threshold: 0.65
    
        record:
          enabled: True
          retain:
            days: 28
            mode: all
          events:
            retain:
              default: 28
              mode: active_objects
      
      02-front-doorbell:
        ffmpeg:
          inputs:
            - path: rtsp://admin:{FRIGATE_RTSP_PASSWORD}@10.4.130.79:554/cam/realmonitor?channel=1&subtype=1&authbasic=64
              roles:
                - detect
            - path: rtsp://admin:{FRIGATE_RTSP_PASSWORD}@10.4.130.79:554/cam/realmonitor?channel=1&subtype=0&authbasic=64
              roles:
                - record
                - rtmp
        detect:
          width: 640 # <---- update for your camera's resolution
          height: 480 # <---- update for your camera's resolution
    
        motion:
          mask:
            - 0,0,640,0,640,0,640,238,0,337
    
        rtmp:
          enabled: true
        snapshots:
          enabled: true
          timestamp: false
          bounding_box: true
          crop: False
          retain:
            default: 30
            objects:
              person: 45
        objects:
          track:
            - person
            - cat
            - dog
            #- car
    
        record:
          enabled: True
          retain:
            days: 28
            mode: all
          events:
            retain:
              default: 28
              mode: active_objects
    
      03-front-yard:
        ffmpeg:
          inputs:
            - path: rtsp://10.4.130.71:554/ch01/1
              roles:
                - detect
                - rtmp
            - path: rtsp://10.4.130.71:554/ch01/0
              roles:
                - record
        detect:
          width: 1280 # <---- update for your camera's resolution
          height: 720 # <---- update for your camera's resolution
    
        motion:
          mask:
            - 338,68,571,57,869,69,1280,150,1280,0,0,0,0,142
    
        rtmp:
          enabled: true
        snapshots:
          enabled: true
          timestamp: false
          bounding_box: true
          crop: False
          retain:
            default: 30
            objects:
              person: 45
        objects:
          track:
            - person
            - cat
            - dog
            - car
          filters:
            car:
              mask:
                - 0,720,1280,720,1280,142,1054,246,796,194,854,68,1280,148,1280,0,0,0
            person:
              mask:
                - 0,720,1280,720,1280,142,1054,246,796,194,854,68,1280,148,1280,0,0,0
                
        record:
          enabled: True
          retain:
            days: 28
            mode: all
          events:
            retain:
              default: 28
              mode: active_objects
        
    ffmpeg:
    
      global_args: -hide_banner -loglevel error
    
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p
    
      input_args:
        - -avoid_negative_ts
        - make_zero
        - -fflags
        - nobuffer
        - -flags
        - low_delay
        - -strict
        - experimental
        - -fflags
        - +genpts+discardcorrupt
        - -use_wallclock_as_timestamps
        - "1"
      
      output_args: 
    
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
    
    logger:
      default: info
    

    Relevant log output

    N/A
    

    FFprobe output from your camera

    N/A
    

    Frigate stats

    No response

    Operating system

    Debian

    Install method

    Docker Compose

    Coral version

    M.2

    Network connection

    Wired

    Camera make and model

    GoSwift 4K

    Any other information that may be helpful

    No response

    support triage 
    opened by SpartacusIam 4
Releases(v0.12.0-beta1)
  • v0.12.0-beta1(Jan 2, 2023)

    Major Changes for 0.12.0

    :exclamation::exclamation:Notice:exclamation::exclamation: I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.

    Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/

    BREAKING CHANGES

    • Changes have been made to the database, a backup of the database will need to be made before updating if you want to roll-back. Otherwise the database will need to be deleted to roll-back successfully.
    • More config validation checks have been added, it is possible that Frigate will fail to start due to an error that has been caught, the error will need to be fixed before frigate can start.
    • RTMP is now disabled by default and the role is not automatically added. It is highly recommend to move to the new RTSP based restream.
    • live configuration has been moved to restream -> jsmpeg
    • Changes have been made to the way recordings segments are stored, external scripts which access the recordings file structure directly may be broken.
    • If using the Frigate-HomeAssistant Integration it will need to be updated to 4.0.0 beta01 to avoid breaking changes with Frigate 0.12
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like ./run: line 7: exec: nginx: not found, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (https://github.com/blakeblackshear/frigate/issues/3223)

    Retention limited by available storage

    Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.

    RTSP restreaming

    Due to many issues with RTMP based restream, RTMP is now deprecated in favor of a new RTSP restream. This also comes with a new restream role which is enabled by default. The restream of a camera can be accessed at rtsp://frigate_ip:8554/config_camera_name. The restream can also be used inside Frigate to reduce connections to the camera, see the restream docs for more info.

    Birdseye restreaming is also now supported at rtsp://frigate_ip:8554/birdseye

    NOTE: Port 8554 will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.

    New live stream options

    The new RTSP restream also enables new MSE and WebRTC live view options in the frontend which enable low-latency full-framerate live views that support audio.

    NOTES:

    The live view options are set in the Frigate WebUI for each camera individually.

    New detector types

    Frigate now supports new detector types along with the Google Coral TPU.

    OpenVINO

    The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements

    TensorRT

    NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.

    NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh

    New system page

    The Debug page has been renamed to System. It now includes much more information and links to easily get vainfo and ffprobe data.

    Screen Shot 2023-01-02 at 09 58 28 AM

    The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a VAINFO button which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.

    Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an FFPROBE button which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.

    The debug config has also been removed, the config can be copied using the config page in the WebUI.

    New storage page

    Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.

    Screen Shot 2023-01-02 at 09 55 49 AM

    New logs page

    Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.

    Screen Shot 2023-01-02 at 09 50 54 AM

    New config editor

    Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.

    NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to :ro or read-only. That will need to be removed for the config editor to be able to save the new file.

    Screen Shot 2023-01-02 at 09 48 49 AM

    MQTT is now optional

    Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.

    NOTE: MQTT is still required for the Frigate-HomeAssistant Integration

    No changes are needed for existing users.

    FFMpeg presets

    FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.

    Example: Enabling Audio In Recordings

    before:

    output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
    

    after:

    output_args:
      record: preset-record-generic-audio
    

    This also enables presets for hardware acceleration which will be used to further reduce CPU usage by using the GPU to optimize scaling and other workloads.

    Improved events filters

    Screen Shot 2023-01-02 at 09 21 31 AM

    • Multi Select Filters: Each filter now supports multi select so multiple cameras, labels, etc. can be viewed at the same time.
    • Favorited Event Filter: Events can now be filtered to only show favorited events along with the existing filters.

    Recordings updates

    Recording segments are now stored in UTC to avoid issues with DST. In order to avoid a breaking change, the path of the stored segments has changed from /media/frigate/recordings/%Y-%m/%d/%H-%s.mp4 to /media/frigate/recordings/%Y-%m-%d/%H-%s.mp4.

    Recordings in the frontend are now shown in the timezone of the device viewing frigate, so the timezone set on the server running frigate is irrelevant.

    No changes are needed for existing users.

    What's Changed

    • Storage Based Retention by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3942
    • Docs update: Update camera specific input_agrs for ESP32-cam using ESPHome by @MariusMueller in https://github.com/blakeblackshear/frigate/pull/4171
    • Add go2rtc and add restream role / live source by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4082
    • Catch case where segment is bad length by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4228
    • Add option enabled for each camera in config by @banthungprong in https://github.com/blakeblackshear/frigate/pull/4162
    • Adding clip duration to Events View by @banthungprong in https://github.com/blakeblackshear/frigate/pull/4133
    • Bump @xmldom/xmldom from 0.7.5 to 0.7.8 in /web by @dependabot in https://github.com/blakeblackshear/frigate/pull/4230
    • Bump vite from 2.8.6 to 2.9.13 in /web by @dependabot in https://github.com/blakeblackshear/frigate/pull/3885
    • Support special characters in passwords, redacted logs & debug config by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4057
    • Update docs to reflect recommended custom birdseye icon size by @Tuurkevg in https://github.com/blakeblackshear/frigate/pull/4065
    • Object Detector Abstraction by @NateMeyer in https://github.com/blakeblackshear/frigate/pull/3656
    • Update go2rtc to rc1 by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4252
    • Update funding list and fix demo link by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4258
    • Support more special chars in camera passwords by @NateMeyer in https://github.com/blakeblackshear/frigate/pull/4259
    • try a different approach for build_web by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4260
    • Configure Dependabot by @herostrat in https://github.com/blakeblackshear/frigate/pull/4271
    • actions updates by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4302
    • Upgrade to latest docusaurus by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4303
    • Update web by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4321
    • More config checks by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4310
    • Go2rtc update and MSE improvements by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4309
    • Update mask editor to have instructions by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4324
    • Update web deps by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4383
    • Revamped debug UI and add camera / process info, ffprobe copying by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4349
    • Fix new lines for instructions by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4371
    • Catch case where recording is not enabled by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4069
    • Remove wheels from final container by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4395
    • Update go2rtc, simplify manual stream, and support audio for MSE & WebRTC by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4391
    • Frontend fixes by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4411
    • Easy Python Updates by @herostrat in https://github.com/blakeblackshear/frigate/pull/4424
    • Update cuvid docs with count param by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4436
    • Fix mixed params for CPU / MEM debug by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4432
    • Fix internal restream error and add docs for reducing camera connections by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4431
    • Typing Part 3: events.py by @herostrat in https://github.com/blakeblackshear/frigate/pull/3352
    • Use testing repo for hwaccel dependencies by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4368
    • Improve the devcontainer experience by @felipecrs in https://github.com/blakeblackshear/frigate/pull/3492
    • Refactor mqtt to handle reconnects and not cause frigate to stop. by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4440
    • rename debug to system by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4447
    • Remove ffplay from docker image by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4449
    • Reduce amount layers of the docker image by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4448
    • Fix makefile by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4491
    • Abstract MQTT from communication and make mqtt optional by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4462
    • update web deps by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4498
    • low risk updatea by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4500
    • fix image build by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4503
    • Fix stats prefix by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4505
    • Remove topic prefix by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4515
    • fix support for yuv models by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4523
    • Clean http password, clean path in debug config as well by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4519
    • Fix recordings set name by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4543
    • Add GPU stats to the /stats API and debug screen by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3931
    • Replace green screen with error message and force camera_fps to 0 by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4544
    • FEAT: Support for ffmpeg presets by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3840
    • Fix gpu stats for ffmpeg presets by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4554
    • FEAT: Storage API & Frontend by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3409
    • Set User Agent for FFmpeg calls by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4555
    • Add OpenVino Detector by @NateMeyer in https://github.com/blakeblackshear/frigate/pull/3768
    • Upgrade s6-overlay from 2.2.0.3 to 3.1.2.1 by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4584
    • Fix intel gpu stats by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4581
    • Do not apply -user_agent for rtmp streams by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4596
    • Set max height so vainfo doesn't overflow by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4598
    • Update go2rtc version by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4616
    • Add config editor to webUI by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4608
    • Cleanup names in webUI by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4607
    • Log all services to memory by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4587
    • Add example of environment_vars by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4634
    • Fix end events for mqtt by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4647
    • Fix ffprobe with special characters by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4646
    • Logs in UI by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4562
    • Restart record process if segments stop being written. by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4604
    • Update method of acquiring signing keys by @NateMeyer in https://github.com/blakeblackshear/frigate/pull/4649
    • Don't catch presets with segment check by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4653
    • Use UTC for recordings by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4656
    • UI Cleanup & Optimization by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4673
    • FEAT: Filter Multi Select by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3367
    • System page improvements by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4707
    • Convert detectors to factory pattern, ability to set different model for each detector by @dennispg in https://github.com/blakeblackshear/frigate/pull/4635
    • Add apache2 reverse proxy documentation by @blacknell in https://github.com/blakeblackshear/frigate/pull/4502
    • Use presets by default by @felipecrs in https://github.com/blakeblackshear/frigate/pull/4597
    • Optimize nginx & recordings by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4688
    • Add note to docs about rpi kernel issue. by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4726
    • Show All and Solo selection buttons for MultiSelect. by @spacebares in https://github.com/blakeblackshear/frigate/pull/4723
    • Fix monaco editor issues by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4724
    • Fix MSE Issues by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4725
    • Folderize Docs: Each topic gets a folder by @herostrat in https://github.com/blakeblackshear/frigate/pull/4514
    • update contributing docs by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4727
    • force upgrade certs by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4728
    • Update certs by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4729
    • Frontend Player Fixes by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4778
    • Fix error when saving the config unsuccessfully by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4780
    • Update Reolink docs by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4757
    • Handle multi-word time zones by @singingtelegram in https://github.com/blakeblackshear/frigate/pull/4816
    • Frontend deps by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4824
    • Fix config missing after leaving and coming back by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4825
    • Nvidia TensorRT detector by @NateMeyer in https://github.com/blakeblackshear/frigate/pull/4718
    • Add hardware accelerated scaling when using ffmpeg hwaccel presets by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4804
    • Update max operations for stalebot by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4828
    • easier python deps by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4827
    • Bump actions/setup-python from 4.3.0 to 4.4.0 by @dependabot in https://github.com/blakeblackshear/frigate/pull/4786
    • Fix handling of timezones by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4831
    • Add ability to restream birdseye by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4761
    • Bump json5 from 2.2.1 to 2.2.2 in /docs by @dependabot in https://github.com/blakeblackshear/frigate/pull/4826
    • [API] filter for favorite events by @spacebares in https://github.com/blakeblackshear/frigate/pull/4737
    • Remove duplicate in docs by @tvdelgado in https://github.com/blakeblackshear/frigate/pull/4836
    • set env vars needed for nvidia support by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/4837

    New Contributors

    • @MariusMueller made their first contribution in https://github.com/blakeblackshear/frigate/pull/4171
    • @banthungprong made their first contribution in https://github.com/blakeblackshear/frigate/pull/4162
    • @Tuurkevg made their first contribution in https://github.com/blakeblackshear/frigate/pull/4065
    • @NateMeyer made their first contribution in https://github.com/blakeblackshear/frigate/pull/3656
    • @dennispg made their first contribution in https://github.com/blakeblackshear/frigate/pull/4635
    • @blacknell made their first contribution in https://github.com/blakeblackshear/frigate/pull/4502
    • @spacebares made their first contribution in https://github.com/blakeblackshear/frigate/pull/4723
    • @singingtelegram made their first contribution in https://github.com/blakeblackshear/frigate/pull/4816
    • @tvdelgado made their first contribution in https://github.com/blakeblackshear/frigate/pull/4836

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.11.1...v0.12.0-beta1

    Images:

    • blakeblackshear/frigate:0.12.0-beta1
    • ghcr.io/blakeblackshear/frigate:0.12.0-beta1
    • blakeblackshear/frigate:0.12.0-beta1-tensorrt
    • ghcr.io/blakeblackshear/frigate:0.12.0-beta1-tensorrt
    Source code(tar.gz)
    Source code(zip)
  • v0.11.1(Oct 8, 2022)

    What's Changed

    • FIX: Set a timeout on github release check by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3969
    • FEAT: Mqtt sub labels by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3899
    • FIX: Update motion topic when enabling due to detect topic by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/3898
    • DOCS: Add an example for birdseye override at camera level by @Mincka in https://github.com/blakeblackshear/frigate/pull/3922
    • DOCS: indentation, device Id by @kamahat in https://github.com/blakeblackshear/frigate/pull/3921
    • FIX: don't overwrite segments that already exist by @blakeblackshear in https://github.com/blakeblackshear/frigate/pull/3995
    • FIX: Fix sub label access by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4015
    • FIX: Catch ffprobe empty stdout by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4016
    • DOCS: Fix some typos in docs by @xconverge in https://github.com/blakeblackshear/frigate/pull/4020
    • FIX: Remove snapshot requirement for thumbnail event query by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4039
    • DOCS: Link to env var option by @NickM-27 in https://github.com/blakeblackshear/frigate/pull/4032
    • DOCS: Restructured camera specific documentation by @menkej in https://github.com/blakeblackshear/frigate/pull/4005

    New Contributors

    • @Mincka made their first contribution in https://github.com/blakeblackshear/frigate/pull/3922
    • @kamahat made their first contribution in https://github.com/blakeblackshear/frigate/pull/3921
    • @xconverge made their first contribution in https://github.com/blakeblackshear/frigate/pull/4020
    • @menkej made their first contribution in https://github.com/blakeblackshear/frigate/pull/4005

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.11.0...v0.11.1

    Image: blakeblackshear/frigate:0.11.1

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0(Sep 22, 2022)

    Major Changes for 0.11.0

    🚨 🚨 BREAKING CHANGES 🚨 🚨

    • Several addon users have reported that a full uninstall and reinstall is necessary. In place upgrades are failing with a "Invalid build environment, can't build this add-on!" message in the supervisor logs.
    • If you are using the Home Assistant integration and/or custom lovelace card, be sure to update those to their latest releases as well.
    • Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
    • Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME=i965 to get similar hardware acceleration performance to previous versions.
    • Upgrading will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable or in the addon configuration page. Note that this cannot be set in the yml configuration file. It must be set in your compose file or docker command.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image. Support for nvidia decoding is built into the single image. There is no longer a need for a special tag.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative timeline UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to Btbn ffmpeg builds
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icon can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers
    • Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)
    • Fix bug with bounding boxes outside of frame
    • Ensure playlist is in front of error messages in videojs
    • Fixes for H265 events and recordings in browsers with native support for H265 (thanks @uvjustin)
    • Fixes for stuttering playback issues in some circumstances (thanks @uvjustin)

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.1...v0.11.0

    Image: blakeblackshear/frigate:0.11.0

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-rc3(Sep 17, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since rc2

    • Fix bug when multiple requests to download clip are initiated
    • Fix bug with bounding boxes outside of frame (round 2)
    • Add ability to view snapshots in UI when video exists
    • Ensure playlist is in front of error messages in videojs

    Changes since rc1

    • Switch to using BtbN ffmpeg builds to resolve AAC errors with rtsp-simple-server (now at version 5.1)
      • NOTE: Those who set the LIBVA_DRIVER_NAME_JELLYFIN variable now need to update it to LIBVA_DRIVER_NAME
    • Fixes for H265 events and recordings in browsers with native support for H265 (thanks @uvjustin)
    • Fixes for stuttering playback issues in some circumstances (thanks @uvjustin)
    • Fix bug where bounding box sometimes outside of frame
    • Ensure labels with spaces work properly
    • Update videojs

    BREAKING CHANGES

    • Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
    • Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME=i965 to get similar hardware acceleration performance to previous builds.
    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to Btbn ffmpeg builds
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icon can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers
    • Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-rc3

    Image: blakeblackshear/frigate:0.11.0-rc3

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-rc2(Aug 28, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since rc1

    • Switch to using BtbN ffmpeg builds to resolve AAC errors with rtsp-simple-server (now at version 5.1)
      • NOTE: Those who set the LIBVA_DRIVER_NAME_JELLYFIN variable now need to update it to LIBVA_DRIVER_NAME
    • Fixes for H265 events and recordings in browsers with native support for H265 (thanks @uvjustin)
    • Fixes for stuttering playback issues in some circumstances (thanks @uvjustin)
    • Fix bug where bounding box sometimes outside of frame
    • Ensure labels with spaces work properly
    • Update videojs

    BREAKING CHANGES

    • Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
    • Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME=i965 to get similar hardware acceleration performance to previous builds.
    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers
    • Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-rc2

    Image: blakeblackshear/frigate:0.11.0-rc2

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-rc1(Jul 23, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since beta 7

    • Fixed "Send to Frigate+" for addon users

    BREAKING CHANGES

    • Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
    • Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME_JELLYFIN=i965 to get similar hardware acceleration performance to previous builds.
    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers
    • Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-rc1

    Image: blakeblackshear/frigate:0.11.0-rc1

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-beta7(Jul 20, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since beta 6

    • Removed logging when recording segments are discarded as these are a false warning in many cases

    Changes since beta 5

    • Note new breaking change! Switch to ffmpeg 5 (I know, I know...)
    • Fixed arm32 compatibility (for now, but this is hanging by a thread)
    • Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)
    • Recordings playback no longer resets when switching windows
    • Experimental timeline UI improvements (#3298)
    • Improve logging if recording segments are discarded when the cache falls behind

    BREAKING CHANGES

    • Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
    • Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME_JELLYFIN=i965 to get similar hardware acceleration performance to previous builds.
    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-beta7

    Image: blakeblackshear/frigate:0.11.0-beta7

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-beta6(Jul 20, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since beta 5

    • Note new breaking change! Switch to ffmpeg 5 (I know, I know...)
    • Fixed arm32 compatibility (for now, but this is hanging by a thread)
    • Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)
    • Recordings playback no longer resets when switching windows
    • Experimental timeline UI improvements (#3298)
    • Improve logging if recording segments are discarded when the cache falls behind

    BREAKING CHANGES

    • Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
    • Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME_JELLYFIN=i965 to get similar hardware acceleration performance to previous builds.
    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-beta6

    Image: blakeblackshear/frigate:0.11.0-beta6

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-beta5(Jul 2, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since beta 4

    • Support for reading Frigate+ api key from hassos addon options
    • Switch back to ffmpeg 4.4.1

    Changes since beta 3

    • Just a re-release with the frontend build updated

    Changes since beta 2

    • Switch to ffmpeg 4.3.2 in hopes of audio encoding and hwaccel fixes
    • Fixes for UI not loading with addons
    • Fix delete icon for firefox
    • Warning when deleting favorite events
    • Gracefully handle failed new version checks when frigate doesn't have internet access
    • Add filtering for sub labels
    • Remove deprecated max_seconds config option

    BREAKING CHANGES

    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-beta5

    Image: blakeblackshear/frigate:0.11.0-beta5

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-beta4(Jun 13, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since beta 3

    • Just a re-release with the frontend build updated

    Changes since beta 2

    • Switch to ffmpeg 4.3.2 in hopes of audio encoding and hwaccel fixes
    • Fixes for UI not loading with addons
    • Fix delete icon for firefox
    • Warning when deleting favorite events
    • Gracefully handle failed new version checks when frigate doesn't have internet access
    • Add filtering for sub labels
    • Remove deprecated max_seconds config option

    BREAKING CHANGES

    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-beta4

    Image: blakeblackshear/frigate:0.11.0-beta4

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-beta3(Jun 11, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    Changes since beta 2

    • Switch to ffmpeg 4.3.2 in hopes of audio encoding and hwaccel fixes
    • Fixes for UI not loading with addons
    • Fix delete icon for firefox
    • Warning when deleting favorite events
    • Gracefully handle failed new version checks when frigate doesn't have internet access
    • Add filtering for sub labels
    • Remove deprecated max_seconds config option

    BREAKING CHANGES

    • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
    • The max_seconds config setting under events has been removed as it no longer has any effect

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-beta3

    Image: blakeblackshear/frigate:0.11.0-beta3

    Source code(tar.gz)
    Source code(zip)
  • v0.11.0-beta2(May 18, 2022)

    Major Changes for 0.11.0

    Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

    BREAKING CHANGES

    • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
    • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)

    Frigate+ Integration

    With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

    To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

    image

    Here is the roadmap for Frigate+:

    • [x] Launch web version allowing manual upload of training examples and labeling
    • [x] Integrate submission in Frigate
    • [ ] Launch Frigate optimized models
    • [ ] Launch individually optimized models
    • [ ] Integrate labeling and suggestions in Frigate

    Updated Events View

    • Speed. The events view has been completely revamped and should be much faster than it was before.
    • Slightly larger thumbnails.
    • You no longer have to refresh the page to see the latest events.
    • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
    • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

    Updated Recordings View

    • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
    • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
    • 16x playback was added for browsers other than Firefox.

    Updated Dockerbuild

    • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

    Experimental Timeline UI

    Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

    Other changes

    • MQTT sensors for any object type #2908
    • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
    • Added a new ratio filter for object filters #2952
    • Camera recordings always in sidebar #2846
    • Enable and set mode per camera for birdseye #3083
    • Customize order and hide cameras from the UI #2981
    • Enable improve_contrast via MQTT #3011
    • Enable/disable motion detection independent of object detection via MQTT #3117
    • MQTT topic for motion detection #3152
    • Batch deletes of recordings when more than 100,000 recordings need to be deleted
    • Switch to jellyfin ffmpeg
    • Improve cache handling for thumbnails and snapshots of completed events
    • Fixes hwaccel issues for Raspberry Pi users
    • Updates to debian 11 as a base image
    • Consolidate Dockerfile to enable multiarch images
    • Birdseye icno can now be customized #2979
    • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
    • Initial implementation of mypy and type checking
    • Images from backend now have appropriate cache headers

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.11.0-beta2

    Image: blakeblackshear/frigate:0.11.0-beta2

    Source code(tar.gz)
    Source code(zip)
  • v0.10.1(Mar 11, 2022)

    Changes:

    • Make dynamic contrast optional and disable by default
    • Cleanup print statement

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.10.0...v0.10.1

    Images:

    • x86: blakeblackshear/frigate:0.10.1-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.1-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.1-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.1-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0(Feb 19, 2022)

    Major Changes for 0.10.0

    BREAKING CHANGES

    Camera Names

    Camera names in the config file must be URL safe starting with this version. Only A-Z, a-z, 0-9, -, and _ are permitted. If your cameras need to be renamed, any associated events will be retained based on your global retain settings, not the new camera name settings. If you want to retain recordings from the previous camera name, you need to ensure you have retain days set globally. For example:

    record: #  <---------- global setting
      retain:
        days: 7 # <------- will retain 7 days of recordings for old cameras
    

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary -> interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    The following settings have been added to tune stationary tracking:

    detect:
      ...
      # Optional: Configuration for stationary object tracking
      stationary:
        # Optional: Frequency for running detection on stationary objects (default: shown below)
        # When set to 0, object detection will never be run on stationary objects. If set to 10, 
        # it will be run on every 10th frame.
        interval: 0
        # Optional: Number of frames without a position change for an object to be considered 
        # stationary (default: 10x the frame rate or 10s)
        threshold: 50
        # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
        # This can help with false positives for objects that should only be stationary for a limited amount of time.
        # It can also be used to disable stationary object tracking. For example, you may want to set a value for person,
        # but leave car at the default.
        max_frames:
          # Optional: Default for all object types (default: not set, track forever)
          default: 3000
          # Optional: Object specific values
          objects:
            person: 1000
    

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations. It may result in more false positives at night.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones
    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Make recording expiration interval configurable (previously hard coded to 60 minutes)
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives
    • Allow recording motion even when detect is disabled
    • Add stacktrace to config errors
    • Tweak error messages when ffmpeg fails
    • Update has_clip to false when an event fails to play
    • Handle rare divide by zero in fps calculation
    • Recordings link is always visible in the UI even when record is disabled
    • Playback rate is retained in recordings viewer

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0

    Images:

    • x86: blakeblackshear/frigate:0.10.0-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-rc1(Feb 15, 2022)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 12

    • None

    BREAKING CHANGES

    Camera Names

    Camera names in the config file must be URL safe starting with this version. Only A-Z, a-z, 0-9, -, and _ are permitted. If your cameras need to be renamed, any associated events will be retained based on your global retain settings, not the new camera name settings. If you want to retain recordings from the previous camera name, you need to ensure you have retain days set globally. For example:

    record: #  <---------- global setting
      retain:
        days: 7 # <------- will retain 7 days of recordings for old cameras
    

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary -> interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    The following settings have been added to tune stationary tracking:

    detect:
      ...
      # Optional: Configuration for stationary object tracking
      stationary:
        # Optional: Frequency for running detection on stationary objects (default: shown below)
        # When set to 0, object detection will never be run on stationary objects. If set to 10, 
        # it will be run on every 10th frame.
        interval: 0
        # Optional: Number of frames without a position change for an object to be considered 
        #                 stationary (default: 10x the frame rate or 10s)
        threshold: 50
        # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
        # This can help with false positives for objects that should only be stationary for a limited amount of time.
        # It can also be used to disable stationary object tracking. For example, you may want to set a value for person,
        # but leave car at the default.
        max_frames:
          # Optional: Default for all object types (default: not set, track forever)
          default: 3000
          # Optional: Object specific values
          objects:
            person: 1000
    

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones
    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Make recording expiration interval configurable (previously hard coded to 60 minutes)
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives
    • Allow recording motion even when detect is disabled
    • Add stacktrace to config errors
    • Tweak error messages when ffmpeg fails
    • Update has_clip to false when an event fails to play
    • Handle rare divide by zero in fps calculation
    • Recordings link is always visible in the UI even when record is disabled
    • Playback rate is retained in recordings viewer

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-rc1

    Images:

    • x86: blakeblackshear/frigate:0.10.0-rc1-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-rc1-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-rc1-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-rc1-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta12(Feb 13, 2022)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 11

    • New max_frames setting to allow per object customization of stationary tracking
    • BREAKING CHANGE refactored stationary settings (previously stationary_threshold and stationary_interval) under a stationary section
    detect:
      ...
      # Optional: Configuration for stationary object tracking
      stationary:
        # Optional: Frequency for running detection on stationary objects (default: shown below)
        # When set to 0, object detection will never be run on stationary objects. If set to 10, 
        # it will be run on every 10th frame.
        interval: 0
        # Optional: Number of frames without a position change for an object to be considered 
        # stationary (default: 10x the frame rate or 10s)
        threshold: 50
        # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
        # This can help with false positives for objects that should only be stationary for a limited amount of time.
        # It can also be used to disable stationary object tracking. For example, you may want to set a value for person,
        # but leave car at the default.
        max_frames:
          # Optional: Default for all object types (default: not set, track forever)
          default: 3000
          # Optional: Object specific values
          objects:
            person: 1000
    

    Changes since beta 10

    • Default for stationary_threshold is now 10x the FPS or ~10s
    • Update birdseye to only show non-stationary objects
    • Recordings link is always visible in the UI even when record is disabled

    BREAKING CHANGES

    Camera Names

    Camera names in the config file must be URL safe starting with this version. Only A-Z, a-z, 0-9, -, and _ are permitted. If your cameras need to be renamed, any associated events will be retained based on your global retain settings, not the new camera name settings. If you want to retain recordings from the previous camera name, you need to ensure you have retain days set globally. For example:

    record: #  <---------- global setting
      retain:
        days: 7 # <------- will retain 7 days of recordings for old cameras
    

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary -> interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    The following settings have been added to tune stationary tracking:

    detect:
      ...
      # Optional: Configuration for stationary object tracking
      stationary:
        # Optional: Frequency for running detection on stationary objects (default: shown below)
        # When set to 0, object detection will never be run on stationary objects. If set to 10, 
        # it will be run on every 10th frame.
        interval: 0
        # Optional: Number of frames without a position change for an object to be considered 
        #                 stationary (default: 10x the frame rate or 10s)
        threshold: 50
        # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
        # This can help with false positives for objects that should only be stationary for a limited amount of time.
        # It can also be used to disable stationary object tracking. For example, you may want to set a value for person,
        # but leave car at the default.
        max_frames:
          # Optional: Default for all object types (default: not set, track forever)
          default: 3000
          # Optional: Object specific values
          objects:
            person: 1000
    

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones
    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Make recording expiration interval configurable (previously hard coded to 60 minutes)
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives
    • Allow recording motion even when detect is disabled
    • Add stacktrace to config errors
    • Tweak error messages when ffmpeg fails
    • Update has_clip to false when an event fails to play
    • Handle rare divide by zero in fps calculation

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta12

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta12-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta12-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta12-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta12-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta11(Feb 12, 2022)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 10

    • Default for stationary_threshold is now 10x the FPS or ~10s
    • Update birdseye to only show non-stationary objects
    • Recordings link is always visible in the UI even when record is disabled

    BREAKING CHANGES

    Camera Names

    Camera names in the config file must be URL safe starting with this version. Only A-Z, a-z, 0-9, -, and _ are permitted. If your cameras need to be renamed, any associated events will be retained based on your global retain settings, not the new camera name settings. If you want to retain recordings from the previous camera name, you need to ensure you have retain days set globally. For example:

    record: #  <---------- global setting
      retain:
        days: 7 # <------- will retain 7 days of recordings for old cameras
    

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary_interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones
    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Make recording expiration interval configurable (previously hard coded to 60 minutes)
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives
    • Allow recording motion even when detect is disabled
    • Add stacktrace to config errors
    • Tweak error messages when ffmpeg fails
    • Update has_clip to false when an event fails to play
    • Handle rare divide by zero in fps calculation

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta11

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta11-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta11-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta11-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta11-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta10(Feb 10, 2022)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 9

    • Publish mqtt updates to events topic on position changes, when an object becomes stationary, and at least once per minute
    • Make stationary_threshold configurable so you can adjust how many frames are required to determine an object is stationary
    • In progress events are now listed in the recordings viewer
    • Playback rate is retained in recordings viewer
    • In progress events can now be downloaded

    BREAKING CHANGES

    Camera Names

    Camera names in the config file must be URL safe starting with this version. Only A-Z, a-z, 0-9, -, and _ are permitted. If your cameras need to be renamed, any associated events will be retained based on your global retain settings, not the new camera name settings. If you want to retain recordings from the previous camera name, you need to ensure you have retain days set globally. For example:

    record: #  <---------- global setting
      retain:
        days: 7 # <------- will retain 7 days of recordings for old cameras
    

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary_interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones
    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Make recording expiration interval configurable (previously hard coded to 60 minutes)
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives
    • Allow recording motion even when detect is disabled
    • Add stacktrace to config errors
    • Tweak error messages when ffmpeg fails
    • Update has_clip to false when an event fails to play
    • Handle rare divide by zero in fps calculation

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta10

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta10-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta10-amd64nvidia
    • ~Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta10-armv7~
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta10-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta9(Feb 7, 2022)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 8

    • Allow recording motion even when detect is disabled
    • Fix bug with active_objects retain mode
    • Keep counting motionless frames for stationary objects
    • Add stacktrace to config errors
    • Tweak error messages when ffmpeg fails
    • Update has_clip to false when an event fails to play
    • Handle rare divide by zero in fps calculation
    • Docs updates

    Changes since beta 7

    • Allow - in camera names

    Changes since beta 6

    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Improve method used to determine when an object is stationary
    • Stop periodic scans on stationary objects by default
    • Make expiration interval configurable (previously hard coded to 60 minutes)
    • Make motion the default retain mode for events
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary_interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta9

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta9-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta9-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta9-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta9-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta8(Feb 5, 2022)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 7

    • Allow - in camera names

    Changes since beta 6

    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Improve method used to determine when an object is stationary
    • Stop periodic scans on stationary objects by default
    • Make expiration interval configurable (previously hard coded to 60 minutes)
    • Make motion the default retain mode for events
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary_interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta8

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta8-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta8-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta8-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta8-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta7(Feb 5, 2022)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 6

    • Frigate now scans for objects in the frame on startup
    • Detected objects that never move no longer generate events or snapshots
    • Improve method used to determine when an object is stationary
    • Stop periodic scans on stationary objects by default
    • Make expiration interval configurable (previously hard coded to 60 minutes)
    • Make motion the default retain mode for events
    • New event datepicker in the events viewer
    • Require camera names to be url safe
    • Ensure clean snapshots are deleted when deleting events
    • Fix bug when last recording in the database does not exist on disk
    • Randomize the region slightly to try and reduce lost true positives

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have motion for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be paused (the new stationary_interval setting allows periodic checks too) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous 10 frames. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings at the interval set in the expire_interval setting (defaults to once per hour).

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones

    Fixes

    • fixes #2129
    • fixes #2734

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta7

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta7-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta7-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta7-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta7-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta6(Dec 13, 2021)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 5

    • Fix issue with migrations for new users
    • Remove disk sync on startup

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have active_objects for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new stationary_interval setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings once per hour.

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones

    Fixes

    • fixes #2129

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta6

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta6-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta6-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta6-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta6-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta5(Dec 13, 2021)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 4

    • Add new retention modes to allow only storing recording segments when tracked objects are active
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones
    • Only sync database recordings with the disk on startup
    • Only expire recordings once per hour
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml

    Retain modes

    This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:

    • all: retain all recording segments. This is consistent with the previous behavior
    • motion: retain only the recording segments that have some motion
    • active_objects: retain only the recording segments that have a moving true positive object that is being tracked

    The default record settings will retain only segments that have active_objects for events.

    Note that the retain_days config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.

    Example: Store all segments with motion for 7 days and events with active objects for 14 days.

    record:
      enabled: True
      retain:
        days: 7
        mode: motion
      events:
        retain:
          default: 14
          mode: active_objects
    

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new stationary_interval setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    Now that recordings are managed proactively, recordings are expired according to the retention settings once per hour.

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions
    • Report coral temperature stats when available (USB Coral not supported)
    • Limit the cache time for playlist urls to avoid recording playback failures
    • Allow yaml extension in addition to yml
    • Sync database recordings with the disk on startup
    • Store motion and objects data in database
    • Entered zones in mqtt messages are now sorted based on the order the object entered zones

    Fixes

    • fixes #2129

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta5

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta5-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta5-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta5-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta5-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta4(Nov 21, 2021)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 3

    • Fix issue causing recording segments to be missing for events that ended before the segment was ready
    • Prevent stationary interval from being less than 1
    • Fix snapshot url for in progress events
    • Prevent segments in playlist from having duration 0
    • Add logging for error messages in VOD endpoints
    • Cleanup recordings missing from disk once per hour

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new stationary_interval setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. This means that the recording segments will be retained for all 5 hours the car was tracked. In addition, the zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions

    Fixes

    • fixes #2129

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta4

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta4-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta4-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta4-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta4-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta3(Nov 19, 2021)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Changes since beta 2

    • Bugfix for local variable 'duration' referenced before assignment errors

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new stationary_interval setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. This means that the recording segments will be retained for all 5 hours the car was tracked. In addition, the zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions

    Fixes

    • fixes #2129

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta3

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta3-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta3-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta3-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta3-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta2(Nov 19, 2021)

    Major Changes for 0.10.0

    Updated docs are available for preview here.

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new stationary_interval setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. This means that the recording segments will be retained for all 5 hours the car was tracked. In addition, the zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. If you have customized either frame_height or contour_area in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjusting contour_area (smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions

    Fixes

    • fixes #2129

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta2

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta2-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta2-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta2-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta2-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.10.0-beta1(Nov 15, 2021)

    Major Changes for 0.10.0

    Stationary objects

    Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new stationary_interval setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.

    I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. This means that the recording segments will be retained for all 5 hours the car was tracked. In addition, the zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived.

    Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

    fixes #841

    In progress events and cache handling

    Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

    Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so no you can enable recording without worrying about SD/SSD wear.

    Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. If too many cache segments exist, they will be deleted and a warning message (Proactively cleaning cache. Your recordings disk may be too slow.) will be printed to the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

    fixes #1885

    Motion detection improvements

    0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

    In this release, motion detection has been reset back to better defaults for frame_height and contour_area. For most users, the sensitivity can be tuned by adjusting contour_area. For very high resolutions with very small objects, the frame_height may need to be increased.

    In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

    Other changes

    • Improved logic for merging motion, bounding boxes, and regions

    Fixes

    • fixes #2129

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta1

    Images:

    • x86: blakeblackshear/frigate:0.10.0-beta1-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta1-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta1-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta1-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.9.4(Oct 24, 2021)

    Bug Fixes:

    • Fix rtmp global config again :facepalm:

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.3...v0.9.4

    Images:

    • x86: blakeblackshear/frigate:0.9.4-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.9.4-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.9.4-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.9.4-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.9.3(Oct 24, 2021)

    Bug Fixes:

    • Fix cleanup of legacy recordings
    • Prevent config validation failure when rtmp disabled globally
    • Revert switch to mpegts for default segment format (0.9.2 issues)
    • Revert default to including audio (0.9.2 issues)

    Changes:

    • Improve performance of cache loop

    Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.2...v0.9.3

    Images:

    • x86: blakeblackshear/frigate:0.9.3-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.9.3-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.9.3-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.9.3-aarch64
    Source code(tar.gz)
    Source code(zip)
  • v0.9.2(Oct 20, 2021)

    NOTICE: There are some known issues with this release.

    • https://github.com/blakeblackshear/frigate/issues/2055
    • https://github.com/blakeblackshear/frigate/issues/1755#issuecomment-948086442

    Bug Fixes:

    • Fix bug causing some recording segments to expire early within an event

    Changes:

    • Switch to mpegts container type for recording cache to reduce lost footage if ffmpeg exits
    • Clearer log messages on invalid config
    • Assume default roles when a single input is specified
    • Restrict max size of live view to specified resolution
    • Audio is included by default in recordings

    Images:

    • x86: blakeblackshear/frigate:0.9.2-amd64
    • x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.9.2-amd64nvidia
    • Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.9.2-armv7
    • Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.9.2-aarch64
    Source code(tar.gz)
    Source code(zip)
Owner
Blake Blackshear
Blake Blackshear
Composable transformations of Python+NumPy programs: differentiate, vectorize, JIT to GPU/TPU, and more

JAX: Autograd and XLA Quickstart | Transformations | Install guide | Neural net libraries | Change logs | Reference docs | Code search News: JAX tops

Google 21.3k Jan 01, 2023
Council-GAN - Implementation for our paper Breaking the Cycle - Colleagues are all you need (CVPR 2020)

Council-GAN Implementation of our paper Breaking the Cycle - Colleagues are all you need (CVPR 2020) Paper Ori Nizan , Ayellet Tal, Breaking the Cycle

ori nizan 260 Nov 16, 2022
Rethinking the Importance of Implementation Tricks in Multi-Agent Reinforcement Learning

RIIT Our open-source code for RIIT: Rethinking the Importance of Implementation Tricks in Multi-AgentReinforcement Learning. We implement and standard

405 Jan 06, 2023
U-Net: Convolutional Networks for Biomedical Image Segmentation

Deep Learning Tutorial for Kaggle Ultrasound Nerve Segmentation competition, using Keras This tutorial shows how to use Keras library to build deep ne

Yihui He 401 Nov 21, 2022
True per-item rarity for Loot

True-Rarity True per-item rarity for Loot (For Adventurers) and More Loot A.K.A mLoot each out/true_rarity_{item_type}.json file contains probabilitie

Dan R. 3 Jul 26, 2022
Human-Pose-and-Motion History

Human Pose and Motion Scientist Approach Eadweard Muybridge, The Galloping Horse Portfolio, 1887 Etienne-Jules Marey, Descent of Inclined Plane, Chron

Daito Manabe 47 Dec 16, 2022
Deeply Supervised, Layer-wise Prediction-aware (DSLP) Transformer for Non-autoregressive Neural Machine Translation

Non-Autoregressive Translation with Layer-Wise Prediction and Deep Supervision Training Efficiency We show the training efficiency of our DSLP model b

Chenyang Huang 36 Oct 31, 2022
Tesla Light Show xLights Guide With python

Tesla Light Show xLights Guide Welcome to the Tesla Light Show xLights guide! You can create and run your own light shows on Tesla vehicles. Running a

Tesla, Inc. 2.5k Dec 29, 2022
Official implementation of Few-Shot and Continual Learning with Attentive Independent Mechanisms

Few-Shot and Continual Learning with Attentive Independent Mechanisms This repository is the official implementation of Few-Shot and Continual Learnin

Chikan_Huang 25 Dec 08, 2022
Multi-tool reverse engineering collaboration solution.

CollaRE v0.3 Intorduction CollareRE is a tool for collaborative reverse engineering that aims to allow teams that do need to use more then one tool du

105 Nov 27, 2022
Weight estimation in CT by multi atlas techniques

maweight A Python package for multi-atlas based weight estimation for CT images, including segmentation by registration, feature extraction and model

György Kovács 0 Dec 24, 2021
Official code repository for the publication "Latent Equilibrium: A unified learning theory for arbitrarily fast computation with arbitrarily slow neurons"

Latent Equilibrium: A unified learning theory for arbitrarily fast computation with arbitrarily slow neurons This repository contains the code to repr

Computational Neuroscience, University of Bern 3 Aug 04, 2022
Pytorch Performace Tuning, WandB, AMP, Multi-GPU, TensorRT, Triton

Plant Pathology 2020 FGVC7 Introduction A deep learning model pipeline for training, experimentaiton and deployment for the Kaggle Competition, Plant

Bharat Giddwani 0 Feb 25, 2022
The official implementation of "Rethink Dilated Convolution for Real-time Semantic Segmentation"

RegSeg The official implementation of "Rethink Dilated Convolution for Real-time Semantic Segmentation" Paper: arxiv D block Decoder Setup Install the

Roland 61 Dec 27, 2022
Code for the paper "Spatio-temporal Self-Supervised Representation Learning for 3D Point Clouds" (ICCV 2021)

Spatio-temporal Self-Supervised Representation Learning for 3D Point Clouds This is the official code implementation for the paper "Spatio-temporal Se

Hesper 63 Jan 05, 2023
Official PyTorch implementation of Spatial Dependency Networks.

Spatial Dependency Networks: Neural Layers for Improved Generative Image Modeling Đorđe Miladinović   Aleksandar Stanić   Stefan Bauer   Jürgen Schmid

Djordje Miladinovic 34 Jan 19, 2022
Semantic code search implementation using Tensorflow framework and the source code data from the CodeSearchNet project

Semantic Code Search Semantic code search implementation using Tensorflow framework and the source code data from the CodeSearchNet project. The model

Chen Wu 24 Nov 29, 2022
Devkit for 3D -- Some utils for 3D object detection based on Numpy and Pytorch

D3D Devkit for 3D: Some utils for 3D object detection and tracking based on Numpy and Pytorch Please consider siting my work if you find this library

Jacob Zhong 27 Jul 07, 2022
Github project for Attention-guided Temporal Coherent Video Object Matting.

Attention-guided Temporal Coherent Video Object Matting This is the Github project for our paper Attention-guided Temporal Coherent Video Object Matti

71 Dec 19, 2022
Statistical-Rethinking-with-Python-and-PyMC3 - Python/PyMC3 port of the examples in " Statistical Rethinking A Bayesian Course with Examples in R and Stan" by Richard McElreath

Statistical Rethinking with Python and PyMC3 This repository has been deprecated in favour of this one, please check that repository for updates, for

Osvaldo Martin 786 Dec 29, 2022