0.14.0 Beta 4

[blakeblackshear]

Beta Documentation: https://deploy-preview-11419--frigate-docs.netlify.app/

Images

• ghcr.io/blakeblackshear/frigate:0.14.0-beta4
• ghcr.io/blakeblackshear/frigate:0.14.0-beta4-standard-arm64
• ghcr.io/blakeblackshear/frigate:0.14.0-beta4-tensorrt
• ghcr.io/blakeblackshear/frigate:0.14.0-beta4-tensorrt-jp4
• ghcr.io/blakeblackshear/frigate:0.14.0-beta4-tensorrt-jp5
• ghcr.io/blakeblackshear/frigate:0.14.0-beta4-rk

Changes since beta 3

• Change authenticated port to 8971
• Disable IPv6 by default, update docs for enabling IPv6
• Update docs for configuring TLS
• Improve Live view intelligent player selection
• Many Live view bugfixes
• Add keyboard shortcut (Ctrl/Cmd-A) to select all review items
• Moved review classification settings (required zones for alerts/detections) to dedicated view in Settings
• Various UI bugfixes and performance improvements
• Improve compatibility with onvif cameras that only support zoom

Major Changes for 0.14.0

Breaking Changes

There are several breaking changes in this release, so a backup of your current config and database is recommended before upgrading:

• Simply copy your current config file to a new location
• Stop Frigate and make a copy of the frigate.db file

Your existing events will not be visible in Frigate's new UI

• An entirely new way of reviewing camera footage has been implemented in Frigate 0.14, and existing events could not be migrated
• Recordings can still be viewed in the new UI using the recordings viewer (From Live view, click/tap on a camera and select the History button at the top left)
• You may want to export any starred/favorite events before upgrading
• If you are using the Home Assistant integration, events can still be viewed there
• Recording (enabled: True for record in your config) is required to see review items and motion data in the UI

Zone/mask coordinates are now stored in the config as relative values

• Frigate's configuration migrator will read your existing mask/zone coordinates and convert them for relative use internally on startup
• Using the built-in mask/zone editor will make your config file incompatible with prior versions of Frigate
• If you have mask/zone coordinate values that exceed the detect resolution, it will be ignored and you will see warnings in the log. Delete the mask or zone from your config and then use the editor in the UI to recreate it.

The UI's live mode is now intelligently selected

• The live_mode config option is now deprecated and should be removed.

Backwards incompatible database changes

• There are a number of changes made to Frigate's database, which are not backwards compatible. A backup of the database is automatically made on startup, but a manual backup is highly recommended.

Other breaking changes

• RTMP was deprecated in 0.13 and has been fully removed in 0.14. You will need to remove any rtmp references in your config file.
• OpenVINO has been upgraded, and Intel Neural Compute sticks are no longer supported. Support for YOLO-NAS models has been added. Additionally, AUTO mode now maps to GPU internally to avoid some unresolved issues with AUTO.

Brand New UI

Frigate 0.14's UI has been completely rewritten (guided demo) and optimized for desktop and mobile devices, aiming to simplify the user experience by focusing on two specific goals:

1. Allow you to quickly see what's currently happening or what just happened on your cameras. The new Live view features a real-time dashboard with live camera feeds and a filmstrip of animated thumbnails showing recent activity.
2. Make reviewing video footage more efficient. Frigate intelligently identifies parts of your timeline for review by leveraging the underlying data about motion and tracked objects. The new Review area implements a scrollable grid of thumbnails alongside a timeline where a hover or swipe begins a preview playback. Review items can be configured to be pre-categorized into alerts or detections based on cameras and/or zones. The review area also provides a motion review mode, allowing real-time scrubbing of video footage for any objects of interest that Frigate may have missed.

Frigate 0.14's UI will likely change the way you review your camera footage. It's a big change, but we love it and hope you do too. See the announcement post for more information regarding the motivation, ideas, and design decisions behind the new UI.

Dashboard

The new home page for Frigate is intended to be a real-time dashboard for your cameras. Recent alerts are represented by animated thumbnails in a filmstrip view above your camera feeds. Your camera images update once per minute when no detectable activity is occurring to conserve bandwidth and resources. As soon as any motion is detected, cameras seamlessly switch to a full-resolution live stream.

• Custom camera groups are now supported. Add any of your cameras (including the Birdseye camera) to user-definable groups and easily toggle between them.
• On desktops and tablets, cameras in a camera group can be resized and rearranged via dragging.

Live View

Clicking a camera from the dashboard will bring up a full-resolution live view where you can quickly access historical footage, use PTZ controls, toggle camera audio, use two-way talk, and more. Zooming with pinch or a scroll wheel is also supported.

Review

The Review area of Frigate 0.14 is for quickly reviewing historical footage of interest from your cameras. Review items are indicated on a vertical timeline and displayed as a grid of previews - bandwidth-optimized, low frame rate, low resolution videos. Hovering over or swiping a preview plays the video and marks it as reviewed. If more in-depth analysis is required, the preview can be clicked/tapped and the full frame rate, full resolution recording is displayed. Review items are filterable by date, object type, and camera.

Alerts and Detections

Not every segment of video captured by Frigate may be of the same level of interest to you. Video of people who enter your property are a different priority than those walking by on the sidewalk. For this reason, Frigate 0.14 categorizes review items as alerts or detections. By default, all person and car objects are considered alerts. You can refine categorization of your review items by configuring required zones for them.

