0.14.0 Release Candidate

[blakeblackshear]

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

Images

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

Major Changes for 0.14.0

Breaking Changes

There are several breaking changes in this release, Frigate will attempt to update the configuration automatically. In some cases manual changes may be required. It is always recommended to backup your current config and database 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 (helpful walkthrough video from a user) 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 footage from older versions of Frigate. 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

Are there any tutorials or videos on how to use the new version?
Yes, see the guided demo and a helpful walkthrough video from a user.

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. Birdseye is also accessible by navigating directly to frigate_ip:port/#birdseye.

Why are there black bars around my cameras in the new Live dashboard?
Cameras are kept in a standard 16x9 aspect ratio grid layout. If your camera's aspect ratio is not 16x9 (or a multiple of 16x9 like a wide angle 32x9), black bars may appear on any of the sides of the camera image. One solution would be to adjust your camera's resolution in firmware to fit any multiple of the 16x9 aspect ratio. You could also use Birdseye, which is Frigate's solution for an automatic live view 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.

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 view snapshots with bounding boxes?
Snapshots have been deprecated in favor of the new review item format. To understand why, consider the situation where two people, one with a dog, walked past your house. At the same time, a car drove by on the street behind them. In this scenario, Frigate would have tracked 4 "events". One for each person, the dog, and the car. In 0.13, you would have had 4 separate videos to watch, even though they would have all overlapped. In 0.14, these separate objects are combined into a single review item which represents the period in time where these objects were active on the camera. Reviews for a single camera cannot overlap. Displaying separate snapshots for this scenario in a way that shows they are connected is not only difficult, but also less helpful than having a combined thumbnail and easy to view video preview that quickly shows what exactly happened. Even though snapshots are no longer available in the 0.14 UI review pipeline, they are still available in the Frigate+ view, on the filesystem, and viewable through Home Assistant's media browser. A screen to help debug review items and answer the question "why was this review item created?" will be coming in a future version.

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. The Camera Settings screen in the UI provides a lot of granular control. 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 based on network conditions and features, 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 can be given a label/name and 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.

Have a question that's not answered here? Open a discussion on Github.

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

---

This discussion was created from the release 0.14.0 Release Candidate 1.

[xconverge]

I have 2 quick questions that I dont think are worth flooding the issue-list with

1. I am glad the "hide-reviewed" toggle is now persistent, however I am surprised that it is not linked behaviorally to the preview gifs on the main page? If I click a preview and then go back, I personally find it disorienting that it is now gone. I was hoping the hide-reviewed toggle would also keep these

2. the preview gifs seem to take quite a long time to load/pop-in (when not already cached), 5ish seconds or so. Are these being generated at this time which is what I am seeing? If so can/should we put thumbnail as a placeholder or is that silly? There should be some sort of skeleton or loading icon probably for these. I tend to use these previews quite a bit, so now when I open frigate I have to just sit there waiting for a few seconds before starting to "look" for what I was trying to look at

[NickM-27]

1. There's no way to toggle it there, so to me I think having them being connected would be unintuitive. If you reviewed something, what would be the reason to continue showing it there?
2. To be clear are you referring to the live view specifically?

[xconverge]

1. I agree that the toggle shouldn't necessarily be connected. (note that what I am about to write is just insight into why I thought this and makes me feel insane to write out how my brain works a bit 😆 ) I don't know I just like keeping things in one place, I find it disorienting when buttons/elements/things move around on the page as you go to/return from other pages, so if I see 3 events, and want to review them and click the right farthest one, I may make a subconcious mental note that I still want to review the middle one. When I then come back to the page a moment later and there are 2 events left, it is "hard" for me to remember which one I had meant to look at because to me the events stick out by "position in the list" moreso than the "time ago" identifier (which is constantly changing)

2. Yea, I dig the skeleton you added though, anything more seems unnecessarily complicated for now

[NickM-27]

that makes sense, perhaps we can look at keeping them around in the future

[theyapps]

Does the new GUI get rid of the ability to view snapshots or am I missing something somewhere. At work my mobile connection can be very shotty so loading videos will be slow so I instead would load snapshots.

[NickM-27]

the ability to view snapshots is not in the UI except on the frigate+ page for submitting to Frigate+. However, this is not an issue for the reason you are describing.

At work my mobile connection can be very shotty so loading videos will be slow so I instead would load snapshots.

The previews that are used are much smaller than even a snapshot and the thumbnails are very small as well. So a thumbnail can be viewed and swipe to see the preview video all using much less data than a single snapshot.

[hawkeye217]

The reason for deprecating snapshots is also discussed in the FAQ in the release notes above.

How can I view snapshots with bounding boxes?
Snapshots have been deprecated in favor of the new review item format. To understand why, consider the situation where two people, one with a dog, walked past your house. At the same time, a car drove by on the street behind them. In this scenario, Frigate would have tracked 4 "events". One for each person, the dog, and the car. In 0.13, you would have had 4 separate videos to watch, even though they would have all overlapped. In 0.14, these separate objects are combined into a single review item which represents the period in time where these objects were active on the camera. Reviews for a single camera cannot overlap. Displaying separate snapshots for this scenario in a way that shows they are connected is not only difficult, but also less helpful than having a combined thumbnail and easy to view video preview that quickly shows what exactly happened. Even though snapshots are no longer available in the 0.14 UI review pipeline, they are still available in the Frigate+ view, on the filesystem, and viewable through Home Assistant's media browser. A screen to help debug review items and answer the question "why was this review item created?" will be coming in a future version.

[theyapps]

