Rebuilding the Frigate UI for 0.14

[blakeblackshear]

TLDR: We have completely overhauled the UI for Frigate to focus on specific common user goals. It’s a big change and we hope you love it. This is just where we started, and the new UI isn’t entirely at feature parity with the current release yet.

Guided Demo of new UI

We plan to release the first beta soon.

Background

Frigate started as a stateless object detection pipeline for live video fees with information relayed over MQTT to be used in Home Assistant. Initially, I had no intention of building a UI for it. HomeAssistant was the UI. After a few years of releases in January 2021, a community contribution with a basic web UI was made as a part of version 0.8.0. Since then, the UI has always been treated as a basic interface to expose some of the backend information that Frigate was using to detect and track objects. As new features like clips and recordings were added the UI was updated to provide an interface to view them.

A new approach

As Frigate has become more mature, it has evolved from a real time object detection pipeline into an NVR. While it still lacks some of the customization and features from NVR solutions that have existed for longer, many users are migrating from those platforms and using Frigate as their primary NVR solution. However, Frigate’s UI was never designed around specific user goals, nor was any real thought put into the efficiency of accomplishing common tasks.

Frigate+ was created in part to help fund the future development of Frigate. While still in the early phases, the initial revenue from Frigate+ subscriptions created an opportunity to hire outside resources for revamping Frigate’s UI. After looking at various options, I decided to hire Jim Designs.

The Goals

I wanted to design the new UI around specific user goals with the intent to have a UI that allows accomplishing those goals as quickly and efficiently as possible. The following goals are where we started. I expect we will continue to find better ways of accomplishing these goals in the future as well as incorporate additional goals.

What is happening right now and/or what just happened?

The first use case centers around the need to quickly see what is happening or what just happened. Imagine you hear a sound outside, your dog barks, or the doorbell rings and you want to quickly be able to see your cameras.

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 live stream. In addition, camera groups have been added so you can quickly switch between indoor and outdoor cameras.

Selecting a camera takes you to a new live view where the scroll wheel can be used to zoom in and out.

What happened last night (or the past 24 hours)?

A common use case for security cameras is reviewing last night’s footage for any concerning activity. The first step of that process is checking to see what Frigate detected. In the current UI, this is accomplished by scrolling through your events. Because events are simply low level tracked objects, their time ranges may overlap or still be in progress. This makes it difficult to review a timeline of video without jumping around or watching the same section of video multiple times. If a person walks by with their dog and a car drives by at the same time, you will end up with 3 separate events all with overlapping time ranges. It is difficult to reason about what periods of time you have and haven’t reviewed.

In order to switch to a more timeline oriented review process, we implemented a new area of the app for reviewing video footage. When reviewing, Frigate intelligently identifies parts of your timeline for review by leveraging the underlying data about motion and tracked objects. These time periods are mutually exclusive, so once you have reviewed a portion of the timeline for a camera, it is marked as reviewed.

The other primary focus was on efficiency. We wanted users to be able to review these segments as efficiently as possible. Rather than scrolling through a timeline and trying to align a single point with an indication of activity, we implemented a scrollable grid of thumbnails alongside a timeline. Hovering (or swiping on mobile) over the thumbnails will start a preview playback for the segment inline. You can also grab the progress bar to scrub through the segment.

After watching a segment, it is marked as reviewed.

Lastly, not all segments are created equal. Video of people who enter your property are a different priority than those walking by on the sidewalk. By default, all person and car objects are considered alerts. You can refine what ends up in the alert tab by configuring required zones for your events.

Was anything missed last night?

In the current release, 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 review, 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 scrub in motion only mode.

Other Notable Improvements

• Many improvements have been made to improve the usability of the mobile UI
• Live view now displays full-resolution camera streams
• Cameras with non standard aspect ratios like panoramic and portrait fit into the UI seamlessly
• Zone / mask editor has been improved to be easier to use and makes more options fully configurable in the UI
• Tune motion detection in real-time directly in the UI

[OnFreund]

This is awesome!
The designs mention that the review screen is filtered by day, which makes the "last night" uses cases a bit tricky because they technically span 2 calendar days. Is it filtered by the current date or the last 24 hours?

[NickM-27]

by default it is the last 24 hours, or a specific day can be selected on the calendar

[OnFreund]

Perfect

[blakeblackshear]

24 hours by default, then the specific day when choosing a date which would include the morning and evening of that day. It's always easy to look at last night each morning.

[nayzm]

Amazing work! Looking forward to this. 👏🏼

[nwish]

Oh man, I can't wait to jump on that beta! I'm excited about the alerts function and scrubbing!! Outstanding work guys!

Edit: When you say you plan to release the beta soon... you mean like in a few hours, right? lol

[nwish]

It is somehow possible to configure one object to alert in multiple zones, while another object alerts in one zone, and only detects in another?

[NickM-27]

yes, just set which objects each zone applies to. You can configure this in the UI by editing your zone and setting which objects apply to that zone

[wjbeckett]

Yep. I currently do this.

On my driveway camera, I have alerts set to person and car, but on my front yard camera, only person alerts where other labels are marked for detection.

The alerts and detections configuration are per camera.

[nwish]

I think I phrased my question improperly. In the UI, in individual zone settings, it seems like I can only enable or disable objects for the zone, but not for alerts and detections specifically, but I'd want to accomplish the following:

Person enters ZONE 1 and then crosses into ZONE 2 - alert for both
Car enters ZONE 1 and then crosses into ZONE 2 - detection for ZONE 1, alert for ZONE 2

So I guess I'm looking for a required_zones setting on a per object basis.

[NickM-27]

you would need 3 zones to accomplish this

zone 2, required for alerts and has person and car object
zone 1_person, required for alerts and has person object
zone_1_car, required for detections and has car object

[TorgeSchmidt]

Awesome stuff, really looking forward to it!
But what do you mean by

initial revenue from Frigate+ subscriptions

?
I setup an account, uploaded labeled images, but the option to change subscription from free to 50$/y is unavailable, marked „coming soon“…
I thought Frigate+ is not ready yet, is there a hidden button or something? 😜

[NickM-27]

Frigate+ has been available for about 8 months now, you just need to email blake@frigate.video to request access

[binarybucks]

looks very promising. Will there be a version optimized for mobile devices?

[NickM-27]

the UI has been built with both desktop and mobile views in mind

[binarybucks]

I just tried the dev build and the new interface really is a vast improvement on both the desktop and mobile.
I really appreciate that some of the Frigate+ earnings are invested into this.

The switching from static to live images on motion is a very neat trick and superbly implemented. The loading times are also so fast that they might replace my existing professional NVR altogether and the new Motion Tuner and Frigate+ Score Range filter are two really helpful details.

Overtall, very well done and a big improvement in the right direction.

The only issue I found so far is that the interface elements on the mobile version are quite small and hard to hit at the moment .

[dz4news]

Looks very impressive and looking forward to the beta. It looks like your revenue from Frigate+ was well spent and I will gladly support you with this effort... I am one of those that completely dumped my proprietary NVR system and adopted Frigate.
Quick question... as you move forward with a standalone UI and as it matures, will the integration with HomeAssistant continue?