See the review docs for more information

Motion review

In Frigate 0.13, there isn’t a way to see motion activity on a timeline and watch video at that time. The ability to scrub video for things Frigate missed has been one of the most common feature requests. Within the Motion tab of the Review section, you can now scrub through the timeline for all cameras simultaneously with a timeline showing relative motion activity. In order to avoid scrubbing over time periods already included in alerts and detections, you can also scrub in motion only mode.

History

In Frigate 0.14, full frame rate, full resolution camera footage (called "recordings" in earlier versions) can be viewed and scrubbed via a timeline. Previews of your other cameras are displayed and scrubbed alongside the main selected camera.

• Exporting footage from the History view has been drastically improved. Choose predefined time periods, enter a time directly, or drag handles on the timeline to select an export range.
• Past exports can be viewed, renamed, deleted, and downloaded from the dedicated Export pane, accessible from the navigation bar.

Other Notable UI Changes

• System stats - New charts and graphs with colored segments to track system usage history and more quickly identify problems or issues.
• Status bar - A new status bar gives at-a-glance CPU/GPU usage as well as any problems or issues with Frigate.
• New log viewer - The log viewer now provides a pane with links to solutions for common issues.
• Real-time motion tuning - Tune motion detection settings for your cameras without editing your config file and restarting.
• New mask and zone editor - Edit your masks and zones with a much-improved editor.

Authentication

Frigate now supports authentication. Frigate manages users and authentication using JWT tokens via a cookie or authorization header. Additionally, a new proxy section in the config allows you to use the user header passed from common authentication proxies such as authelia, authentik, oauth2_proxy, etc.

• Authentication is enforced on a new port 8971, and port 5000 is still unauthenticated for backwards compatibility. If you want to use Frigate's authentication, update your reverse proxy to point at port 8971 instead of 5000.
• Support for role based authorization (admin/user roles) will come in a future release and will support upstream authentication proxies.
• The Home Assistant integration needs to be pointed at port 5000. Some recommended configuration examples are in the updated docs.

See the documentation for more information.

TLS

Since Authentication should really be used over secure connections, TLS is also enabled by default for port 8971. It can be disabled in the config file with the following yaml:

tls:
  enabled: False

Custom certificates can also be used following the tls docs.

Frigate+

Frigate 0.14 now offers a dedicated page for Frigate+ submissions, allowing more specific filtering by score and a faster workflow. Support has also been added to upload frames directly from the History view.

Other notable improvements

• Loitering Time - Zones now support a loitering_time configuration which can be used to only consider an object as part of a zone if they loiter for the specified number of seconds. This can be used, for example, to create alerts for cars that stop on the street but not cars that just drive past your camera.
• Two-way talk - For supported cameras, two-way talk can be used directly from a camera's live view.
• PWA-optimized - The UI has been optimized to work as a progressive web app. Pin Frigate to your iOS home screen or install on Android for a full app-like experience.
• Rockchip boards now support object detection - See the Rockchip documentation for more information.
• Automatic hardware acceleration - automatic detection and configuration of hardware acceleration for ffmpeg is attempted on startup
• New review related MQTT topics and API endpoints - New MQTT topics and api endpoints are available for reviews. These will likely be a better topic for notifications.

Fixes and changes

• Better ONVIF support - PTZ controls will now show for more ONVIF PTZ cameras
• Use ZMQ for interprocess communication
• hwaccel_args are now automatically detected for Nvidia, AMD, and Intel based systems.
• Stationary object detection has been improved especially for parked cars.
• Additional support for IPV6
• RTMP has been removed (after previous deprecation). This is handled by the automatic config migration upon upgrade.

FAQ

Have a question that's not answered here? Look at the most updated list of FAQs here or open a discussion on Github.

Upgrade issues

I'm seeing "add mask expects relative coordinates only" in my logs.
This is usually caused by a mask or zone having coordinates larger than the camera's detect resolution. The easiest fix would be to remove the mask/zone, restart Frigate, and use the new mask/zone editor to recreate it.

What happened to all my events?
An entirely new way of reviewing camera footage has been implemented in Frigate 0.14, so any "events" from any previous versions of Frigate will not be migrated and will not be visible in the new UI. This includes any favorited/starred events. Recordings can still be viewed in the new UI using the recordings viewer (From Live view, click/tap on a camera and select the History button at the top left).

I'm seeing "Preview Not Found" in the UI a lot. Why?
Frigate 0.14 now generates "previews": bandwidth-optimized, low frame rate, low resolution videos for your camera footage. These previews are not generated for any past footage from 0.13, so just wait an hour or two and try again. Historical full recordings are still viewable from your cameras, however. From Live view, click/tap on a camera and select the History button at the top left.

Usage

Can I make the cameras take up more space on my dashboard?
Yes you can, on desktop screens only. Create a camera group, and then use the edit layout button (bottom right) to resize/reposition your cameras on the dashboard.

Where is Birdseye view in the new UI?
Birdseye is accessible by creating a camera group and adding the Birdseye camera to the camera group.

Why are there black bars around my cameras in the new Live dashboard?
Cameras are kept in a 16x9 aspect ratio grid layout. If your camera's aspect ratio is not 16x9, black bars may appear to the sides of the camera image. Birdseye is Frigate's solution for an automatic layout without black bars.

