0.14.0 Release #12829
Replies: 47 comments 166 replies
-
|
Saw the notes on "Automatic hardware acceleration", due this: #8470 I've currently disabled hardware acceleration by purpose everywhere. Can I keep it disabled? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, just set it to null or an empty list |
Beta Was this translation helpful? Give feedback.
-
|
can you still submit to frigate plus in this release? |
Beta Was this translation helpful? Give feedback.
-
|
yes, using the Frigate+ page in the sidebar |
Beta Was this translation helpful? Give feedback.
-
|
I must have missed this as i cant see it :) |
Beta Was this translation helpful? Give feedback.
-
|
Something I just noticed when doing an export. If you do a custom range, you can use the mouse to pick the date but if you then try to manually type the time with the keyboard, the date changes to today rather than staying on the date you selected. The only way to specify an exact date and time is by using the date/time picker with the mouse. |
Beta Was this translation helpful? Give feedback.
-
|
I'd suggest creating a separate bug discussion so we can look into it further |
Beta Was this translation helpful? Give feedback.
-
|
First of all, thanks to everyone who put in the work! This might be a silly question. I understand that it's not possible to view older events in the new version. But do I need to delete these manually from the disk, or do they get deleted automatically when the retention period expires? |
Beta Was this translation helpful? Give feedback.
-
|
Events inside of Frigate are not going anywhere, they are just not surfaced in the UI in the same way. Event retention will continue to function in the background just the same as before. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Pacman, I had to delete them manually, would you mind checking yours to see? I had loads of files beyond the retention period, unless I am doing something wrong (quite likely, but I don't think I am this time haha). |
Beta Was this translation helpful? Give feedback.
-
|
Awesome work! Frigate is getting better and better. Even better as every other expensive NVR I know! Congratulations 🎉🎉🎉 Edit: Is there no more way to make you a donation via PayPal? Unfortunately GitHub Sponsors do not accept it anymore. |
Beta Was this translation helpful? Give feedback.
-
|
Really nice new UI. Thanks for the the terrific app. |
Beta Was this translation helpful? Give feedback.
-
|
well what a great update... all this for a shitty UI? |
Beta Was this translation helpful? Give feedback.
-
The recordings are not transcoded, they are literally dumped from the camera to the disk. If your recordings look bad now, maybe you changed settings in your cameras or you are pulling a lower resolution subfeed from your cameras. |
Beta Was this translation helpful? Give feedback.
-
Yes i know, and those were in low res aswell "i could have lived with the low res in the Previews, but it was in live view, the history page, even the recordings it saved was low res," it was full hd in 0.13.2 and low res in 0.14.0 that all i care about, Clearly something was updated in the code between 0.13.2 to 0.14.0 that made something in my config be wrong, and it might have been all the time, 0.13.x might just not have given a fuck and just decided to show it in the cameras full resolution anyway. |
Beta Was this translation helpful? Give feedback.
-
Frigate doesn't send phone notifications, HA doing that for you. You will need to make adjustments to HA to resolve your issues. My guess is your old config involved a lot of copy/pasting and not a lot of actual understanding of the structure of the MQTT events feed. There are a lot of people that would be willing to hold your hands but man, your attitude isn't going to get you very far. |
Beta Was this translation helpful? Give feedback.
-
please elighten me then, this is the config from 0.13.2 that gave me problems in 0.14.0 mqtt: detectors: cameras: version: 0.14 and yes my attitude is shit, i know |
Beta Was this translation helpful? Give feedback.
-
|
You are sharing the Frigate config, but as I said, Frigate does NOT send phone notifications. HA does that. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all ! |
Beta Was this translation helpful? Give feedback.
-
|
PWA-optimized - The UI has been optimized to work as a progressive web app. Pin Frigate to your iOS home screen or install on Android for a full app-like experience. I apologize for my naivety, but how do you "install on Android" the frigate interface? I currently just use the HomeAssistant app with NabuCasa, then just click on the frigate button in the side bar to view my cameras. If there is a way to just click on a app and go right into frigate I will be beyond happy! P.S. this is an amazing update, been following the beta waiting for full release. Can not wait to upgrade when I get back later this weekend. (dont want to remote update, feel like thats tempting fate.) |
Beta Was this translation helpful? Give feedback.
-
|
Is there any docs showing how to set this up? |
Beta Was this translation helpful? Give feedback.
-
|
https://docs.frigate.video/guides/reverse_proxy Shows how to setup a reverse proxy, exposing externally can be done in many different ways and that's outside the purview of frigate |
Beta Was this translation helpful? Give feedback.
-
|
Is a reverse proxy required when accessing from LAN or using a VPN? |
Beta Was this translation helpful? Give feedback.
-
|
It's not required but you need to expose the service as a domain because a PWA can't be pointed at an ip address:port |
Beta Was this translation helpful? Give feedback.
-
|
What would be the easiest way to do that? |
Beta Was this translation helpful? Give feedback.
-
|
I've just updated to v0.14.. I'm pretty amazed about the new features.. everything is working as expected!! But my old recordings, are on my network disk , and now they are not reachable because they were created with v0.13 , aren't they? is there a way to safety delete them to save space? thanks |
Beta Was this translation helpful? Give feedback.
-
|
Your old recordings are still accessible via the History view for your cameras. They will be automatically deleted according to the retention settings you have set in your config file. |
Beta Was this translation helpful? Give feedback.
-
|
It´s supposed to.. but when I select other day than today (today works even with recordings pre-v0.14 update), it doesn´t play.. |
Beta Was this translation helpful? Give feedback.
-
|
you can delete the files manually from the file system if you don't need them |
Beta Was this translation helpful? Give feedback.
-
|
With the new timeline sidebar, I see "02:13:56 PM" but I don't see an option anywhere to show as a 24H clock so "14:13:56" |
Beta Was this translation helpful? Give feedback.
-
|
you can set the time format in the config |
Beta Was this translation helpful? Give feedback.
-
|
I just stop by to thank everyone for the hard work around Frigate. |
Beta Was this translation helpful? Give feedback.
-
|
The new user interface is a step in the right direction, but in its current form it feels like a massive downgrade from a usability point of view. For example: Sometimes you need to find the right frame where you can see a persons face or a license plate as best as possible, especially when the object is moving fast and it's dark. The alerts(clips) are now played inside the "history" view with only a very imprecise timeline to navigate through the video feed (except for +10 and -10 seconds buttons). On PC, you can use the keyboard (arrow keys) for a little more granular control, which is good, but there is still no way for frame by frame navigation. So if you want to pinpoint a certain moment, you have to get close to the right frame and try to hit pause in the exact right moment. An additional seekbar for presicion seeking (frame by frame) would be very useful. Deleting alerts is also very time consuming now, since you have to select every single alert one by one and use the delete button. In addition to the "unselect" button, a "select all" button could be helpful. A multi select feature like in file browsers (shift clicking) would also be great. Another thing I noticed is the filter for zones. I have one zone close to the house, but person detection for the entire driveway. In the previous versions, I could unselect the one zone in the filter and it would show me only clips from outside the zone. This is no longer possible. Isn't it possible to add the "unknown" zone (or whatever it was called before) back, which matches all areas that are not in any zone? I have added a second zone for testing, which covers everything except the first zone. If you apply a filter for Zone2 and then open the filter view again, all other zones are now gone. You have to select "All zones" and apply, then open the filter view again to select the new zone(s) you'd like to view. I think the zone toggles in the filter view should stay available all the time. |
Beta Was this translation helpful? Give feedback.
-
How do you set it up, so zone 1 creates alerts and the rest only detection? |
Beta Was this translation helpful? Give feedback.
-
It's in the new docs. Check them out, a lot has changed. Look at the full config sample and look at the comments. The "review" section is where the magic is. For example I have this in my doorbell camera config: review:
alerts:
required_zones: PorchSo if someone walks down the street and my Doorbell sees them, it will add a "detection" to the review page but not an alert. If this person walks onto my porch, it will trigger an alert. When you speak of "Frigate card", I assume you are talking about a card in HA. I don't use HA so I can't really answerer that for you. I'm only discussing the Frigate UI, specifically, the review page. |
Beta Was this translation helpful? Give feedback.
-
Also worth mentioning that this can be done from the UI under Settings --> Camera Settings. |
Beta Was this translation helpful? Give feedback.
-
|
Yes they can both show up in the frigate card |
Beta Was this translation helpful? Give feedback.
-
Thanks, I gave it a try, but detections are not shown in the clips gallery of the Frigate card. So I tried to use a workaround with zone2 (object mask minus zone1) for filtering purposes. This doesn't work, because an object can enter zone 1 and 2. In fact, everyone entering zone1 has been walking through zone2, so that approach is useless. The only proper way would be to add a filter option called "Without Zone" or something, which would display only alerts for objects the did not enter any zone, like it was possible in 0.13. This should be an easy implementation and is pretty useful imo. The filter list would be something like: Zones:
The last option can be selected regardless of the zones selected before. So if "All Zones" and "Without Zones" is enabled, it shows everything. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe I am not smart enough but I find it almost impossible to draw a zone using the new ui. If I want to have a simple box with 4 corners my assumption would be that I click 4 times and with the 5th click I click on the first point to complete the box. But in most cases that does not work. Only in some random cases the mouse cursor changes and I can complete the box. |
Beta Was this translation helpful? Give feedback.
-
|
That assumption is correct. Are you using Brave browser? If so, you need to disable Brave Shields. |
Beta Was this translation helpful? Give feedback.
-
|
yes that was the case |
Beta Was this translation helpful? Give feedback.
-
|
I am running firgate in k8s the config used to be read only and stored in git and mounted as a configmap file to /config/config.yml. In 0.13 that setup was perfect because frigate itself would not mess with the config. In 0.14 the config is changed on the fly. How are other people handling this issue? |
Beta Was this translation helpful? Give feedback.
-
|
One solution could be that frigate detects that the config file is readonly and says cannot modifiy it but I will write to some temporary config file and the human can look into these changes and move them to git if the changes are good to be persistet. |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing a trend in the comments where people are expecting a complete overhaul of the UI to function exactly like the old UI. You have to stop trying to do your old routines and look at this new UI with an open mind. After a few days of getting used to this new UI, you will develop new routines and fall in love with it. I love how you can click on an alert to see the full size video with the thumbnail videos from other cameras at the bottom, synced to the same timecode. This new UI makes the old UI feel like a toy. |
Beta Was this translation helpful? Give feedback.
-
|
I just wanted to say I have been absolutely thrilled with the latest version. It is so professional and clean looking now. It works so much faster. Everything is amazing. Thank you to everyones efforts in making Frigate what it is today. |
Beta Was this translation helpful? Give feedback.
-
I went from version 0.13 to 0.14 and for some reason people are detected very well, but it has stopped detecting cats and birds, where is my mistake, thanks this issue is driving me crazy |
Beta Was this translation helpful? Give feedback.
-
|
if you remove the required_zones for detections then it should have them show up as detections. If they are not detected at all that could be a separate issue, it's not clear what is going on with the information that has been provided |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'll delete the detection zones, let's see if it detects, thanks for your help, I'll let you know now if I have results |
Beta Was this translation helpful? Give feedback.
-
|
I unchecked both options and it has trouble detecting cats. I see that in debug it frames it, but it doesn't detect it. This comes from the latest version. I downloaded the motion detection tune, and sometimes it detects it, but very rarely. Watching the video live, I see the frame but it doesn't identify it, which it does well with people. |
Beta Was this translation helpful? Give feedback.
-
|
This is my setup config which captures cats very well. One thing to note is cats can be quite fast compared to people so I have mine set to 8fps detection. Personally I would start with no zones. For me cameras are on the drive, then catflaps, and other movable camera. I do use frigate+ and have tuned it but it always detected cats before just with more false positives. These days it always detects a cat that is a cat and some times thinks a persons hair is a cat but along as the cat is a cat bit works I'm good with it. mqtt:
enabled: true
host: 192.168.22.2
port: 1883
# Optional: topic prefix (default: shown below)
# WARNING: must be unique if you are running multiple instances
topic_prefix: frigate
ffmpeg:
# Optional: global ffmpeg args (default: shown below)
global_args: -hide_banner -loglevel warning -threads 2
# Optional: global hwaccel args (default: shown below)
# NOTE: See hardware acceleration docs for your specific device
hwaccel_args: preset-vaapi
# Optional: global input args (default: shown below)
input_args: preset-rtsp-generic
# Optional: global output args
output_args:
# Optional: output args for detect streams (default: shown below)
detect: -threads 2 -f rawvideo -pix_fmt yuv420p
# Optional: output args for record streams (default: shown below)
record: preset-record-generic-audio-aac
# Optional: output args for rtmp streams (default: shown below)
#rtmp: preset-rtmp-generic
# Optional: Time in seconds to wait before ffmpeg retries connecting to the camera. (default: shown below)
# If set too low, frigate will retry a connection to the camera's stream too frequently, using up the limited streams some cameras can allow at once
# If set too high, then if a ffmpeg crash or camera stream timeout occurs, you could potentially lose up to a maximum of retry_interval second(s) of footage
# NOTE: this can be a useful setting for Wireless / Battery cameras to reduce how much footage is potentially lost during a connection timeout.
retry_interval: 10
detectors:
coral:
type: edgetpu
device: usb
model:
path: plus://123privatecode
#4881f608f0d15dce070d3a80f6fb18b0
#4881f608f0d15dce070d3a80f6fb18b0
#37a4590ee871209742e0f69d0bc7d718
#3aab4c5eeead526ad178cf93afee5284
#aa726f072f0ea4a19e43277ca8066212
snapshots:
enabled: true
bounding_box: false
quality: 100
birdseye: # Include all cameras by default in Birdseye view
enabled: true
mode: motion
audio:
# Optional: Enable audio events (default: shown below)
# Optional: Audio Events Configuration
# NOTE: Can be overridden at the camera level
enabled: true
# Optional: Configure the amount of seconds without detected audio to end the event (default: shown below)
max_not_heard: 30
# Optional: Configure the min rms volume required to run audio detection (default: shown below)
# As a rule of thumb:
# - 200 - high sensitivity
# - 500 - medium sensitivity
# - 1000 - low sensitivity
min_volume: 150
# Optional: Types of audio to listen for (default: shown below)
listen:
- fire_alarm
- car_alarm
- alarm
- bell
- doorbell
- ding-dong
- knock
- slam
- scream
- yell
- tire_squeal
- siren
- emergency_vehicle
- police_car
- ambulance
- fire_engine
# Optional: Filters to configure detection.
#filters:
# Label that matches label in listen config.
# speech:
# Minimum score that triggers an audio event (default: shown below)
# threshold: 0.8
# Optional: Object configuration
# NOTE: Can be overridden at the camera level
objects:
# Optional: list of objects to track from labelmap.txt (default: shown below)
track:
#- person
#- cat
#- bird
- package
- amazon
- face
- license_plate
# Optional: mask to prevent all object types from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object.
# NOTE: This mask is COMBINED with the object type specific mask below
#mask: 0,0,1000,0,1000,200,0,200
# Optional: filters to reduce false positives for specific object types
filters:
package:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 5000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.9
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.5
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.9
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask: 0,0,1000,0,1000,200,0,200
# Optional: Record configuration
# NOTE: Can be overridden at the camera level
record:
# Optional: Enable recording (default: shown below)
# WARNING: If recording is disabled in the config, turning it on via
# the UI or MQTT later will have no effect.
enabled: true
# Optional: Number of minutes to wait between cleanup runs (default: shown below)
# This can be used to reduce the frequency of deleting recording segments from disk if you want to minimize i/o
expire_interval: 60
# Optional: Sync recordings with disk on startup and once a day (default: shown below).
sync_recordings: false
# Optional: Retention settings for recording
retain:
# Optional: Number of days to retain recordings regardless of events (default: shown below)
# NOTE: This should be set to 0 and retention should be defined in events section below
# if you only want to retain recordings of events.
days: 4
# Optional: Mode for retention. Available options are: all, motion, and active_objects
# all - save all recording segments regardless of activity
# motion - save all recordings segments with any detected motion
# active_objects - save all recording segments with active/moving objects
# NOTE: this mode only applies when the days setting above is greater than 0
mode: all
# Optional: Recording Export Settings
export:
# Optional: Timelapse Output Args (default: shown below).
# NOTE: The default args are set to fit 24 hours of recording into 1 hour playback.
# See https://stackoverflow.com/a/58268695 for more info on how these args work.
# As an example: if you wanted to go from 24 hours to 30 minutes that would be going
# from 86400 seconds to 1800 seconds which would be 1800 / 86400 = 0.02.
# The -r (framerate) dictates how smooth the output video is.
# So the args would be -vf setpts=0.02*PTS -r 30 in that case.
timelapse_args: -vf setpts=0.003*PTS -r 25
# Optional: Event recording settings
events:
# Optional: Number of seconds before the event to include (default: shown below)
pre_capture: 7
# Optional: Number of seconds after the event to include (default: shown below)
post_capture: 20
# Optional: Objects to save recordings for. (default: all tracked objects)
objects:
- person
- cat
- package
- amazon
# Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones)
#required_zones: []
# Optional: Retention settings for recordings of events
retain:
# Required: Default retention days (default: shown below)
default: 28
# Optional: Mode for retention. (default: shown below)
# all - save all recording segments for events regardless of activity
# motion - save all recordings segments for events with any detected motion
# active_objects - save all recording segments for event with active/moving objects
#
# NOTE: If the retain mode for the camera is more restrictive than the mode configured
# here, the segments will already be gone by the time this mode is applied.
# For example, if the camera retain mode is "motion", the segments without motion are
# never stored, so setting the mode to "all" here won't bring them back.
mode: active_objects
# Optional: Per object retention days
# objects:
# person: 14
# cat: 14
# bird: 7
# Optional: Motion configuration
# NOTE: Can be overridden at the camera level
motion:
# Optional: The threshold passed to cv2.threshold to determine if a pixel is different enough to be counted as motion. (default: shown below)
# Increasing this value will make motion detection less sensitive and decreasing it will make motion detection more sensitive.
# The value should be between 1 and 255.
threshold: 12
# Optional: The percentage of the image used to detect lightning or other substantial changes where motion detection
# needs to recalibrate. (default: shown below)
# Increasing this value will make motion detection more likely to consider lightning or ir mode changes as valid motion.
# Decreasing this value will make motion detection more likely to ignore large amounts of motion such as a person approaching
# a doorbell camera.
lightning_threshold: 1
# Optional: Minimum size in pixels in the resized motion image that counts as motion (default: shown below)
# Increasing this value will prevent smaller areas of motion from being detected. Decreasing will
# make motion detection more sensitive to smaller moving objects.
# As a rule of thumb:
# - 10 - high sensitivity
# - 30 - medium sensitivity
# - 50 - low sensitivity
contour_area: 12
# Optional: Alpha value passed to cv2.accumulateWeighted when averaging frames to determine the background (default: shown below)
# Higher values mean the current frame impacts the average a lot, and a new object will be averaged into the background faster.
# Low values will cause things like moving shadows to be detected as motion for longer.
# https://www.geeksforgeeks.org/background-subtraction-in-an-image-using-concept-of-running-average/
frame_alpha: 0.02
# Optional: Height of the resized motion frame (default: 100)
# Higher values will result in more granular motion detection at the expense of higher CPU usage.
# Lower values result in less CPU, but small changes may not register as motion.
frame_height: 90
# Optional: motion mask
# NOTE: see docs for more detailed info on creating masks
#mask: 0,900,1080,900,1080,1920,0,1920
# Optional: improve contrast (default: shown below)
# Enables dynamic contrast improvement. This should help improve night detections at the cost of making motion detection more sensitive
# for daytime.
improve_contrast: true
# Optional: Delay when updating camera motion through MQTT from ON -> OFF (default: shown below).
mqtt_off_delay: 30
# Optional: Detect configuration
# NOTE: Can be overridden at the camera level
detect:
# Optional: width of the frame for the input with the detect role (default: use native stream resolution)
width: 640
# Optional: height of the frame for the input with the detect role (default: use native stream resolution)
height: 360
# Optional: desired fps for your camera for the input with the detect role (default: shown below)
# NOTE: Recommended value of 5. Ideally, try and reduce your FPS on the camera.
fps: 8
# Optional: enables detection for the camera (default: True)
enabled: true
# Optional: Number of consecutive detection hits required for an object to be initialized in the tracker. (default: 1/2 the frame rate)
min_initialized: 2
# Optional: Number of frames without a detection before Frigate considers an object to be gone. (default: 5x the frame rate)
max_disappeared: 400
# Optional: Configuration for stationary object tracking
stationary:
# Optional: Frequency for confirming stationary objects (default: same as threshold)
# When set to 1, object detection will run to confirm the object still exists on every frame.
# If set to 10, object detection will run to confirm the object still exists on every 10th frame.
interval: 8
# Optional: Number of frames without a position change for an object to be considered stationary (default: 10x the frame rate or 10s)
threshold: 800
# Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
# This can help with false positives for objects that should only be stationary for a limited amount of time.
# It can also be used to disable stationary object tracking. For example, you may want to set a value for person, but leave
# car at the default.
# WARNING: Setting these values overrides default behavior and disables stationary object tracking.
# There are very few situations where you would want it disabled. It is NOT recommended to
# copy these values from the example config into your config unless you know they are needed.
max_frames:
# Optional: Default for all object types (default: not set, track forever)
#default: 6000
# Optional: Object specific values
objects:
cat: 1000
#person: 1000
package: 1000
# person: 1000
# bird: 1000
# Optional: Milliseconds to offset detect annotations by (default: shown below).
# There can often be latency between a recording and the detect process,
# especially when using separate streams for detect and record.
# Use this setting to make the timeline bounding boxes more closely align
# with the recording. The value can be positive or negative.
# TIP: Imagine there is an event clip with a person walking from left to right.
# If the event timeline bounding box is consistently to the left of the person
# then the value should be decreased. Similarly, if a person is walking from
# left to right and the bounding box is consistently ahead of the person
# then the value should be increased.
# TIP: This offset is dynamic so you can change the value and it will update existing
# events, this makes it easy to tune.
# WARNING: Fast moving objects will likely not have the bounding box align.
# annotation_offset: 0
# Optional: Review configuration
# NOTE: Can be overridden at the camera level
review:
# Optional: alerts configuration
alerts:
# Optional: labels that qualify as an alert (default: shown below)
labels:
- cat
- person
- package
# Optional: required zones for an object to be marked as an alert (default: none)
#required_zones:
# - driveway
# Optional: detections configuration
detections:
# Optional: labels that qualify as a detection (default: all labels that are tracked / listened to)
labels:
- cat
- person
- package
# Optional: required zones for an object to be marked as a detection (default: none)
#required_zones:
# - driveway
go2rtc:
streams:
barn_catflap HQ: ffmpeg:rtsp://MPG7QbYQ:ICRGvtBU2xo3DxMy@192.168.22.202:554/live/ch0
road_cam HQ: ffmpeg:rtsp://admin:annke2023@10.0.0.2:554/H265/ch1/main/av_stream
porch_cam HQ: ffmpeg:rtsp://admin:annke2023@10.0.0.3:554/H265/ch1/main/av_stream
bird_cam HQ: ffmpeg:rtsp://admin:annke2023@10.0.0.7:554/H265/ch1/main/av_stream
barn HQ: ffmpeg:rtsp://admin:annke2023@10.0.0.4:554/H265/ch1/main/av_stream
# kitchen_cam HQ: ffmpeg:rtsp://admin:annke2023@10.0.0.5:554/H265/ch1/main/av_stream
# house_cam HQ: ffmpeg:rtsp://admin:annke2023@10.0.0.6:554/H265/ch1/main/av_stream
cameras:
bird_cam: #Cam Name: Bird Cam (kitchen cat flap) #Brand: Annke c500 #Quality:3k #Link:POE
enabled: true
ui:
# Optional: Configuration for how camera is handled in the GUI.
# Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below)
# By default the cameras are sorted alphabetically.
order: 4
# Optional: Whether or not to show the camera in the Frigate UI (default: shown below)
dashboard: true
live:
stream_name: bird_cam HQ
ffmpeg:
inputs:
- path: rtsp://admin:annke2023@10.0.0.7:554/Streaming/Channels/102 # SQ Link
input_args: preset-rtsp-generic
roles:
- detect
- audio
- path: rtsp://192.168.22.2:8554/bird_cam%20HQ?mp4 # HQ Link
input_args: preset-rtsp-restream
roles:
- record
objects:
track:
- person
- cat
filters:
cat:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 2000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.5
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.6
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.7
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask: []
person:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 2000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.9
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.55
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.65
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask:
# - 28,228,80
motion:
mask:
- 0,37,189,37,190,0,0,0
- 109,143,144,76,145,31,0,35,0,128
audio:
enabled: true # <- enable audio events for the this camera
barn_catflap: #Cam name: Barn Catflap #Brand: wansview #Quality:1080p #Link:WIFI
enabled: true
ui:
# Optional: Configuration for how camera is handled in the GUI.
# Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below)
# By default the cameras are sorted alphabetically.
order: 5
# Optional: Whether or not to show the camera in the Frigate UI (default: shown below)
dashboard: true
live:
stream_name: barn_catflap HQ
detect:
fps: 8
ffmpeg:
inputs:
#- path: rtsp://MPG7QbYQ:ICRGvtBU2xo3DxMy@192.168.22.202:554/live/ch1 # SD Link
# input_args: preset-rtsp-generic
# roles:
# - detect
# - audio
- path: rtsp://192.168.22.2:8554/barn_catflap%20HQ?mp4 # HD Link
input_args: preset-rtsp-restream
roles:
- record
- detect
- audio
objects:
track:
- person
- cat
filters:
person:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 2000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.8
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.65
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.75
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask: 0,0,1000,0,1000,200,0,200
#mask: []
cat:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 3000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.4
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.6
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.7
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask: 0,0,1000,0,1000,200,0,200
motion:
mask:
- 640,0,640,21,481,21,477,0,477,0
audio:
enabled: true # <- enable audio events for the this camera
#zones:
# zone_0:
# coordinates: 0,360,270,360,268,0,0,0
barn: #Cam name: Barn #Brand: Annke c500 #Quality:3k #Link:POE
enabled: true
ui:
# Optional: Configuration for how camera is handled in the GUI.
# Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below)
# By default the cameras are sorted alphabetically.
order: 3
# Optional: Whether or not to show the camera in the Frigate UI (default: shown below)
dashboard: true
live:
stream_name: barn HQ
ffmpeg:
inputs:
- path: rtsp://admin:annke2023@10.0.0.4:554/Streaming/Channels/102 # SD Link
input_args: preset-rtsp-generic
roles:
- detect
- audio
- path: rtsp://192.168.22.2:8554/barn%20HQ?mp4 # HD Link
input_args: preset-rtsp-restream
roles:
- record
objects:
track:
- person
- cat
filters:
person:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 5000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 1
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.65
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.7
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask:
cat:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 9000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.7
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.6
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.7
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask:
motion:
mask:
- 0,38,191,39,193,0,0,0
- 245,71,283,76,279,0,202,0
- 365,100,479,120,600,98,583,0,438,0,336,38
- 281,82,439,67,446,0,263,0
audio:
enabled: true # <- enable audio events for the this camera
porch_cam: #Cam Name: Porch #Brand: Annke c500 #Quality:3k #Link:POE
enabled: true
ui:
# Optional: Configuration for how camera is handled in the GUI.
# Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below)
# By default the cameras are sorted alphabetically.
order: 1
# Optional: Whether or not to show the camera in the Frigate UI (default: shown below)
dashboard: true
live:
stream_name: porch_cam HQ
ffmpeg:
inputs:
- path: rtsp://admin:annke2023@10.0.0.3:554/Streaming/Channels/102 # SQ Link
input_args: preset-rtsp-generic
roles:
- detect
- audio
- path: rtsp://192.168.22.2:8554/porch_cam%20HQ?mp4 # HQ Link
input_args: preset-rtsp-restream
roles:
- record
objects:
track:
- person
- cat
- package
- amazon
filters:
person:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 2000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.4
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.5
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.67
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
mask:
- 441,57,443,102,303,112,306,67
- 640,227,640,360,592,360,519,360,522,265,577,215
cat:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 1000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.3
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.4
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.65
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
mask:
- 640,261,640,360,592,360,553,360,563,308,593,272
package:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 9000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.8
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.7
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.9
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask: 0,0,1000,0,1000,200,0,200
#mask:
motion:
mask:
- 0,36,195,40,194,0,0,0
- 290,67,428,63,421,0,285,0
- 640,0,640,166,570,189,501,188,410,120,402,0
- 469,291,526,298,569,243,571,193,538,132,468,109,424,216
audio:
enabled: true # <- enable audio events for the this camera
road_cam: #Cam name: Road #Brand: Annke c500 #Quality:3k #Link:POE
enabled: true
ui:
# Optional: Configuration for how camera is handled in the GUI.
# Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below)
# By default the cameras are sorted alphabetically.
order: 2
# Optional: Whether or not to show the camera in the Frigate UI (default: shown below)
dashboard: true
live:
stream_name: road_cam HQ
ffmpeg:
inputs:
- path: rtsp://admin:annke2023@10.0.0.2:554/Streaming/Channels/102 # SQ Link
input_args: preset-rtsp-generic
roles:
- detect
- audio
- path: rtsp://192.168.22.2:8554/road_cam%20HQ?mp4 # HQ Link
input_args: preset-rtsp-restream
roles:
- record
objects:
track:
- cat
- person
filters:
cat:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 1000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.3
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.4
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.65
person:
# Optional: minimum width*height of the bounding box for the detected object (default: 0)
min_area: 2000
# Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
max_area: 100000
# Optional: minimum width/height of the bounding box for the detected object (default: 0)
min_ratio: 0.9
# Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
max_ratio: 2.0
# Optional: minimum score for the object to initiate tracking (default: shown below)
min_score: 0.55
# Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
threshold: 0.7
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask:
# - 28,228,80
# Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
# Checks based on the bottom center of the bounding box of the object
#mask:
audio:
enabled: true # <- enable audio events for the this camera
# Optional
#motion:
#mask:
ui:
# Optional: Set the default live mode for cameras in the UI (default: shown below)
#use_experimental: false
# Optional: Set the time format used.
# Options are browser, 12hour, or 24hour (default: shown below)
time_format: browser
# Optional: Set the date style for a specified length.
# Options are: full, long, medium, short
# Examples:
# short: 2/11/23
# medium: Feb 11, 2023
# full: Saturday, February 11, 2023
# (default: shown below).
date_style: short
# Optional: Set the time style for a specified length.
# Options are: full, long, medium, short
# Examples:
# short: 8:14 PM
# medium: 8:15:22 PM
# full: 8:15:22 PM Mountain Standard Time
# (default: shown below).
time_style: medium
# Optional: Ability to manually override the date / time styling to use strftime format
# https://www.gnu.org/software/libc/manual/html_node/Formatting-Calendar-Time.html
# possible values are shown above (default: not set)
strftime_fmt: '%Y/%m/%d %H:%M'
# Optional: Telemetry configuration
telemetry:
# Optional: Enabled network interfaces for bandwidth stats monitoring (default: empty list, let nethogs search all)
network_interfaces:
- eth
- enp
- eno
- ens
- wl
- lo
# Optional: Configure system stats
stats:
# Enable AMD GPU stats (default: shown below)
amd_gpu_stats: false
# Enable Intel GPU stats (default: shown below)
intel_gpu_stats: true
# Enable network bandwidth stats monitoring for camera ffmpeg processes, go2rtc, and object detectors. (default: shown below)
# NOTE: The container must either be privileged or have cap_net_admin, cap_net_raw capabilities enabled.
network_bandwidth: true
# Optional: Enable the latest version outbound check (default: shown below)
# NOTE: If you use the HomeAssistant integration, disabling this will prevent it from reporting new versions
version_check: true
version: 0.14 |
Beta Was this translation helpful? Give feedback.
-
|
Awesome setup, this opens up a new horizon, I'm still sticking with this, thank you very much |
Beta Was this translation helpful? Give feedback.
-
|
With the new history playback, is there a way to display the footage using |
Beta Was this translation helpful? Give feedback.
-
|
No. jsmpeg and webrtc are live streaming players in Frigate. The recordings player uses HLS. Firefox lacks H.265 support for patent reasons. |
Beta Was this translation helpful? Give feedback.
-
|
Weird, the recordings player does not work on Firefox for me. Is there a way to force another playback codec? |
Beta Was this translation helpful? Give feedback.
-
|
You’d need to change the output codec type in your camera’s firmware or transcode with go2rtc. |
Beta Was this translation helpful? Give feedback.
-
|
User error then maybe as I can’t see a submit to frigate button anywhere :)
…On Thu, 22 Aug 2024 at 19:46, Nicolas Mowen ***@***.***> wrote:
yes, using the Frigate+ page in the sidebar
—
Reply to this email directly, view it on GitHub
<#12829 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHUULJGEIHNJLTEE5EPRY43ZSYWXBAVCNFSM6AAAAABMGPKF7WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANBSGI3TQOI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Does 'Up to 12 model trainings' mean that if I want to train models for my father, mother, myself, wife, and son, it would count as 5 out of the 12 allowed? |
Beta Was this translation helpful? Give feedback.
-
|
What do you mean train a model for your son? It doesn't support face recognition if that's what you're asking. It supports face detection though. One model detects all of the objects listed in the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
If I subscribe to Frigate+, can I create models based on the physical characteristics of my father, mother, son, and wife? |
Beta Was this translation helpful? Give feedback.
-
|
No that is not what frigate+ is |
Beta Was this translation helpful? Give feedback.
-
|
You can use something like compreface for that |
Beta Was this translation helpful? Give feedback.
-
|
In Frigate v0.14, where can I view the labeled images like I did in v0.13? I can only find short clips under the 'Review' menu |
Beta Was this translation helpful? Give feedback.
-
|
I believe you have to use the filters under the gear icon. |
Beta Was this translation helpful? Give feedback.
-
|
How can the ratio of a detected object be viewed? |
Beta Was this translation helpful? Give feedback.
-
|
currently it is not available in the UI, there is a pinned feature request already that covers debugging review items with information like that |
Beta Was this translation helpful? Give feedback.
-
|
To be clear you can use the debug view's "object list" in 0.14 to view the ratio of any active objects. But for historical footage, there is a pinned feature request as @NickM-27 mentioned. |
Beta Was this translation helpful? Give feedback.
-
|
Just a note to say check your storage space manually at least once - I had a lot of space being used by both full retain recordings and events way past my retention periods, it looks like something (perhaps the update to Frigate 14, or maybe a Linux update?) caused them to remain there causing my HDD to fill up, luckily Frigate deals with this by deleting recordings allowing new ones to record - but it will effectively lower your actual retention period during this period - along with eating CPU during the deletion processes. Don't rely on the storage space indicator in the storage stats alone. This is just a friendly note to other Frigate users, I am no way at all bashing this great software! |
Beta Was this translation helpful? Give feedback.
-
That is an awesome idea, if you ever feel like sharing it I'd be very interested, and I'm sure many others would here? :) Hopefully in the future Frigate can support reading the actual recordings drive total and used capacity and warning the user of a mismatch. |
Beta Was this translation helpful? Give feedback.
-
|
to be clear frigate supports this directly https://docs.frigate.video/configuration/record#syncing-recordings-with-disk |
Beta Was this translation helpful? Give feedback.
-
Whilst cool, That seems to do the exact opposite? Unless it does the opposite too? |
Beta Was this translation helpful? Give feedback.
-
|
it makes sure the DB and the file system are in sync, files without DB entries are deleted and DB entries without files are deleted |
Beta Was this translation helpful? Give feedback.
-
Ah ok, it doesn't read like but that is sweet news, and poor Noel probably could have saved some time. I'll add this to my Frigate notes to use if it goes out of sync again in the future. Cheers |
Beta Was this translation helpful? Give feedback.
-
|
The percent per an hour of storage per a camera which used to be in previous versions of Frigate has gone now right? At least I cannot seem to find it? It was quite useful I thought. I'm sure I am not dreaming of it, ha. |
Beta Was this translation helpful? Give feedback.
-
|
yes, it is not shown in the UI |
Beta Was this translation helpful? Give feedback.
-
Thanks for confirming, is there a way to show it in the CLI of Frigate or perhaps you meant it is still there, just behind the scenes and may make a return in the future in the UI? |
Beta Was this translation helpful? Give feedback.
-
|
if you use the network tab of your browser tools, the bandwidth is still included in the api response |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I think a screen recording would be best to see, we have not gotten any other reports of this |
Beta Was this translation helpful? Give feedback.
-
|
Hi Nick so sorry for wasting your time, I deleted my comment not sure if you will see this, it was a Chrome addon which I use for an ultrawide monitor but it synced it's enabled status to my laptop causing the zoom issue. If this comment persists for anyone searching with a zoom issue check your Chrome addons doh! |
Beta Was this translation helpful? Give feedback.
-
|
I can't seem to see the confidence % of the detection anymore. How do I view that now in new UI??? |
Beta Was this translation helpful? Give feedback.
-
|
All my detections come up as alerts. I don't seem to have any detections at all. But some screen shots I saw a % next to the floating person or car icon on top left. I don't see the % on any of my alerts. Clicked around also couldn't find anyway to see what confident percentage the detection/alert was? How can I see the confidence percentage again?? |
Beta Was this translation helpful? Give feedback.
-
|
For now they are shown on the frigate+ screen. In 0.15 there will be an additional panel to view this and other information. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the update. Oh well I will wait for 0.15. Also cannot see the bounging box either. will that also be included in the 0.15 release? I did prefer the old video play which you can drag the timeline. Now viewing is plus or minus 10 seconds. |
Beta Was this translation helpful? Give feedback.
-
|
@beatmag , while waiting for the next release, just create a free frigate+ account and then generate an API key and then create an environment variable to set the key for your frigate container. You can create the account here: https://plus.frigate.video/. Then once logged in, click the settings button and then the generate button. Then edit your docker-compose.yaml to add this env variable: environment:
- PLUS_API_KEY=<YOUR_API_KEY_HERE>Then The little jump buttons on the old release to jump to the exact timecodes was handy but I find the timeline on the right side of the video player just as easy to use. You just drag the slider until you see the even start. The events are also marked in the timeline on the right so it's easy to see. Also, the left right arrows on the keyboard jump 10 seconds but the up down arrows jump 1 second. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
If I remove the labels deer, ups, fedex, amazon, and package, will I only be able to use the labels person, face, car, license_plate, dog, and cat in Frigate+? |
Beta Was this translation helpful? Give feedback.
-
|
No, changing the setting in frigate+ is just a UI change, it does not change the labels that the model is trained on |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
For now you can't label that, you'll have to wait until frigate+ supports more labels (which is coming soon I believe) |
Beta Was this translation helpful? Give feedback.
-
|
Understood. Do I need to wait for the developers to update? |
Beta Was this translation helpful? Give feedback.
-
|
wow this is great! Frigate went from 'it does what it has to do but the interface is a bit clunky' to: one of the best solutions out there! amazing job guys! |
Beta Was this translation helpful? Give feedback.
-
|
I gotta add my thanks here for the new release. At first I was kinda... I dunno... Scared? about the new interface, and config changes and thought "oh no, this is gonna suck" since I don't really like change all that much. But since I've had a couple of issues with older versions, I decided to setup an entirely fresh box (connected to the same cameras, but independent) to fine-tune my configuration and really figure out how the new frigate "works", and I have to say now that I've gotten familiar to why things are a certain way, it's lovely. I think it was a good move on my part to setup a second system - because I could not only break it in interesting ways and learn how to fix, it meant I wasn't disrupting others on the old one and finally figure out "why are the options this way" Anyway, excellent work on this new version, I can't wait now to replace the old system once I've finished my field testing. <3 |
Beta Was this translation helpful? Give feedback.
-
|
Is there an easy way to go back to 13.2? So many issues with performance, locking up, go2rtc streams getting murdered, detectors wigging out or just full on stopped working with a config that works merrily in 13.2. |
Beta Was this translation helpful? Give feedback.
-
|
Just restore the database backup and use the 0.13.2 docker container. However, if you open a separate support discussion with your config file and logs, we'd be happy to help get you sorted out on the new version. |
Beta Was this translation helpful? Give feedback.
-
|
I figured out the problem. OpenVino has a bug and Debian 11 is near impossible to fix it in.
If the output does not list GPU (notice capital letters there), follow along.
Now when you run the python command you should see GPU as supported. A quick way to make this easier as you will get stuck on a couple of those intel packages in debian 11 (PLEASE UPDATE TO 12 for the official docker image of frigate), is to use the proxmox LXC script from tteck and run it in advanced mode and select debian 12. This will make fixing it much easier. Ok... good luck to anyone on this journey. I wish someone had documented this before I spent days figuring it out. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, this is helpful for users running 0.14. Updating the base image will be very involved as many things depend on this. However, Frigate 0.15 now installs the intel drivers out of tree using their specific apt repo so this is no longer an issue, I tested specifically with an intel arc card |
Beta Was this translation helpful? Give feedback.
and others
-
Images
ghcr.io/blakeblackshear/frigate:0.14.0ghcr.io/blakeblackshear/frigate:0.14.0-standard-arm64ghcr.io/blakeblackshear/frigate:0.14.0-tensorrtghcr.io/blakeblackshear/frigate:0.14.0-tensorrt-jp4ghcr.io/blakeblackshear/frigate:0.14.0-tensorrt-jp5ghcr.io/blakeblackshear/frigate:0.14.0-rkChanges since RC2
Major Changes for 0.14.0
Breaking Changes
There are several breaking changes in this release, Frigate will attempt to update the configuration automatically. In some cases manual changes may be required. It is always recommended to backup your current config and database before upgrading:
frigate.dbfileYour existing events will not be visible in Frigate's new UI
enabled: Trueforrecordin your config) is required to see review items and motion data in the UIZone/mask coordinates are now stored in the config as relative values
The UI's live mode is now intelligently selected
live_modeconfig option is now deprecated and should be removed.Backwards incompatible database changes
Other breaking changes
rtmpreferences in your config file.AUTOmode now maps toGPUinternally to avoid some unresolved issues withAUTO. The existingYOLO-Xmodel will not work in this version.Brand New UI
Frigate 0.14's UI has been completely rewritten (helpful walkthrough video from a user) and optimized for desktop and mobile devices, aiming to simplify the user experience by focusing on two specific goals:
Frigate 0.14's UI will likely change the way you review your camera footage. It's a big change, but we love it and hope you do too. See the announcement post for more information regarding the motivation, ideas, and design decisions behind the new UI.
Dashboard
The new home page for Frigate is intended to be a real-time dashboard for your cameras. Recent alerts are represented by animated thumbnails in a filmstrip view above your camera feeds. Your camera images update once per minute when no detectable activity is occurring to conserve bandwidth and resources. As soon as any motion is detected, cameras seamlessly switch to a full-resolution live stream.
Live View
Clicking a camera from the dashboard will bring up a full-resolution live view where you can quickly access historical footage, use PTZ controls, toggle camera audio, use two-way talk, and more. Zooming with pinch or a scroll wheel is also supported.
Review
The Review area of Frigate 0.14 is for quickly reviewing historical footage of interest from your cameras. Review items are indicated on a vertical timeline and displayed as a grid of previews - bandwidth-optimized, low frame rate, low resolution videos. Hovering over or swiping a preview plays the video and marks it as reviewed. If more in-depth analysis is required, the preview can be clicked/tapped and the full frame rate, full resolution recording is displayed. Review items are filterable by date, object type, and camera.
Alerts and Detections
Not every segment of video captured by Frigate may be of the same level of interest to you. Video of people who enter your property are a different priority than those walking by on the sidewalk. For this reason, Frigate 0.14 categorizes review items as alerts or detections. By default, all person and car objects are considered alerts. You can refine categorization of your review items by configuring required zones for them.
See the review docs for more information
Motion review
In Frigate 0.13, there isn’t a way to see motion activity on a timeline and watch video at that time. The ability to scrub video for things Frigate missed has been one of the most common feature requests. Within the Motion tab of the Review section, you can now scrub through the timeline for all cameras simultaneously with a timeline showing relative motion activity. In order to avoid scrubbing over time periods already included in alerts and detections, you can also scrub in motion only mode.
History
In Frigate 0.14, full frame rate, full resolution camera footage (called "recordings" in earlier versions) can be viewed and scrubbed via a timeline. Previews of your other cameras are displayed and scrubbed alongside the main selected camera.
Other Notable UI Changes
Authentication
Frigate now supports authentication. Frigate manages users and authentication using JWT tokens via a cookie or authorization header. Additionally, a new proxy section in the config allows you to use the user header passed from common authentication proxies such as authelia, authentik, oauth2_proxy, etc.
See the documentation for more information.
TLS
Since Authentication should really be used over secure connections, TLS is also enabled by default for port 8971. It can be disabled in the config file with the following yaml:
Custom certificates can also be used following the tls docs.
Frigate+
Frigate 0.14 now offers a dedicated page for Frigate+ submissions, allowing more specific filtering by score and a faster workflow. Support has also been added to upload frames directly from the History view.
Other notable improvements
loitering_timeconfiguration which can be used to only consider an object as part of a zone if they loiter for the specified number of seconds. This can be used, for example, to create alerts for cars that stop on the street but not cars that just drive past your camera.Fixes and changes
FAQ
Have a question that's not answered here? Look at the most updated list of FAQs here or open a discussion on Github.
Upgrade issues
I'm seeing "add mask expects relative coordinates only" in my logs.
This is usually caused by a mask or zone having coordinates larger than the camera's
detectresolution. The easiest fix would be to remove the mask/zone, restart Frigate, and use the new mask/zone editor to recreate it.What happened to all my events?
An entirely new way of reviewing camera footage has been implemented in Frigate 0.14, so any "events" from any previous versions of Frigate will not be migrated and will not be visible in the new UI. This includes any favorited/starred events. Recordings can still be viewed in the new UI using the recordings viewer (From Live view, click/tap on a camera and select the History button at the top left).
I'm seeing "Preview Not Found" in the UI a lot. Why?
Frigate 0.14 now generates "previews": bandwidth-optimized, low frame rate, low resolution videos for your camera footage. These previews are not generated for any footage from older versions of Frigate. Historical full recordings are still viewable from your cameras, however. From Live view, click/tap on a camera and select the History button at the top left.
Usage
Are there any tutorials or videos on how to use the new version?
Yes, see the guided demo and a helpful walkthrough video from a user.
Can I make the cameras take up more space on my dashboard?
Yes you can, on desktop screens only. Create a camera group, and then use the edit layout button (bottom right) to resize/reposition your cameras on the dashboard.
Where is Birdseye view in the new UI?
Birdseye is accessible by creating a camera group and adding the Birdseye camera to the camera group. Birdseye is also accessible by navigating directly to
frigate_ip:port/#birdseye.Why are there black bars and empty space around my cameras in the new Live dashboard?
Cameras are kept in a standard 16x9 aspect ratio grid layout. If your camera's aspect ratio is not 16x9 (or a multiple of 16x9 like a wide angle 32x9), black bars may appear on any of the sides of the camera image. One solution would be to adjust your camera's resolution in firmware to fit any multiple of the 16x9 aspect ratio. You could also use Birdseye, which is Frigate's solution for an automatic live view layout without black bars. See the Birdseye docs for ways to configure Birdseye's resolution, aspect ratio, and layout preferences.
It doesn't seem like my cameras are streaming on the Live dashboard. Why?
On the Live dashboard, your camera images will update once per minute when no detectable activity is occurring to conserve bandwidth and resources. As soon as any motion is detected, cameras seamlessly switch to a full-resolution live stream.
Can I export footage from the review screen?
Yes, right click (desktop) or long press (mobile) to choose item(s) you want to export, then press the export button in the header.
What happened to the timelapse export feature?
It's not in the UI, but the API is still available. Most users were using that feature to create videos to manually review each day. One of the main focuses of the new UI was to ensure that isn't necessary. The only remaining use cases we are aware of are for very long periods of time. Having frigate do long exports on high resolution recordings on the server is a really inefficient way to accomplish that.
How can I view snapshots with bounding boxes?
Snapshots have been deprecated in favor of the new review item format. To understand why, consider the situation where two people, one with a dog, walked past your house. At the same time, a car drove by on the street behind them. In this scenario, Frigate would have tracked 4 "events". One for each person, the dog, and the car. In 0.13, you would have had 4 separate videos to watch, even though they would have all overlapped. In 0.14, these separate objects are combined into a single review item which represents the period in time where these objects were active on the camera. Reviews for a single camera cannot overlap. Displaying separate snapshots for this scenario in a way that shows they are connected is not only difficult, but also less helpful than having a combined thumbnail and easy to view video preview that quickly shows what exactly happened. Even though snapshots are no longer available in the 0.14 UI review pipeline, they are still available in the Frigate+ view, on the filesystem, and viewable through Home Assistant's media browser. A screen to help debug review items and answer the question "why was this review item created?" will be coming in a future version (feature request is here).
How can I tune what I see in alerts and detections?
You can restrict alerts and detections to specific objects/labels or exclude a camera entirely. See the review docs. You can also restrict alerts and detections to objects entering zones. The Camera Settings screen in the UI provides a lot of granular control. See the zone docs.
How can I switch the live view type?
In Frigate 0.13, a dropdown menu in the UI allowed users to select between jsmpeg, MSE, or WebRTC. In 0.14, Frigate intelligently selects the best type of live view method for the cameras on your dashboard based on network conditions and features, so this is no longer user selectable.
Can I "star" or "favorite" events like in 0.13?
No, that feature has been removed in 0.14 in favor of Exports. If you have footage you'd like to "favorite" or retain in 0.14, use the export tools. Unlike favorite events in 0.13, exported footage in 0.14 can be given a label/name and is searchable from the Exports page.
Are there any keyboard shortcuts in the UI for desktop devices?
Yes. In the Review pane, Ctrl/Cmd-A selects all of your review items. On Live camera view, you can use the arrow keys along with + and - to control a PTZ camera. In the Logs view, page up/page down and arrow up/arrow down will scroll the logs. Wherever video controls appear (History view, Motion Review), the left and right arrows will seek the video backwards and forwards by 10 seconds. The up and down arrow keys will seek the video by 1 second. The "f" key toggles fullscreen, "m" toggles muting, and the space bar toggles playback/pause.
Have a question that's not answered here? Open a discussion on Github.
Full Changelog: v0.13.2...v0.14.0
This discussion was created from the release 0.14.0 Release.
Beta Was this translation helpful? Give feedback.
All reactions