frigate hardware acceleration detector | Home Assistant | Page 1

novel pewter Mar 9, 2025, 9:23 PM

#

Howdy, after A TON of trial and error, i finally got those rascally NVIDIA drivers working in Ubuntu. I followed Frigate's instructions here - and the GPU is showing up at the bottom of frigate and it shows in the system metrics! Whoo hoo!

However, it still appears that the detector stuff is running on CPU and not my GPU. Am i missing something here? Is there some arbitrary setting in the config.yml file i missed?

I'll post my config in the next message (if i can - if i can't i'll paste a file with it i guess?)

Should be noted that I am running on HA Docker Container with NVIDIA driver 470.xxx with a Quadro K4200 (old i know).

#

This is my config so far:

ffmpeg:
  hwaccel_args: preset-nvidia


go2rtc:
  streams:
    front_door:
      - rtsp://<user>:<password>@<ip_addr>:554/cam/realmonitor?channel=1&subtype=0  # <- stream which supports video & aac audio.
      - ffmpeg:front_door  # <- copy of the stream which transcodes audio to opus
    front_door_detect:
      - rtsp://<user>:<password>@<ip_addr>:554/cam/realmonitor?channel=1&subtype=1 # <- stream which supports video & aac audio.
      - ffmpeg:front_door_detect


mqtt:
  enabled: true
  host: <mqtt_addr>
  user: <user>
  password: <pass>

cameras:
  front_door:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/front_door                # <--- the name here must match the name of the camera in restream
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/front_door_detect             # <--- the name here must match the name of the camera_sub in restream
          input_args: preset-rtsp-restream
          roles:
            - detect
    motion:
      threshold: 30
      contour_area: 10
      improve_contrast: true
    zones:
      Front_door:
        coordinates: 0.127,0.396,0.641,0.219,0.738,0.687,0.686,1,0.089,1,0.052,0.753,0.12,0.396
        loitering_time: 0
        objects: person
        inertia: 3
    review:
      alerts:
        required_zones: Front_door
      detections:
        required_zones: Front_door


record:
  enabled: true
  retain:
    days: 3
    mode: all
  alerts:
    retain:
      days: 30
      mode: motion
  detections:
    retain:
      days: 30
      mode: motion


version: 0.15-1
semantic_search:
  enabled: true
  reindex: false
  model_size: small

tight matrix Mar 9, 2025, 9:30 PM

#

looks like you have set up the gpu for video hardware acceleration but its not set up as a detector

#

if you look at the documentaion here - https://docs.frigate.video/configuration/object_detectors/
you can see some info on running detectors on a nvidia gpu

Object Detectors | Frigate

Frigate supports multiple different detectors that work on different types of hardware:

novel pewter Mar 9, 2025, 9:34 PM

#

aha i knew i was missing something. Probably should not have skimmed the Detector section lol - welp looks like i may be out of luck. Seems i need >=530 driver. Definitely gonna read up on it more. Thanks!

tight matrix Mar 9, 2025, 9:35 PM

#

if grabbing a coral tpu is an option then thats a good way to go

#

i put an m.2 one inside the mini pc i have running HA and frigate (on proxmox) but the usb one works well according to others

novel pewter Mar 9, 2025, 9:39 PM

#

i might look at the usb one (my mobo doesn't have any m.2 slots)

tight matrix Mar 9, 2025, 9:41 PM

#

its probably going to be a lot more power efficient than a gpu doing it too

#

for what its worth when getting it working, it was the GPU hw acel stuff thats was the tricky bit. getting a coral working is pretty easy going

novel pewter Mar 9, 2025, 11:59 PM

#

i ordered one -thanks for the help!

#frigate hardware acceleration detector