[SUPPORT] blakeblackshear - Frigate

yayitazale · July 26

On 7/24/2024 at 10:52 AM, John Graham said:

I know that you all are talking abut a docker version. But does anyone know how to get the Google Coral TPU pci version to show up on a VM i like running it as a VM so what or HOW. Can anyone help. I know that i might have been talked about here on UNraid forums but i have not found it yet 🙃

Thanks John G.

Just bind the device to the VM

mikey6283 · July 26

1 minute ago, yayitazale said:

Run the command "ls -l /dev/" in the unraid console and see if you have the apex_0

I have been able to get it works , I prolems was HA frigate addon was competing with Frigate Gu it seems to working at the moment. go2rtc is the problem now but has been for awhile.

yayitazale · July 26

6 hours ago, SavageAUS said:

I have been using Frigate for a little while now and it is working ok but i think I have room for improvement.
Can anyone see anything I could change / optimize?

mqtt:
  enabled: true
  host: 192.168.XX.XX
  port: 1883
  user: XXXXXXXX
  password: XXXXXXX
  topic_prefix: XXXXXXXXXX
  client_id: XXXXXXXXXXX
  stats_interval: 60

##------------------------------------------------------------------------------------------------------------------------------------------------------
detectors:
  coral1:
    type: edgetpu
    device: pci:0
  coral2:
    type: edgetpu
    device: pci:1

##------------------------------------------------------------------------------------------------------------------------------------------------------
database:
  path: /config/frigate.db

##------------------------------------------------------------------------------------------------------------------------------------------------------
auth:
  enabled: true
  reset_admin_password: false
  #cookie_name: frigate_token
  cookie_secure: false
  session_length: 86400 # 24 hours
  refresh_time: 43200 # 12 hours
  failed_login_rate_limit: None
  # trusted_proxies: [https://XXXXXXX.XXXXXXXXXX.XXX]
  hash_iterations: 600000

##------------------------------------------------------------------------------------------------------------------------------------------------------
model:
  path: /edgetpu_model.tflite
  labelmap_path: /labelmap.txt
  width: 320
  height: 320
  input_pixel_format: rgb
  input_tensor: nhwc
  model_type: ssd
  labelmap:
    1: person
#    2: car

##------------------------------------------------------------------------------------------------------------------------------------------------------
birdseye:
  enabled: true
  mode: continuous
  quality: 5
  restream: true
  width: 1920
  height: 1080

##------------------------------------------------------------------------------------------------------------------------------------------------------
ffmpeg:
  global_args: -hide_banner -loglevel warning -threads 2
  hwaccel_args: auto
  input_args: preset-rtsp-generic
  retry_interval: 10

##------------------------------------------------------------------------------------------------------------------------------------------------------
detect:
  width: 1920
  height: 1080
  fps: 15
  enabled: true
  min_initialized: 2
  max_disappeared: 50
  stationary:
    interval: 50
    threshold: 50

##------------------------------------------------------------------------------------------------------------------------------------------------------
objects:
  track:
    - person
    #- fox
    #- car
    #- dog
    #- cat
  filters:
    person:
      # Optional: minimum width*height of the bounding box for the detected object (default: 0)
      min_area: 2000
      # Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
      #max_area: 100000
      # Optional: minimum width/height of the bounding box for the detected object (default: 0)
      #min_ratio: 0
      # Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
      #max_ratio: 0.8
      # Optional: minimum score for the object to initiate tracking (default: shown below)
      min_score: 0.50
      # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
      threshold: 0.6
#    car:
#      threshold: 0.7
#    fox:
#      threshold: 0.5
#    cat:
#      threshold: 0.5
#    dog:
#      threshold: 0.5

##------------------------------------------------------------------------------------------------------------------------------------------------------
review:
  alerts:
    labels:
#      - car
      - person
#    required_zones:
#      - Turret-Front
#      - PTZ-Front
  detections:
    labels:
#      - car
      - person
#    required_zones:
#      - Turret-Front
#      - PTZ-Front

##------------------------------------------------------------------------------------------------------------------------------------------------------
motion:
  threshold: 20
  lightning_threshold: 0.8
  contour_area: 10
  frame_alpha: 0.01
  frame_height: 100
  improve_contrast: true

##------------------------------------------------------------------------------------------------------------------------------------------------------
record:
  #sync_recordings: True
  enabled: true
  retain:
    days: 7
    mode: all
  preview:
    quality: medium
  export:
    timelapse_args: -vf setpts=0.04*PTS -r 30
  events:
    pre_capture: 5
    post_capture: 5
    objects:
      - person
    retain:
      default: 7
      mode: motion
      objects:
        person: 7

##------------------------------------------------------------------------------------------------------------------------------------------------------
snapshots:
  enabled: true
  clean_copy: true
  timestamp: true
  bounding_box: true
  crop: false
  height: 1080
  retain:
    default: 7
    objects:
      person: 7
  quality: 80
#  required_zones:
#    - Turret-Front
#    - PTZ-Front

##------------------------------------------------------------------------------------------------------------------------------------------------------
go2rtc:
  streams:
    Turret:
      - ffmpeg:rtsp://192.168.XX.XX:554/11
    PTZ:
      - ffmpeg:rtsp://192.168.XX.XX:554/12

##------------------------------------------------------------------------------------------------------------------------------------------------------
cameras:
  Turret:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://192.168.XX.XX:554/11
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
            - rtmp
    motion:
      threshold: 30
      contour_area: 10
      improve_contrast: 'true'
      mask: 0.752,0.04,1,0.044,1,0,0.752,0
    objects:
      filters:
        car: {}
      mask: 0,0,0,0.28,0.271,0.173,0.684,0.118,0.905,0.203,1,0.346,1,0
    zones:
      Turret-Front:
        coordinates: 0.284,0.178,0.093,0.235,0.001,0.286,0,1,1,1,1,0.354,0.903,0.209,0.685,0.127
    mqtt:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: true
      height: 270
      quality: 70

##------------------------------------------------------------------------------------------------------------------------------------------------------
  PTZ:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://192.168.XX.XX:554/12
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
            - rtmp
    motion:
      threshold: 30
      contour_area: 10
      improve_contrast: 'true'
      mask: 0.754,0,0.755,0.038,1,0.038,1,0
    zones:
      PTZ-Front:
        coordinates: 
          0.074,0.099,0.085,0.305,0.122,0.636,0.177,1,1,1,1,0.124,0.735,0.087,0.728,0.036,0.564,0.024,0.352,0.036
        inertia: 3
    objects:
      mask: 0,0,0.072,0.096,0.349,0.034,0.561,0.021,0.729,0.034,0.738,0.084,1,0.121,1,0
    mqtt:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: true
      height: 270
      quality: 70

##------------------------------------------------------------------------------------------------------------------------------------------------------
live:
  #stream_name: Turret
  height: 1080
  quality: 10

##------------------------------------------------------------------------------------------------------------------------------------------------------
telemetry:
  network_interfaces:
    - eth
    - enp
    - eno
    - ens
    - wl
    - lo
  # Optional: Configure system stats
  stats:
    # Enable AMD GPU stats (default: shown below)
    #amd_gpu_stats: True
    # Enable Intel GPU stats (default: shown below)
    #intel_gpu_stats: True
    # Enable network bandwidth stats monitoring for camera ffmpeg processes, go2rtc, and object detectors. (default: shown below)
    # NOTE: The container must either be privileged or have cap_net_admin, cap_net_raw capabilities enabled.
    network_bandwidth: true
  # Optional: Enable the latest version outbound check (default: shown below)
  # NOTE: If you use the HomeAssistant integration, disabling this will prevent it from reporting new versions
  version_check: true
version: 0.14

##------------------------------------------------------------------------------------------------------------------------------------------------------
logger:
  # Optional: default log level (default: shown below)
  default: info
  # Optional: module by module log level configuration
  logs:
    frigate.mqtt: info

##------------------------------------------------------------------------------------------------------------------------------------------------------
camera_groups:
  All_Camera's:
    order: 1
    icon: LuCamera
    cameras:
      - PTZ
      - Turret
      - birdseye

It is pretty good but you are using go2rtc to create a internal steam, using the restream input profile but not using it since you are pointing to the original camera feed so you are using CPU and GPU for nothing. If you will to use the restream feeds, your camera config part should look like:

cameras:
  Turret:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/Turret
          input_args: preset-rtsp-restream

And you should delete the "- rtmp" from the camera roles as it has been replaced in fact by the rtsp restream feeds.

In any case, you are using the same input_args and output_args in all the cameras, so you can just add it to the global ffmpeg entry (where you have a input arg that you are not using) like so:

ffmpeg:
  global_args: -hide_banner -loglevel warning -threads 2
  hwaccel_args: auto
  input_args: preset-rtsp-restream
  output_args:
    record: preset-record-generic-audio-aac
  retry_interval: 10

For a better performance, is such a config you will have one thread of ffmpeg to restream and another audo recodification threat to the record role. I suggest you to change the go2trc to this:

go2rtc:
  streams:
    Turret:
      - rtsp://192.168.XX.XX:554/11
	  - "ffmpeg:Turret#audio=aac"
    PTZ:
      - rtsp://192.168.XX.XX:554/12
	  - "ffmpeg:PTZ#audio=aac"

and then use this general config for ffmpeg:

ffmpeg:
  global_args: -hide_banner -loglevel warning -threads 2
  hwaccel_args: auto
  input_args: preset-rtsp-restream
  output_args:
    record: preset-record-generic-audio-copy
  retry_interval: 10

yayitazale · July 26

4 hours ago, John Graham said:

more qustions .. i have move Frigate out of Home Assistant and in to a docker. Looks like it's running very good thanks for the poke in the right direction. now for the question. startedd up and look at the log file and i see this:

05:26:07] detector.coral INFO : Starting detection process: 3051

05:26:07] frigate.app INFO : Output process started: 3053

05:26:07] frigate.detectors.plugins.edgetpu_tfl INFO

: Attempting to load TPU as pci:0

05:26:07] frigate.detectors.plugins.edgetpu_tfl INFO

: TPU found 2024-07-26 05:26:07.133535528

05:26:07] frigate.app INFO : Camera processor started for Frount_Door_Cam: 3073

so i see nothing after that .. i see if found it but does that mean it working ?

and also i see prople talking about also haveing a GPU is that something i need to add to the system?

I know a lot of questions .. sorry more to come 🤓

John G

If you can access to the web ui then yes everything is up and running.

GPU can be used for hardware acceleration and / or object sound detection:

https://docs.frigate.video/configuration/hardware_acceleration

https://docs.frigate.video/configuration/object_detectors#nvidia-tensorrt-detector

If you already own a TPU, I don't recommend you to use a GPU detector since the TPU is much faster and more energy efficient.

For hardware acceleration you can use either the integrated GPU (Intel or AMD) or a dedicated Nvidia card and you will get a substantial CPU usage reduction (the greater the number of cameras, the greater the reduction). It is a little bit tricky to set it up so read de docs and the template instructions carefully.

yayitazale · July 26

22 minutes ago, mikey6283 said:

I have been able to get it works , I prolems was HA frigate addon was competing with Frigate Gu it seems to working at the moment. go2rtc is the problem now but has been for awhile.

go2rtc is not easy to set up

Edited July 26 by yayitazale

mikey6283 · July 26

1 hour ago, yayitazale said:

go2rtc is not easy to set up

Don't i know all this p[roblem started beacuse of go2rtc. I can't even updare to the latest version with the mthods posted. As i have been advised?

mikey6283 · July 31

On 7/26/2024 at 2:23 PM, yayitazale said:

Run the command "ls -l /dev/" in the unraid console and see if you have the apex_0

As you can see my coral M2 is loaded and working well , Why is the M2 coaral TPU not fold when using the HA Frigate Addon. I cannot understand why its is not now recgonised?

ConnerVT · August 4