[NickM-27]

I don't speak for the project but personally I can see the integration sensors and services progressing but I think the media browser gets replaced with a link to the frigate ui in the sidebar

[hawkeye217]

Like @NickM-27, I am only a contributor to the project so I can't speak to future goals and direction. But the new UI does not provide automation features, notifications, or sensors. Home Assistant and Frigate work very well together, and there has been no discussion to change that whatsoever.

[dz4news]

Completely understandable.. I personally find myself using the Frigate Proxy more often to review events, etc and just use HA for the alerts and quick viewing of the cameras.

[OnFreund]

FWIW my vote would be against dropping the media browser - it's really useful and is an easy way to integrate with media players in HA (e.g. cast device)

[nomonkeynodeal]

When I saw the title I thought "oh they are finally making it possible for non-experts to configure Frigate. Maybe I will never have to type 'nano config.yml' again because I entered one wrong character and now Frigate won't start".

[NickM-27]

frigate has supported a config editor for over a year now, this config editor checks your file validity before restarting among other benefits like lint checking and auto complete. so there really is no reason to be using nano

[NickM-27]

also, the new UI does make more things configurable directly from the UI

[hawkeye217]

Motion/object masks, motion parameters, and new camera groups can be configured from the new UI without editing the config file, but configuring every parameter from frigate exclusively from the UI is a massive development undertaking. I suspect frigate will get there eventually.

[nomonkeynodeal]

And yet somehow a user with a significantly developed homelab and over a year of Frigate experience still makes configuration errors and has trouble understanding how Frigate works. What do you attribute that to exactly? Low IQ? Moral failing?

[nwish]

What do you attribute that to exactly? Low IQ? Moral failing?

Maybe just frustration getting the best of you. We've all been there. Always be ready to poke at the logs when things go south. It also took me a while to get used to Frigate's configuration.

[nomonkeynodeal]

What do you attribute that to exactly? Low IQ? Moral failing?

Maybe just frustration getting the best of you. We've all been there. Always be ready to poke at the logs when things go south. It also took me a while to get used to Frigate's configuration.

No, the answer is obviously that Frigate is difficult to configure properly and not well documented. Let me be clear that this is NOT a complaint. I'm just stating my opinion that a camera viewing GUI is low-priority compared to a configuration UI. That's it.

[shinyzard123]

I have to disagree, the inability to review motion footage is a big pain point for us and I have found Frigate's documentation to be better than many other projects that I have used. It does have a learning curve but after some time spent it is pretty straightforward in my opinion

[nwish]

A configuration UI would be nice, but obviously that wasn't part of the original set of goals, and has been set back in favor of high quality and accurate object detection. Also, did you know that you can copy/paste the example "full configuration" from the docs into your own file and start removing things that you aren't changing? If you're still having trouble, maybe start over by doing that.

[adamburgoyne]

It would be nice to have an "Add camera" wizard and camera config editor in the UI to be fair but now my cameras are setup I rarely need to touch the config whereas I do quite often review footage so I'm pretty excited for this. I'd say for most people the ability to view footage is likely to be more important.

[NickM-27]

yes, that will come in some future version

[shinyzard123]

This is awesome to see, we might fully drop Blue Iris when this launches if it solves all of our needs

[nomonkeynodeal]

A configuration UI would be nice, but obviously that wasn't part of the original set of goals, and has been set back in favor of high quality and accurate object detection. Also, did you know that you can copy/paste the example "full configuration" from the docs into your own file and start removing things that you aren't changing? If you're still having trouble, maybe start over by doing that.

I did that nearly two years ago.

[xconverge]

I have been checking in on progress/using a dev build every few weeks the past few weeks and I was always wondering/waiting for the Debug view for the camera

I just started using the latest dev build and wow, you guys have done a great job! I was blind and missing the Settings page and it is really great!

Nice work, especially @hawkeye217 and @NickM-27, I know you guys have been busy!

[nwish]

I just pulled the dev build today as well.. any pointers from your end so far? :)

[xconverge]

Nope, seems to be running pretty well! If I experience anything strange I would politely open an issue and follow best reporting practices to not be a headache for the active developers who are managing a pretty large userbase! Running a dev build I would take on additional responsibility if you can to look into problems or just revert back to stable if something is not to your liking 🤷

[nwish]

That’s my plan. I’ve got a list 😊

[NickM-27]

We do want feedback, will help to either fix things or give ideas for things that need to be emphasized in the beta release notes

[towerhand]

Great job. That looks amazing so far.

Are there any configuration changes that need to be made before switching from v0.13 to 0.14 dev?

[towerhand]

It looks like the config migration didn't like something in my config file because frigate won't start after changing to v14.