Yes I can see the previews, they are zoomed in so do not give the full context nor highlight the tracked subject. I liked being able to see both of those. It is just a minor loss in personal workflow, I think that the improvements to the UI will overcome that minor loss. Just wanted to be sure that I wasn't missing a button somewhere. Thanks!

[NickM-27]

Yes I can see the previews, they are zoomed in so do not give the full context nor highlight the tracked subject. I liked being able to see both of those.

the previews are not zoomed in. They are full camera frame, seems like you are referring to the thumbnail which is different. Have you tried swiping to the right on the thumbnail? that is how you view the preview on mobile

[theyapps]

Ah okay I was missing that, and you are right it did load fast. I will test drive that for a while. Thanks.

[stoneobscurity]

system/cameras page is blank for me. i suspect it's because i'm using an external g2r and not the built in one. the internal g2r still cannot be disabled. this needs to be a feature for us advanced users.

[NickM-27]

the system / cameras page has nothing to do with go2rtc, the stats showing there is entirely unrelated to that

[stoneobscurity]

okay its loading now. i guess it needed more data to populate.

still, g2r disable needs to be a thing, even if you make it a hidden config and not the gui.

[NickM-27]

all of the features can't be supported if go2rtc is external, this has been explained throughly multiple times #10181

[FeatherKing]

just updated to the RC (looks great!), my doorbell puts out a 2560x1920 resolution (reolink). In 13.2 this UI camera card was slightly taller than the rest

in the new UI each box seems to be based on a 16:9 ratio like

if i make my own camera group and make the doorbell bigger, the dimensions box is constrained to 16:9 always, so i end up wasting a lot of space

curious if there is a way to do this differently in the new UI, or maybe im the only one with a weird resolution

[hawkeye217]

This is covered in the release notes FAQ above:

Why are there black bars around my cameras in the new Live dashboard?
Cameras are kept in a standard 16x9 aspect ratio grid layout. If your camera's aspect ratio is not 16x9 (or a multiple of 16x9 like a wide angle 32x9), black bars may appear on any of the sides of the camera image. One solution would be to adjust your camera's resolution in firmware to fit any multiple of the 16x9 aspect ratio. You could also use Birdseye, which is Frigate's solution for an automatic live view layout without black bars.

[NickM-27]

No matter what size the columns are based on, there will be wasted space if the cameras are not the same aspect. This is working as expected.

[FeatherKing]

thanks! will continue to poke around. I had no issues upgrading and all my alerts continue to flow through HA. i have 8 cameras, some hardwired, some wyze over docker-wyze-bridge, and a reolink doorbell with rtsp. very painless, thanks all.

[FeatherKing]

Is this discussion the best place to put feedback on the RC? seeing one other odd issue with one camera after a little more time in the UI

[NickM-27]

What are the durations of the files in the file system?

[FeatherKing]

looks like ten seconds, but i dont see any files older than 6pm MDT, the failed clips all seem to be prior to 6pm, but the low resolution scrubbing still works. Is there something that would have cleaned out recordings? I have restarted a few times with the RC and changing configs, perhaps the recordings got wiped in some restart? i updated at 3:30 MDT

[NickM-27]

If this only applies to recordings done before the update then might be something with the way it's starting at the beginning of the day, considering that you only have 1 day of continuous recording

[FeatherKing]

after watching things for a day, i havent seen this specific thing reproduced. but related, any time that the review clip is gone the UI just spins and i get that 503 on the backend, the UI never recovers and will just spin forever. maybe if it gets a 503 it could change to say that there was an error finding the clip or something

[FeatherKing]

*i have restarted multiple times today as well and the review recordings were always there, so im not sure why for an hour things were broken

[nicoleise]

Looks like awesome progress, and I'm looking forward to v0.14. I think many of us are checking for updates with a cron job, and this update contains a lot of breaking changes, a "config-converter" and drastic UI changes. Which is all fair.

But are you going to "do something" to ensure this update is user-initiated so stuff doesn't just potentially break in the dead of some random night? I can be pretty time consuming and inconvinient to fix, if we can't plan for it. :) Something like checking for allowversion14: True in config, so users can enter the line when ready after release, and have Frigate update when restarted/config applied?

Sorry if it's been asked before, couldn't find anything about it. :)

[noelhibbard]

I use watchtower to update some of my containers but not with Frigate for this reason. It would be nice if we could use a tag like :0.13 and automatically pick up for example v0.13.4, but not v0.14.0. The :latest tag is a little dangerous because it would jump from 0.13 to 0.14 if you did a pull.

[davison]

agreed - my compose file references stable as a tag, presumably that tag will move once 0.14 is GA. I don't know which version stable refers to since tags are not searchable in github packages and there are almost 6500 tagged versions of the package making finding it very difficult. The best solution would be @noelhibbard 's suggestion of additionally tagging the latest major / minor versions with 0.13 and 0.14

[noelhibbard]

I don't know which version stable refers to since tags are not searchable in github packages and there are almost 6500 tagged versions of the package making finding it very difficult.

This is the most ridiculous limitation of GitHub packages. They don't even have an API to let you pull the list of packages so you can build your own search.

[davison]

think this should work.. I tagged the image locally with a v13 tag and then edited the docker compose file to use it instead of stable. If the stable tag is moved to a new image it shouldn't affect my running instance, right?

docker tag 8ef1bb9aad44 ghcr.io/blakeblackshear/frigate:v13

[NickM-27]

Even if you kept using the stable tag it wouldn't affect your running image. Like Blake said, docker does not auto update images. You'd have to pull the new image and apply via CLI. (docker compose up -d)