I'm preparing to do a fresh install Frigate on my backup server (so nothing to carry over or save). My thoughts are to start directly with v0.14.0-rc2, as to avoid any re-configuring once this release candidate is a stable release (and also enjoy the new features).

I know I can set the Repository to ghcr.io/blakeblackshear/frigate:v0.14.0-rc2 to pull the 0.14 release candidate. The question(s) I have is this all I need to change in the Docker template currently in CA or are there other mappings/changes needed? Or is there another template that I should use?

These are questions that came to me reading a post from you, from back in June:

yayitazale · August 4

3 hours ago, ConnerVT said:

I'm preparing to do a fresh install Frigate on my backup server (so nothing to carry over or save). My thoughts are to start directly with v0.14.0-rc2, as to avoid any re-configuring once this release candidate is a stable release (and also enjoy the new features).

I know I can set the Repository to ghcr.io/blakeblackshear/frigate:v0.14.0-rc2 to pull the 0.14 release candidate. The question(s) I have is this all I need to change in the Docker template currently in CA or are there other mappings/changes needed? Or is there another template that I should use?

These are questions that came to me reading a post from you, from back in June:

There are some changes that you may need to do. You can see the changes of the next template version here so you edit it and add the changes manually:

https://gitlab.com/yayitazale/unraid-templates/-/blob/v14/yayitazale/frigate.xml

ConnerVT · August 4

Thanks for the quick response and your feedback. My plan is to get this installed this week, and your reply boosts my confidence.

ConnerVT · August 6

I have 0.14-rc2 fired up on my server. Things seem to be running well. Just wish to pass on an observation, and get feedback on one thing I'm seeing, and find out if I'm chasing ghosts.

Setup is using AMD graphics hardware acceleration, USB Coral, and a Amcrest IP5M-T1179EW-28MM. I wish to get this configuration nailed down, as final setup will have 6 cameras.

The observation is that I needed to update your template, changing the WebUI to 5000 from the 8554 in your template. Otherwise, the WebUI would not launch when clicking the frigate icon and selecting Webui on the Unraid Docker tab.

Is this an oversight on your part? Or is there something I need to add to my config.yml?

The question I have is that on the System Metrics/Stats page, I am seeing a warning that my primary feed "has high FFMPEG CPU usage" an the low-mid 20% range.

image.png.3a4203c1de7a1a508f0ca17f0caa412d.png

Is this something I should be concerned about, or is this expected? I believe I have my camera settings and config.yml file set properly, but would really appreciate your feedback and suggestions.

image.png.f53c36fbf9a3dd032f8df0047e4716ef.png

mqtt:
  host: 192.168.1.29
  user: mqtt-user
  password: password

#---------------------------------------------------------------------

ffmpeg:
  global_args: -hide_banner -loglevel warning -threads 2
  hwaccel_args: preset-vaapi
  input_args: preset-rtsp-restream
  output_args:
    record: preset-record-generic-audio-copy #was =  preset-record-generic-audio-aac
  retry_interval: 10

#--------------------------------------------------------------------

detectors:
  coral:
    type: edgetpu
    device: usb

#----------------------------------------------------------------------------------------

record:
  enabled: true
  retain:
    days: 7
    mode: motion
  events:
    retain:
      default: 30
      mode: motion

#----------------------------------------------------------------------

snapshots:
  enabled: true
  retain:
    default: 30

#--------------------------------------------------------------------------------

go2rtc:
  streams:
    basement:
      - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0
#     - ffmpeg:basement#audio=aac
    basement_sub:
      - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1
#     - ffmpeg:basement_sub#audio=aac

#-----------------------------------------------------------------------------------

cameras:
  basement:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy #was = preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/basement
          input_args: preset-rtsp-restream
          roles:
            - record
    motion:
      mask: 0.732,0.023,0.732,0.081,0.969,0.088,0.966,0.025
  basement_sub:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy # was = preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/basement_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
#           - audio # <- only necessary if audio detection is enabled
    motion:
      mask: 0.712,0.018,0.712,0.097,0.982,0.105,0.973,0.018

