Frigate no longer working with ffmpeg camera after recent update

Configuration
1

I was using frigate with a Foscam fi9800p.
I recently updated to Frigate 0.11.1 (not sure what version I was on previously)

Unfortunately, my camera stopped working.
My config looks like this:

cameras: 
  voortuin_camera:
    record:
      events:
        required_zones:
          - voortuin
    ffmpeg:
      inputs: 
        - path: "rtsp://myUser:[email protected]:554/videoMain"
          roles: 
            - record
            - detect
    detect:
      width: 1280
      height: 720
    zones:
      voortuin:
        coordinates: 0,720,1280,720,1280,628,1045,605,834,431,439,494,0,494
    motion:
      mask:
        - 1280,0,0,0,0,626,215,562,342,600,433,659,537,560,427,308,0,374,0,234,1280,67,1280,209,757,254,1050,609,1280,558
detectors:
  coral: 
    type: cpu
mqtt: 
  host: core-mosquitto
  user: mqtt_user
  password: mqtt_pass
record:
  enabled: true
  retain_days: 0
  events:
    retain:
      default: 5
ffmpeg:
  hwaccel_args:
    - -hwaccel
    - qsv
    - -qsv_device
    - /dev/dri/renderD128
objects:
  track:
    - person

logger:
  default: info

When I open the url rtsp://myUser:[email protected]:554/videoMain with a player like VLC, I can see the camera is working fine.

When I open the frigate log (right after a restart of frigate), I see:

[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.
[2023-04-01 19:25:25] frigate.app                    INFO    : Starting Frigate (0.11.1-2eada21)
[2023-04-01 19:25:25] frigate.config                 WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain'
[2023-04-01 19:25:25] frigate.app                    INFO    : Creating directory: /tmp/cache
Starting migrations
[2023-04-01 19:25:25] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2023-04-01 19:25:25] peewee_migrate                 INFO    : There is nothing to migrate
[2023-04-01 19:25:25] frigate.app                    INFO    : Output process started: 217
[2023-04-01 19:25:25] ws4py                          INFO    : Using epoll
[2023-04-01 19:25:25] frigate.app                    INFO    : Camera processor started for voortuin_camera: 223
[2023-04-01 19:25:25] frigate.app                    INFO    : Capture process started for voortuin_camera: 226
[2023-04-01 19:25:25] detector.coral                 INFO    : Starting detection process: 216
[2023-04-01 19:25:25] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
[2023-04-01 19:25:25] frigate.video                  ERROR   : voortuin_camera: Unable to read frames from ffmpeg process.
[2023-04-01 19:25:25] frigate.video                  ERROR   : voortuin_camera: ffmpeg process is not running. exiting capture thread...
[2023-04-01 19:25:27] ws4py                          INFO    : Using epoll
[2023-04-01 19:25:45] watchdog.voortuin_camera       ERROR   : Ffmpeg process crashed unexpectedly for voortuin_camera.
[2023-04-01 19:25:45] watchdog.voortuin_camera       ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2023-04-01 19:25:45] ffmpeg.voortuin_camera.detect  ERROR   : [AVHWDeviceContext @ 0x5633f2d817c0] No VA display found for device /dev/dri/renderD128.
[2023-04-01 19:25:45] ffmpeg.voortuin_camera.detect  ERROR   : Device creation failed: -22.
[2023-04-01 19:25:45] ffmpeg.voortuin_camera.detect  ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Invalid argument
[2023-04-01 19:25:45] ffmpeg.voortuin_camera.detect  ERROR   : Error parsing global options: Invalid argument
[2023-04-01 19:25:45] frigate.video                  ERROR   : voortuin_camera: Unable to read frames from ffmpeg process.
[2023-04-01 19:25:45] frigate.video                  ERROR   : voortuin_camera: ffmpeg process is not running. exiting capture thread...

Any idea what could be the issue?

2

What hardware are you running on?

3

I’m running HA om a intel NUC NUC10i7FNH with a 10th gen Core i7. I use proxmox as a hypervisor.

4

It is missing access to /dev/dri/renderD128. Try taking out the hwaccel stuff to test.

5

Thanks, that did the trick!

I still don’t really understand why hardware acceleration is no longer working, but by looking at the load in proxmox, I might be ok without it:

image
image1087×336 24.6 KB

6

I would post in the frigate issues on github.

7

Hi, I have been having the same, issue. How did you fix/go around it please?

(On a Pi4 4GB but was changing my config to enable Coral Edge TPU and since then, even going back to previous config results in the above reported errors)

8

This is not the frigate forum. See my last reply.

9

I actually didn’t dive further into the issue, since running it without hardware acceleration worked fine for me.