[percy-punch]

Amazing work by all those who have contributed to the project update! Looking forward to using the new features/updates. Thank you.

[yayitazale]

Hi I'm having some issues to startup the RC1 that I didn't face with beta 4.

Attached logs, ffmpeg doesn't even start:
frigate_logs.txt
go2rtc_logs.txt

Deployed in unraid 6.12.11 with the following config:

My config:

detectors:
  coral:
    type: edgetpu
    device: usb

audio:
  enabled: false
  min_volume: 500
  listen:
    - meow
    - speech

mqtt:
  # Required: host name
  host: 192.168.1.XX
  # Optional: port (default: shown below)
  # port: 1883
  # Optional: topic prefix (default: shown below)
  # WARNING: must be unique if you are running multiple instances
  topic_prefix: frigate
  # Optional: client id (default: shown below)
  # WARNING: must be unique if you are running multiple instances
  client_id: frigate
  # Optional: user
  user: user
  # Optional: password
  # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}.
  #       eg. password: '{FRIGATE_MQTT_PASSWORD}'
  password: pass
  # Optional: interval in seconds for publishing stats (default: shown below)
  stats_interval: 60

# Optional: TLS configuration
tls:
  # Optional: Enable TLS for port 8971 (default: shown below)
  enabled: False

snapshots:
  # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
  # This value can be set via MQTT and will be updated in startup based on retained value
  enabled: true
  # Optional: print a timestamp on the snapshots (default: shown below)
  timestamp: true
  # Optional: draw bounding box on the snapshots (default: shown below)
  bounding_box: true
  # Optional: Camera override for retention settings (default: global values)
  retain:
    # Required: Default retention days (default: shown below)
    default: 1

birdseye:
  # Optional: Enable birdseye view (default: shown below)
  enabled: true
  # Optional: Width of the output resolution (default: shown below)
  width: 1920
  # Optional: Height of the output resolution (default: shown below)
  height: 1080
  # Optional: Encoding quality of the mpeg1 feed (default: shown below)
  # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
  quality: 10
  # Optional: Mode of the view. Available options are: objects, motion, and continuous
  #   objects - cameras are included if they have had a tracked object within the last 30 seconds
  #   motion - cameras are included if motion was detected in the last 30 seconds
  #   continuous - all cameras are included always
  mode: objects

record:
  enabled: true
  retain:
    days: 2
    mode: all
  events:
    retain:
      default: 2
      mode: motion


timestamp_style:
  # Optional: Position of the timestamp (default: shown below)
  #           "tl" (top left), "tr" (top right), "bl" (bottom left), "br" (bottom right)
  position: tl
  # Optional: Format specifier conform to the Python package "datetime" (default: shown below)
  #           Additional Examples:
  #             german: "%d.%m.%Y %H:%M:%S"
  format: '%m/%d/%Y %H:%M:%S'
  # Optional: Color of font
  color:
    # All Required when color is specified (default: shown below)
    red: 255
    green: 255
    blue: 255
  # Optional: Line thickness of font (default: shown below)
  thickness: 2

# Optional: Motion configuration
# NOTE: Can be overridden at the camera level
motion:
  # Optional: The threshold passed to cv2.threshold to determine if a pixel is different enough to be counted as motion. (default: shown below)
  # Increasing this value will make motion detection less sensitive and decreasing it will make motion detection more sensitive.
  # The value should be between 1 and 255.
  threshold: 30
  # Optional: The percentage of the image used to detect lightning or other substantial changes where motion detection
  #           needs to recalibrate. (default: shown below)
  # Increasing this value will make motion detection more likely to consider lightning or ir mode changes as valid motion.
  # Decreasing this value will make motion detection more likely to ignore large amounts of motion such as a person approaching
  # a doorbell camera.
  lightning_threshold: 0.8
  # Optional: Minimum size in pixels in the resized motion image that counts as motion (default: shown below)
  # Increasing this value will prevent smaller areas of motion from being detected. Decreasing will
  # make motion detection more sensitive to smaller moving objects.
  # As a rule of thumb:
  #  - 10 - high sensitivity
  #  - 30 - medium sensitivity
  #  - 50 - low sensitivity
  contour_area: 10
  # Optional: Alpha value passed to cv2.accumulateWeighted when averaging frames to determine the background (default: shown below)
  # Higher values mean the current frame impacts the average a lot, and a new object will be averaged into the background faster.
  # Low values will cause things like moving shadows to be detected as motion for longer.
  # https://www.geeksforgeeks.org/background-subtraction-in-an-image-using-concept-of-running-average/
  frame_alpha: 0.01
  # Optional: Height of the resized motion frame  (default: 50)
  # Higher values will result in more granular motion detection at the expense of higher CPU usage.
  # Lower values result in less CPU, but small changes may not register as motion.
  frame_height: 50
  # Optional: motion mask
  # NOTE: see docs for more detailed info on creating masks
  #mask: 0,900,1080,900,1080,1920,0,1920
  # Optional: improve contrast (default: shown below)
  # Enables dynamic contrast improvement. This should help improve night detections at the cost of making motion detection more sensitive
  # for daytime.
  improve_contrast: true
  # Optional: Delay when updating camera motion through MQTT from ON -> OFF (default: shown below).
  #mqtt_off_delay: 30

objects:
  # Optional: list of objects to track from labelmap.txt (default: shown below)
  track:
    - person
    - cat
  # Optional: filters to reduce false positives for specific object types
  filters:
    person:
      # Optional: minimum width*height of the bounding box for the detected object (default: 0)
      min_area: 3000
      # Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
      #max_area: 10000
      # Optional: minimum score for the object to initiate tracking (default: shown below)
      min_score: 0.60
      # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
      threshold: 0.70
    cat:
      min_area: 3000
      #max_area: 1000
      min_score: 0.60
      threshold: 0.70
    bird:
      min_area: 3000
      #max_area: 1000
      min_score: 0.55
      threshold: 0.65

detect:
  # Optional: width of the frame for the input with the detect role (default: shown below)
  width: 1920
  #width: 640
  # Optional: height of the frame for the input with the detect role (default: shown below)
  height: 1080
  #height: 360
  # Optional: desired fps for your camera for the input with the detect role (default: shown below)
  # NOTE: Recommended value of 5. Ideally, try and reduce your FPS on the camera.
  fps: 5
  # Optional: enables detection for the camera (default: True)
  # This value can be set via MQTT and will be updated in startup based on retained value
  enabled: true
  # Optional: Number of frames without a detection before frigate considers an object to be gone. (default: 5x the frame rate)
  max_disappeared: 25
  # Optional: Configuration for stationary object tracking
  stationary:
    # Optional: Frequency for confirming stationary objects (default: shown below)
    # When set to 0, object detection will not confirm stationary objects until movement is detected.
    # If set to 10, object detection will run to confirm the object still exists on every 10th frame.
    interval: 20
    # Optional: Number of frames without a position change for an object to be considered stationary (default: 10x the frame rate or 10s)
    threshold: 50
    # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
    # This can help with false positives for objects that should only be stationary for a limited amount of time.
    # It can also be used to disable stationary object tracking. For example, you may want to set a value for person, but leave
    # car at the default.
    # WARNING: Setting these values overrides default behavior and disables stationary object tracking.
    #          There are very few situations where you would want it disabled. It is NOT recommended to
    #          copy these values from the example config into your config unless you know they are needed.

ffmpeg:
  hwaccel_args: preset-vaapi
  input_args: preset-rtsp-restream
  output_args:
    record: preset-record-generic-audio-copy

go2rtc:
  rtsp:
    username: user
    password: pass
  streams:
    pasillo:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:pasillo#audio=aac
    oficina:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:oficina#audio=aac
    cocina:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:cocina#audio=aac
    salon:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:salon#audio=aac
    garaje:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:garaje#audio=aac
    terraza:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:terraza#audio=aac
    balcon:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:balcon#audio=aac
    barbacoa:
      - rtsp://user:pass@192.168.1.XX:554/stream1
      - ffmpeg:barbacoa#audio=aac