#-----------------------------------------------------------------------------------

version: 0.14
camera_groups:
  Basement_Group:
    order: 1
    icon: LuArrowBigDownDash
    cameras: basement

Thanks in advance for your input, and for this great application.

Edited August 6 by ConnerVT
speeling, added camera graphs

John Graham · August 7

hello all... all seems to be working very well .. thanks for the help and pointing me where i needed to go.

i would like you all to look and my config file and ( be nice still very new here ) and see what i have done wrong and could do better

upload.txt

John Graham · August 7

mqtt:
enabled: true
host: 192.168.5.101
port: 1883
topic_prefix: frigate
client_id: frigate
user: XXXXXXXXX
password: XXXXXXXXXXX
stats_interval: 60

detectors:
coral:
type: edgetpu
device: pci:0

database:
path: /config/frigate.db

birdseye:
enabled: true
restream: false
width: 640
height: 480
quality: 15
mode: motion
inactivity_threshold: 30
layout:
scaling_factor: 2.0
max_cameras: 1

motion:
threshold: 30
contour_area: 10
lightning_threshold: 0.8

record:
enabled: true
retain:
    days: 7
    mode: active_objects
events:
    pre_capture: 15
    post_capture: 15
    objects:
    - person
    - face
    - amazon
    - fedex
    - ups
    - package
    required_zones:
    - primary_zone
    retain:
      default: 7
      mode: active_objects

snapshots:
enabled: true
timestamp: true
bounding_box: true
crop: false
retain:
default: 7

cameras:

a_Frount_Door:
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
      - path: rtsp://XXX:[email protected]:88/videoMain
        roles:
        - detect

motion:
      mask:
      - 0,714,0,851,95,978,269,787
      - 391,1080,1075,1080,1092,978,402,722,144,978,206,1010

    zones:
      primary_zone:
        coordinates: 813,500,953,527,1011,638,971,913,1109,976,1111,1080,367,1080,187,927,376,736

zone_0:
coordinates: 0,664,60,964,287,802

b_Swing_Porch:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://XXXX:[email protected]:88/videoMain
        roles:
        - detect

c_Back_Yard:
    enabled: true
    ffmpeg:
#     onvif;
      inputs:
      - path: rtsp://XXXX:[email protected]:554/1/mpeg4
      #width: 2592
      #height: 1944
        roles:
          - detect

yayitazale · August 7

13 hours ago, ConnerVT said:
I have 0.14-rc2 fired up on my server. Things seem to be running well. Just wish to pass on an observation, and get feedback on one thing I'm seeing, and find out if I'm chasing ghosts.

Setup is using AMD graphics hardware acceleration, USB Coral, and a Amcrest IP5M-T1179EW-28MM. I wish to get this configuration nailed down, as final setup will have 6 cameras.

The observation is that I needed to update your template, changing the WebUI to 5000 from the 8554 in your template. Otherwise, the WebUI would not launch when clicking the frigate icon and selecting Webui on the Unraid Docker tab.

Is this an oversight on your part? Or is there something I need to add to my config.yml?

The question I have is that on the System Metrics/Stats page, I am seeing a warning that my primary feed "has high FFMPEG CPU usage" an the low-mid 20% range.

Is this something I should be concerned about, or is this expected? I believe I have my camera settings and config.yml file set properly, but would really appreciate your feedback and suggestions.
mqtt:
  host: 192.168.1.29
  user: mqtt-user
  password: password

#---------------------------------------------------------------------

ffmpeg:
  global_args: -hide_banner -loglevel warning -threads 2
  hwaccel_args: preset-vaapi
  input_args: preset-rtsp-restream
  output_args:
    record: preset-record-generic-audio-copy #was =  preset-record-generic-audio-aac
  retry_interval: 10

#--------------------------------------------------------------------

detectors:
  coral:
    type: edgetpu
    device: usb

#----------------------------------------------------------------------------------------

record:
  enabled: true
  retain:
    days: 7
    mode: motion
  events:
    retain:
      default: 30
      mode: motion

