I thought part of purpose for combining clips and recordings was to eliminate cache use?
Well I deleted all the files in the cache, we will see how long it will run for.
1 Like
You are a champion!!! Thank you.
Awesome instructions too.
I managed to get it working with the following config
cameras:
camera_name:
ffmpeg:
inputs:
- path: rtsp://admin:[email protected]:554//h264Preview_01_sub
record:
enabled: true
retain_days: 10
objects:
track:
- person
- car
- dog
- cat
For anyone who needs it, firmware file v3.0.0.236_21040831 in the link here
Hope this can help others
1 Like
Hello, in the Events Tab are multiple events listed for the same person detected, is there any way to optimize it so that I see only one event with the person? So for example a person is visible for 30minutes , I get 15 events that are around 2 minutes long, instead I want a event that is the full 30minutes long.
I think there is some option for that.Maybe this one?
detect:
enabled: True
max_disappeared: 25
Or maybe its not it, maybe you shold found some minimal clip legth?
So my 1.9gig cache filled up in about 3 hours. Not sure what is going on, or what next steps I should complete to correct this issue. Is anyone else encountering this?
Is it possibly this bug: [Support]: Daylight saving bug? After jumping back in time makes new events unavailable Ā· Issue #2158 Ā· blakeblackshear/frigate Ā· GitHub ? Are you able to see the similar error I posted in your log?
A frigate restart should resolve the issue until next year.
The timing and symptoms are suspicious, but I have restarted many times since the original occurrence. I had even deleted the db and restarted. Just to be sure I have restarted the container one more time to see how long it runs for. Should we be passing the Timezone to the container some how?
Anyone else having issues viewing camera streams on older android devices after updating Home Assistant to 2021.11.0 or 2021.11.1? There were no issues with 2021.10.6. iOS devices have no issues viewing any of the feeds on 2021.11.x.
Live view through the Frigate admin UI works fine on these devices. However, viewing the feed through the integration does not.
Frigate container running version 0.9.4
Frigate integration version 2.1.0
Amazon HD Fire 10 version 5.6.8.0
iOS Device version 15.1
All cameras are fed into Frigate and using the integration to view the feeds. One of my cameras is viewable, itās an Amcrest AD410. The other three cameras are not, they are Dahua IPC-HDW5231R-Z.
Below is the codex info with VLC directly pulling the cameraās RTSP stream.
Amcrest AD410 - Viewable through the Frigate integration
Dahua IPC-HDW5231R-Z - Not viewable through the Frigate integration
cameras:
driveway_left:
ffmpeg:
inputs:
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
roles:
- detect
- rtmp
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
roles:
- record
motion:
mask:
- 0,0,0,167,123,173,169,230,233,223,228,0
- 0,720,24,365,42,325,122,271,184,313,231,472,190,564,215,720
front_patio:
ffmpeg:
inputs:
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
roles:
- detect
- rtmp
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
roles:
- record
motion:
mask:
- 239,0,180,79,169,163,159,244,219,508,328,555,438,720,0,720,0,0
- 704,0,1002,0,997,55,997,156,993,252,981,408,683,358,628,266,660,223,665,155,707,90
driveway_right:
ffmpeg:
inputs:
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
roles:
- detect
- rtmp
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
roles:
- record
motion:
mask:
- 730,152,873,151,957,209,968,340,846,308,849,403,812,489,677,550,582,470,576,376,624,300,745,270,699,181
- 1157,720,1127,648,1082,649,998,601,956,648,934,720
doorbell:
ffmpeg:
inputs:
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
roles:
- detect
- rtmp
- path: rtsp://user:[email protected]/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
roles:
- record
detect:
width: 720
height: 576
motion:
mask:
- 0,0,270,0,323,51,361,98,328,113,267,125,219,151,183,207,187,333,197,439,94,576,0,555
- 519,348,510,283,498,78,475,69,404,107,371,206,358,287,394,462
ffmpeg:
global_args: -hide_banner -loglevel warning
hwaccel_args:
- -hwaccel
- vaapi
- -hwaccel_device
- /dev/dri/renderD128
- -hwaccel_output_format
- yuv420p
input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1
output_args:
detect: -f rawvideo -pix_fmt yuv420p
record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a copy
rtmp: -c:v copy -c:a copy -f flv
objects:
track:
- person
- dog
filters:
person:
threshold: 0.75
dog:
threshold: 0.6
cat:
threshold: 0.6
car:
threshold: 0.75
detectors:
coral:
type: edgetpu
device: pci
mqtt:
host: 192.168.8.12
port: 1883
topic_prefix: frigate
client_id: frigate
user: user
password: password
stats_interval: 60
record:
enabled: True
# 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.
retain_days: 7
events:
max_seconds: 300
pre_capture: 5
post_capture: 5
objects:
- person
- dog
- cat
required_zones: []
retain:
default: 10
objects:
person: 15
snapshots:
enabled: True
timestamp: False
bounding_box: False
crop: False
height: 300
required_zones: []
retain:
default: 10
objects:
person: 15
detect:
width: 1280
height: 720
fps: 5
enabled: True
# Optional: Number of frames without a detection before frigate considers an object to be gone. (default: 5x the frame rate)
max_disappeared: 25
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: 25
# Optional: Minimum size in pixels in the resized motion image that counts as motion (default: ~0.17% of the motion frame area)
# Increasing this value will prevent smaller areas of motion from being detected. Decreasing will make motion detection more sensitive to smaller
# moving objects.
contour_area: 100
# Optional: Alpha value passed to cv2.accumulateWeighted when averaging the motion delta across multiple frames (default: shown below)
# Higher values mean the current frame impacts the delta a lot, and a single raindrop may register as motion.
# Too low and a fast moving person wont be detected as motion.
delta_alpha: 0.2
# 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.2
# Optional: Height of the resized motion frame (default: 1/6th of the original frame height, but no less than 180)
# This operates as an efficient blur alternative. 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: 180
# Optional: motion mask
# NOTE: see docs for more detailed info on creating masks
# mask: 0,900,1080,900,1080,1920,0,1920
Is there a way to get a link that opens to the āEventsā page rather than the Dashboard? or possibly Birdseye page?
For those running Frigate on a Raspberry Pi 4 8GB, looks like a slight performance boost is possible;
Not 100% certain what is being asked, are you just looking for the url for the events page?
In HA I use the custom:frigate-card
http://yourFrigateIP:5000/events
http://yourFrigateIP:5000/birdseye
So my system has been running for >24 hours now since I restarted and things are looking stable.
I guess I can conclude that I was hit by the Daylight saving bug. Thanks @mattthewclayton for linking the issue.
1 Like
Yes locally that works but I am trying to go through the HA ingress window so when the user clicks frigate it is still within the HA window but having events be the first view that comes up.
Would it be at all possible to allow configuration for ffmpeg āinput_argsā to be configurable at individual input level? This would greatly benefit those who like to ātinkerā with ffmpeg configuration for bespoke reasons, I especially 
I was thinking something along the lines of permitting configuration also at the global role level (ie. rtmp, detect, record etc) as well as camera level for each āinputā.
At the moment Frigate only permits configuration at the global level and applies that same āinput_argsā to all roles, and as far as I can see at the camera level it applies to all inputs (which does indeed lack granularity for customisation per input).
Or maybe I missed this level of configurability altogether?
ā¦and as has been said by countless others, thank you for this great piece of work, it takes Home-Assistant to a whole new level. I left OpenHab behind because of Frigate, this NVR has got serious potential and has brought me over to HomeAssistant, absolutely beautiful.
this is already Global and Per Camera Stream
someone know to create .mp4 from events?
Dev said to me that is possible with http endpoint via mqtt, but i didnāt understand how to.
Trying to get my config.yml installed into docker container. I am unable to see what is wrong with the config.
#detectors:
# coral:
# type: edgetpu
# device:pci: 0
cpu1:
type: cpu
num_threads: 3
cpu2:
type: cpu
num_threads: 3
mqtt:
host: 192.168.0.81
user: mikey
password: mqtt6283
database:
path: /media/frigate/frigate.db
cameras:
front:
ffmpeg:
inputs:
- path: rtmp://192.168.0.48/bcs/channel0_main.bcs?channel=0&user=admin&password=Front1
# - path: rtsp://admin:[email protected]:554//h264Preview_01_main
# - path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@192.168.0.48:554/cam/realmonitor?channel=1&subtype=2
roles:
- detect
- rtmp
detect:
width: 640
height: 480
fps: 7
garage_driveway:
ffmpeg:
inputs:
- path: rtmp://192.168.0.51/bcs/channel0_main.bcs?channel=0&user=admin&password=Garage1
# - path: rtsp://admin:[email protected]:554//h264Preview_01_main
# - path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@192.168.0.51:554/cam/realmonitor?channel=1&subtype=2
roles:
- detect
- rtmp
detect:
width: 640
height: 480
fps:
Here is the error message from container system & portainer log.
*************************************************************
*** Your config file is not valid! ***
*** Please check the docs at ***
*** https://docs.frigate.video/configuration/index ***
*************************************************************
*************************************************************
*** Config Validation Errors ***
*************************************************************
expected '<document start>', but found '<block mapping start>'
in "<unicode string>", line 14, column 1:
^
*************************************************************
*** End Config Validation Errors ***
*************************************************************
[cmd] python3 exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
any help would be appreciated so i carry on.
I didnāt see this described in the doco.
Quick example of this?
Here is an example of how it can be specified for individual inputs: Separate hw accel args for different output functions Ā· Issue #2160 Ā· blakeblackshear/frigate Ā· GitHub
1 Like