Can I export footage from the review screen?
Yes, right click (desktop) or long press (mobile) to choose item(s) you want to export, then press the export button in the header. You can also export from a camera's full recordings "event" list through a right click on desktops.

What happened to the timelapse export feature?
It's not in the UI, but the API is still available. Most users were using that feature to create videos to manually review each day. One of the main focuses of the new UI was to ensure that isn't necessary. The only remaining use cases we are aware of are for very long periods of time. Having frigate do long exports on high resolution recordings on the server is a really inefficient way to accomplish that.

How can I tune what I see in alerts and detections?
You can restrict alerts and detections to specific objects/labels or exclude a camera entirely. See the review docs. You can also restrict alerts and detections to objects entering zones. See the zone docs.

How can I switch the live view type?
In Frigate 0.13, a dropdown menu in the UI allowed users to select between jsmpeg, MSE, or WebRTC. In 0.14, Frigate intelligently selects the best type of live view method for the cameras on your dashboard, so this is no longer user selectable.

Can I "star" or "favorite" events like in 0.13?
No, that feature has been removed in 0.14 in favor of Exports. If you have footage you'd like to "favorite" or retain in 0.14, use the export tools. Unlike favorite events in 0.13, exported footage in 0.14 is searchable from the Exports page.

Are there any keyboard shortcuts in the UI for desktop devices?
Yes. In the Review pane, Ctrl/Cmd-A selects all of your review items. On Live camera view, you can use the arrow keys along with + and - to control a PTZ camera. In the Logs view, page up/page down and arrow up/arrow down will scroll the logs. Wherever video controls appear (History view, Motion Review), the left and right arrows will seek the video backwards and forwards by 10 seconds. The up and down arrow keys will seek the video by 1 second. The "f" key toggles fullscreen, "m" toggles muting, and the space bar toggles playback/pause.

Full Changelog: v0.13.2...v0.14.0-beta4

---

This discussion was created from the release 0.14.0 Beta 4.

[bagobones]

Well I figure by Beta 4 it has to be stable enough to use.

Looks great!

Going to take me a while shift my config / use to use alerts and detections however.

Not sure I fully understand how alerts/detections impact the recording settings for retention and the recording section still references events, and makes no mention of alerts/detections.

[NickM-27]

I have a patch of road set as a zone that I don't want to be an alert as there is too much noise from cars that drive close enough to trigger it when empty or park a short time but it is still helpful to have all the cars tagged to find the clips fast.

You could use a zone required for alerts here with the loitering time set to 1 hour or whatever makes sense

That's what I do although I only set it to 2 minutes

[bagobones]

I hadn't even gotten to the new zone features that might work for letting me use it for alerts which would then also take it out of the detections noise.

[bagobones]

So this isn't working and I don't know why.. setting loiter time to 60 caused me to have no event when someone parked Infront of my place.

Removing the loiter and treating it as an alert I am getting many of them even with the vehicle not actually moving>

Since 0.14 no longer has a review option showing the time line of entering / exiting zones with bounding boxes I have no idea WHY it keeps redetecting.

Looking at it in the current debug view the center bottom should have been in the zone but maybe the bounding box is unstable and jittering or something. no way to know.

One theory might be zone naming.. will it screw up loiter time if more than one camera as a zone with the same name?

[NickM-27]

Removing the loiter and treating it as an alert I am getting many of them even with the vehicle not actually moving>

What do you mean by the second part "treating it as an alert" ?

That makes it seem like when you had the loiter configured it wasn't treated as an alert?

[bagobones]

I can see how that might be confusing.. I am just saying I am STILL using required zones in the alert section to make it an alert.. We started the conversation with the road being a detection .

[dioni-dev]

More stable comparing the previous version but it's still having several problems like this: Failed to load resource: the server responded with a status of 404 (Not Found)

[NickM-27]

That's not really helpful, a full set of logs would be good to see. Many users have been running it for months with no issues

[Iceman248]

Anyone have any issues using a reverse proxy with the new 8971 auth port? If I leave it at HTTP like it was at 8080, it says it's actually a HTTPS port, but when I change it to reflect that, I just get a 502 Bad Gateway, so for now I just had to have my reverse proxy use the 5000 port.

[NickM-27]

You need to disable tls in the frigate config

[Iceman248]

Thanks, solved.

[shred86]

I was having similar issues but disabling TLS solved it. Thanks!

[LaurenceGough]

Thanks for the update, I am most likely being silly but I am not seeing the option to show the bounding box of what caused the event detection to happen. In Frigate 13 this was recently added as an option when viewing an event and I found it extremely handy to find out what area set the object detection off to remove intermittent false positives.

Many thanks

[hawkeye217]

This is not available in 0.14, but there is a feature request here: #11399

Feel free to leave a thumbs up!

[LaurenceGough]

Thanks, I have done now. It's a shame there was a regression on that really great feature, hopefully it'll be added back.

Does loading your System Metrics page freeze any webserver being hosted by your host for 30 seconds or so?

[hawkeye217]

Thanks, I have done now. It's a shame there was a regression on that really great feature, hopefully it'll be added back.

It's not technically a regression, because events are different from review items in 0.14. This is a helpful explanation: #12432 (reply in thread)

Does loading your System Metrics page freeze any webserver being hosted by your host for 30 seconds or so?

No. I don't recall seeing any other reports of that either.

[LaurenceGough]