#----------------------------------------------------------------------

snapshots:
  enabled: true
  retain:
    default: 30

#--------------------------------------------------------------------------------

go2rtc:
  streams:
    basement:
      - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0
#     - ffmpeg:basement#audio=aac
    basement_sub:
      - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1
#     - ffmpeg:basement_sub#audio=aac

#-----------------------------------------------------------------------------------

cameras:
  basement:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy #was = preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/basement
          input_args: preset-rtsp-restream
          roles:
            - record
    motion:
      mask: 0.732,0.023,0.732,0.081,0.969,0.088,0.966,0.025
  basement_sub:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy # was = preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/basement_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
#           - audio # <- only necessary if audio detection is enabled
    motion:
      mask: 0.712,0.018,0.712,0.097,0.982,0.105,0.973,0.018

#-----------------------------------------------------------------------------------

version: 0.14
camera_groups:
  Basement_Group:
    order: 1
    icon: LuArrowBigDownDash
    cameras: basement
Thanks in advance for your input, and for this great application.

Hi:

The webui port change to 8971 it is a breaking change for V14 to add TLS and auth capabilities, and it is already covered in the next template version I sent you in the github:

<Config Name="Authenticated UI and API access without TLS. Reverse proxies should use this port." Target="8971" Default="" Mode="tcp" Description="" Type="Port" Display="always" Required="true" Mask="false">8971</Config>

The CPU usage seems normal, but you can lower the FPS if you want to have a lower usage.

Regarding the config file you can delete the input and output args from each camera if they are the same that you have defined in the global ffmpeg entry. In any case the rest of the config looks ok.

yayitazale · August 7

3 hours ago, John Graham said:

mqtt:
enabled: true
host: 192.168.5.101
port: 1883
topic_prefix: frigate
client_id: frigate
user: XXXXXXXXX
password: XXXXXXXXXXX
stats_interval: 60

detectors:
coral:
    type: edgetpu
    device: pci:0

database:
path: /config/frigate.db

birdseye:
enabled: true
restream: false
width: 640
height: 480
quality: 15
mode: motion
inactivity_threshold: 30
layout:
    scaling_factor: 2.0
    max_cameras: 1

motion:
threshold: 30
contour_area: 10
lightning_threshold: 0.8

record:
enabled: true
retain:
    days: 7
    mode: active_objects
events:
    pre_capture: 15
    post_capture: 15
    objects:
    - person
    - face
    - amazon
    - fedex
    - ups
    - package
    required_zones:
    - primary_zone
    retain:
      default: 7
      mode: active_objects

snapshots:
enabled: true
timestamp: true
bounding_box: true
crop: false
retain:
    default: 7

cameras:

a_Frount_Door:
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
      - path: rtsp://XXX:[email protected]:88/videoMain
        roles:
        - detect

motion:
      mask:
      - 0,714,0,851,95,978,269,787
      - 391,1080,1075,1080,1092,978,402,722,144,978,206,1010

    zones:
      primary_zone:
        coordinates: 813,500,953,527,1011,638,971,913,1109,976,1111,1080,367,1080,187,927,376,736

    zone_0:
        coordinates: 0,664,60,964,287,802

b_Swing_Porch:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://XXXX:[email protected]:88/videoMain
        roles:
        - detect

c_Back_Yard:
    enabled: true
    ffmpeg:
#     onvif;
      inputs:
      - path: rtsp://XXXX:[email protected]:554/1/mpeg4
      #width: 2592
      #height: 1944
        roles:
          - detect

It looks OK but if you want to use hardware acceleration to use less CPU of the host you should check: https://docs.frigate.video/configuration/hardware_acceleration

Also, if you want to embed the streams in WebRTC for example in a Home Asssitant frontend, it is a good idea to use the Restream capability: https://docs.frigate.video/configuration/restream

ConnerVT · August 7

3 hours ago, yayitazale said:

In any case the rest of the config looks ok.

