yayitazale

You find out by yourself: https://github.com/blakeblackshear/frigate/releases

Yes but read the docs carefully since there are some breaking changes. For a more safe deployment and to be able to rollback to v11 as many times as you need: Create a new folder on appdata called frigate-new or something like that. Create a new media folder again with a different name. Just stop v11 frigate, don't delete. Create a new config file with the new requirements in the new folder Launch the new frigate 12 with a different name, like "frigate12" and change the path of the config file and media path to the new ones. In this way you can have both old and new frigate (only one running but both containers). You can make trials to make v12 to work, but if you don't make it in just one try, you can just stop the frigate 12 and start the 11 as many times as you need. When you are ready to move to v12 definitely, stop and remove the v11 app, delete de v11 config file, move the v12 config to original frigate config folder, rename the v12 app to just frigate, and launch it pointing to the original appdata and media paths.

Theorically yes but in my experience, it doesn't work as good as in normal mode.

Use cache unless you have a specific NVR HDD.

You can change it the extra commands under advanced view

The template is the same for both versions, it just changes the tag of the dockers build. It is already in the installing instructions of the template.

Sorry for sure I'm not doing it on purpose, I also made a mistake in the padding LOL. Here ou have again the file. config.yml

Sorry my bad. Pasting here is not the best way so there you have attached the file. Hope you can at least startup frigate for the first time but as you can see, this is not a easy software to config and make running. I'm not a developer, I just maintain the unraid template so don't blame me.I'm not the main dev, I just maintain the unraid template so don't blame me. config.yml

I tried to make the easiest and more complete template to fits everybodys needs and thats for sure is not something easy. 2 years ago I had the template only with the minimal entries and I can assure that it was much more confusing and much more people asked for help. Anyway, you can create your own template and publish it following the unraids community template creation guide and maintaining it by yourself.

The config docs apply to unraid. MQTT is not mandatory, you don't need it and it is not included as it is standard service that can be used to any other communication purposes so if you want to use it, you must install it separatelly. As you can read in the error log: yaml.parser.ParserError: expected '<document start>', but found '<block mapping start>' in "<unicode string>", line 3, column 1: cameras: ^ In YAML lenguage the padding must be the correct one to work. You have a error in the padding at line 3. You can test any YAML code here, for example the first config of frigate to startup for the first time, then you shoul use the frigate internal config editor witch will tell you if you have any spelling/padding error before saving. Your config file shoul look like this, in the same way it is defined in the getting started doc: mqtt: enabled: false cameras: back: ffmpeg: inputs: - path: rtsp://XXX:[email protected]:1338/11/ roles: - detect detect: width: 1280 height: 720 The rest of the configuration docs applies to unraid as it is indepentant of the host OS.

This are separated things. An OOM errors means you are out of memory. This issue is something happening since july to some people: https://github.com/blakeblackshear/frigate/issues/6731 https://github.com/blakeblackshear/frigate/issues/7018 https://github.com/blakeblackshear/frigate/issues/6560 There is a topic opened already as it looks something related to docker engine or hardware itself: Some possible fixes here: https://github.com/blakeblackshear/frigate/issues/6731#issuecomment-1583071981

You can change the size just changing the value of the tmpfs size: - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear target: /tmp/cache tmpfs: size: 1000000000 You have the explanation here: https://docs.frigate.video/frigate/installation#storage

Remove means remove, not blank it. You should delete the entries using the "REMOVE" button.

Maybe @ich777 you can help us here, is this supported by the docker version we have in unraid?

I think preset-rstp doesn't exists. You should use preset-rtsp-generic.

You have a incorrect nesting: ffmpeg: hwaccel_args: preset-intel-qsv-h264 input_args: preset-rtsp-restream-low-latency output_args: record: preset-record-generic-audio-copy Also, you are defining as the generla input arg the "preset-rtsp-restream-low-latency" but then you define "preset-rtsp-restream" at the camera level. You can delete the one on the camera: cameras: garden: ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/garden_camera input_args: preset-rtsp-restream roles: - record - detect

