-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop running detection on stationary objects #195
Comments
Motion masks are not motion masks. edit: I see you defined both. The object masks operate based on the bottom center of the bounding box. Are you certain that point is within the mask? |
I disabled car tracking in my front yard - as my parked car would generate far more videos than any person / cat / .. really moving through. I'm speculating here - but quite some of those 'parked car videos' contain a bypassing car on the street. The street is masked in both, object filter car + motion.
The mask works perfect for pedestrians, after some fine tuning its very precise, so I believe the mask is correct, yes. I saw your post in another topic - i might re-enable with bounding boxes to narrow down the scenario:
|
It's sort of ridiculous that it keeps detecting my parked car. Why Frigate is concerned with stationary objects to begin with is beyond me. |
All objects should remain tracked otherwise frigate will pick that vehicle up again when motion happens around it and treat it as a new event when it's actually not. There's no consequences to tracking stationary objects as it is efficient and enables finer control of what gets recorded https://docs.frigate.video/configuration/record#what-do-the-different-retain-modes-mean |
What frigate must track to do it's job properly is not something the user should be bombarded with. Dozens of events about stationary things is preposterous. How about the program work intuitively out of the box without users having to fix it's quirks just to get something that's not overly annoying? |
Not sure what you're referring to exactly. There's no reason a user needs to be "bombarded" with notifications. There's countless notifications blueprints for HA and a guide I wrote #2898 that properly setup notifications that and don't sent notifications for stationary objects. If you're going to setup notifications yourself then you should be aware of how the system works and account for it. All of this is in the documentation. |
You seems to have blinders on concerning this issue. I am talking about events within Frigate, not HA. I see loads of useless events for a stationary car. These events and recordings are a waste of energy and resources and should be fixed instead of being called a feature. You might need to step back from the code to get a normal perspective every now and then. |
Ah I see, I misunderstood what you were referring to. In that case you probably don't have frigate configured properly so it's creating multiple events, when the expected behavior is to have one event the whole time the car is there. If you create a support issue we'd be happy to help make suggestions. |
There should not be complication involved or a special setup required for stationary objects to be redetected over and over. Why it has the need to record video of stationary items to begin with seem counter intuitive. If I have to jump through hoops to make Frigate behave normally then that would mean there is an unresolved issue that needs attention. This should never be a user issue. I just set this software up and it has no special configuration. All I know is I have numerous recordings of no movement other than drifting snow, and it keeps identifying my stationary car. It would be nice if there was just a simple option to stop all detection of anything that doesn't move. A security system that detects things that do not move is the exact opposite of what I or anyone desires. |
For things like parked cars, there is no reason to keep running detection on the car if there is no motion within the bounding box of the car. It should just assume the object is still there.
The text was updated successfully, but these errors were encountered: