Replies: 9 comments 28 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Updated to the latest dev build b3ce448-amd64 from e84a89e-amd64. Didn't change anything configuration wise. Reverted back to e84a89e-amd64 and it's working agian. Got the following configuration error. `Your configuration is invalid. Line 56: genai -> openai - Extra inputs are not permitted |
Beta Was this translation helpful? Give feedback.
-
|
Next thought - it would be super helpful to create some linkage between go2rtc streams and camera ffmpeg inputs. Lots of ways this could work, as one example could the stream names defined in go2rtc config be added to a drop down or similar in the camera ffmpeg config page? The number of times I've had a typo or other mistake here - I think it's been a fairly common error over time. It also feels slightly disconnected currently that streams are under System - I get that that is how the config is structured, but logically, my go2rtc streams relate to specific cameras. It's not a really global setting like MQTT connections details, TLS, Auth etc...again, it arguably exposes users to implementation details that might confuse them. |
Beta Was this translation helpful? Give feedback.
-
|
Niche request: YAML config |
Beta Was this translation helpful? Give feedback.
-
|
I think I’ve found the reason why the object classification model I reported earlier may have failed. I currently have three object classification models, each with thousands of training images, and training them requires a huge amount of memory. If I train all these models at the same time, my system memory gets completely maxed out. After training finishes, there isn’t enough free memory left to load the trained models, so the post-training model reload operation fails. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, I'm trialing
Regarding the new cases feature and the UI:
I still need to play around more with the new configuration UI. Our current setup is the following: |
Beta Was this translation helpful? Give feedback.
-
|
How to use dev builds with Home Assistant apps? Currently on frigate full access beta |
Beta Was this translation helpful? Give feedback.
-
|
I don't know if this is at all related to the hour-mark seeking issue mentioned above, but I find the "rewind 10s" button won't go backwards past the hour, it only goes to e.g 17:59:59 (according to camera's own timestamp, so maybe actually 18:00:00 to Frigate). You can click it as many times as you like, it won't backwards further. |
Beta Was this translation helpful? Give feedback.






Uh oh!
There was an error while loading. Please reload this page.
-
Frigate 0.18 includes many new features, some of which require additional feedback to ensure a smooth user experience. Frigate 0.18 is still under active development and is not recommended for use in production systems (there may be large / breaking bugs).
As we start gearing up for the next beta, we are looking for any and all feedback from users on the dev builds.
If you experience any bugs with config migration, or bugs with existing 0.17 functionality then please give that feedback as well.
When providing feedback please do so in this discussion, if a new discussion must be created then use the
Beta Supportcategory notBugThe docs are: https://docs-dev.frigate.video/
Note that docs links in the UI in
devbuilds point to the stable docs hostname and may lead to an outdated page or 404s. You can manually add-devto the hostname for the correct link. For example:https://docs.frigate.video/configuration/genai/configbecomeshttps://docs-dev.frigate.video/configuration/genai/configWe are still looking for more feedback on the following:
Exports
Frigate 0.18 brings substantial improvements to exports.
Case Management
Exports can now be organized into named cases, making it much easier to manage exports related to a single incident or investigation.
Custom Exports
Frigate 0.18 provides a dedicated exports API that accepts arbitrary ffmpeg arguments, allowing for fully custom export pipelines (custom filters, encoders, output formats, and so on). A CPU fallback path is automatically used if hardware-accelerated encoding fails. For security, custom ffmpeg arguments are restricted for non-admin users and a number of dangerous flags (such as
-filter_complex,-vf, and-attach) are blocklisted to prevent arbitrary file reads via filter sources.In addition, exports now use Frigate's
Jobinfrastructure end-to-end, providing more reliable progress reporting and better cleanup of interrupted jobs. Per-camerarecord.export.hwaccel_argssettings cascade up through camera and global configuration, allowing per-camera tuning of export hardware acceleration. See the recording documentation for export configuration details.Config UI
Frigate 0.18 introduces complete UI-based configuration management. The new Settings experience provides:
Please provide any feedback on the above aspects of the Settings UI. One suggested testing method would be to set up a fresh instance of
devto match your existing stable instance's configuration by exclusively using the Settings UI.Beta Was this translation helpful? Give feedback.
All reactions