Thanks so much for the input. I wish to nail this down, before I scale up adding the rest of the cameras and find I need to change a ton of configuration. I'll play with my FPS when I add the cameras, if usage starts to be too extreme.

I figured the 8971 port change was correct, but I was eager to see frigate actually run and 5000 got me there. I'll work on getting it configured for 8971 the next time I get a chance to work with it. (Time again to do my real job.)

coltonc18 · August 8

Good morning/afternoon,

Can someone glance at my config?

Im not sure what happened, it was working fine yesterday. Now I'm getting an error about required_zones. I checked, and dont have mroe that one required zones section per camera, and like I said this was working yesterday. So I'm not sure exactly what has happend.

image.png.624bab6e487147ba2ba670121430be36.png

config.yml

Bruceflix · August 9

7 hours ago, coltonc18 said:

Good morning/afternoon,

Can someone glance at my config?

Im not sure what happened, it was working fine yesterday. Now I'm getting an error about required_zones. I checked, and dont have mroe that one required zones section per camera, and like I said this was working yesterday. So I'm not sure exactly what has happend.

config.yml 6.06 kB · 1 download

There was an update overnight. Did you read the changelog before you updated?

deliverer · August 9

I haven't even started using coral yet with Frigate, but I noticed this when I looked under settings. Any thoughts? Frigate isn't even started? Temps were fine the other day and I haven't changed anything.

I also see this in Unraid logs

Aug 9 08:09:41 MEDIA01 kernel: apex 0000:03:00.0: Apex performance not throttled due to temperature Aug 9 08:09:46 MEDIA01 kernel: apex 0000:03:00.0: Apex performance not throttled due to temperature Aug 9 08:09:51 MEDIA01 kernel: apex 0000:03:00.0: Apex performance not throttled due to temperature Aug 9

What could be causing temperate shutdowns?

Edited August 9 by deliverer

yayitazale · August 9

FRIGATE V14 RELEASED

Please read the change-log and the new docs carefully as there are some breaking changes that can affect you. It is recommended to delete the container and install it again from scratch as the new v14 requires a new unraid template to meet the requirements of the new functionalities.

coltonc18 · August 9

14 hours ago, Bruceflix said:

There was an update overnight. Did you read the changelog before you updated?

i see his post below, looking at it now.

PZ303 · August 9

22 hours ago, coltonc18 said:

Good morning/afternoon,

Can someone glance at my config?

Im not sure what happened, it was working fine yesterday. Now I'm getting an error about required_zones. I checked, and dont have mroe that one required zones section per camera, and like I said this was working yesterday. So I'm not sure exactly what has happend.

config.yml 6.06 kB · 1 download

I'm having the exact same error. It updated overnight. Have not had a chance to review things yet but wanted to let you know you're not alone here.

yayitazale · August 9

6 minutes ago, PZ303 said:

I'm having the exact same error. It updated overnight. Have not had a chance to review things yet but wanted to let you know you're not alone here.

22 hours ago, coltonc18 said:

Good morning/afternoon,

Can someone glance at my config?

Im not sure what happened, it was working fine yesterday. Now I'm getting an error about required_zones. I checked, and dont have mroe that one required zones section per camera, and like I said this was working yesterday. So I'm not sure exactly what has happend.

config.yml 6.06 kB · 1 download

Check records entry:

https://docs.frigate.video/configuration/record

events:

pre_capture: 0

post_capture: 0

required_zones: []

And also https://docs.frigate.video/configuration/zones#restricting-snapshots-to-specific-zones

SohailS · August 9

from what i understand all i need to do is delete my original installation and keep the config file upon loading the new template the config file will be adjusted automatically?

PZ303 · August 9

4 hours ago, yayitazale said:

Check records entry:

https://docs.frigate.video/configuration/record

events:

pre_capture: 0

post_capture: 0

required_zones: []

And also https://docs.frigate.video/configuration/zones#restricting-snapshots-to-specific-zones

Thanks. Commenting out required_zones: [] got it to strart.

[SUPPORT] blakeblackshear - Frigate

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

yayitazale

ich777

IpDo

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation