Make timeout of object detection configurable per camera
See original GitHub issuePer this post: https://community.home-assistant.io/t/local-realtime-person-detection-for-rtsp-cameras/103107/1779
It’d be great to be able to change how many frames it takes for Frigate to determine when an object has disappeared. Even with my 3fps cameras (without -vsync drop
and explicitly set at -f 3
) Frigate seems to be frame hungry and I see frame rates increase to the point that objects that should technically take ~3 seconds to mark as no longer there seem to disappear in less than a second, thus causing a quick flip of my binary sensor in HA.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
DOODS - Dedicated Open Object Detection Service
This leads to excessive processing if the image on the camera hasn't changed, as the default scan_interval is 10 seconds. You can override...
Read more >How to configure the object detection laser timeout.
Go to section "Object Detection Laser Timeout" page 4-9 ff: If scanner is working from a stand, read the bar code labelled as...
Read more >Tips to Configure Camera Analytic Events for Better Analytics ...
Using the ACC Client, set up the camera analytic events using the following approaches to help tweak your detection success. Make sure Analytics...
Read more >Configuration File - Frigate Docs
Optional: enables detection for the camera (default: True). # This value can be set via MQTT and will be updated in startup based...
Read more >Object Identification in Offline Videos — FindFace Multi 1.2 ...
Configure the timestamps for object recognition events. On the Advanced tab, fine-tune the video processing: video_advanced_en. Check detectors that you ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
it was recently readded: https://github.com/blakeblackshear/frigate/commit/69406343eedc7ca20dce4bd30efc7d32cefe66d2
I just added the
-r <fps>
to theoutput_args
and am testing it now. If that fixes the issue, great. It would still be helpful to have the frame count configurable, however.