cameras:
  # Name of your camera
  pasillo:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/pasillo
          roles:
            - record
            - detect

  # Name of your camera
  oficina:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/oficina
          roles:
            - record
            - detect
    zones:
      oficina_zone:
        coordinates: 1920,1080,1920,0,0,0,0,1080
    onvif:
      # Required: host of the camera being connected to.
      host: 192.168.1.134
      # Optional: ONVIF port for device (default: shown below).
      port: 2020
      # Optional: username for login.
      # NOTE: Some devices require admin to access ONVIF.
      user: user
      # Optional: password for login.
      password: pass
      # Optional: PTZ camera object autotracking. Keeps a moving object in
      # the center of the frame by automatically moving the PTZ camera.
      autotracking:
        # Optional: enable/disable object autotracking. (default: shown below)
        enabled: false
        # Optional: calibrate the camera on startup (default: shown below)
        # A calibration will move the PTZ in increments and measure the time it takes to move.
        # The results are used to help estimate the position of tracked objects after a camera move.
        # Frigate will update your config file automatically after a calibration with
        # a "movement_weights" entry for the camera. You should then set calibrate_on_startup to False.
        calibrate_on_startup: false
        # Optional: the mode to use for zooming in/out on objects during autotracking. (default: shown below)
        # Available options are: disabled, absolute, and relative
        #   disabled - don't zoom in/out on autotracked objects, use pan/tilt only
        #   absolute - use absolute zooming (supported by most PTZ capable cameras)
        #   relative - use relative zooming (not supported on all PTZs, but makes concurrent pan/tilt/zoom movements)
        zooming: disabled
        # Optional: A value to change the behavior of zooming on autotracked objects. (default: shown below)
        # A lower value will keep more of the scene in view around a tracked object.
        # A higher value will zoom in more on a tracked object, but Frigate may lose tracking more quickly.
        # The value should be between 0.1 and 0.75
        zoom_factor: 0.3
        # Optional: list of objects to track from labelmap.txt (default: shown below)
        # Optional: list of objects to track from labelmap.txt (default: shown below)
        track:
          - person
          - cat
        # Required: Begin automatically tracking an object when it enters any of the listed zones.
        required_zones:
          - oficina_zone
        # Required: Name of ONVIF preset in camera's firmware to return to when tracking is over. (default: shown below)
        return_preset: preset1
        # Optional: Seconds to delay before returning to preset. (default: shown below)
        timeout: 10

  # Name of your camera
  cocina:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/cocina
          roles:
            - record
            - detect

  # Name of your camera
  salon:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/salon
          roles:
            - record
            - detect
    zones:
      salon_zone:
        coordinates: 1920,1080,1920,0,0,0,0,1080
    onvif:
      # Required: host of the camera being connected to.
      host: 192.168.1.247
      # Optional: ONVIF port for device (default: shown below).
      port: 2020
      # Optional: username for login.
      # NOTE: Some devices require admin to access ONVIF.
      user: user
      # Optional: password for login.
      password: pass
      # Optional: PTZ camera object autotracking. Keeps a moving object in
      # the center of the frame by automatically moving the PTZ camera.
      autotracking:
        # Optional: enable/disable object autotracking. (default: shown below)
        enabled: false
        # Optional: calibrate the camera on startup (default: shown below)
        # A calibration will move the PTZ in increments and measure the time it takes to move.
        # The results are used to help estimate the position of tracked objects after a camera move.
        # Frigate will update your config file automatically after a calibration with
        # a "movement_weights" entry for the camera. You should then set calibrate_on_startup to False.
        calibrate_on_startup: false
        # Optional: the mode to use for zooming in/out on objects during autotracking. (default: shown below)
        # Available options are: disabled, absolute, and relative
        #   disabled - don't zoom in/out on autotracked objects, use pan/tilt only
        #   absolute - use absolute zooming (supported by most PTZ capable cameras)
        #   relative - use relative zooming (not supported on all PTZs, but makes concurrent pan/tilt/zoom movements)
        zooming: disabled
        # Optional: A value to change the behavior of zooming on autotracked objects. (default: shown below)
        # A lower value will keep more of the scene in view around a tracked object.
        # A higher value will zoom in more on a tracked object, but Frigate may lose tracking more quickly.
        # The value should be between 0.1 and 0.75
        zoom_factor: 0.3
        # Optional: list of objects to track from labelmap.txt (default: shown below)
        track:
          - person
          - cat
        # Required: Begin automatically tracking an object when it enters any of the listed zones.
        required_zones:
          - salon_zone
        # Required: Name of ONVIF preset in camera's firmware to return to when tracking is over. (default: shown below)
        return_preset: preset2
        # Optional: Seconds to delay before returning to preset. (default: shown below)
        timeout: 10

  # Name of your camera
  garaje:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/garaje
          roles:
            - record
            - detect
    objects:
      track:
        - person

  # Name of your camera
  terraza:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/terraza
          roles:
            - record
            - detect
    objects:
      track:
        - bird
        - person
    motion:
      mask:
        - 0,360,0,286,115,237,271,360
    mqtt:
      enabled: true
      bounding_box: false #this will get rid of the box around the bird. We already know it is a bird. Sheesh.
      timestamp: false #this will get rid of the time stamp in the image. 
      quality: 95 #default quality is 70, which will get you lots of compression artifacts

  # Name of your camera
  balcon:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/balcon
          roles:
            - record
            - detect
    objects:
      track:
        - bird
        - person
      filters:
        bird:
          mask:
            - 1920,1080,1920,435,1335,409,1066,626,1029,1080
    mqtt:
      enabled: true
      bounding_box: false #this will get rid of the box around the bird. We already know it is a bird. Sheesh.
      timestamp: false #this will get rid of the time stamp in the image. 
      quality: 95 #default quality is 70, which will get you lots of compression artifacts
    motion:
      mask:
        #- 564,0,1012,0,990,286,805,257,593,286
        - 1042,1080,1658,1080,1711,736,1749,441,1261,371,1085,552,1040,706

# Name of your camera
  barbacoa:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/barbacoa
          roles:
            - record
            - detect
    objects:
      track:
        - bird
        - person
      filters:
        bird:
          mask:
            - 883,899,630,1080,486,1080,98,1080,22,789,0,446,111,259,262,146,506,244,1002,102,1118,0,1298,0,1322,298,766,609
    mqtt:
      enabled: true
      bounding_box: false #this will get rid of the box around the bird. We already know it is a bird. Sheesh.
      timestamp: false #this will get rid of the time stamp in the image. 
      quality: 95 #default quality is 70, which will get you lots of compression artifacts
    motion:
      mask:
        - 1042,1080,0,1080,0,0,477,0,266,150,350,250,458,205,552,262,571,372,966,296,940,62,1065,0,1212,0,1324,30,1280,312,1494,407,1505,642

# Optional: Telemetry configuration
telemetry:
  # Optional: Enabled network interfaces for bandwidth stats monitoring (default: shown below)
  network_interfaces: []
  # Optional: Configure system stats
  stats:
    # Enable AMD GPU stats (default: shown below)
    amd_gpu_stats: false
    # Enable Intel GPU stats (default: shown below)
    intel_gpu_stats: true
    # Enable network bandwidth stats monitoring for camera ffmpeg processes, go2rtc, and object detectors. (default: shown below)
    network_bandwidth: false
  # Optional: Enable the latest version outbound check (default: shown below)
  # NOTE: If you use the HomeAssistant integration, disabling this will prevent it from reporting new versions
  version_check: true
version: 0.14

[hawkeye217]

It looks like your vaapi hardware acceleration driver isn't loading.

libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

There were no changes from beta4 to rc1 in this area. Did you make any changes to your docker-compose file or with your hardware?

[hawkeye217]

You should try the i965 vaapi driver if iHD isn't working.

[yayitazale]

It looks like your vaapi hardware acceleration driver isn't loading.

libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

There were no changes from beta4 to rc1 in this area. Did you make any changes to your docker-compose file or with your hardware?

Rebooted the host and now it is working, something was stuck with vaapi driver in the host...

[blaess]

I don't know if my question was already asked before.
On the review tab, Frigate 14 shows thumbnails of the object which generated an alert or detection.
But on the frigate+ tab, we see the full camera view. I would be helpful to have the same thumbnails from the review tab also in the frigate+ tab to determin if it is a false negative.

