yayitazale

Okay, this is useful for a very small percentage of deployments. In any case, if this is really that useful, I think it would be better for you to contribute these features to the main Frigate development branch—not as a separate project—since that’s what a Free Software project created and maintained by a community is for. https://github.com/blakeblackshear/frigate

This is pretty much useless in an UnRAID environment, where the OS already has a built-in system for periodically moving files from the cache pool (designed for use with SSDs) to the disk array (designed for use with HDDs)...

I think the problem resides on the Unraid side, not on the container side.

Did you created a V9 model?

Not sure but I think you don't need this: providers: - CUDAExecutionProvider cuda_graphs: false https://github.com/blakeblackshear/frigate/discussions/23546#discussioncomment-17412679

https://docs.frigate.video/frigate/installation#ports 8971 Authenticated UI and API access without TLS. Reverse proxies should use this port. EDIT: You're right, https://docs.frigate.video/configuration/tls, so I just modified the template so that future new installations will use HTTPS by default for the web UI. Thanks

I cannot help you without more info, can you share a screenshot of the configuration of the container and the configuration file (config.yaml) created during the initial startup?

From your logs, I notice that Frigate is starting successfully, but I don't see any specific detector initialization logs that would indicate whether the YOLOv9 model is loading correctly. The logs show the detector process starting but don't show model compilation or loading details. Check your config file and check if the model file is in the correct place.

What do you see in the logs after restarting the container?

Yes, the GTX 1080 Ti is perfectly suitable because, thanks to its 11 GB of VRAM, it has more than enough memory to run the YOLOv9 models and handle multiple video streams simultaneously and it’s more than capable of keeping model inference times low. In the first step of installing the instance, you must select the NVIDIA branch: Next, as you mentioned, you need to add “--runtime=nvidia” to the additional parameters and configure the NVIDIA entries in the configuration form. As for models, I recommend using YOLO V9: From your Unraid machine's console (not the container one), navigate to the folder where you want to save the model, preferably in the default path (model_cache): cd /mnt/user/appdata/frigate/model_cache/Run the command listed in the documentation at https://docs.frigate.video/configuration/object_detectors/#yolov9-for-other-detectors; if you have many cameras—more than 6, for example—start with a “tiny” (T) size and IMG_SIZE=320 to ensure acceptable inference times. Otherwise, with fewer than 6 cameras, you can try IMG_SIZE=640 and S or M sizes, but keep in mind that the larger the model, the longer the inference time and the higher the power consumption will be. Verify that your ONNX file was created correctly in the specified folder Configure detection with the ONNX detector pointing to your ONNX file (if you placed it in model_cache, you don’t need to change anything) https://docs.frigate.video/configuration/object_detectors#yolo-v3-v4-v7-v9-2 Restart Frigate and check the logs to see if the model has loaded correctly. In addition, if you're also going to perform hardware-accelerated video decoding using the NVIDIA GPU itself, you should use the NVIDIA decoder preset: https://docs.frigate.video/configuration/hardware_acceleration_video#setup-decoder

You should try a minimal setup, without any cameras configured or anything like that... just as described in the documentation. https://docs.frigate.video/guides/getting_started#configuring-frigate

You must read the docs before posting: https://docs.frigate.video/configuration/authentication#onboarding

No, that's normal; unless you run the container in privileged mode (which is not recommended for security reasons), it won't be able to retrieve the CPU/iGPU statistics, which is why you're getting that error.

Is this happening all the time? "Frigate employs "smart streaming" where camera images update once per minute when no detectable activity is occurring to conserve bandwidth and resources. As soon as any motion or active objects are detected, cameras seamlessly switch to a live stream." https://docs.frigate.video/configuration/live Can you check the camera FPS under /system#cameras if there is any issue also.

The same Path where you are running the script I suppose

You have configure onnx https://docs.frigate.video/configuration/object_detectors/#onnx

With such little info is not easy to help you. Are you using the GPU just for video decoding or also for detection? In case that you are using it for detection, did you installed the proper branch? Did you configured the ffmpeg hardware acceleration properly? https://docs.frigate.video/configuration/hardware_acceleration_video In case that you are using it for detection, did you followed the steps to generate de model and configured it properly? https://docs.frigate.video/configuration/object_detectors#nvidia-tensorrt-detector ...

Are you following the getting started? https://docs.frigate.video/guides/getting_started#configuring-frigate Are you looking in the logs for errors?

Please give us some info. Copy and paste de error logs for example

I wasn't aware of this, but since the Merge request has already been accepted, I assume this option will be released as a feature in the next version. Just be patient.

As you can read in the description, this container is an HDHomeRun emulator for Tvheadend users. Literally, the first line of the post: "Support for Antennas docker container. HDHomeRun emulator for Plex/Jellyfin/Emby DVR to connect to Tvheadend." For Tvheadend users, native integration with Plex does not work immediately as it does with HDHomeRun.

There is a open discussion for this issue: https://github.com/blakeblackshear/frigate/discussions/18850#discussioncomment-14717742

Did you try to unisntall the plugin and install it again?

Frigate v16 doesn't support NPU, v17 will do. https://github.com/blakeblackshear/frigate/discussions/13248 https://github.com/blakeblackshear/frigate/pull/20536

If you are sure that it is not related to temperature issues, test with https://coral.ai/software/, maybe you have a faulty device.