Yes, presets will simplify your life. In your case you should delete the ffmpeg part and add only: ffmpeg: hwaccel_args: preset-intel-qsv-h264 Or this, if qsv doesn't work: ffmpeg: hwaccel_args: preset-vaapi In my case, I also add this to the ffmpeg part to work with webrtc in low latency and to record with the transcoded audio: input_args: preset-rtsp-restream-low-latency output_args: record: preset-record-generic-audio-copy And this in the go2rtc part in order to be able to connect from Home Assistant: webrtc: candidates: - 192.168.X.XX:8555 - stun:8555 I see that you should also simplify the definition of cameras. You defined the substream that you are not using, and also, you are transcoding to opus and then to acc. I think you shoud only transocde once and keep that, so you should have something like this (chnage the opus to aac if needed): go2rtc: streams: garden_camera: - http://10.19.64.220/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password={FRIGATE_RTSP_PASSWORD} - "ffmpeg:garden_camera#audio=opus" cameras: garden: ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/garden_camera input_args: preset-rtsp-restream roles: - record - detect For this last part, you should have defined the ffpmeg > output_args > records as I told you to preset-record-generic-audio-copy to record with the opus/aac (whatever you keep with) audio. In any case, you can also maintain the flv stream to detection and only restream for recording, you have the specific example for reolink config to do that here: https://docs.frigate.video/configuration/ffmpeg_presets#input-args-presets

No, I'm talking about the config file. You didn't read the docs properly: https://docs.frigate.video/configuration/restream The log points clearly that you are not nesting the config file correctly. It should be cameras -> Rear_Deck -> ffmpeg -> output_args: preset-record-generic

I think you should add a input arg: input_args: preset-rtsp-generic And for output, you should use a preset too: output_args: preset-record-generic In any case, http video streams seem to be the most reliable for Reolink, there you have some info about how to setup the got2rtc restreaming: https://docs.frigate.video/configuration/camera_specific#reolink-cameras For more doubts about your config, please see https://github.com/blakeblackshear/frigate/issues/3235#issuecomment-1135876973 and you can ask there.

First of all, to your info, I only maintain the template for unraid. I'm not a developer of frigate so the script is not mine, and I only translated the deploying instruction from pure docker of the frigate docs to a unraid app template. I would like to have both, the screenshot and the file, to see if there is something to fix in the way you are launching the container or in the config file.

1. I wasn't judging, only pointing out something that some people doesn't understand or even read. 2. This is something basic of docker, not something exclusive from frigate. In any case, if you have complains about the docs you are welcome to send a PR with the suggested changes to the template: https://gitlab.com/yayitazale/unraid-templates/-/blob/main/yayitazale/frigate.xml or to the docs of the project: https://github.com/blakeblackshear/frigate/tree/dev/docs 3. Can you attach a screenshot of the template config you are using and the config file? You can expand the docker image from unraid if you are out of space, this is something that I can't expect from every user. You are the responsible of your system not me. If you don't like this just buy any commercial software.

Can you try with frigate stopped?

Are you going to use Nvidia GPU as a detector? If it is not the case, you should use the default branch. You should add "--runtime=nvidia" as first extra parameter, not last. Can you post the error of the FFMPEG? Where are you running the nvidia-smi command? You have to run it in the unraid OS console, you will not see anything inside the container.

Watching your config file, thing you should change: RTMP is deprecated, so you should start using the new restream, here the info: https://docs.frigate.video/configuration/restream Also you should change the camera role definition to the new scheme using the restream: https://docs.frigate.video/configuration/cameras Maybe you need to change a little bit also the events definition on cameras (not sure, maybe not): https://docs.frigate.video/configuration/record#what-do-the-different-retain-modes-mean You can change the FFMPEG args to presets: https://docs.frigate.video/configuration/hardware_acceleration#intel-based-cpus I suggest you to star from scratch with a new config file with a minimal configuration as it's recommended here: https://docs.frigate.video/configuration/ Then start adding or changing specific things one by one to avoid multiple errors at the same time that are harder to tackle.

I think you can't but you can open a discussion here: https://github.com/blakeblackshear/frigate/discussions