Upgrade Frigate LXC

[DonPablo1010]

🌟 Briefly describe the feature

14.1 -> 15.1

📝 Detailed description

The script for the Frigate LXC is currently hardcoded to pull version 0.14.1. Would it be possible to update this to pull the latest stable version 0.15.1 instead?

💡 Why is this useful?

While the script must use a hardcoded version of Frigate due to dependency and compatibility constraints, updating it from v0.14.1 to the current stable v0.15.1 brings significant benefits:
Version 0.15.1 includes major improvements in detection accuracy, stream stability, and hardware acceleration support (e.g., Coral and VAAPI). It also resolves several critical bugs present in 0.14.1, making the system more reliable and performant.
Keeping the hardcoded version up to date ensures the deployment remains stable while benefiting from important upstream enhancements.

[michelroegl-brunner]

Upgrade happens when 16.0 is there, not befor. They break the install/update with every patch. We dont redo it for 15 and then again for 16.

[DonPablo1010]

Thanks for the clarification. I understand the concern about breaking changes and the effort required to update the install script.

That said, I strongly recommend updating the hardcoded version now to 0.15.1, and explicitly skipping 0.16.0 later in favor of 0.16.1, for the following reasons:
• 0.15.1 is a stable, production-ready release with significant improvements over 0.14.1, including detection performance, stream reliability, and hardware acceleration support.
• Skipping 0.15.x and upgrading directly from 0.14.1 to 0.16.0 compounds the risk of breaking changes and configuration incompatibilities.
• In past cycles, .0 releases often required immediate fixes (e.g. 0.14.0 → 0.14.1), so 0.16.0 is likely to be less stable than 0.15.1.
• Upgrading to 0.15.1 now provides stability and prepares the ground for a cleaner transition to 0.16.1 later.

I believe this two-step upgrade path (0.14.1 → 0.15.1 → 0.16.1) offers the best balance of reliability and up-to-date features, without the churn and risk of dealing with unstable .0 releases.

[MickLesk]

read this discussion and you see all informations: #2187