Replies: 18 comments 142 replies
-
|
Just going to write a comment of appreciation for the manual / API events. By having an event on doorbell press I am FINALLY getting consistent clear face pictures for doubetake.. Before I was getting fairly off to the side profile pics as people waited, but just about everyone looks directly at the camera / button as they press it. |
Beta Was this translation helpful? Give feedback.
-
Also for clarity in my example there are some redundant values. My event is called doorbell and so is the camera. Likewise I define a default of 60 for the duration in case none is passed but in my example I pass a duration of 60 but it could be what ever you want. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, Do you know if there is a retention policy for manuals calls, does it follow the camera defined one? |
Beta Was this translation helpful? Give feedback.
-
|
yes, it follows whatever is set for the camera or you can set it for that specific label |
Beta Was this translation helpful? Give feedback.
-
|
One important thing to note is that manual events do not generate recording segments. YOu need a recording policy of all or if you have motion set as the recording type there must be motion at the time of the event. This is a limitation of manual events and it confused me as I expected them to record ALWAYS but events happen on top of recordings with the way frigate works. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for sharing. It works like a charm. Is there a way to grab the snapshot of the created event from Home Assistant? |
Beta Was this translation helpful? Give feedback.
-
|
I saw some of the new API changes and one of them was Submits the snapshot of the event to Frigate+ for labeling. I tried to use a simple bash loop script to send a bunch of images I know are valid to Frigate+ so that I can go and verify and save them pretty quickly hoping the Frigate bounding box would be sent if I included a include_annotation=1 in the POST but all the ones I tested uploaded with no bounding box. I know there is a separate function for false_positive but are my expectations wrong? Here is my super simple bash script for testing: Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
You need to set the type to json with the json header. |
Beta Was this translation helpful? Give feedback.
-
|
And the include_annotation is a json body arg not a query arg. |
Beta Was this translation helpful? Give feedback.
-
|
hey, |
Beta Was this translation helpful? Give feedback.
-
|
I found a small casting issue that will be fixed
|
Beta Was this translation helpful? Give feedback.
-
|
Anyone else having Frigate never loading after upgrading to beta3 from beta2? I seem to see nothing in my logs, but haven't had time to dig deeper yet... reverting to beta2 got me going again frigate | s6-rc: info: service s6rc-fdholder: starting |
Beta Was this translation helpful? Give feedback.
-
|
To be clear, it was 3 hours the first time. Subsequent startups seem to take 10-15 minutes on the same version. After upgrading to another new dev version I let it go 30 minutes and gave up and reverted since I was busy. The events page was also super sluggish on the last dev version I ran. Beta 2 startup time is 1-2 minutes and events page is quite snappy. |
Beta Was this translation helpful? Give feedback.
-
|
Are you defining the camera detect resolutions in your config? In beta2 I'd expect the startup time to be basically instant unless you are not defining detect resolutions in which case opencv has to be used to pull them in. Based on what you're saying though, it will likely make sense to limit the number of timeline entries processed on each startup and automatic background update of the region grid |
Beta Was this translation helpful? Give feedback.
-
|
I am defining detect resolutions in config, I am saying startup time as till birdseye starts working and cameras streams are all loaded and recording. The 1-2 minute startup I had before was on par with the fastest of any other software I've tried (I tried Shinobi and iSpy and Blue Iris before settling on Frigate). Most of my streams are loaded over a VPN so I don't know if that slows it down, but also on startup I do notice CPU is at 100% for quite some time on all 32 cores (it settles down to about ~50% usage once booted), so it may just be a resource limitation (again, not unique to Frigate). Email just went through, I just sent another with my latest config file but I don't think I've updated it since the last time you've helped me! |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that explains it a bit better, I have a couple changes that should help with this |
Beta Was this translation helpful? Give feedback.
-
|
@niyazFattahov I believe Nick got the issues I was having resolved in cc5357a You may have a one time startup time of a few hours but after that it should be snappy again once the DB changes get applied. |
Beta Was this translation helpful? Give feedback.
-
I have a giant shit ton of events lol. I left it running for 15 minutes with no output, how long should I try leaving it for? |
Beta Was this translation helpful? Give feedback.
-
|
it can depend on a lot of things, I tested it with my setup that had a few thousand events and it only took a few seconds. Based on your number of cameras and events it may be longer. If you want you can enable debug logs for |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Seen this in the log, anything to be concerned on or checked? 2023-10-30 17:13:21.574932954 [2023-10-30 17:13:21] ws4py ERROR : Failed to receive data |
Beta Was this translation helpful? Give feedback.
-
|
we are aware of it but it is nothing to be worried about, it is not causing any problems |
Beta Was this translation helpful? Give feedback.
-
|
Just put up the Halloween decorations and I am on beta 3.. object tracking might need some work.
Setup.. The Orange, Green and Purple zones are required for events, and the yellow and brown/grey are included as well as required for snapshots.
Top half of this area is already motion masked due to the sun and birds, is is my revised motion mask now the hanging decoration was poking just below it when this event happened last night.
Yet this flying "person" filled up my event list last night as he "entered and left" those required zones
Tracking moved to the trees Guess he was busy possessing objects. Reality here is the wind however it doesn't leave me with much option to filter this out.
The detection moving to such far away and different objects seems like a object tracking issue to me. Even with the false positive the fact it persistent onto several different objects is problematic. Maybe setting a sky zone with a higher person threshold and maybe upping my min score over all will help but I find with lower min_score my persistence suffers with people and I way more individual events global settings doorbell config below |
Beta Was this translation helpful? Give feedback.
-
|
Object tracking like this is very difficult issue, you can have cases where someone opens a car door and is obstructed that you would want to be detected as the same person even if the shape (legs underneath the car door) is different. But then you have cases like you are showing where you would want the distance to be different. It is worth noting that if you had these "person" objects detected separately then you'd just have even more events as each one would be its own. It is also worth noting that the improvements to object detection and object tracking had nothing to do with the distance logic (which is what decides if a detected object is the same or a different object) or directly reducing false positives. It was mostly around initial regions when motion is detected, and true positive stationary objects like cars being detected more accurately. With the COCO model to me it seems like a lot of these false positives could be improved by using a person object mask in the sky (where no real person would be) and a small person mask at the bottom center of each tree. |
Beta Was this translation helpful? Give feedback.
-
|
If I understand it correctly threshold will start an event but min_score will be used to continue it correct? IE the sky object in this case exceeded the threshold but he other objects only had to exceed the min_score correct as they where "tracked" as the same event / object? I can also try bumping up min score a little I guess. I will try some person masks as well, however I generally try to avoid using them., |
Beta Was this translation helpful? Give feedback.
-
|
yes that is correct, a median score of threshold is required for the event to be created, but min_score is what is used to decide if the detection should be considered or immediately thrown out. So if the min_score is too high then lower scoring true positives may be thrown out, and if it is too low then false positives may be detected. |
Beta Was this translation helpful? Give feedback.
-
|
After upgrade from beta2 to beta3 I see the following in birdseye: Screen.Recording.2023-10-30.at.5.54.11.PM.mov |
Beta Was this translation helpful? Give feedback.
-
|
your birdseye resolution is not using a standard aspect ratio, I tried to fix this but it seems to cause an issue with pixel mapping so instead the config will be considered invalid |
Beta Was this translation helpful? Give feedback.
-
|
So I'm getting the same issue as aneisch with the random colors corrupted birdseye view... my resolution was 1920x1200... I tried deleting the resolution and let it do what it wants by default, and now whenever 2 of my panoramic cameras are appearing at the same time, every single camera goes onto the same line... infact, sometimes its with just one... but its a little unpredictable then. The panos have a detect resolution of 1920x536 I did have some funkiness where it had half the screen empty under the old algorithm for seemingly no reason (usually when my reolink 2 duo was active on the screen) but this got worse... you want my full config again or is there anything else to try first? The motion detection does seem to be MUCH better for me with the regions. My cameras that always were active at night due to bugs being attracted to the light are finally not activating the motion detection... (assuming I'm not missing any real motion events, lol, I'm getting far fewer motion events, but it also just so happens that one of my facility door locks failed keeping everyone locked out so its not super unexpected 😣 ) |
Beta Was this translation helpful? Give feedback.
-
|
Here's a simple example where I think its fairly obvious it should be on 2 lines: Resolution of first camera is 1920x536, second is 1920x1080 |
Beta Was this translation helpful? Give feedback.
-
|
I've already put up a new addition to the logic. But will need to force resolutions to fit standard aspect ratios. |
Beta Was this translation helpful? Give feedback.
-
|
Alright, cool, just started running that version and after running for 5 minutes it seems better then ever! Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
In beta 2, my dog would get identified correctly, when he was in the front yard...
with beta3, he gets the red bounding box... but never gets identified. I have not changed my config... |
Beta Was this translation helpful? Give feedback.
-
this sounds like the bug I just described fixing, nothing to do with the regions that are calculated. beta4 will fix the bug and offer tools for seeing the grid |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good, will check it again with beta4, would make sense for the road as well if the grid is only based on events. As passing cars will not generate them but cars coming home into the driveway will. |
Beta Was this translation helpful? Give feedback.
-
|
I don't expect that to be a problem, the grid is based on timeline events. So they do require the event to be saved but timeline events can include times when the object is outside the zone like when it is first detected, last detected, becomes stationary / active, etc. My camera with my driveway has no issues with this
|
Beta Was this translation helpful? Give feedback.
-
|
Here is a screen shot with the grid for the same camera. 
Comparing to yours, there are some obvious holes in the grid and this actually holds true for all my cameras. I am guessing that frigate is going to struggle identifying things that are outside of the grids... is that a correct thought? I currently have my Thanks for coding the grid overlay.. I think this will go a long way to understanding how things work. |
Beta Was this translation helpful? Give feedback.
-
|
Your whole grid is using the model size so I don't think this should be causing any issues. I'd expect the behavior you were seeing last time on beta 3 should be fixed.
No, it simply means when there is motion in those areas it will use whatever size region holds the motion boxes instead of using an optimized size. However in the case of this camera they're all 320 anyway so the grid isn't going to change any behavior.
No, these come from timeline items so the only times grids will get created is when an object is detected, lost, enters a zone, or becomes stationary / active. |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, having an issue with 13beta3 and Codeproject.AI On the Frigate side I get the following On the Code Project Side I get this So from what I can tell information is being communicated between the two, but Frigate is saying that its timing out. Any suggestions? Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Then I have it way too high. In the config, I have it as 1.2 when it should be 1.002 |
Beta Was this translation helpful? Give feedback.
-
|
Like I said there will be additional latency for the transmission as codeproject just shows the inference time itself |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha, Thanks. Again awesome work guys |
Beta Was this translation helpful? Give feedback.
-
|
Just as a heads up, I am speaking to the guys over at CodeProject about the slow inference. Hopefully this would get fixed soon. Its interesting though. They are using Tensor libraries with the Coral instead of COCO libraries. I wonder if that is whats making the difference. Anyway. Just wanted to leave this info. |
Beta Was this translation helpful? Give feedback.
-
|
Seeing this morning that my disk is full and old recordings aren't being discarded to make more room: My config here |
Beta Was this translation helpful? Give feedback.
-
|
Is this on beta4 or after the recent commit that I did? |
Beta Was this translation helpful? Give feedback.
-
|
This is beta 4. My disk was 100%, so I mnaully cleared some space and upgraded to beta 4 and now it is working as expected. |
Beta Was this translation helpful? Give feedback.
-
|
Update to beta4 and I'm now seeing the cleanup 2023-11-10 03:57:46.409960698 [2023-11-10 03:57:46] frigate.storage INFO : Less than 1 hour of recording space left, running storage maintenance...
2023-11-10 03:57:49.883490882 [2023-11-10 03:57:49] frigate.storage INFO : Cleaned up 3739.8999999999996 MB of recordings
2023-11-10 05:57:50.112733089 [2023-11-10 05:57:50] frigate.storage INFO : Less than 1 hour of recording space left, running storage maintenance...
2023-11-10 05:57:52.622767832 [2023-11-10 05:57:52] frigate.storage INFO : Cleaned up 3739.700000000007 MB of recordings
2023-11-10 07:42:52.784851529 [2023-11-10 07:42:52] frigate.storage INFO : Less than 1 hour of recording space left, running storage maintenance...
2023-11-10 07:42:55.499798695 [2023-11-10 07:42:55] frigate.storage INFO : Cleaned up 3739.499999999992 MB of recordings
2023-11-10 08:57:55.633852147 [2023-11-10 08:57:55] frigate.storage INFO : Less than 1 hour of recording space left, running storage maintenance...
2023-11-10 08:57:56.160178640 [2023-11-10 08:57:56] frigate.storage INFO : Cleaned up 3740.8999999999924 MB of recordingsOne question I have - is it possible to configure how much disk Frigate tries to consume? For example, my disk space is currently sitting at 99% - is there a way to tell Frigate to start a cleanup at 80% instead? |
Beta Was this translation helpful? Give feedback.
-
|
No it's not possible, this is because this isn't meant to be a full frigate disk usage feature. It's meant to be a last ditch effort to ensure frigate can keep recording. It's still recommended to just configure the retention period to fit the amount of space that you want. |
Beta Was this translation helpful? Give feedback.
-
|
Makes sense. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I didn't see it mentioned, but were there any changes to go2rtc from beta2 to beta3? I often stream a couple cameras to a browser using the "/live/webrtc/stream.html?src=" method through frigate and have noticed with beta3 the playback is really choppy and will lose like up 10 seconds at a time quite often. Nothing stood out to me in any of the logs. When I switch back to beta2 the issue is gone. BTW, I'm also routing it all through a traefik https proxy located on the same host if that matters. Any ideas on how to troubleshoot this? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, go2rtc was updated to 1.8.1 |
Beta Was this translation helpful? Give feedback.
-
|
Ok, since it looks like beta2 was 1.7.1 and my issue started with beta3 (1.8.1) I think this bug with 1.8.X may be causing it. I'll try using the custom go2rtc version configuration option to go back to 1.7.1 with beta3 when i have time to see if that's my issue. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
yes, I have also seen a couple reports on go2rtc for the same so it may be fixed in a future update |
Beta Was this translation helpful? Give feedback.
-
|
On the other hand, being on 1.8.1 fixes an issue with go2rtc with grabbing a full frame jpg from certain cameras. Nice to not have to override the go2rtc version in beta3... |
Beta Was this translation helpful? Give feedback.
-
|
Just to follow up, manually configuring beta3 to use go2rtc 1.7.1 did fix my issue. Nice to have the flexibility to use any version of go2rtc! |
Beta Was this translation helpful? Give feedback.
-
|
When trying to watch a clip for an in progress long running event, I get a misleading error message. I think the issue is really that the clip is too long to view. I don't think this issue is new to Beta 3, I seem to recall having difficulty looking a long events in the past. So the question is: Should long running (multiple hour) events be viewable? If not, should the error message be more descriptive? (Like maybe "clip too large" or "not enough temp space" or whatever is the underlying issue that prevents long clips from playing.) If long running events should be viewable, then I have an issue in my environment or there is a bug... Here is what I see when I try. Nothing shows up in the logs when I try to view the event. 
|
Beta Was this translation helpful? Give feedback.
-
|
In my environment, I have the recording storage NFS mounted over the network, so it's not super fast, if that matters. Short clips play fine. |
Beta Was this translation helpful? Give feedback.
-
|
This is some what expected but a difficult issue to solve around the max number of segments |
Beta Was this translation helpful? Give feedback.
-
|
Anyone test the auto tracking? Really cool that's being added. I've been hankering to buy the dahua 25x ptz with auto tracking, but if it works well in frigate I could get something smaller and cheaper. |
Beta Was this translation helpful? Give feedback.
-
|
The release notes have 2 different demo videos that are from the auto tracking feature in frigate. There are multiple people who have been testing it in the cameras channel of the HA discord. |
Beta Was this translation helpful? Give feedback.
-
|
You'll want to make sure you pick up a camera with robust ONVIF support if you decide on something other than the Dahua. Many camera manufacturers say their firmware fully supports ONVIF, but the implementation ends up beings subpar. Amcrest, Dahua, and Hikvision seem to be the best at it, according to user reports. But be sure to check out the autotracking docs and growing list of supported cameras before making a purchase. |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 @blakeblackshear On all of my camera's I'm missing the first 20 minutes or so of footage. Segments are still on the disk, Frigate doesn't play them. Also, all events that are within the first 20 minutes of that specific hour can't be played anymore. Problem started on 11/03 on 15:00. All recordings before that date seem to be there. |
Beta Was this translation helpful? Give feedback.
-
|
That still doesn't explain why the entries in de recordings table are missing? |
Beta Was this translation helpful? Give feedback.
-
|
Yes it does, 2023/... < 00.01.mp4 so that file wasn't included in the list so frigate thought it was deleted from the folder even though it wasn't, so it was removed from the DB |
Beta Was this translation helpful? Give feedback.
-
|
This problem should affect more people than just me I would say... |
Beta Was this translation helpful? Give feedback.
-
|
Yes I see it too |
Beta Was this translation helpful? Give feedback.
-
|
I downgraded to beta 3 this morning, I assume beta 5 will be out soon? |
Beta Was this translation helpful? Give feedback.
-
|
Didn't see a beta4 thread but I am running beta4 and noticed something weird today with an on-going event related to a car. I have my Driveway camera broken up into two zones: This morning as my wife was leaving her minivan triggered the car in the Front_Yard zone as expected but for some reason the event went on much longer than expected. I can see in the event snapshots shows the following:
Skipping other stuff... Car enters the street according to Frigate:
Then the weirdness starts as you can see below it hops to a car in my neighbor's driveway in the Street zone and becomes stationary.
At this point Frigate is flopping between active and stationary all in the Street zone until finally this:
Overall, the event lasted for 29m and 7s and I've never seen this recently with my other car come and go from the garage onto the Front_Yard zone. |
Beta Was this translation helpful? Give feedback.
-
|
the car drove by occluding the other car and the tracker became confused about which car was which. The new tracker is much smarter but cases where one object occludes another is very challenging. There are ways this can be improved in future versions of frigate |
Beta Was this translation helpful? Give feedback.
-
|
Would doing a min_size of a giant number in the Street zone for car help as a work around? |
Beta Was this translation helpful? Give feedback.
-
|
no that wouldn't help because the objects are still detected and tracked, whether or not the object is currently in a zone is irrelevant to the tracker |
Beta Was this translation helpful? Give feedback.
-
|
Hi: I don't know if this a issue or something not implemented yet a unraid user pointed me here that the Is there something missing? Are we doing something wrong? I see also this opened #2365 Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I run the same 1440 time and I've not seen my array spinning up every hour, I think more information would be helpful to how the conclusion was drawn that it is frigate running and that the files are deleted every hour. Also, would be good to see the config |
Beta Was this translation helpful? Give feedback.
-
|
I added a log to the recordings cleanup and it is not running once an hour time is now 08:15 it is important that you are setting the expire_interval at the global level, setting it at the camera level does nothing |
Beta Was this translation helpful? Give feedback.
-
|
Yes is see there is something else spinning up the array. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I just came across the use_experimental feature in the UI and love the "scrubbing" feature but noticed in the live view the audio isn't working. When I switch back to it being False it works as expected. Not sure if this is expected behavior but since it is use_experimental I wanted to proceed with caution and awareness. |
Beta Was this translation helpful? Give feedback.
-
|
It only supports jsmpeg which doesn't support audio |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! That makes perfect sense. |
Beta Was this translation helpful? Give feedback.
-
|
it would be nice to have a beta 5 as beta 4 problem fixed hopefully |
Beta Was this translation helpful? Give feedback.
and others
-
Beta docs for this release: https://deploy-preview-6262--frigate-docs.netlify.app
Major Changes For 0.13.0
Security Advisories
The Github Security Lab team reached out to report the following security vulnerabilities.
config_saveandconfig_setrequest handlers (GHSL-2023-198)/<camera_name>API endpoints (GHSL-2023-195)load_config_with_no_duplicatesoffrigate/util/builtin.py(GHSL-2023-190)Exploiting these vulnerabilities requires the attacker to both know very specific information about a user's Frigate server and requires an authenticated user to be tricked into clicking a specially crafted link to their Frigate instance.
This vulnerability could exploited by an attacker under the following circumstances:
If you haven't click any links to your Frigate server from unknown sources, there is no reason to believe that you have been compromised.
I have enabled the private vulnerability disclosure features inside Github for the project as well as the automated CodeQL scanning features to identify future issues.
Changes since Beta 2
Breaking Changes
interval: 0will need to delete this field from the config or increase the valueNOTE: Some users have reported migrations taking a while and frigate frontend is not available until the migrations are complete.
frigate.db: Due to the support for network shares in HA OS and the popularity of storing recordings on a NAS in general, the database has a new default location of/config/frigate.db. This change is going to be done for existing users too, so frigate will automatically move the db for you.For Frigate Addon Users:
The migration is handled automatically and no action is required from the user.
For Docker Container Users:
The migration is handled for you, but you must make sure that the docker CLI or docker-compose binds the entire
/configdirectory and not just the/config/config.ymlfile.For example, if your current volume mapping is
- /host/path/config_folder/config.yml:/config/config.ymlit should now be- /host/path/config_folder/:/config/record -> retain_daysconfig has been removed, this should be migrated torecord -> retain -> daysif you have not already./statshave been moved to their owncamerasblock. This only affects users that were directly reading from the/statsdata via the API or MQTT.Frigate+
Frigate+ Model Launch
Frigate+ models are now rolling out by invitation. If you would like to be invited for early access to purchase a subscription, please send an email to [email protected] from the email address on your Frigate+ account. For more information, see this discussion.
False positive submissions
You can now submit false positive detections to Frigate+ for training feedback. Note that you will still need to login to your Frigate+ account and verify the images to ensure all relevant objects are labeled before the image will be used during training. Confirming the object is a true positive will also upload the image.
Models
Frigate+ models are almost ready for launch, and this release has support for automatically downloading from Frigate+. The model and related information are stored at
/config/model_cache. Once Frigate+ models are launched, you will be able to use the model id in your config.Community Supported Boards
In version 0.12 Frigate gained support for Intel iGPUs via OpenVINO and for Nvidia GPUs, this was a great step forward for compatibility and for more users being able to use Frigate effectively. There are many other devices, including dedicated SBCs (Small Board Computers), that Frigate could support but the maintainers do not have the time or hardware to support.
The community supported boards framework will allow community members who want to contribute to create and manage support for a particular board. This will allow Frigate to support more devices while allowing the maintainers to focus on improving the core of Frigate.
Nvidia Jetson Support
@madsciencetist is the first to contribute a community supported board build by adding support for Jetson 4.6 and Jetson 5 devices!
More information can be found in the detector docs on how to set this up.
https://deploy-preview-6262--frigate-docs.netlify.app/configuration/object_detectors#nvidia-tensorrt-detector
Object Tracking & Motion Detection
There have been many improvements to object tracking and motion detection which make Frigate more efficient and can reduce false positives.
New Object Tracker
Frigate now uses Norfair for object tracking, this means that object attributes like size, width/height ratio, and position are used to intelligently track objects. ID swapping between tracked objects is greatly reduced in situations where a car in the driveway was confused with a car passing in the street.
Improved Motion Detection
Frigate's motion detection is now more efficient. Motion detection will also re-calibrate for flashes like lightning or when the camera switches from color to IR mode or it is moved via PTZ. This reduces CPU usage during these changes and reduces false positives caused by excessive motion.
Historical Data
Frigate now uses the recordings timeline data to generate an 8x8 grid for each camera. This grid holds the range of expected regions (portions of the image sent to detection) for that area of the camera frame. This helps to improve accuracy of detection after motion has occurred and can reduce false positives in some cases.
The grid is updated on each startup and every day at 2 AM for each camera that is enabled.
Minimum Time For Zone Presence
Frigate now has a configurable field for the minimum amount of time an object needs to be in a zone before it is considered in a zone. For example, currently in Frigate if you have a front_yard zone and someone is walking by and briefly steps into the front yard Frigate would create an event for this. However, you may prefer for events to only be created if a person is in the front yard for multiple frames before creating an event.
Recordings Improvements
There have been a number of improvements to the management of recordings
Recordings Exporting
Frigate now supports exporting recordings in standard format or as a time-lapse. Exported recordings are stored in
/media/frigate/exportsand are downloadable from the UI.Recordings Timeline Metadata
Frigate now saves metadata for key moments in an event such as when the tracked object is detected, enters or exits zone, becomes active / stationary, and leaves. This metadata is used to overlay on top of the recordings so it is easy to see what was detected and where. Note that the timing of the bounding boxes will likely be slightly off because it is based on the detect stream, but overlayed on the record stream. The
annotation_offsetvalue in the config can be used to adjust for any differences.Internal Processing Improvements
There have been many improvements to the recordings management process to make it faster and more efficient:
sync_on_startupenabled which will check for recordings in the db that are not on the disk and delete themAudio Events
Frigate now supports audio events via YamNet. Over 600 labels are included so there are too many to list here, but Frigate can listen to a cameras audio feed to create events and update MQTT when speech, yell, fire alarm, dog bark, etc. are heard. Version 5.0 of the HomeAssistant integration also supports sensors for these audio detections so automations can be fired when certain types of audio are detected.
Manual Events API
Frigate now supports creating events manually via the API. This means that custom events can be created, for example an event when the doorbell is pressed or a sensor is tripped. The API allows full control of event length, if recordings should be saved, and much more. The request and response can be seen in the documentation.
Curl Example:
PTZ Control
Frigate now supports PTZ cameras.
Basic PTZ Autotracking
https://deploy-preview-6262--frigate-docs.netlify.app/configuration/autotracking
Along with Frigate's improved tracking algorithm, basic autotracking is now supported. Not all PTZ cameras will support this as relative movement is required (see the docs for more details).
PTZ Controls In The WebUI
Frigate also supports controlling PTZ cameras in the WebUI and via the Home Assistant Integration.
Other Notable Changes:
Images
ghcr.io/blakeblackshear/frigate:0.13.0-beta3ghcr.io/blakeblackshear/frigate:0.13.0-beta3-standard-arm64ghcr.io/blakeblackshear/frigate:0.13.0-beta3-tensorrtghcr.io/blakeblackshear/frigate:0.13.0-beta3-tensorrt-jp4ghcr.io/blakeblackshear/frigate:0.13.0-beta3-tensorrt-jp5Full Changelog: v0.12.1...v0.13.0-beta3
Beta Was this translation helpful? Give feedback.
All reactions