I kind of miss the way the debug menu was so easy to get to before, using the debug menu was a very quick way to see if anything was constantly triggering motion and/or object detection. I might be alone in this feeling.

[hawkeye217]

It was moved to "Settings" to help simplify the Live view UX. The reasoning was that once you've tuned your motion settings and dialed in object detection, there's not really a reason to watch the debug view.

It's been improved from 0.13 though, now providing a time-delayed list of tracked objects.

[LaurenceGough]

Understood and I can agree that it didn't have to be quite so prominent. However it's nice to know that if your cameras are stuck in motion detection and/or object detection as camera views can change all the time, perhaps from foliage that has grown or moved outside of your masks, spider webs, trash etc. I used it at least probably about once a week on average, so granted not that much, but then again I don't really open Frigate that much as we receive notifications via home assistant for everything we need.

[Pureaznangel]

Can we control the zoom speed? My camera has this but the zooming speed is to slow because it used camera's default (5), and should we activate an detector by a schedule time?

[hawkeye217]

No, setting any speeds on a PTZ is not possible in Frigate currently.

Frigate does not support any kind of feature scheduling. Enabling and disabling many frigate features can be done with MQTT, the HTTP API, or an automation platform like Home Assistant.

[bagobones]

Opinion: The recent alert thumbnails at the top of the screen should be filtered by the currently selected camera group

[NickM-27]

I have gone back and forth on this because on one hand it makes sense, but on the other hand if you are not looking at a camera then you might miss something that happens and the alert filmstrip could show that this happened. After discussing some more, #12456 will implement the filtering based on selected group

[bagobones]

The thumbnails are 100% useless if you have at least one camera with a crowd of people active in it all day, it just covers the more intermittent activity from other cameras and YES I want to be recording that busy camera when there are people there.

Maybe it should only show the LAST clip from each camera at a minimum?

[NickM-27]

YES I want to be recording that busy camera when there are people there.

but do you want it to be an alert always? this is one of those cases where you could create zone(s) for alerts and a secondary zone(s) for detections, since only alerts show at the top.

[bagobones]

This is going to go back to , how does that impact retention.. I do want all the time with People retained for an extended period of time, do I not need it to be an alert for that to happen with "event" recording? Still not clear on that.

[NickM-27]

Making that change I described won't affect the retention of recordings.

[mattbruman]

Beta 4 did something weird to my Bridseye, it was working great in Beta 3 but now after a few hours my Birdseye looks like this until I reboot. I made no changes from Beta 3 to 4. But whatever is causing it it is fixed after a Frigate Reboot.

[NickM-27]

Nothing has changed in regards to birdseye between these betas. This has always been a possibility when birdseye is being restreamed because go2rtc will get out of sync pulling data from the pipe. Simply removing all consumers of the birdseye stream will cause it to get cleared and work normally when viewing birdseye again

[mattbruman]

Weird how I have been streaming the BE to VLC and only now this has happened. This is reliable happening after a few hours since Beta 4. I only restream to VLC and have restarted the stream and it never fixes itself until reboot.

[mattbruman]

Could the changes to the Live view caused something weird?

[NickM-27]

No, live view would not affect birdseye coloration, this is very distinctly what happens when the pipe is out of sync and ffmpeg is reading the wrong channels for color

[LaurenceGough]

I have disabled port 5000 so that TLS is used instead to view cameras via the new port. Is it possible to get the Home Assistant Integration working for notification images without this 5000 port being enabled? Currently I am getting notifications but no images at all.

My understanding of it might be incorrect.

[NickM-27]

assuming home assistant and frigate are on the same device then you should enable 5000 locally so the integration can access it but outside devices can not. https://deploy-preview-11419--frigate-docs.netlify.app/integrations/home-assistant#home-assistant-running-with-host-networking

[LaurenceGough]

Thanks Nick, yeah they are on the same host. I take it you cannot just relink them using port 8971 instead of port 5000?

[NickM-27]

No, the integration has not been updated to support authentication

[LaurenceGough]

Thanks, I've got it all working again now after some container network tweaking to keep it private.

[mat967]

New Frigate user on unraid (docker) here. I started on beta 3 and had a good experience but with spotty/laggy live view.

Happy to say that since beta 4, those problems disapeared! I don't have to refresh the webpage multiple times anymore.

Thank you guys for your awesome work!

[mostlychris]

Hello. Quick question and/or feature request. On the review page, is there way to prevent auto playing clips when hovering over them? I want to be able to scroll through the list without things starting to play and there is no place, at least in the Chrome browser, where I can scroll without putting the mouse on a clip.

[NickM-27]

if you scroll without moving the mouse, it will not auto play, it only auto plays when there is mouse movement.

[mostlychris]

Lemme give that a go.

[mostlychris]

I guess there will always be one clip that auto plays just so I can get the mouse onto a scrollable part of the screen. Once I get the mouse over the first clip, I can scroll with the mouse wheel and nothing else plays.

[PovilasID]

Minor UI problems:
Pinch to zoom broke on mobile. I maybe misremembering but I think I could use pinch to zoom on my mobile on the video feed in betas and now if I zooms the entire page not the video. I can still double tap to zoom video only but not pinch.

No visual indicator for video steam buffering Loading spinner is visible if you chose to play history of the stream but it does not seem to check if video chunk is loaded/playing. I have cameras on mobile connection, so it sometimes takes a while to load each chunk and after what looks to be first frame of video has been loaded video loading indicator diapers but the video is still frozen and there is no visual indicator if the video feed is buffering or playing. I have to rely on audio/seek movement to check if it is actually playing vs buffering. For stream buffering I do not think it needs to throw up a spinner in the middle of the feed but a pulsing dot in the corner similar to live or tiny pill indicator like for detections would make it clearer.

[hawkeye217]

Minor UI problems: Pinch to zoom broke on mobile. I maybe misremembering but I think I could use pinch to zoom on my mobile on the video feed in betas and now if I zooms the entire page not the video. I can still double tap to zoom video only but not pinch.

This regression is actually caused by a bug in one of the packages that we use. We've reverted to the previous version for now, so this should be fixed. Thanks for reporting it!

[LaurenceGough]

I am seeing /tmp/cache at 214GB out of 233GB in the built system storage monitor. I checked Frigate's shell it's listing the folder as 22MB.

I am also seeing Recordings with an incorrect limit in the same system storage monitor.

What have I done wrong? :D

[NickM-27]

Sounds like something is mounted incorrectly, that's very odd

[noelhibbard]

After getting the hang of this new UI, I am loving it. I'm sure there will be small tweaks along the way but overall this is a massive improvement. Just wanted to say thanks!

[hawkeye217]

Thanks for the kind words! We really appreciate it.

[hexatrim]

Could we have a Mon-Sun calendar layout? I've just spent ages looking for something that happened on Tuesday only to finally realise I was on Monday :(

[hawkeye217]

Implemented in #12491

[hexatrim]

Great, thank you!

[noelhibbard]

How do you delete a point in the mask editor? A right click deleted a point in 0.13, but that isn't working for me in 0.14.

[hawkeye217]

Use the "Undo" button in the control pane on the left.

In 0.13, it was impossible to use the mask/zone editor on mobile devices. Having an "undo" button rather than a right click provides a consistent UX experience between mobile and desktop in 0.14.

[noelhibbard]

@hawkeye217 , I figured that would only work when creating a new zone but it turns out it will undo even on an existing zone which is being edited. It would still be nice to delete a point somewhere in the middle of the mask though. Not a big deal really.

Thanks for the response.

[bagobones]

I feel like supporting the right click on desktop wouldn't take anything away from the touch friendly UNDO, however maybe make an always on toggle that is ether in add point mode or subtract point mode would work for both.. I have seen that on some editors.

Feels like a downgrade in the zone editing, thankfully you don't have to do it often.

[slug56]

If I apply the "Sort" on the Frigate+ page without actually selecting either of the Date/Score radio buttons, I get no results and the pill text changes to "Undefined". I feel like this might not be the intended behaviour.

[NickM-27]

thanks, fixed in #12513

[noelhibbard]

It would be cool if the left and right keys would step forward/backward frame by frame if the video is paused.

[NickM-27]

this has been discussed, this is not possible in a browser #12448 (reply in thread)

[noelhibbard]

I was afraid this would be the case.

[Mincka]

However, it would be possible to do half-seconds or quarter-seconds and that would be compatible with most of the configurations. So 2x or 4x more precise scrubbing.

Edit: Maybe you don't know that you can have second steps with up / down arrows already.

[noelhibbard]

Maybe you don't know that you can have second steps with up / down arrows already.

Yep, I know about the 1sec increments.

[bagobones]

This was previously discuss but is there ANY chance the built in frigate+ submission could Auto label ALL objects it has seen, no just the single event object? Adjusting bounding boxes vs having to create all of them and switch labels would save a lot of time.

With my current doorbell and Duo2 I have to label about a minimum of 5 cars or more every time I make a submission.

[NickM-27]

See #12516 (reply in thread)

[PovilasID]

Minor localization issue:
Timestamps format in timeline where I am from we do not use AM or PM we use 24 format (1:00 PM is 13:00 ). Frigate permits setting your timestamp in format for timestamp footage overlay in timestamp_style: format: and it helps a lot, however, timeline is using AM and it is not major issue because you can see in preview if it dark or sunny outside I still keep forgetting is AM after midnight or after midday. This totally a localization and my dyslectic brain problem.

[Mincka]

Did you set this? Because 24-hour format is supported on timeline. The only place I see where it's not supported yet is the hour picker for event exports.

ui:
  time_format: 24hour

See documentation:
https://deploy-preview-11419--frigate-docs.netlify.app/configuration/reference

# Optional
ui:
  # Optional: Set a timezone to use in the UI (default: use browser local time)
  # timezone: America/Denver
  # Optional: Set the time format used.
  # Options are browser, 12hour, or 24hour (default: shown below)
  time_format: browser

[PovilasID]

Ops I was searching for "timestamp" in the docs.
Thanks!

[hawkeye217]

The only place I see where it's not supported yet is the hour picker for event exports.

Frigate is using a standard HTML time input for this. The format you see is dependent on your browser's locale. We cannot change the way it's displayed, but you can.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/time#time_value_format
https://stackoverflow.com/questions/70878499/show-format-time-24hours-in-input-type-time

[nriel]

In our household multiple people access the timeline. Any possibility to auto show all events/alerts and stop hiding those already viewed/reviewed?

If I open the timeline and my wife already saw some alerts/events, the are hidden from me until ticking the checkbox "show reviewed"

[NickM-27]

In the future we can probably keep track of the reviewed status based on which user is logged in. For now just need to press the show reviewed button

