Roll back beyond the last update for frigate

Hey,

Hopefully someone can help me out, I’m using truenas scale 24.10.
Ryzen 5 5600G
96GB RAM

I used the discover apps tab and installed Frigate almost a year ago when 0.13.2 was the version available. Everything worked perfect with 4 cameras recording for 6 months and only using like 5-10% CPU and 5-15% GPU. (I didnt use any detection just 24/7 recording).

When version 0.14 released i updated and launched frigate to find that it would crash after 5 mins. I figured there was some issue with the update so i rolled back to 0.13.2 and everything with fine again for 4 month.

0.15 releases so i try and update to it and it keeps crashing just like 0.14 so i research and find out i should try and increase the shm_size: “64mb” to 512. I do and it stops crashing and is actually working now… However the container is using like 40-60% CPU.

So i decide to roll back again to 0.13.2 but that option is no longer available in the drop down menu only 0.14… I attempted to setup frigate via yaml install and it only crashes. I have 5 containers installed via yaml with no issues.

Is there anyway to add the 0.13.2 release back into the truenas drop down menu pool? i dont care if i have to redo the configuration file from scatch or could i cheat and just rename the 0.13.2 docker file to 0.15?

Thanks

Learn to use yaml and config frigate as your own custom app. Then you will have complete control over versions. And likely, it will run better also.

No. I went through an identical process with the same degree of pain and failed.

However - I am now using the official app which supplies frigate version v0.15.0 and it is running well. If you search my various posts here you’ll see that I set up using host paths rather than iX and this allows me to ssh into the subdir with the actual config.yaml in it. I then start with a sparse fresh config (not the one from 0.13.2 because there are too many changes in later versions).

After some effort I now have something working very well with acceptable CPU burden (33%). This is using a Xeon E3-1265L V2 @ 2.50GHz and 16 GB of RAM.

If you are still stuck after seeing my various posts here and also at the Frigate github discussion pages, please update this thread and I will see if I can help directly. I think you’ll be able to end up with 0.15 running in a stable manner with not too much CPU consumption.

Good luck - let us know what happens.

1 Like

Thanks for the replies guys.

I was about to follow one of your posts E_B when i noticed there was an update for frigate to 0.15.1. So i gave it shot because why not and everything works again. 8% CPU, 3% GPU and recording normally… Must of been some unknown issue i guess.

I know this doesnt help anyone unfortunately.

1 Like