How to setup HW accseleration on a dell 9020 mini

Third party integrations
1

Hi

I have installed on Dell 9020 mini
Home Assistant Operating System and
Home Assistant Add-on: Frigate (Full Access) 0.15.2

To use HW acceleration, I asked Gemini
A.I. Gemini says:

ad this in frigate.yml
global:
ffmpeg:
hwaccel_args:
- -hwaccel
- vaapi
- -hwaccel_device
- /dev/dri/renderD128
- -hwaccel_output_format
- vaapi

AND do this:

How to Enable GPU Hardware Acceleration for Frigate

To enable hardware acceleration for Frigate, you need to provide the Frigate add-on’s Docker container with access to your host machine’s GPU. This is done through a specific field in the Home Assistant add-on configuration, which is separate from the frigate.yaml file.

Step 1: Navigate to the Add-on Configuration

  1. In Home Assistant, go to Settings → Add-ons .
  2. Find and click on the Frigate add-on tile.

Step 2: Add the Device Path

  1. On the Frigate add-on page, select the Configuration tab.
  2. Scroll down until you find a field labeled “Devices” .
  3. In this field, you must add the path to your GPU device. For most Intel-based systems, this path is:/dev/dri/renderD128
  4. Click the “Save” button.

Step 3: Restart the Add-on

  1. After saving the changes, go back to the Info tab of the Frigate add-on and click “Restart” .

By performing these steps, you are telling the Home Assistant Supervisor to map the specified device from your host machine into the Frigate Docker container. This is a critical step for hardware acceleration to work.

Verifying the Configuration

After restarting, you can check the Frigate logs to confirm that it is correctly accessing the GPU. You should see messages indicating that it is using the hardware for video decoding. If you have an Intel GPU, the logs should show it is utilizing the VAAPI driver.

If you are also configuring hardware acceleration in your frigate.yaml , make sure your FFmpeg input arguments are set correctly to use the new access you have granted. The add-on’s “Devices” field is what makes the GPU available; the frigate.yaml file is what tells FFmpeg to actually use it.

This section described has no such??

image
image1097×726 25.4 KB

Is this true?
But as I’m a newbie I kindly ask for real How To here
many THX

2

Hello Witzker

If you are adding this to HAOS running machine, the OS probably is not supporting this.
Just sayin…
If HA is in a docker or a VM and you run this on the host you could get lucky.

I don’t have any experience with frigate or that hardware specifically though.

1 Like
3

I don’t speak German, but try clicking that button :wink:
If that doesn’t work, you can switch to yaml mode and paste the code (correctly formatted) there.

image
image681×264 22.9 KB

Also, don’t rely on AI for info, especially when frigate has an extremely extensive documentation site. The info provided by AI will be based on its cutoff time (probably last year), while the official docs get updated constantly.

1 Like
4

Ok THX
Now I can put in a code
BUT
No idea what to put there for my OptiPlex :thinking::woozy_face:

The doc says:
(not for proxy addon) If you are using hardware acceleration for ffmpeg, you may need to disable “Protection mode”

As I have frigate full access - so to find HowTo disable

here it is a big switch

image
image1052×680 58.3 KB