[hawkeye217]

Hmm, I don't seem to be able to find where to do that. Except the debug viewport? Is it to show on the recording what has triggered? (Like the idea, often I'm looking at it wondering why was it triggered :) )

Do this in your frigate config file with:

snapshots:
  bounding_box: True

[darmach]

I'm afraid I'm utterly lost @hawkeye217 - added it to the config and restarted, but I don't see any bounding box on the recording seen in Frigate/review. Where should I look for it?

EDIT: Got it, had snapshots completely disabled before (default)

[hawkeye217]

To be clear, with that setting, bounding boxes will only be shown for events in the UI in the Frigate+ view. The Review pane does not show bounding boxes. See the FAQ, "How can I view snapshots with bounding boxes?" to understand why.

[darmach]

Ah, one more reason to go for Frigate+ then! Thanks!
I can see snapshots in Home Assistant - the Frigate integration (awesome) seem to send me a snapshot when it happens, also nicely showing percentage of matching :) Can we see percentage matching in 0.14 somewhere like on 0.13 event list?

The snapshot time in HA is off for some reason - while in Frigate it's fine, in HA is fine, on the hosts it's fine, and on the snapshot I seem to get GMT time :)

Really sorry for a lot of questions, and thanks for helping a newbie!

[hawkeye217]

Happy to help!

There's already a feature request here for a screen to debug review items. It will be coming in a future version of Frigate. Feel free to give another thumbs up there.

[darmach]

Hi, I've been tinkering with Frigate for about a week (love it, coming from Zoneminder) and realized there is a new version coming. Deployed 0.14 rc1 on a side and I noticed few things, if you guys are open to a newbie review :)

1. I managed to create a camera group, I can't create second one (created in web ui) - error received is: Failed to save config changes: Error updating config, my config attached at the end of this post.

2. New dashboard "Cameras": while it is nice having detections on top, in the same time I feel like we lost functionality - in the previous version one could toggle detecting/recording from that page, and jump straight to the events/recordings of particular cam. The dashboard overall seem to work better - comparing them side-by-side (I automated deployment, and set up two VMs with different versions) - the new dashboard shows motion in real time, marking camera with movement with red border, when old one was not updating.

3. I'm aware that it's arguable - but I'd say that rounding radius of the panels (like camera view) is too aggressive, by a half ,)
   It would look nicer, more streamlined, if it would be the same as the buttons: (pic to compare - button overlayed on camera feed):
   

4. On the single camera view:

• it was useful to have the ability to switch between jsmpeg and mse. But maybe it's just me - tinkering with it, and not a normal user point of view. When mse is superior why even switch to jsmpeg :)
• it was convenient to be able to directly switch from the camera view to debugging - lost a bit of functionality while simplifying the interface (I'm aware that you can go trough gear button > settings on the popup menu > Debug tub - it's just way longer)

It may just be me, but recently I often feel that with simplification of the interface in varius apps we're loosing functionality, or it's getting buried more and more in the menus. Been guilty of it myself :)

5. Ha! Love the themes :)

6. I added Birdseye as one of the camera groups - as I like Birdseye a lot from 0.13 :) In 0.13 I could make it bigger without having to click on it / open in fullscreen. In 0.14 it's tiny - unless clicked to expand. That, however, requires an additional click - and moreover - it hides the event view on the top (new thing that I fancy :D)

7. Last thing - not related to the new version, so I might get scolded here - I deployed Frigate on a Proxmox VM running on baremetal Zen3 with integrated graphics (Ryzen 5600G - Cezanne), passing-trough Coral and AMD iGPU. I can't really see any difference in CPU load whether I have GPU hardware acceleration enabled or not. Should the difference be noticeable? Running 4 cams, 1080p, 25fps detection (aware that's it's too high, by performance-wise it works flawlessly). Should I notice higher CPU usage when disabling hwaccel_args: preset-vaapi ? Either way VM seem to use about 50% of 4 cores

[hawkeye217]

As far as hwaccel goes, running in Proxmox adds layers of complexity. It's not one of the official recommended installation methods, but many users have had success. Take a look at the docs and search the discussions.

Reducing your detect fps will have a significant impact on performance. There's no advantage for detect fps higher than 10 in extreme cases. The recommendation for 95% of users is 5fps.

[darmach]

Oh, don't get me wrong @hawkeye217 I'm not complaining! :)
Pretty happy with the performance, running those 25fps mostly because "I paid for the whole CPU I'm gonna use the whole CPU!" ;)

I just don't have experience with using GPU for hardware accelerated decoding (except for all the cases when it just works and user doesn't even think about the benefits of modern technology) and I just suspected I should notice a difference with and without it :)

[hawkeye217]

Hardware acceleration is highly recommended. Setting frigate to use 25fps for detection doesn't actually improve anything (and in some cases may actually reduce the efficiency of Frigate's pipeline), but if that's not ideal for you, think of it as keeping your CPU available for other things :)

[NickM-27]

Also worth mentioning that you can edit your birdseye layout and make it bigger

[darmach]

@hawkeye217 I should have read faq sooner - the camera groups layout can be resized and customized in the web gui! Great feature.
@NickM-27 O-M-G ^

...ashamed to admit, I did not notice these icons in the bottom right corner at all!

[FeatherKing]

running rc-2 and seeing a review behavior that i didnt see in rc-1. When reviewing a detected person tonight, it failed to load the video (spinning loading circle), that i had seen before when the video didnt exist underneath. This particular camera keeps recordings for a day and this incident was only an hour ago. However the new behavior is that any other clip i try to review, it is taking me back to the one that wouldnt load