[hawkeye217]

Feel free to give a thumbs up on this feature request as well: #11621

[Jbvest88]

i dont understand why i cant get this working it wont start on boot even tho its ticked, I've changed the stuff it mentions in the log, MQTT password it correct, removed roles that weren't mentioned in the list below. i feel like it something simple , but I've spent the last 4 hours trying to get it to boot, i had frigate working fine and changed to the beta to try it out. i changed the url for integration too. to reflect beta. i hope this is ok to post here. thanks in advance for any advice! i also even flashed a fresh new drive (needed more space) and just restored a core update backup.

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-22 04:27:10.144393893 [INFO] Preparing Frigate...
2024-07-22 04:27:10.145332330 [INFO] Starting NGINX...
2024-07-22 04:27:10.146352608 [INFO] Preparing new go2rtc config...
2024-07-22 04:27:10.151598232 [INFO] No TLS certificate found. Generating a self signed certificate...
2024-07-22 04:27:10.155209538 [INFO] Starting Frigate...
curl: (22) The requested URL returned error: 400 Bad Request
2024-07-22 04:27:10.178329036 [WARN] Failed to get IP address from supervisor
2024-07-22 04:27:10.452705299 [INFO] Starting go2rtc...
2024-07-22 04:27:10.614582995 00:27:10.614 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-22 04:27:10.614601602 00:27:10.614 INF config path=/dev/shm/go2rtc.yaml
2024-07-22 04:27:10.614951803 00:27:10.614 INF [api] listen addr=:1984
2024-07-22 04:27:10.614997221 00:27:10.614 INF [rtsp] listen addr=:8554
2024-07-22 04:27:10.615129700 00:27:10.615 INF [webrtc] listen addr=:8555/tcp
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
2024-07-22 04:27:10.815955948 [INFO] Starting certsync...
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-07-22 04:27:10.883207181 127.0.0.1 - - [22/Jul/2024:00:27:10 -0400] "" 400 0 "-" "-" "-"
2024-07-22 04:27:11.480613937 [2024-07-22 00:27:11] frigate.app INFO : Starting Frigate (0.14.0-a4eb435)
2024-07-22 04:27:11.480690993 [2024-07-22 00:27:11] frigate.app INFO : Creating directory: /tmp/cache
2024-07-22 04:27:11.480789990 [2024-07-22 00:27:11] frigate.util.config INFO : Checking if frigate config needs migration...
2024-07-22 04:27:11.508976729 [2024-07-22 00:27:11] frigate.util.config INFO : frigate config does not need migration...
2024-07-22 04:27:11.514818542 *************************************************************
2024-07-22 04:27:11.514820995 *************************************************************
2024-07-22 04:27:11.514824288 *** Your config file is not valid! ***
2024-07-22 04:27:11.514826740 *** Please check the docs at ***
2024-07-22 04:27:11.514828007 *** https://docs.frigate.video/configuration/index ***
2024-07-22 04:27:11.514845935 *************************************************************
2024-07-22 04:27:11.514847246 *************************************************************
2024-07-22 04:27:11.514861453 *** Config Validation Errors ***
2024-07-22 04:27:11.514862688 *************************************************************
2024-07-22 04:27:11.514953051 mqtt.password: Input should be a valid string
2024-07-22 04:27:11.514955364 cameras.rear.ffmpeg.inputs.1.roles.1: Input should be 'audio', 'record' or 'detect'
2024-07-22 04:27:11.514956881 cameras.front.ffmpeg.inputs.1.roles.1: Input should be 'audio', 'record' or 'detect'
2024-07-22 04:27:11.514958212 cameras.side.ffmpeg.inputs.1.roles.1: Input should be 'audio', 'record' or 'detect'
2024-07-22 04:27:11.514959511 *************************************************************
2024-07-22 04:27:11.514960700 *** End Config Validation Errors ***
2024-07-22 04:27:11.514961825 *************************************************************
2024-07-22 04:27:12.741497743 [INFO] Service Frigate exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service go2rtc-healthcheck: stopping
s6-rc: info: service certsync: stopping
2024-07-22 04:27:12.749694603 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-22 04:27:12.750758737 [INFO] Service CERTSYNC exited with code 256 (by signal 15)
s6-rc: info: service certsync successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service certsync-log: stopping
s6-rc: info: service certsync-log successfully stopped
2024-07-22 04:27:12.794984119 [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
s6-rc: info: service nginx-log successfully stopped
2024-07-22 04:27:12.802495849 exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-07-22 04:27:12.814770526 [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[bagobones]

*** Your config file is not valid! ***

YAML requires EXACT spacing in the config file, you probably have something off in it.

You can use an editor like VC Code or NotePad++ to better see the formatting, or dump it into a YAML linter to check the spacing / format https://www.yamllint.com/

[Mincka]

Would it be possible to choose a default home page?
When I open Frigate (through HA addon proxy), it's 99 % of the time to review alerts and detections, so I would like this screen to open first.
I cannot use bookmarks since I cannot pass a full URI.
Maybe it would be possible to do that using the proxy addon (or the base HA addon) by specifying the URL to open.
I'm also open to other suggestions. Thanks!

[a-lunatic]

Maybe able to do it with a Custom panel?

[bagobones]

Custom events in 0.14?

Since we don't have events in the UI but alerts and detections is there any way to use the API to manually create an alert?

I have a few configured in HA and they still show up in the HA integration / with custom frigate card but don't cause an alert/detection in frigates new UI.

[NickM-27]

Custom events create alerts. If you have labels included in the config for alerts then that label needs to be added as well.

[bagobones]

If you have labels included in the config for alerts then that label needs to be added as well.

Aww that is probably the the cause then

[bagobones]

since person and car are the only default labels for alerts I had to add them plus my custom label to each camera that had a custom event.

[Mincka]

When using the HA addon proxy, I get a strange behavior when clicking on the camera button or the logo.
I was expecting to get back to the "All cameras" view, but that's not the case if I click on another group first.

Let's say I click on "Outdoor" group, then go to the review tab, then click on the logo (it goes back to "Outdoor"), then click on "Indoor" group, and clicking again on the logo, I go back to "Outdoor" with the "Indoor" icon still active, I don't understand why.

[NickM-27]

Thanks, fixed in #12596

[notgood]

Any particular technical, political or religious reason for disabling IPv6 by default?

It is year 2024, and every distribution worth running on has IPv6 supported and switched on by default.

[notgood]

I've read the #11684.

Users complaining are knowledgeable enough to explicitely disable IPv6 on their hosts, for whatever reason. It takes knowledge and effort to modify kernel command line in bootloader or to blacklist particular module to completely disable IPv6 stack. It's not a single checkbox on consumers router, every host has to be intentionally and deliberately crippled. These users are certainly competent enough to disable it in Frigate as well, overriding nginx.conf.

As I mentioned, every single OS and distribution these days ships with IPv6 enabled, and defaults really matter in these case. Companies like Google and Facebook are running their internal hosts in IPv6-only mode for ten years already. No iOS app is allowed to be deployed without being able to function in IPv6-only environment. List can go on and on.

Disabling default IPv6 in modern application like Frigate would be rather unfortunate and backwards decision.

[NickM-27]

The feedback we received showed that disabling IPv6 is much more common than using it, so this default will reduce the amount of support we would need to provide to users that have it disabled. It also would be a breaking change to enable it by default. The documentation explains how to enable it.

Perhaps in the future we can have some startup logic that detects if IPv6 is enabled and templatize the configuration to have an intelligent default, for now it is disabled by default.

[notgood]

Your statement "..disabling IPv6 is much more common than using it.." is factually incorrect.

99% point something instances of Frigate already do run, and certainly will continue to be run on IPv6 enabled hosts. Its a fact of life and power of sane defaults provided by every modern distribution. Every network interface has at least one link-local IPv6 address and every app can count on it.

These are hard cold facts: one doesn't need to make surveys, get feedback or collect telemetry to confirm it.

My opinion stands: disabling nice and useful feature because of a few loud users who misconfigured their hosts isn't the best decision in the long run.

[NickM-27]

Your statement "..disabling IPv6 is much more common than using it.." is factually incorrect.

I am speaking in the context of Frigate. Frigate only started supporting IPv6 in 0.14. In all that time before, we received far fewer requests to add support for it than the negative feedback we received in one week about it being enabled by default.

My opinion stands: disabling nice and useful feature because of a few loud users who misconfigured their hosts isn't the best decision in the long run.

Sure, you are entitled to your opinion. However, you don't have to provide support to Frigate's user base. Making IPv6 the default, it is clear there would be a considerable number of support requests and this would take away from our time to support other users, work on new features, etc.

Like I said, there are potential ways to implement it in the future such that users won't have to change anything, but that is not in scope for 0.14.

[notgood]

"You break it, you fix it" line is the only support required for users who disable IPv6 and write bugreports.

Just some food for thought, or rather learning from other's mistakes:

1. Ubuntu briefly disabled default IPv6 listen in their nginx package back to 2019, for the same reason as Frigate in Beta 2 does not start without ipv6 #11684 ....
   only to completely rollback changes after users uproar and close as "wontfix" later. Plenty of arguments there, see https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592

2. Debian team facing the similar report was more blunt: "We've now determined this is because the user disabled IPv6 support on their system. This isn't simply a non-standard case, it's a nonsensical one. Accommodating this use case would cause headaches for pretty much every single other person that uses Nginx." See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779825#97

Both Ubuntu and Debian have quite a bit larger userbase than Frigate, yet have no problems closing invalid bugreports.

In the end, accomodating for broken host configurations with templates, complicated checks and #ifdefs will result more work and more support headaches. But if there is a will, there is a way, right?

[c0nfus3]

I'm using the latest Beta since few days and I like the new Alert thingi, which I mainly use for notification now.
Anyhow I observed that some clear detections are not shows as alert.
I defined an alert zone in the driveway. If somebody pass this area / zone, it will throw an alert.
In 8 of 10 cases, the alert will be triggered. Detection is always correctly shown.
Anything I can do, to improve the alerts, the detections already works fine.

   objects:
     track:
       - person
       - car

     mask: 0.538,0.374,0.537,0.456,0.561,0.456,0.565,0.376


   motion:
     mask:
       - 0,0.764,0.134,0.291,1,0.177,1,0,0,0
       - 0.513,1,1,1,1,0.647
       - 1,0.596,0.889,0.472,0.937,0,1,0

     threshold: 30
     contour_area: 10
     improve_contrast: true
   review:
     alerts:
       required_zones:
         - Einfahrt

   zones:
     Einfahrt:
       coordinates: 0.134,0.293,0.089,0.455,0.462,0.39,0.389,0.257
       objects:
         - car
         - person
       inertia: 3

[hawkeye217]

The bottom center of an object's bounding box must appear in the Einfahrt zone in order for it to be marked as an alert. See the image here: https://docs.frigate.video/configuration/zones/

If you watch the debug view, this will give you a better idea of what might be happening with the objects that don't make it as an alert.

[c0nfus3]

Unfortunately it's my parents home, so I'm not able to do it with the debug view at the moment and for the next days.
Based on my image which is from the detection clip, my mum drives from the street to the end position (left picture).
From my point of view she passes the alert zone, but stops at the bottom end of the zone.
Should I do the zone smaller? I mean the cars / persons has to pass the zone, there is no other option ;) ( at least not in 2024 :D )
Interestingly it works better with my das car, which is black.

picture removed for privacy reasons

[hawkeye217]

I would highly recommend removing the motion mask as you are using it incorrectly. A large mask will make it more difficult for frigate to track objects.

https://docs.frigate.video/configuration/masks/#further-clarification

If an object is coming in from the street, your motion mask is likely preventing Frigate from detecting the object until it's already in the zone. This may explain why it's not consistent every time.

[c0nfus3]

Okay, makes sense. Thanks!

Only downside, I'm getting more detections as needed, but if the alerts are working, I won't check them :)

