Rebuilding the Frigate UI for 0.14 #11136
Replies: 184 comments 751 replies
-
|
This is awesome! |
Beta Was this translation helpful? Give feedback.
-
|
by default it is the last 24 hours, or a specific day can be selected on the calendar |
Beta Was this translation helpful? Give feedback.
-
|
Perfect |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Amazing work! Looking forward to this. 👏🏼 |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 So I guess I'm looking for a required_zones setting on a per object basis. |
Beta Was this translation helpful? Give feedback.
-
|
you would need 3 zones to accomplish this zone 2, required for alerts and has person and car object |
Beta Was this translation helpful? Give feedback.
-
|
Awesome stuff, really looking forward to it!
? |
Beta Was this translation helpful? Give feedback.
-
|
Frigate+ has been available for about 8 months now, you just need to email blake@frigate.video to request access |
Beta Was this translation helpful? Give feedback.
-
|
looks very promising. Will there be a version optimized for mobile devices? |
Beta Was this translation helpful? Give feedback.
-
|
the UI has been built with both desktop and mobile views in mind |
Beta Was this translation helpful? Give feedback.
-
|
I just tried the dev build and the new interface really is a vast improvement on both the desktop and mobile. 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 . |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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) |
Beta Was this translation helpful? Give feedback.
-
|
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". |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
also, the new UI does make more things configurable directly from the UI |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
yes, that will come in some future version |
Beta Was this translation helpful? Give feedback.
-
|
This is awesome to see, we might fully drop Blue Iris when this launches if it solves all of our needs |
Beta Was this translation helpful? Give feedback.
-
I did that nearly two years ago. |
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
I just pulled the dev build today as well.. any pointers from your end so far? :) |
Beta Was this translation helpful? Give feedback.
-
|
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 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
That’s my plan. I’ve got a list 😊 |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
It looks like the config migration didn't like something in my config file because frigate won't start after changing to v14. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
I don't see anything, but I'll send you my config via a discord DM just in case. |
Beta Was this translation helpful? Give feedback.
-
|
Perfect |
Beta Was this translation helpful? Give feedback.
-
|
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' |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
There's already a feature request. See #1074 |
Beta Was this translation helpful? Give feedback.
-
|
With the Home Assistant/MQTT Integration, will there be different events published for an "alert" as opposed to a "detection" and "motion" events? |
Beta Was this translation helpful? Give feedback.
-
|
Naturally the messages are not 1:1 |
Beta Was this translation helpful? Give feedback.
-
|
alright, trying to play around with Notifications in HA for alerts as opposed to events. Have you implemented notifications based on the alerts part of the /reviews endpoint at all? |
Beta Was this translation helpful? Give feedback.
-
|
you can not use a review ID for the event clips / snapshots. As part of the payload there is a list of |
Beta Was this translation helpful? Give feedback.
-
|
Ooh the new preview gif and MP4 files would be nice! |
Beta Was this translation helpful? Give feedback.
-
|
home assistant integrations are not compiled, you only need to add a few lines to make it work blakeblackshear/frigate-hass-integration#664 |
Beta Was this translation helpful? Give feedback.
-
|
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". |
Beta Was this translation helpful? Give feedback.
-
exporting using handles on the timeline is already implemented as well Screen.Recording.2024-04-29.at.6.42.41.AM.mov |
Beta Was this translation helpful? Give feedback.
-
|
@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 |
Beta Was this translation helpful? Give feedback.
-
|
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!!!!!!!!!!!!!!!!!!!! |
Beta Was this translation helpful? Give feedback.
-
|
@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.) |
Beta Was this translation helpful? Give feedback.
-
Thanks for sharing your experience, I'll look into it, I don't know how it works, I don't know if I have to change my config, etc. I'll explore but it's nice to know that there's an advantage to paying apart from just saying thanks for delivering a good product and responsible support, which was my only intention :) |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to get audio playback in history/review mode? The speaker button on the video player controls doesn't seem to be having any effect. |
Beta Was this translation helpful? Give feedback.
-
|
Ah yeah that bit is working fine. Live view has audio. The recording files have audio. History/Review has no audio. |
Beta Was this translation helpful? Give feedback.
-
|
Aargh, sorry, it may have been config and not an issue with .14. I'll do more investigation before saying anything next time. |
Beta Was this translation helpful? Give feedback.
-
|
opus audio is for WebRTC. AAC audio is required for recordings |
Beta Was this translation helpful? Give feedback.
-
|
Opus audio is required for webrtc |
Beta Was this translation helpful? Give feedback.
-
|
I'm not saying I would have found it, but it might be a useful note to have in the documentation, the only reference is: |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 You mentioned in my frigate HASS integration feature request that "starred events are going away in favor of exported clips." Am I to understand that in 0.14 if we want to save an event beyond the retention period, the only option will be to export externally? |
Beta Was this translation helpful? Give feedback.
-
|
The only option will be to use the export function within the UI which also shows exported clips and makes them searchable |
Beta Was this translation helpful? Give feedback.
-
|
I'm a little confused. "Export", to me, only means to extract them from the host system...so maybe I am misunderstanding. Do you have this new export function documented yet? I perused the new docs but did not find. In short: Regardless of the mechanism or what it is called, will it be possible to save certain clips/recordings/snapshots indefinitely without having to rely on external resources? |
Beta Was this translation helpful? Give feedback.
-
Yes, export simply means retain indefinitely and makes it easily searchable |
Beta Was this translation helpful? Give feedback.
-
|
Hi @NickM-27 - Are you expanding the date selector in review/history to be a date range / all, or just more than one day? My use case: I have audio detection. I want to see all the BEEPS/HONKS/SKIDDING etc events. But it appears I have to do this by selecting each 24h period one by one. I probably look at these events only once a week because I get 2-3 of these events a week only. It becomes more of an effort to review than a quick glance. The calendar shows red dots where those events did exist when a filter is applied, but I'm not sure this is very efficient to click through all the days unless I'm missing the reason for the limitation. I have the same issue with my front door camera and lack of events. |
Beta Was this translation helpful? Give feedback.
-
|
The view is designed for a 24 hour review time period otherwise the timeline is not really suitable. A future update will include more search options |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info @NickM-27 👍 The UI is great for daily reviewing or a high number of events for business/commercial - just a little less convenient now for my very low-event camera system. |
Beta Was this translation helpful? Give feedback.
-
|
PWA - Password save I have installed frigate as an app on the android phone. Each time I have to put the password in the field. |
Beta Was this translation helpful? Give feedback.
-
|
I installed as a PWA on my Android and haven't had to re-enter my password. There might be a cookie setting or something causing this. |
Beta Was this translation helpful? Give feedback.
-
|
Does it remember the password after a cold boot? |
Beta Was this translation helpful? Give feedback.
-
|
It should unless you are changing the JWT secret. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to ignore events from specific cameras? There are a few I'd like to 'mute' in terms of alerts, birdseye, etc. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
missed that in the docs. thanks for your patience. |
Beta Was this translation helpful? Give feedback.
-
|
Small fix/requests for the logger pages, in order of priority:
Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the feedback, most of the things here are working as intended due to implementation details and also the way it is designed |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible to maybe add a scaling feature to the Frigate+ image reviewing section in the Frigate UI? Maybe allow for folks to make the images larger to do a quick scan to see if anything needs to be submitted as false positives and true positives in other means? Today I am working to give back by training as many images as possible and use API calls to send events to F+ only after I've weeded out the false positives but it would be nice to quickly scroll through the images and even using the zoom in on browser makes the rest of the web UI blown out. |
Beta Was this translation helpful? Give feedback.
-
|
In for this as well. I find the images are too small to be able to read the text - I'm not sure if it's a cat, how confident the model was in the detection, the area of the box, etc. All useful for tuning detections. |
Beta Was this translation helpful? Give feedback.
-
|
One of the things I loved about events in 0.13 was the images for when the object entered/left each zone. I think this topic is to be eventually addressed in #11399 ([UI] Screen to solve the goal "why was this review item created). Is there any way manually figure this out until addressed? edit: Manually logging every event update via MQTT notwithstanding ;) Reason: In 0.14, I have had a few reviews where something entered a zone and I can't figure out exactly how/when (likely bottom of object obscured from view), and I'm trying to figure out how to fix my config to correct for it. |
Beta Was this translation helpful? Give feedback.
-
|
There's no manual way to figure that out at this time. Feel free to leave a thumbs up on the feature request! |
Beta Was this translation helpful? Give feedback.
-
|
i have one wireless camera (Amcrest IP4M-1041B) that I cannot seem to get working with two-way talk via iOS. It was previously working fine with frigate-hass-card via Home Assistant. If i load the camera, and click the microphone button it goes blank (it needs to reload or something I assume--frigate-hass-card did this as well) but then never loads up again. I have to go back to the live home screen then click on the camera again to even view the video again, but clicking on the microphone button causes the same issue to re-occur. Any ideas? I've already tried the latest go2rtc to see if it was on that end of the spectrum and ive also tried elimating the go2rtc:
streams:
garage:
- rtsp://****:****@192.168.**.**:554/cam/realmonitor?channel=1&subtype=0
- ffmpeg:garage#audio=opus
cameras:
garage:
enabled: true
ffmpeg:
hwaccel_args: preset-nvidia-h265
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp://192.168.**.**:8554/garage
input_args: preset-rtsp-restream
roles:
- record
mqtt:
enabled: false
record:
retain:
days: 14
mode: all
objects:
track:
- person
- dog
detect:
enabled: false
motion:
threshold: 50
contour_area: 50
frame_height: 25
ui:
order: 2
onvif:
host: 192.168.**.**
port: 80
user: ****
password: **** |
Beta Was this translation helpful? Give feedback.
-
|
here is the output: {
"consumers": [
{
"medias": [
"video, sendonly, H264, H265",
"audio, sendonly, MPEG4-GENERIC"
],
"remote_addr": "172.17.19.1:48512",
"sdp": "v=0\r\no=- 1 1 IN IP4 0.0.0.0\r\ns=go2rtc/1.9.2\r\nc=IN IP4 0.0.0.0\r\nt=0 0\r\nm=video 0 RTP/AVP 96\r\na=rtpmap:96 H265/90000\r\na=fmtp:96 profile-id=1;sprop-sps=QgEBAUAAAAMAAAMAAAMAAAMAmaADwIARB8uWu5Gwa5VB;sprop-pps=RAHAc8BMkA==;sprop-vps=QAEMAf//AUAAAAMAAAMAAAMAAAMAmawJ\r\na=control:trackID=0\r\nm=audio 0 RTP/AVP 97\r\na=rtpmap:97 MPEG4-GENERIC/16000\r\na=fmtp:97 streamtype=5;profile-level-id=1;mode=AAC-hbr;sizelength=13;indexlength=3;indexdeltalength=3;config=1408\r\na=control:trackID=1\r\n",
"send": 63366619,
"senders": [
"96 H265, bytes=62062024, receivers=1",
"97 MPEG4-GENERIC/16000, bytes=527091, receivers=1"
],
"type": "RTSP passive consumer",
"url": "rtsp://192.168.42.12:8554/garage",
"user_agent": "FFmpeg Frigate/0.14.0-272a21f"
},
{
"medias": [
"video, sendonly, H264, H265",
"audio, sendonly, MPEG4-GENERIC, PCMA, PCMU, L16, PCML, OPUS"
],
"remote_addr": "192.168.32.103, ::ffff:192.168.2.19, 127.0.0.1:41536",
"send": 748808,
"senders": [
"98 H265, bytes=739255, receivers=1",
"97 MPEG4-GENERIC/16000, bytes=4952, receivers=1"
],
"type": "MSE/WebSocket active consumer",
"user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
},
{
"medias": [
"video, sendonly, ANY",
"audio, sendonly, ANY"
],
"remote_addr": "127.0.0.1:59114",
"sdp": "v=0\r\no=- 1 1 IN IP4 0.0.0.0\r\ns=go2rtc/1.9.2\r\nc=IN IP4 0.0.0.0\r\nt=0 0\r\nm=video 0 RTP/AVP 96\r\na=rtpmap:96 H265/90000\r\na=fmtp:96 profile-id=1;sprop-sps=QgEBAUAAAAMAAAMAAAMAAAMAmaADwIARB8uWu5Gwa5VB;sprop-pps=RAHAc8BMkA==;sprop-vps=QAEMAf//AUAAAAMAAAMAAAMAAAMAmawJ\r\na=control:trackID=0\r\nm=audio 0 RTP/AVP 97\r\na=rtpmap:97 MPEG4-GENERIC/16000\r\na=fmtp:97 streamtype=5;profile-level-id=1;mode=AAC-hbr;sizelength=13;indexlength=3;indexdeltalength=3;config=1408\r\na=control:trackID=1\r\n",
"send": 753311,
"senders": [
"96 H265, bytes=739255, receivers=1",
"97 MPEG4-GENERIC/16000, bytes=4952, receivers=1"
],
"type": "RTSP passive consumer",
"url": "rtsp://127.0.0.1:8554/garage?video&audio",
"user_agent": "go2rtc/ffmpeg"
},
{
"medias": [
"video, sendonly, ALL",
"audio, sendonly, ALL",
"audio, recvonly, ANY"
],
"receivers": [
"0 ANY, bytes=0, senders=1"
],
"remote_addr": "127.0.0.1:41520",
"senders": [
"98 H265, bytes=0, receivers=1",
"96 H265, bytes=0, receivers=1",
"97 MPEG4-GENERIC/16000, bytes=0, receivers=1",
"97 MPEG4-GENERIC/16000, bytes=0, receivers=1"
],
"type": "probe",
"user_agent": "python-requests/2.32.3"
}
],
"producers": [
{
"medias": [
"video, recvonly, H265",
"audio, recvonly, MPEG4-GENERIC/16000",
"audio, sendonly, PCMA/8000"
],
"receivers": [
"98 H265, bytes=62062024, senders=4",
"97 MPEG4-GENERIC/16000, bytes=527091, senders=4"
],
"recv": 63176851,
"remote_addr": "192.168.72.11:554",
"sdp": "v=0\r\no=- 2252262794 2252262794 IN IP4 0.0.0.0\r\ns=Media Server\r\nc=IN IP4 0.0.0.0\r\nt=0 0\r\na=control:*\r\na=packetization-supported:DH\r\na=rtppayload-supported:DH\r\na=range:npt=now-\r\nm=video 0 RTP/AVP 98\r\na=control:trackID=0\r\na=framerate:10.000000\r\na=rtpmap:98 H265/90000\r\na=fmtp:98 profile-id=1;sprop-sps=QgEBAUAAAAMAAAMAAAMAAAMAmaADwIARB8uWu5Gwa5VB;sprop-pps=RAHAc8BMkA==;sprop-vps=QAEMAf//AUAAAAMAAAMAAAMAAAMAmawJ\r\na=recvonly\r\nm=audio 0 RTP/AVP 97\r\na=control:trackID=1\r\na=rtpmap:97 MPEG4-GENERIC/16000\r\na=fmtp:97 streamtype=5;profile-level-id=1;mode=AAC-hbr;sizelength=13;indexlength=3;indexdeltalength=3;config=1408\r\na=recvonly\r\nm=audio 0 RTP/AVP 8\r\na=control:trackID=5\r\na=rtpmap:8 PCMA/8000\r\na=sendonly\r\n",
"senders": [
"8 PCMA/8000, bytes=0, receivers=1"
],
"type": "RTSP active producer",
"url": "rtsp://192.168.72.11:554/cam/realmonitor?channel=1&subtype=0/",
"user_agent": "go2rtc/1.9.2"
},
{
"medias": [
"video, recvonly, H265",
"audio, recvonly, MPEG4-GENERIC/16000"
],
"receivers": [
"96 H265, bytes=0, senders=1",
"97 MPEG4-GENERIC/16000, bytes=0, senders=1"
],
"remote_addr": "127.0.0.1:60744",
"sdp": "v=0\r\no=- 0 0 IN IP4 127.0.0.1\r\ns=go2rtc/1.9.2\r\nc=IN IP4 127.0.0.1\r\nt=0 0\r\na=tool:libavformat LIBAVFORMAT_VERSION\r\nm=video 0 RTP/AVP 96\r\na=rtpmap:96 H265/90000\r\na=fmtp:96 sprop-vps=QAEMAf//AUAAAAMAAAMAAAMAAAMAmawJ; sprop-sps=QgEBAUAAAAMAAAMAAAMAAAMAmaADwIARB8uWu5Gwa5VB; sprop-pps=RAHAc8BMkA==\r\na=control:streamid=0\r\nm=audio 0 RTP/AVP 97\r\na=rtpmap:97 MPEG4-GENERIC/16000/1\r\na=fmtp:97 profile-level-id=1;mode=AAC-hbr;sizelength=13;indexlength=3;indexdeltalength=3; config=1408\r\na=control:streamid=1\r\n",
"type": "RTSP passive producer",
"url": "rtsp://127.0.0.1:8554/e6a497d938525699a18b60f310b825d2",
"user_agent": "ffmpeg/go2rtc"
}
]
} |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 not in a hurry for a solution here, but do you have any thoughts on what might be going on? |
Beta Was this translation helpful? Give feedback.
-
|
Your camera is h265 so webrtc is not supported it seems. The camera is producing the correct backchannel |
Beta Was this translation helpful? Give feedback.
-
|
correct, ive changed the cameras to h265 to save on bandwidth lately. on iOS, i've enabled all the advanced Safari feature flags for h265 webRTC so it should work? Not sure how to determine what else might be happening. I dont have any issues viewing the other h265 streams or enabling sound on them, its only when trying to enable microphone on specifically the garage camera this happens. |
Beta Was this translation helpful? Give feedback.
-
|
Does it work in the go2rtc dashboard? Are you connecting to frigate via https? |
Beta Was this translation helpful? Give feedback.
-
|
Loving the new UI. I would completely ditch my dashboard but I can't seem to use the 2 Way Audio from my Reolink doorbell from the frigate ui. Is this possible? |
Beta Was this translation helpful? Give feedback.
-
|
this is something that would be reported as an issue to go2rtc and fixed there. let's try one other thing though, open up the live stream in frigate and while that is happening open the |
Beta Was this translation helpful? Give feedback.
-
|
Stupid question, is go2rtc included in the ha addon or do I need to install it? You said dashboard never knew there was one |
Beta Was this translation helpful? Give feedback.
-
|
Yes it's included. You'll need to map port 1984 in the addon settings to view the dashboard |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help. I had a custom binary apparently. I deleted it and now it works |
Beta Was this translation helpful? Give feedback.
-
|
Any way to get bell press as a sensor? |
Beta Was this translation helpful? Give feedback.
-
|
What version of go2rtc is bundled with 0.14? Just curious how current it is as I started running the recent releases externally with 0.13.x as they were a little more stable with my cameras. Obviously I could continue to do that if needed but I prefer to not have to maintain external dependencies if not needed. |
Beta Was this translation helpful? Give feedback.
-
|
1.9.2 currently, and I am testing 1.9.3 |
Beta Was this translation helpful? Give feedback.
-
|
First off, the new UI and functionality are looking great. Well done. I've been using this since beta1. I am truly looking forward to this going stable. This and another Frigate+ base model update or two and I feel like I'll finally fully replace my Unifi NVR. My biggest gripe right now, which is a fairly big one, is that it has gotten much harder to usefully submit to Frigate+. Previously I could skim through and submit the lowest confidence true positives and highest confidence false positives. Now I can't see the score, and half the time I can't see the object either, because they're too small. It also just feels clunky that this is separate from the Review page. I review all the events, then... I go review all the events again on the Frigate+ page, but now they're harder to see? |
Beta Was this translation helpful? Give feedback.
-
Related to this, the Frigate+ page makes you feel like you have to submit each image as either a true or false positive, which I suppose isn't the intention, because many of the images and detections will be very similar and won't add much to the model. Maybe there should be a way to dismiss images you don't want to submit? What is the intended review workflow? Also related, it would be nice if there was a more straightforward way to find and submit false negatives. Currently, unless I've missed something, the only way is to look for them manually, save a frame and then submit it through the Frigate+ web app. |
Beta Was this translation helpful? Give feedback.
-
|
reviewing what has happened on your cameras and submitting true / false positives are two different goals. The objects are combined for review items but this would make the UI for submitting to frigate+ really complicated and detract from the usefulness of the review flow itself due to the relevant filters, interaction, etc. being entirely different Eventually the entire frigate+ submission flow including annotating the images will be done inside of the frigate+ UI itself. You can also sort by score and filter by the score range making it easier to find what to submit. I personally have had no issues picking out false positives and submitting those skimming through the frigate+ view |
Beta Was this translation helpful? Give feedback.
-
Maybe I just misunderstand something, but I don't see why they are different? If I'm reviewing the detections on my cameras, and one of them is a tree detected as a car, why wouldn't I just want to click the "nope" button right there? I understand that the reviewed events are videos rather than frames, but that actually sounds more useful to me. Sometimes I actually want to submit a different frame from the event than what is chosen in the Frigate+ view. If I could just scrub through the event video and submit multiple samples, that sounds great.
Again this sounds like a positive to me in the long run, if the UI were there to support it. My other biggest issue with Frigate+ right now is #8229. I pretty much never "confirm" images from my street-facing cameras anymore, because there are always like 6 cars to draw boxes around as a baseline. If there are multiple objects tagged / boxed in one frame of the event to be submitted, that sounds... good. It would then need the ability, either locally or on the Frigate+ website, to mark individual bounding boxes as negatives rather than the frame as a whole, but that's it? And then submitting, at least the way I do it, would be much faster? I'm also fully open to the possibility that I've been doing something wrong / misunderstanding something this whole time, and if so I would love to hear it.
Agreed, I did start using the score range filter and that does help. Two relatively small things that I think might make that workflow easier are:
|
Beta Was this translation helpful? Give feedback.
-
because the filters useful for just checking your cameras to see what activity happened vs looking at each individual objects, their bounding box, their score, etc. are different. When I am out and about I also have no interest in submitting false positives at that time, but I do want to check and see what has happened on my cameras. The view that is best at one thing and the view that is best at another are not the same. Especially as more feature for submitting to frigate+ are implemented.
except that is not how it works, the frame that is saved for one object (which also means the metadata like bounding box and score) is not the same for the next object. So again, there is no crossover. It will only get easier as the flow is improved and new features like automatic bounding boxes is added, but that will only reinforce the need for the views to be separate. |
Beta Was this translation helpful? Give feedback.
-
|
So far I am enjoying the new UI interface and I do like its streamlined and user-focused approach. The new auth system is a nice bonus on top of that, no more worries of exposing Frigate to the open internet without proper authentication. Having all the cameras on the front page switch when there's motion and making them group-able is all I wanted improved from pre-0.14's UI. Yet they gave so much more. The live view is much more focused on the camera's view. The ability to zoom in makes it much better than the old UI's. I like the new Review page and being able to watch recordings/events throughout the day. Switching from two separate pages, of "Recordings" and "Events", to one page that the recordings with the events highlighted is a great improvement. Having exports be a searchable page where exports have their own names, along with the ability to both delete and re-name is nice. Not really anything to complain about there. Frigate+'s page is okay. I wish a more robust system of submitting images was implemented. Such as editing the image's bounding boxes to fit objects and adding other bounding boxes, just like Frigate+'s site. Though a central hub for submitting images is nice, and I understand the local hosted frigate and the Frigate+ site only interact via an API. Overall, I'm pretty happy. Still getting used to the new interactions and behavior but overall it's enjoyable. Now that the UI has been overhauled, that opens future opportunities in the future. Personally I can't wait until a UI camera/advanced configuration is made. |
Beta Was this translation helpful? Give feedback.
-
you can right click on an event in the reviews page and press "export" without using the timeline at all. You can also do this on the events list inside of the recording viewer |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your feedback! We've worked hard on this massive overhaul, and there's much more to come in future versions. |
Beta Was this translation helpful? Give feedback.
-
Oh! Apologies, still figuring out the new UI 🙃 |
Beta Was this translation helpful? Give feedback.
-
|
I think I have found an issue with the UI on 0.14 beta 2 related to changing object type on an existing object mask. Using chrome on android, mobile version of frigate UI, when attempting (within Masks/Zones) to change the object type of an existing object mask's object type, on a camera different to the one initially/default selected, the change in object type is not committed after save and frigate reboot. I have not attempted on desktop/non mobile version.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the report, this has been fixed for the next beta. |
Beta Was this translation helpful? Give feedback.
-
|
Is timelapse export hidden somewhere in the new UI? I only see the export which doesn't give you the timeline option |
Beta Was this translation helpful? Give feedback.
-
|
No, it's not available. More info is in the FAQ in the release notes. |
Beta Was this translation helpful? Give feedback.
-
|
I found it, in the second beta FAQ after pressing view more… easy to miss. Thanks. I will paste it in here so others are aware and don’t need to go on the treasure hunt. What happened to the timelapse export feature? |
Beta Was this translation helpful? Give feedback.
and others
-
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.
Updated Documentation
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
Beta Was this translation helpful? Give feedback.
All reactions