frigate_rc2_bug.mp4

[NickM-27]

There were no changes to any of the recording pages or backend, seems like a coincidence. Probably best to create a fresh support discussion

[darmach]

@FeatherKing Have you seen this in the logs?

2024-08-07 06:31:04
frigate.api.media
No recordings found for cam2 during the requested time range
error
2024-08-07 06:31:06
frigate.api.media
No recordings found for cam2 during the requested time range
error
2024-08-07 06:31:09
frigate.api.media
No recordings found for cam2 during the requested time range
error
2024-08-07 06:31:10
frigate.api.media
No recordings found for cam2 during the requested time range

I get this trying to review the detections from ~15 minutes ago. Earlier are fine. Storage wise we're also fine (new deployment yesterday)

[darmach]

Videos are there - I clicked on the one from 07:04:

root@frigate:/var/lib/frigate/storage/recordings/2024-08-07# tree
.
├── 05
│   └── cam2
│       ├── 04.16.mp4
│       ├── 04.26.mp4
│       ├── 04.36.mp4
│       ├── 04.44.mp4
│       └── 04.55.mp4
└── 06
    ├── cam2
    │   └── 54.58.mp4
    └── cam3
        ├── 40.57.mp4
        ├── 41.08.mp4
        ├── 41.18.mp4
        ├── 41.26.mp4
        ├── 41.36.mp4
        ├── 41.46.mp4
        ├── 41.56.mp4
        └── 42.06.mp4

6 directories, 14 files
root@frigate:/var/lib/frigate/storage/recordings/2024-08-07# ls -l 05/cam2/
total 20760
-rw-r--r-- 1 root root 4542974 Aug  7 07:04 04.16.mp4
-rw-r--r-- 1 root root 4380520 Aug  7 07:04 04.26.mp4
-rw-r--r-- 1 root root 3439782 Aug  7 07:04 04.36.mp4
-rw-r--r-- 1 root root 4359384 Aug  7 07:04 04.44.mp4
-rw-r--r-- 1 root root 4525290 Aug  7 07:05 04.55.mp4
root@frigate:/var/lib/frigate/storage/recordings/2024-08-07# ls -l 06/cam2/
total 4380
-rw-r--r-- 1 root root 4484220 Aug  7 08:55 54.58.mp4

[darmach]

The video from 07:04 doesn't open in review panel, logs "frigate.api.media
No recordings found for cam2 during the requested time range", however if I click on export I can export it and view the export just fine.

Should I open a separate discussion or issue about it?
I will redeploy the frigate along with the whole VM and config after I get back from work, and try to get it replicated.

[hawkeye217]

Yes, a separate support discussion would be good.

[consolecwby]

Just want to chime in that the new update looks great. Blake et al. you have all done well with this and i thank you for helping make my home more secure. I did take me a while to get things working i didnt have my GPU setup correctly i guess but once i set ffmpeg:hwaccel_arg: auto things started working

[DJOma]

Hey, here are some thoughts/questions I had.

1. Awesome update! This is a huge step forward.
2. The contrast in some of the dark themes is to low. I know, I can use a theme with better contrast or even the high contrast one. But in the default dark theme for example some text is allmost unreadable. And in the "Nord" theme, the toggle switches look allmost grayed out. There is no vissible colour contrast between on and off.
3. When in the settings (motion tuner for example, which is awesome), I can switch through my cameras. But why is this a list of toggle switches for the cameras? This is not intuitive. These toggle switches would indicate, that one can activate/deactivate one or more cams. But it is just a selector for which camera to display.
4. I don't fully get the frigate+ section. Maybe I just havent found a good description of it, yet. What does it do? I know, I can view snapshots there. I know, I can accept or decline detections there. But I did expect, that the snapshots I rate there would somehow appear in my frigate+ page. I tried troubleshooting the API connection for a while, until I understood, that my reviewed detections just won't show up there. Would this be possible? What happens to the detections I accept or decline?

[hawkeye217]

Are you using Brave browser?

[noelhibbard]

Are you using Brave browser?

Unrelated to this issue but I've had a lot of issues with Brave browser randomly refusing to connect websockets and once it's in this state, only a restart of the browser fixes it. Even with all the ad blocked/shields disabled. This seems to be a known issue with Brave.

[hawkeye217]

Unrelated to this issue but I've had a lot of issues with Brave browser randomly refusing to connect websockets and once it's in this state, only a restart of the browser fixes it. Even with all the ad blocked/shields disabled. This seems to be a known issue with Brave.

Right. There's also known issues when using Frigate's new mask/zone editor with Brave. We definitely recommend Chrome, Firefox, or Safari for the best experience with Frigate 0.14.

[noelhibbard]

Unrelated to this issue but I've had a lot of issues with Brave browser randomly refusing to connect websockets and once it's in this state, only a restart of the browser fixes it. Even with all the ad blocked/shields disabled. This seems to be a known issue with Brave.

Right. There's also known issues when using Frigate's new mask/zone editor with Brave. We definitely recommend Chrome, Firefox, or Safari for the best experience with Frigate 0.14.

Oh yeah, I've noticed that issue too but disabling shields in Brave fixes that. The websocket issue can't be resolved and it impacts any website that uses websockets. Once it gets into this state where websockets will not connect, all websites that use websockets will stop working correctly. go2RTC is highly reliant on websockets so it really struggles on Brave. This bug has been reported for 3 years and they (Brave) seem completely uninterested in fixing it. I hate Chrome on iOS because Google refuses to move all the controls to the bottom so one handed operation is frustrating. Brave on iOS is really nice and it has a properly functioning sync. That is the main reason I prefer Brave. If I could reliably sync Chrome with Safari, I'd go back to Chrome on the desktop and Safari on my phone.