[hawkeye217]

Happy to help.

If you don't want to see objects on the street as detections, you can limit detections to zones as well. For example, you could create a zone for everything that doesn't appear on the street, and then limit detections to that zone. Check the Camera Settings pane in Settings in the UI, it will walk you through everything.

[pyrodex]

Is there a chance for a future UI change under the Frigate+ review section in the on-premise Frigate UI?

Here are some thoughts...

Image re-sizing features could allow for folks who are unable to see those smaller images and stuff quickly at glance. In my experience with Safari on macOS even when you use the browser ZOOM it seems to take a LARGE amount of zoom to get the images to become larger but unfortunately as you increase the zoom level the ICON grows just as large. I think giving some type of sliding bar or a drop down that could have zoom percentages could allow users who are visually impaired to make the images larger while the rest of the UI stays the same and you don't need to rely on the browser zoom levels. It would be nice to also retain these settings at a per browser level via cookies or maybe some user settings retention in the database (future).

The colors being used by default, which are not customizable by the user, are some what to be desired for certain labels. For the person label it is a GREY border and to be honest that is hard to see when the images are the size they are right now on a larger resolution. Are there changes to maybe make this an end-user customization that could be stored at the user settings level or maybe do some more "brighter" and "attention seeking" colors for label borders?

In the older 0.13 UI you had the ability under Frigate+ UI on the local interface to DELETE or IGNORE images but in the new 0.14 UI you are basically stuck with having a building page of images and if there is one you DO NOT want to submit you can't ignore it, you have to Cancel (keep it around), Submit as False, or Submit as True. Additionally, there is no way to go back and see images you submitted or if you allowed an ignore option it would be nice to see those similar as is in the review section for events.