frigate  | 2024-04-28 23:36:56.823125673  *************************************************************
frigate  | 2024-04-28 23:36:56.823128853  *************************************************************
frigate  | 2024-04-28 23:36:56.823132973  ***    Your config file is not valid!                     ***
frigate  | 2024-04-28 23:36:56.823134845  ***    Please check the docs at                           ***
frigate  | 2024-04-28 23:36:56.823136042  ***    https://docs.frigate.video/configuration/index     ***
frigate  | 2024-04-28 23:36:56.823158596  *************************************************************
frigate  | 2024-04-28 23:36:56.823159823  *************************************************************
frigate  | 2024-04-28 23:36:56.823161296  ***    Config Validation Errors                           ***
frigate  | 2024-04-28 23:36:56.823162428  *************************************************************
frigate  | 2024-04-28 23:36:56.823163394  invalid literal for int() with base 10: '0.121'
frigate  | 2024-04-28 23:36:56.823889708  Traceback (most recent call last):
frigate  | 2024-04-28 23:36:56.823891717    File "/opt/frigate/frigate/app.py", line 603, in start
frigate  | 2024-04-28 23:36:56.823892859      self.init_config()
frigate  | 2024-04-28 23:36:56.823894053    File "/opt/frigate/frigate/app.py", line 136, in init_config
frigate  | 2024-04-28 23:36:56.823895194      self.config = user_config.runtime_config(self.plus_api)
frigate  | 2024-04-28 23:36:56.823896361    File "/opt/frigate/frigate/config.py", line 1456, in runtime_config
frigate  | 2024-04-28 23:36:56.823897421      camera_config.objects.filters[object] = RuntimeFilterConfig(
frigate  | 2024-04-28 23:36:56.823898522    File "/opt/frigate/frigate/config.py", line 484, in __init__
frigate  | 2024-04-28 23:36:56.823899563      mask = get_relative_coordinates(config.get("mask"), frame_shape)
frigate  | 2024-04-28 23:36:56.823900716    File "/opt/frigate/frigate/util/config.py", line 160, in get_relative_coordinates
frigate  | 2024-04-28 23:36:56.823901616      [
frigate  | 2024-04-28 23:36:56.823902717    File "/opt/frigate/frigate/util/config.py", line 161, in <listcomp>
frigate  | 2024-04-28 23:36:56.823903869      f"{round(int(points[i]) / frame_shape[1], 3)},{round(int(points[i + 1]) / frame_shape[0], 3)}"
frigate  | 2024-04-28 23:36:56.823906012  ValueError: invalid literal for int() with base 10: '0.121'
frigate  | 2024-04-28 23:36:56.823906908  
frigate  | 2024-04-28 23:36:56.823907991  *************************************************************
frigate  | 2024-04-28 23:36:56.823927703  ***    End Config Validation Errors                       ***
frigate  | 2024-04-28 23:36:56.823928905  *************************************************************

[NickM-27]

Do you have a decimal as one of your points? Otherwise I may have just missed something when working on the conversion to relative coordinates

[towerhand]

I don't see anything, but I'll send you my config via a discord DM just in case.

[NickM-27]

Perfect

[niqu1982]

This same problem. If anybody resolve this problem please describe how. My ovinf config https://pastebin.com/dmSkGepa

2024-05-11 19:02:07.549507734 invalid literal for int() with base 10: '0.0'
2024-05-11 19:02:07.549912934 Traceback (most recent call last):
2024-05-11 19:02:07.549914580 File "/opt/frigate/frigate/app.py", line 604, in start
2024-05-11 19:02:07.549915494 self.init_config()
2024-05-11 19:02:07.549916408 File "/opt/frigate/frigate/app.py", line 137, in init_config
2024-05-11 19:02:07.549917240 self.config = user_config.runtime_config(self.plus_api)
2024-05-11 19:02:07.549918129 File "/opt/frigate/frigate/config.py", line 1466, in runtime_config
2024-05-11 19:02:07.549918974 camera_config.objects.filters[object] = RuntimeFilterConfig(
2024-05-11 19:02:07.549919826 File "/opt/frigate/frigate/config.py", line 484, in init
2024-05-11 19:02:07.549920648 mask = get_relative_coordinates(config.get("mask"), frame_shape)
2024-05-11 19:02:07.549921544 File "/opt/frigate/frigate/util/config.py", line 162, in get_relative_coordinates
2024-05-11 19:02:07.549922241 [
2024-05-11 19:02:07.549923095 File "/opt/frigate/frigate/util/config.py", line 163, in
2024-05-11 19:02:07.549924326 f"{round(int(points[i]) / frame_shape[1], 3)},{round(int(points[i + 1]) / frame_shape[0], 3)}"
2024-05-11 19:02:07.549925190 ValueError: invalid literal for int() with base 10: '0.0'

[RichE85]

This looks awesome. I would like to see a password protected UI just to keep people from casually getting into the config or camera feed.

[hawkeye217]

There's already a feature request. See #1074

[wjbeckett]

With the Home Assistant/MQTT Integration, will there be different events published for an "alert" as opposed to a "detection" and "motion" events?

[NickM-27]

Naturally the messages are not 1:1

[wjbeckett]

alright, trying to play around with Notifications in HA for alerts as opposed to events.
I have the text of an alert being sent based on the alert and the object that was detected, I just can't get the thumbnail or clip of the alert. It If I try to use the after ID, it tells me the object (whether it's a thumbnail or clip) doesn't exist.

Have you implemented notifications based on the alerts part of the /reviews endpoint at all?

[NickM-27]

you can not use a review ID for the event clips / snapshots. As part of the payload there is a list of detections which is the list of relevant event IDs, those can be used. Otherwise, you can use some of the new preview.gif or preview.mp4 endpoints though this will require a slight addition to the integration

[wjbeckett]

Ooh the new preview gif and MP4 files would be nice!
I assume I need to wait for the HA Integration to be updated to utilise those?

[NickM-27]

home assistant integrations are not compiled, you only need to add a few lines to make it work blakeblackshear/frigate-hass-integration#664

[Majestic7979]

Firstly thanks so much for being constantly active here and listening to your needs. I guess I will have to eat the dog shit like I promised! lol. One thing: I absolutely love that I can scroll through the timeline and see all the events from all the cameras in sync. But what I really, really need (since I don't use events) is a timeline with a playhead where I can set the playhead at a specific place on the timeline and ALL the cameras will sync up to that specific point, then I want to press Play All and see all the cameras play in sync together. Please please please please I beg you to implement this. As I explained in a previous post, I live in Europe and it's very common to live in townhouses where your doorstep is level with the sidewalk and just have a meter of distance between your front porch and the sidewalk, with people walking by the detections are moot because an urban neighborhood of townhouses will see hundreds of people walking past the door every day just to go to work etc. So as you can imagine, in situations like that when the timeline is saturated with motion events that are merely people walking past the camera, it becomes totally irrelevant and the relevancy is more about being able to quickly play all sources in sync and without stuttering. One thing I suffer with is the stuttering when the player moves from one 10s segment to another. Every time it moves from segment A to segment B to segment C and so on, I get a half-second stutter. The more you increase the playback scale, the more stuttering. It's like a buffering effect. And if you play at 16x kiss bye bye to your sanity! As you will see is incessant stuttering as the player cannot move to the next segment seamlessly. Please for the love of almighty Jesus Christ address this major issue. It's during playback/review that any NVR shines... All NVRs can record, indeed my cameras will happily let me throw all the raw footage into a simple NFS mount. But it is the reviewing itself to find the crucial moments that makes a NVR special. I know you guys focus on detections but seriously your NVR can't be touched in terms of development speed and I sincerely hope you listen to my plight and do it 🙏🏻 God bless.

PS. I was just thinking I forgot to mention how exporting easily is equally as important as finding the relevant event in question. Currently I have to use dropdowns to select camera, whether it's live or a timelapse, and then use date/time fields. I wish I could quickly use a timeline to set in/out points just like I can do in a video editing app... put the start handle at the beginning of where I want to export and the finish handle at the end of my export, then select cameras with checkboxes, click "export" and job done, the visual timeline would help a lot. But for those who want to still be exact please include a button to "enter date and time".

[NickM-27]

But what I really, really need (since I don't use events) is a timeline with a playhead where I can set the playhead at a specific place on the timeline and ALL the cameras will sync up to that specific point, then I want to press Play All and see all the cameras play in sync together. Please please please please I beg you to implement this.

this already exists in the recordings viewer page like it is shown in the demo

the motion viewer also supports a play button that will just play back previews of all cameras at the same time

One thing I suffer with is the stuttering when the player moves from one 10s segment to another. Every time it moves from segment A to segment B to segment C and so on, I get a half-second stutter. The more you increase the playback scale, the more stuttering. It's like a buffering effect

as part of the new UI we have switched to a new HLS player (hls.js from video.js) so it is possible that this change will fix what you are describing. I used to have buffering when setting the playback speed to 8x or higher but with the new player I do not

[NickM-27]

PS. I was just thinking I forgot to mention how exporting easily is equally as important as finding the relevant event in question. Currently I have to use dropdowns to select camera, whether it's live or a timelapse, and then use date/time fields. I wish I could quickly use a timeline to set in/out points just like I can do in a video editing app... put the start handle at the beginning of where I want to export and the finish handle at the end of my export, then select cameras with checkboxes, click "export" and job done, the visual timeline would help a lot. But for those who want to still be exact please include a button to "enter date and time".

exporting using handles on the timeline is already implemented as well

Screen.Recording.2024-04-29.at.6.42.41.AM.mov

[NickM-27]

@Majestic7979 also one other thing to note, there is a new "loitering time" field that is added to zones. So maybe you will find that you want to use "events" (reviews) now, because you can make it an alert if a person loiters but a detection if the person just walks by. That way you get more information on the timeline of when an object was detected

[Majestic7979]

Thanks, I'm very eager to explore and see how it all works with my own footage. And I hope the development goes well :) How do I subscribe to support? Because I don't necessarily need the AI detections/models I don't subscribe to Frigate+, it would be nice to have a basic tier where I just make monthly payments to basically thank you guys for your development and customer service. It would be nice to be able to decide how much I can contribute rather than having a fixed price, that way I could vary based on an ongoing budget. While I'd like to pay for the work, some months would be less, some more, I'd rather give something rather than nothing on those months when budget is tigther.

Edit: just saw you addressing the other issues. OMG you guys are freaking amazing!!!!!!!!!!!!!!!!!!!!

[detroitgoose]

@Majestic7979 I've been super impressed with frigate+ detection. Even the base model is leaps and bounds more confident that the yolo model. A huge benefit is that you are given 12 "trainings" that allow you to tweak your model to your specific environment, and at the same time upgrade to newly released base models.

You also don't need to keep your subscription active (although it needs to be active to train new models / upgrade to new base models.) Even after you deactivate your subscription, you can still use the superior + models!

All that said, I'm really desperately waiting for improvements to the training process, but it still works ok. My issue is mostly with the difficultly in going back over images you've already trained and tweaking them. It's very clumsy at the moment, but I it'll get better.

Just giving a recommendation as someone who was very weary of "if it's worth it," and sharing personal camera images that could eventually be used in the base model. I've gotten over it. It's been pretty incredible. (the "free" models are trained on images that are far different than what a security camera sees. By crowd sourcing actual camera images, it's made a far more accurate model.)

[Majestic7979]

Any plans to make the timeline zoomable, like the Nest system? To make easier to put the playhead more exactly...

[hawkeye217]

Right now the timeline's granularity is about 7 seconds per pixel. Between scrubbing with the timeline and the video seeking controls, do you feel there's a real need to be more granular than that?

[YBonline]

I think the issue for most is getting more of the day onto the screen (at the very least, thats the most annoying thing about the new interface, not that I'm complaining, I still think its amazing regardless), or at least being able to scroll throughout the day faster. A full screen height on my desktop is 1 hour. On my phone, its only 20 minutes, so if I wanna look at 8 hours earlier, its a lot of scrolling. This is a bit compounded by the fact that scrolling doesn't actually move the video (like it does in UniFi Protect and Scrypted, but not on Nest Protect), which I do enjoy that since I can keep watching while getting positioning to the next clip ready at the same time, but it does mean an extra click to start playing each time...

Nest, UniFi Protect, Scrypted, are all zoomable. I think alternatively if you did something like what you did on the events screen for a full day summary as a scrollbar to the timeline would be slick as well, giving multiple views of the timeline at once, but something just feels like it could be better to scroll through full days more quickly...

I also recently came across Scrypted, where the timeline seems like a copy of UniFi Protect with detection icons, snapshots zoomed in when you point to them, and frames on the timeline as well to help you get where you want to go faster... https://demo.scrypted.app/#/timeline/43

YouTube's scrubbing view is also awesome no doubt.

[NickM-27]

the original post here said To make easier to put the playhead more exactly... which doesn't seem like a scrolling issue, though I hear what you are saying.

I think what you are describing comes down to a different use case though, like was discussed earlier #11136 (reply in thread)

[hawkeye217]

Maybe you are referring to the motion timeline or recordings timeline, but for others reading It's also worth mentioning that in events review, the summary timeline to the right of the main timeline shows your entire 24 hour period. It's draggable/clickable and the highlighted section shows what part of the timeline you're viewing.

[Majestic7979]

Guys to simplify, yes I do, that's why I wrote it... on the nest I can zoom in to sections and finely scrub through the video. I never make requests willy-nilly, if I take my time to write something down it's because I really need it. Sometimes it's very useful when the police is standing next to you and asking to go backwards and forwards slowly... using the playback controls is a pain in the ass for that. So zooming in and being able to slide the playhead is a big time saver to check frame by frame.

[MarcA711]

It would be nice to make the "Detectors" section from the system stats more customizable for each platform.
For example Rockchip Socs could report the load and frequency of each NPU core and maybe some information like the driver version and api version. However, currently there is no good way to add this.
It seems currently rockchip is the only platform that is able to provide those additional statistics but maybe other platforms in the future can implement other stats as well.

[aneisch]

Are manual events expected to appear under reviews? I am manually creating events via the API, and they're appearing on the cameras tab at the top, but the events do not appear under review detections.

[NickM-27]

If they appear at the top then they will also appear in the alerts section of the review page. Unless you could on it from the filmstrip which marks it as reviewed

[dz4news]

It seems with the past two dev versions, I have noticed some of the snapshots are blank.. an example is below.. any idea on what would be causing this to happen? The alert detection videos are fine and I am not seeing any errors in the logs.

[NickM-27]

I'm surprised by how all of these are so square, I'd expect them to be 16:9. Missing images is a known issue for audio events

[OnFreund]

I don't have audio detection enabled

[blakeblackshear]

Mine are square too. I have my snapshots cropped.

[NickM-27]

oh hold on I didn't realize this was the frigate+ screen. The reason this would happen is due to restarting the container while an event is in progress, the snapshot is not saved in that case

[dz4news]

I will do some more testing and see if I can determine a pattern.. I dont think I was restarting the container at the times of the missing images, but it is possible. This is just a small example, I have alot that dont have images in the frigate+ screen.

[rajil]

Frigate is complaining about a missing recording when trying to play it but the file is present

frigate  | 2024-05-09 04:13:33.882939894  [2024-05-09 04:13:33] frigate.api.media              WARNING : Recording clip is missing or empty: /media/frigate/recordings/2024-05-09/04/maingate/12.57.mp4

$ ls -lah recordings/2024-05-09/04/maingate/12.57.mp4 
-rw-r--r-- 1 root root 5.8M May  9 04:13 recordings/2024-05-09/04/maingate/12.57.mp4

The review preview also plays the recording.

I had sync_recordings: True set which i will now set as false.

[NickM-27]

to be clear "previews" do not play the recording, they use an entirely different file. This is mot likely due to sync recordings which is not recommended to be left on

[Mincka]

Hi,

Overall, the new interface is very nice looking and professional, congratulations!

I needed to revert to the stable version, but I can give a quick feedback about the mask editor:

1. It's confusing to see, at the same time, all the masks of different categories (motion, zone, object) together. Even with a light color, it's hard to read when masks are overlapping. I would prefer to only see the mask of a specific category.

2. I really struggled to find how to change the camera. Top right is very far from the command panel on the left.

3. Since operations are done per camera, it does not make sense for me to have toggles to select the camera. They are fancier, but in that case, a simple dropdown would make more sense from a UX perspective. You can never select more than one camera.

One more thing, about the timeline, I though that the cursor with the current time was hiding too much the zone of the events:

I would suggest maybe something with a window for a cursor, or just a little bit of transparency, or align left the event / motion bars would help.

__/---------\__
|->         <-|
--\---------/--
    2:04PM

[hawkeye217]

On desktop browsers, the top right corner of your window provides all sorts of controls and filters on many of the new screens. In the mask and zone editor, you'll find a Filter button (next to the camera selection) where you can choose to show/hide zones and the different types of masks.

We really appreciate your feedback!

As Blake mentioned in his write-up, he hired a professional UI designer (jimdesigns.co) for the redesign. Along with Blake's input, he meticulously thought out many of the details of the new UI. As a contributor to the project and a developer of the new UI, we're really happy with his work!

[Mincka]

Yes, I read about that. It's great that the contributors to Frigate+ could also bring that to the project.
I am not "requesting" specific changes, just giving feedback with the point of view of a "new" user. :)

[hawkeye217]

For sure! And we really do appreciate the feedback we get like yours.

[OnFreund]

I 100% agree with the cursor hiding too much of the events.

[rajil]

Agree with this. The timestamp should be transparent, and the red arrow show be outside the timeline.

[OnFreund]

Finally getting around to writing my thoughts (though I did mention some of it on discord):
First of all, the new UI is really awesome, for so many. reasons, including:

1. I can quickly review what happened last night (or any other period for that matter). My reviews are synced across devices, and I can decide if I want to focus just on important stuff (alerts), or go broader (detections). I'd actually love having another level - alerts for the critical stuff (e.g. person where one shouldn't be), one for normal stuff that I want to review frequently (person walking up to the door), and detections for everything else (car passing by in the street).
2. I can easily go over the Frigate+ screen to find the snapshots I need to fine tune the model.
3. The combination of the stationary tracking changes and the 2024.1 base model mean I'm barely seeing any false positives.
4. Review grouping events together makes so much sense - the timeline is no longer littered with multiple events for the same object.

Some suggestions for improvements:

Frigate+ screen:

• Keyboard navigation would be really helpful (once I open a snapshot, I'd like to use cursor keys to navigate to others)
• Would be great if we can have a way to mark snapshots as reviewed, or at the very least mark the last snapshot that was reviewed.
• The icon showing what was detected helps a lot. Maybe we can also add the confidence level next to it? That can help find low confidence true positives that can be used to train the model.
• Would also be great to be able to view or jump to the recording when the snapshot was taken. I understand the the model is working on an image, not a video, but unlike the model, my eyes are limited by things such as zoom and contrast, and sometimes seeing the recording helps make out objects.

Review screen:

• As noted by @Mincka, the playhead is hiding too much. Specifically, I'd like to see the length of the event.
• When I click on a review activity, I lose the connection to the activity. I can no longer export the video for it, I don't have any indication in the video of when it started/ended, and if I go back, that activity would be marked as reviewed, and be gone from the screen (yes, I know I can mark "show reviewed" and look for it, but that's far from ideal). The only connection I have is the marking in the timeline, but as mentioned, this is covered by the playhead, and also, I think, too loose of a connection.

I'm also seeing UI glitches with Frigate Proxy, which I assume will also be relevant for the Frigate add-on, but I guess those will surface during the beta.

Overall, I think 0.14 is better than 0.13 by leaps and bounds (which in turn was better than 0.12 by leaps and bounds), so a huge shoutout and thank you to everyone involved.

[nwish]

Could we potentially get the ability via MQTT, API or both to relabel alerts as detections and vice versa? I have an interior camera for which dogs are detections and people are alerts. However, I don't want people creating alerts while we are home, only away or sleeping. I don't necessarily need this built into Frigate's config or UI, I can use NodeRed or HA to do this. Thoughts?

[NickM-27]

Is there a reason to have object detection enabled at all while this is the case? And even if they are alerts I don't necessarily see an issue with that given they can be cleared as reviewed either way.

In the long run it might make sense to have some additional "dynamic" inputs to decide when to mark something as alert vs detection like you are describing, I don't really see an api to adjust what frigate has stored as the best way to go about it. Either way I doubt it would come in 0.14

[nwish]

I suppose that's a good point, but I do still want to save detections in the event of an incident while we're there, I just don't need a bunch of alerts mixed in of me and the wife doing unremarkable things lol.

[rajil]

It will be great to get some user authentication. To begin with atleast two roles, Admin and User. The User role should not have access to the config file.

In the future it can be expanded so certain camera's are limited to certain users.

[NickM-27]

#11347

[rajil]

This is awesome. Thank you for bringing this in. Looking forward to this landing in dev branch.

[gonzalezcalleja]

Hi!

I have been testing dev version with my 20 cameras setup + coral accelerator PCIe and the new UI it's a huge leap of qualitative improvement!

My suggestions as a long time frigate user:

• On the history (/review) view, in the lateral timeline, would be great identify the detection (person, dog, etc ... with colours/icons).
• On the live view I miss the button/dropdown to select the type of live view (mse, webrtc, jpeg) etc.

Congratulations on this enormous work for the new UI, it already looks so spectacular (and is dev!).

[niqu1982]

Migration have problem.
After check couple version of dev i have error:

2024-05-13 13:09:40.230461617  invalid literal for int() with base 10: '0.0'
2024-05-13 13:09:40.230875366  Traceback (most recent call last):
2024-05-13 13:09:40.230876995    File "/opt/frigate/frigate/app.py", line 604, in start
2024-05-13 13:09:40.230877923      self.init_config()
2024-05-13 13:09:40.230878917    File "/opt/frigate/frigate/app.py", line 137, in init_config
2024-05-13 13:09:40.230879788      self.config = user_config.runtime_config(self.plus_api)
2024-05-13 13:09:40.230880660    File "/opt/frigate/frigate/config.py", line 1466, in runtime_config
2024-05-13 13:09:40.230881515      camera_config.objects.filters[object] = RuntimeFilterConfig(
2024-05-13 13:09:40.230882363    File "/opt/frigate/frigate/config.py", line 484, in __init__
2024-05-13 13:09:40.230883191      mask = get_relative_coordinates(config.get("mask"), frame_shape)
2024-05-13 13:09:40.230884107    File "/opt/frigate/frigate/util/config.py", line 162, in get_relative_coordinates
2024-05-13 13:09:40.230884820      [
2024-05-13 13:09:40.230885718    File "/opt/frigate/frigate/util/config.py", line 163, in <listcomp>
2024-05-13 13:09:40.230886921      f"{round(int(points[i]) / frame_shape[1], 3)},{round(int(points[i + 1]) / frame_shape[0], 3)}"
2024-05-13 13:09:40.230887796  ValueError: invalid literal for int() with base 10: '0.0'
2024-05-13 13:09:40.230902304  
2024-05-13 13:09:40.230903279  *************************************************************
2024-05-13 13:09:40.230904117  ***    End Config Validation Errors                       ***
2024-05-13 13:09:40.230905073  *************************************************************

Config file:

mqtt:
  host: 192.168.2.152
  user: xxxxxxxxxxxxxx
  password:xxxxxxxxxxxxxxx
logger:
  default: info
  logs:
    frigate.ptz.onvif: info
go2rtc:
  streams:
    brama:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.181:554/Streaming/channels/101
    brama_sub:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.181:554/Streaming/channels/102
    komorka:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.182:554/Streaming/channels/101
    komorka_sub:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.182:554/Streaming/channels/102
    garage:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.183:554/Streaming/channels/101
    garage_sub:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.183:554/Streaming/channels/102
    ogrod_przod:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.184:554/Streaming/channels/101
    ogrod_przod_sub:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.184:554/Streaming/channels/102
    garaz:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.185:554/Streaming/channels/101
    garaz_sub:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.2.185:554/Streaming/channels/102
    PrzodDzialka:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.3.181:554/cam/realmonitor?channel=1&subtype=0
    TylDzialka:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.3.182:554/cam/realmonitor?channel=1&subtype=0
    DrzwiDzialka:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.3.183:554/cam/realmonitor?channel=1&subtype=0
    BokDzialka:
    - rtsp://xxxxxxxxxxxx:xxxxxxxxxxxx@192.168.3.184:554/cam/realmonitor?channel=1&subtype=0



cameras:
  DrzwiDzialka:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/DrzwiDzialka
        input_args: preset-rtsp-restream
        roles:
        - detect
        - record
    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person
      - bird
      - cat

      filters:
        person:
          min_score: 0.68
          threshold: 0.30
          mask:
          - 1279,1049,1920,819,1920,0,638,0,587,331
        bird:
          min_score: 0.70
          threshold: 0.4
        car:
          min_score: 0.65
          threshold: 0.3
    snapshots:

      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 30

    motion:
      mask:
      - 0,968,104,643,26,178,671,59,853,606,1276,1047,1920,1016,1920,0,0,0

      threshold: 20
    record:
      enabled: true
      retain:
        days: 30
      events:
        retain:
          default: 30
          mode: motion
        pre_capture: 5
        post_capture: 20
  BokDzialka:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/BokDzialka
        input_args: preset-rtsp-restream
        roles:
        - detect
        - record
    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person

      - cat
      filters:
        person:
          min_score: 0.65
          threshold: 0.20

    snapshots:

      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 30

    motion:
      mask:
      - 0,278,0,968,679,133,1433,0,0,0
      threshold: 20
    record:
      enabled: true
      retain:
        days: 30
      events:
        retain:
          default: 30
          mode: motion
        pre_capture: 5
        post_capture: 20
  PrzodDzialka:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/PrzodDzialka
        input_args: preset-rtsp-restream
        roles:
        - detect
        - record
    detect:
      width: 2560
      height: 1440
      fps: 5
    objects:
      track:
      - person

      - cat
      filters:
        person:
          min_score: 0.75
          threshold: 0.20
          mask:
          - 2327,751,2509,1086,1175,1286,1075,929
          - 2327,751,2509,1086,0,483,700,98
        cat:
          min_score: 0.65
          threshold: 0.30

    snapshots:
      required_zones:
      - test1

      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 30
    zones:
      test1:
        coordinates: 0,1440,2560,1440,2560,301,1690,303,1637,940,385,935,338,406,0,436
        objects:
        - person

    motion:
      mask:
      - 743,474,1129,453,1729,564,2031,515,2560,650,2560,0,0,0,0,396
      - 184,921,762,869,758,414,84,455,116,683

      threshold: 20

    record:
      enabled: true
      retain:
        days: 30
      events:
        retain:
          default: 30
          mode: motion
        pre_capture: 5
        post_capture: 20

    onvif:

      host: 192.168.3.181

      port: 80


      user: frigate

      password: MyPass_xxxxx
      autotracking:

        enabled: true


        calibrate_on_startup: false
        zooming: relative
        zoom_factor: 0.30
        # Optional: list of objects to track from labelmap.txt (default: shown below)
        track:
        - person
        required_zones:
        - test1

        return_preset: poczatek
        timeout: 5
        movement_weights: 0.25, 1.0, 6.350177764892578, 5.608901967284498, 0.5309139274781763

  TylDzialka:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/TylDzialka
        input_args: preset-rtsp-restream
        roles:
        - detect
        - record
    detect:
      width: 2560
      height: 1440
      fps: 5
    objects:
      track:
      - person
      - bird

      - cat
      filters:
        person:
          min_score: 0.68
          threshold: 0.10
        bird:
          min_score: 0.60
          threshold: 0.15
    snapshots:
      required_zones:
      - test
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 30
    zones:
      test:
        coordinates: 0,1440,1195,1440,2560,1440,2560,691,1557,352,0,728
        objects:
        - person
        - bird
        - cat
    motion:
      threshold: 30
      contour_area: 20
      mask:
      - 2560,0,2560,431,1868,358,1907,0
      - 314,1219,937,1190,751,881,329,929
      - 0,623,295,554,421,0,0,0
    record:
      enabled: true
      retain:
        days: 30
      events:
        retain:
          default: 30
          mode: active_objects
        pre_capture: 5
        post_capture: 20

    onvif:

      host: 192.168.3.182

      port: 80

      user: frigate

      password: Mypass_xxxxxxxxxx

      autotracking:

        enabled: true

        calibrate_on_startup: false

        zooming: relative

        zoom_factor: 0.40

        track:
        - person
        - bird
        - cat

        required_zones:
        - test

        return_preset: preset1

        timeout: 10

        movement_weights: 0.25, 1.0, 6.525627374649048, 5.843108956531812, 0.3336184893884972
  brama:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/brama
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://127.0.0.1:8554/brama_sub
        input_args: preset-rtsp-restream
        roles:
        - record

    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person

      filters:
        person:
          min_score: 0.68
          threshold: 0.3
          min_area: 700
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      required_zones:
      - bramaclose_in
      - brama_whole_area
      crop: true
      height: 500
      retain:
        default: 3
    zones:
      bramaclose_in:
        coordinates: 0,1440,2210,1440,2249,1179,2248,736,1821,680,1870,474,986,423,0,751
        objects:
        - person
      brama_whole_area:
        coordinates: 407,0,2560,0,2316,564,959,404,495,377
        objects:
        - person
    motion:
      mask:
      - 0,816,943,412,930,0,0,0
      threshold: 20
      contour_area: 15
    record:
      enabled: true
      retain:
        days: 14
        #mode: active_objects 
      events:
        retain:
          default: 5
          mode: motion
        pre_capture: 3
        post_capture: 10
  balkon:
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/garaz
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://127.0.0.1:8554/garaz_sub
        input_args: preset-rtsp-restream
        roles:
        - record
    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person
      filters:
        person:
          mask:
          - 1572,622,1606,0,0,0,0,1080,397,1080,592,335,802,259,1128,366,1154,440
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 7
    motion:
      mask:
      - 825,277,1025,331,1316,478,1630,640,1920,0,0,0,0,1080,409,1080,565,434,616,282
    record:
      enabled: true
      retain:
        days: 7
      events:
        retain:
          default: 3
          mode: motion
        pre_capture: 5
        post_capture: 15

  garage:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/garage_sub
        roles:
        - detect
      - path: rtsp://127.0.0.1:8554/garage
        roles:
        - record
      output_args:
        record: preset-record-generic-audio-aac
    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 3
    record:
      enabled: true
      retain:
        days: 7
      events:
        retain:
          default: 3
          mode: active_objects
        pre_capture: 5
        post_capture: 15
    motion:
      mask:
      - 0,405,136,461,162,611,554,579,709,665,611,802,278,782,137,697,0,590
      - 1222,0,1920,0,1920,1080,1221,394

  komorka:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/komorka
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://127.0.0.1:8554/komorka_sub
        input_args: preset-rtsp-restream
        roles:
        - record
    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person
      mask:
      - 345,811,300,665,525,590,325,690,925,691,1145,680,1360,703,1565,1080,1920,1080,1920,0,0,0,0,902
      filters:
        person:
          mask:
          - 345,811,300,665
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: true
      retain:
        default: 5
    motion:
      mask:
      - 345,811,300,665,525,590,925,550,925,691,1145,680,1360,703,1565,1080,1920,1080,1920,0,0,0,0,902
    record:
      enabled: true
      retain:
        days: 5
      events:
        retain:
          default: 4
          mode: active_objects
        pre_capture: 3
        post_capture: 10


  ogrod_przod:
    ffmpeg:
      hwaccel_args: preset-nvidia-h264
      inputs:
      - path: rtsp://127.0.0.1:8554/ogrod_przod
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://127.0.0.1:8554/ogrod_przod_sub
        input_args: preset-rtsp-restream
        roles:
        - record
    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person
      - motorcycle
      mask:
      - 0,745,1225,490,2560,758,2560,0,0,0
      - 2560,881,2560,0,1262,0,1149,606
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 14
    motion:
      mask:
      - 1920,690,959,489,981,354,608,418,468,485,126,510,169,609,0,627,0,0,1920,0

    zones:
      deck_area:
        coordinates: 0,1080,1682,1080,1748,647,812,449,572,524,0,663
    record:
      enabled: true
      retain:
        days: 14
      events:
        retain:
          default: 7
          mode: motion
        pre_capture: 5
        post_capture: 15




detectors:
  coral:
    type: edgetpu
    device: usb

birdseye:
  enabled: true
  restream: false
  width: 1280
  height: 720
  quality: 2
  mode: objects

live:
  height: 1920
  quality: 6

[NickM-27]

@niqu1982 your config is incorrect. For your camera you have a detect resolution of 1920x1080 but one of your masks has a coordinte at 2560

    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
      - person
      - motorcycle
      mask:
      - 0,745,1225,490,2560,758,2560,0,0,0
      - 2560,881,2560,0,1262,0,1149,606

[niqu1982]

Still this same problem. I delete wrong mask, i check rest - rebuild proper and not starting with this same error :/

[NickM-27]

some of the zones and motion masks are also incorrect. After fixing these your config works

[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,758 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.
[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,0 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.
[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,881 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.
[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,0 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.
[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,758 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.
[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,0 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.
[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,881 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.
[2024-05-13 14:58:09] frigate.util.config            ERROR   : Not applying mask due to invalid coordinates. 2560,0 is outside of the detection resolution 1920x1080. Use the editor in the UI to correct the mask.

[niqu1982]

I check once again and back with answer. Now i reading config

[niqu1982]

Working Thankyou :)

[mabed-fr]

Hello, Great !

Which docker tag should I use to have the latest beta version that the admins and other users test, I would like to give you my opinions
(Intel nuc)

[mabed-fr]

Chrome Version 124.0.6367.118 (Build officiel) (64 bits) on Debian 12

PS: I restart now and he work ...

[mabed-fr]

I think my hardware is underwater

[mabed-fr]

The problem is there again.

No browser logs but high CPU load on the server.

[mabed-fr]

i try on my windows

[mabed-fr]

i try on safari apple is ok
windows 11 is ok

the preview view has intermittent problem with chrome on linux

[mabed-fr]

After some tests last night, I'm starting to use the new UI well.

I have a comment for the /plus page

I find that the scores are difficult to see

[themoosman]

I fired up the new UI, and my thoughts are mixed. I did hit an issue right away. I tried to view events from two days ago and got the following errors.

2024-05-15 16:44:57.261497106  /usr/local/lib/python3.9/dist-packages/pandas/core/dtypes/astype.py:133: RuntimeWarning: overflow encountered in cast
2024-05-15 16:44:57.261499276    return arr.astype(dtype, copy=True)

and

2024-05-15 16:44:57.319006614  [2024-05-15 16:44:57] frigate.api.media              ERROR   : No recordings found for the requested time range
2024-05-15 16:44:57.402191230  /opt/frigate/frigate/api/review.py:467: RuntimeWarning: invalid value encountered in scalar subtract
2024-05-15 16:44:57.402193830    / (part["motion"].max() - part["motion"].min())

Full Log

2024-05-15 16:44:57.261497106  /usr/local/lib/python3.9/dist-packages/pandas/core/dtypes/astype.py:133: RuntimeWarning: overflow encountered in cast
2024-05-15 16:44:57.261499276    return arr.astype(dtype, copy=True)
2024-05-15 16:44:57.263814292  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_03-FrontDoor-SSE-1715809467.824214.webp/thumbnail.webp HTTP/1.1" 200 14022 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.274952378  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/01-Garage-SE/recordings?before=1715809497&after=1715806800 HTTP/1.1" 200 3 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.319006614  [2024-05-15 16:44:57] frigate.api.media              ERROR   : No recordings found for the requested time range
2024-05-15 16:44:57.402191230  /opt/frigate/frigate/api/review.py:467: RuntimeWarning: invalid value encountered in scalar subtract
2024-05-15 16:44:57.402193830    / (part["motion"].max() - part["motion"].min())
2024-05-15 16:44:57.419481245  2024/05/15 16:44:57 [error] 311#311: *1293 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: ::ffff:192.168.1.50, server: , request: "GET /vod/01-Garage-SE/start/1715806800/end/1715809497/master.m3u8 HTTP/1.1", host: "frigate.apps.example.com", referrer: "https://frigate.apps.example.com/review"
2024-05-15 16:44:57.419495105  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /vod/01-Garage-SE/start/1715806800/end/1715809497/master.m3u8 HTTP/1.1" 502 559 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.420220013  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_06-Backyard-W-1715809477.037908.webp/thumbnail.webp HTTP/1.1" 200 13852 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.420493226  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_05-Front-SSE-1715809467.96901.webp/thumbnail.webp HTTP/1.1" 200 18238 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.421154954  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_11-Indoor-Garage-Entry-1715809480.064555.webp/thumbnail.webp HTTP/1.1" 200 11326 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.421260255  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/review/activity/motion?before=1715809497.192&after=1715723097.192&scale=15&cameras=01-Garage-SE HTTP/1.1" 200 320591 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.421332716  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_09-Side-ESE-1715809469.339689.webp/thumbnail.webp HTTP/1.1" 200 10416 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.426273571  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_07-Backyard-E-1715809467.790382.webp/thumbnail.webp HTTP/1.1" 200 12606 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.426977608  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_08-Backyard-N-1715809472.295622.webp/thumbnail.webp HTTP/1.1" 200 10676 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.432716173  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_04-FrontDoor-1715809478.319962.webp/thumbnail.webp HTTP/1.1" 200 9768 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:57.432740834  ::ffff:192.168.1.50 - - [15/May/2024:16:44:57 -0500] "GET /api/preview/preview_10-Garage-1715809488.331881.webp/thumbnail.webp HTTP/1.1" 200 11224 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:58.481231995  2024/05/15 16:44:58 [error] 233#233: *1204 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: ::ffff:192.168.1.50, server: , request: "GET /vod/01-Garage-SE/start/1715806800/end/1715809497/master.m3u8 HTTP/1.1", host: "frigate.apps.example.com", referrer: "https://frigate.apps.example.com/review"
2024-05-15 16:44:58.481256055  ::ffff:192.168.1.50 - - [15/May/2024:16:44:58 -0500] "GET /vod/01-Garage-SE/start/1715806800/end/1715809497/master.m3u8 HTTP/1.1" 502 559 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:44:58.481320706  [2024-05-15 16:44:58] frigate.api.media              ERROR   : No recordings found for the requested time range
2024-05-15 16:45:00.299471549  ::ffff:192.168.1.50 - - [15/May/2024:16:45:00 -0500] "GET /api/review?reviewed=1&before=1715662799.999&after=1715576400 HTTP/1.1" 200 3 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:45:00.335359413  /usr/local/lib/python3.9/dist-packages/pandas/core/dtypes/astype.py:133: RuntimeWarning: overflow encountered in cast
2024-05-15 16:45:00.335361633    return arr.astype(dtype, copy=True)
2024-05-15 16:45:00.336785509  ::ffff:192.168.1.50 - - [15/May/2024:16:45:00 -0500] "GET /api/config HTTP/1.1" 200 86353 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:45:00.428885016  ::ffff:192.168.1.50 - - [15/May/2024:16:45:00 -0500] "GET /api/01-Garage-SE/recordings?before=1715580000&after=1715576400 HTTP/1.1" 200 3 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:45:00.455033910  [2024-05-15 16:45:00] frigate.api.media              ERROR   : No recordings found for the requested time range
2024-05-15 16:45:00.460192408  2024/05/15 16:45:00 [error] 311#311: *1293 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: ::ffff:192.168.1.50, server: , request: "GET /vod/01-Garage-SE/start/1715576400/end/1715580000/master.m3u8 HTTP/1.1", host: "frigate.apps.example.com", referrer: "https://frigate.apps.example.com/review"
2024-05-15 16:45:00.460208038  ::ffff:192.168.1.50 - - [15/May/2024:16:45:00 -0500] "GET /vod/01-Garage-SE/start/1715576400/end/1715580000/master.m3u8 HTTP/1.1" 502 559 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:45:00.476031586  ::ffff:192.168.1.50 - - [15/May/2024:16:45:00 -0500] "GET /api/review/activity/motion?before=1715662799&after=1715576400&scale=15&cameras=01-Garage-SE HTTP/1.1" 200 252870 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:45:01.564784300  2024/05/15 16:45:01 [error] 311#311: *1216 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: ::ffff:192.168.1.50, server: , request: "GET /vod/01-Garage-SE/start/1715576400/end/1715580000/master.m3u8 HTTP/1.1", host: "frigate.apps.example.com", referrer: "https://frigate.apps.example.com/review"
2024-05-15 16:45:01.564801760  ::ffff:192.168.1.50 - - [15/May/2024:16:45:01 -0500] "GET /vod/01-Garage-SE/start/1715576400/end/1715580000/master.m3u8 HTTP/1.1" 502 559 "https://frigate.apps.example.com/review" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36" "192.168.1.35"
2024-05-15 16:45:01.564843621  [2024-05-15 16:45:01] frigate.api.media              ERROR   : No recordings found for the requested time range

[NickM-27]

Events that are created before updating aren't really meant to be viewable as everything in the new UI requires new data.

And yes events older than 24 hours can be viewed, just use the calendar to choose a day to view

[themoosman]

If I try to get events > 24 hours (from the review page), I see this stack:

2024-05-15 21:17:41.888846751  [2024-05-15 21:17:41] frigate.api.app                ERROR   : Exception on /preview/all/start/1715824800/end/-64800 [GET]
2024-05-15 21:17:41.888849181  Traceback (most recent call last):
2024-05-15 21:17:41.888849951    File "/usr/local/lib/python3.9/dist-packages/flask/app.py", line 1473, in wsgi_app
2024-05-15 21:17:41.888850461      response = self.full_dispatch_request()
2024-05-15 21:17:41.888850961    File "/usr/local/lib/python3.9/dist-packages/flask/app.py", line 882, in full_dispatch_request
2024-05-15 21:17:41.888851361      rv = self.handle_user_exception(e)
2024-05-15 21:17:41.888851851    File "/usr/local/lib/python3.9/dist-packages/flask/app.py", line 880, in full_dispatch_request
2024-05-15 21:17:41.888852231      rv = self.dispatch_request()
2024-05-15 21:17:41.888852691    File "/usr/local/lib/python3.9/dist-packages/flask/app.py", line 865, in dispatch_request
2024-05-15 21:17:41.888853191      return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
2024-05-15 21:17:41.888853651    File "/opt/frigate/frigate/api/preview.py", line 82, in preview_hour
2024-05-15 21:17:41.888854131      datetime(int(parts[0]), int(parts[1]), int(day), int(hour), tzinfo=timezone.utc)
2024-05-15 21:17:41.888854551  ValueError: invalid literal for int() with base 10: 'all'

If I go to the individual camera, then history, then pick a day. The UI either hangs or says "No recordings found for this time
", with this log message.

2024-05-15 21:24:02.401340204  2024/05/15 21:24:02 [error] 144#144: *523 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: ::ffff:192.168.1.50, server: , request: "GET /vod/01-Garage-SE/start/1715230800/end/1715234400/master.m3u8 HTTP/1.1", host: "frigate.apps.example.com.", referrer: "https://frigate.apps.example.com/review"

[NickM-27]

based on your message you haven't been running the new UI very long, and like I said previous data from before updating isn't meant to be viewable. Previous days are viewable when those previous days have data for the new UI

[themoosman]

So any events created by 0.13.x that are older than 24 hrs are basically gone?

[NickM-27]

Not necessarily, in my testing the recordings still work when going to the recordings page directly so what you saw there is potentially a bug. But yes in general 0.13 events won't show in the new reviews UI. there is just no feasible way to translate them to the new format.

[Majestic7979]

One question... is the new UI being tested on mobile? Because I'm seeing some really weird behavior on mobile. For example I can't see the whole video, I can only zoom in but not out. And in landscape the layout does not fill the whole screen so I'm left with a timeline that's not fixed to the edge of the screen and a tiny little square for the video, which is useless. I also wanted to reiterate my request to make the timeline zoomable, especially important when trying to export by selecting points on the timeline, then it's useful to zoom into a section (like Nest) to make the range more accurate for the export.

[NickM-27]

yes, we've been testing and using it on mobile. screenshots would be helpful to understand what you are seeing. Both layouts that you describe work as expected on my Android and iPhone