Anyways, off topic, sorry.

[DJOma]

Are you using Brave browser?

Nope just simple silly Chrome.
I am running frigate on proxmox in a container. I know, that is not the official recommended way, but I can't see, how this would be the cause.

[SpangleLabs]

It seems like a shame that starred events won't exist in future, but sounds like the new exports functionality is much improved! I couldn't see anything in the new docs about the new export functionality though, might be something that should be added to them?

I see an example of exports in the user video you've linked here:
https://youtu.be/iJa3dNEO5qQ?t=945
Which is exporting videos of cat-foxes, which, funnily enough, is exactly the saved events I want to keep too! Except mine are cow-foxes

<3

Would it be too much to ask that starred events are automatically exported in the upgrade to 0.14, or something? It does seem a shame, and a bit weird, to just suddenly lose them all. That could be quite a disaster for someone if they didn't read the release notes. It's a sudden change from starred events being kept forever, to potentially being deleted.
I can imagine some people might be keeping something more important than cat-foxes and cow-foxes in their starred events, and backing up the database and config file won't be enough to restore them if they upgrade without manually exporting them.

It seems like manually exporting them is a pretty tedious process too, going through each starred event, getting the exact start and end time and camera name, then entering that on the export page. It's definitely a task that seems very tedious to do manually, but pretty easy to automate, plus if the automation is actually part of the upgrade, it can set some semi-decent export name at the same time? Rather than, again, having to manually export, then upgrade, then manually going through each export (both the basic exports that already existed from 0.13 exports, and the starred exports you've just made), and rename the exports from default filenames to Starred event (Cow) 2024-06-20 or whatever

[SpangleLabs]

that is incorrect, nothing happens to the data when you upgrade, all of the events are still in the databse and will remain there for eternity unless you unstar the event

Ohhh, sorry, I misunderstood the release notes I suppose. Events will still exist in the database, and will still be accessible via the API, and presumably recording preservation will still be calculated with consideration of events still existing, but no new events will get created, as that's just not how 0.14 works. Is that right?
Instead 0.14 has review items, (which can be alerts or detections), and has motion review independent of object detection (which I am looking forward to a lot!)

just for clarity, they would not be removed, the stared events are not being deleted

Okay, cool. I don't need to fret about getting that script done before upgrading then!

For full clarity and double-checking, given my record config is currently this:

record:
  enabled: true
  retain:
    days: 10
    mode: all
  events:
    retain:
      default: 30
      mode: active_objects

And I have starred events much older than that, so, in 0.13 the recording segments are basically being kept for the times around the starred events indefinitely, and around all new events for 30 days, and everywhere else for 10 days.
After upgrade to 0.14, there won't be new events, but the recording segments around old events and starred events will continue to be stored and cleaned up according to the same record logic as now, meaning that 30 days after upgrading to 0.14, the recording segments will only be the last 10 days, plus any starred events? As the non-starred events will have been removed from the DB and API, and recording segments around non-starred events will have been cleaned up.

Though, I see the beta docs recording page still talks about setting record: events: , and talks about events throughout the page, without mentioning how any of it applies to review items, or motion review.
At a guess, review items will be kept according to the record.events config, and motion review will not be kept longer than the standard record.retain, right? (That might be worth updating and clarifying in the documentation there)

Again, many thanks for all this! I am really excited about upgrading to frigate 0.14, y'all have done some really incredible work, thanks so much

[hawkeye217]

We didn’t want to create too many breaking changes to the config file for this release, which is why events are still referenced in the recordings section. The new Review docs discusses the differences between events and review items: https://deploy-preview-11419--frigate-docs.netlify.app/configuration/review/

[hawkeye217]

Your config looks good, by the way. Nothing has changed with retention in 0.14, so your understanding is correct.

[SpangleLabs]

Yes, I saw the review page explaining the differences, but wasn't sure the depth of that. It phrases it as "events are no more, now we have review items", but nothing clarifies that when the recording config talks about events, that will apply to review items now.
The review page lists a number of new config entries for review items, but doesn't mention that.

I think it could be clarified in the recordings page:
https://deploy-preview-11419--frigate-docs.netlify.app/configuration/record#most-conservative-ensure-all-video-is-saved
even if it just changing "events" to "review items" in the text (not the config, obviously)
In fact, I'll make a pull request! Sorry, should have just done that earlier.
#12805
Hopefully that better illustrates it, and improves the docs for 0.14

[hawkeye217]

Technically, events are still the underlying building blocks of each review item. The UI just obscures them and combines any number of events into review items.

Not quite sure we want to make that drastic of a change to the docs at this point, but the other maintainers can certainly chime in and give their thoughts.

[bagobones]

I am currently away from home and trying to review alerts / events from my iPhone.

Sometimes tapping on an alert presents a loading screen indicator then just a still image.

When going through the timeline I see events scrub to them but the timeline does not advance.

Other times it just works. For the same alert or timeline.

Seems to clear up if I reboot frigate but nothing to nail this down other than to report it had happened a few times .

Looking at logs I see the occasional error that no clip for x camera was found for x time.

Frigates storage is on a local SSD so IO performance should not be an issue.

[makerwolf1]

I'm on HA OS and run the Frigate Beta Addon, I only have RC1 available but not RC2, is this intended behaviour?