I am by no means visually impaired but I am an aging individual, 😢 , and my vision isn't as good as possible but my mind is still as sharp 😄 .

[NickM-27]

I'm sure more improvements will come to that page in future versions.

To be clear colors are not assigned to certain labels across the board. My color for person is different than your color for person. They are built from a collection of colors and assigned based on the number of labels you are tracking.

Not sure a see a reason to view already submitted images for the purpose of frigate+. Maybe for debugging purposes but there will be other pages to serve that propose in the future.

[pyrodex]

I'm sure more improvements will come to that page in future versions.

Thanks! I think improving the visibility functions will help all aspects consumers of the UI

To be clear colors are not assigned to certain labels across the board. My color for person is different than your color for person. They are built from a collection of colors and assigned based on the number of labels you are tracking.

Ahh! Same statement as above.

Not sure a see a reason to view already submitted images for the purpose of frigate+. Maybe for debugging purposes but there will be other pages to serve that propose in the future.

I think it would be good to go back and re-submit it if possible when you make a mistake on the false or true submission of an image since in the case of a false submission you need that data from the on-premises UI and can't do that via the Frigate+ WebUI.

[NickM-27]

I think it would be good to go back and re-submit it if possible when you make a mistake on the false or true submission of an image since in the case of a false submission you need that data from the on-premises UI and can't do that via the Frigate+ WebUI.

that will require additional changes on the Frigate+ side as well

[patdemko]

Really liking the new UI and everything with it. Great job to all involved! I do wish it was easier to see which objects caused the alerts in the review section. The icons are OK for some of them, but not really useful for audio detections if you have a few configured. I know you can hover on it and get the text of what was detected, but if you have a bunch to review it takes a while and it also doesn't work if you're looking at it on a phone. Would love it if there was an configuration option to overlay the text of the detection object on the thumbnails in the review section.

[hawkeye217]

Thanks for your feedback, we're glad you like it! There will be additional ways to discover this information in upcoming versions.

[track0x1]

Loading Frigate on my iPhone is very slow... taking over 10 seconds until I can even see the thumbnail of the camera. Viewing on my Macbook is much faster. Is there anything I can do to speed it up?

[NickM-27]

Not sure why it would be slow, my android and iPhone are fast even when using cellular data. You could try disabling automatic live view and see if it improves.