Closed MrSiO closed 2 years ago
0 is the default and just means once an object is stationary it will not have any checks to confirm it is still there. If you want to disable stationary then you should use the max_frames option as described in the docs
What I'm looking to achieve is to stop the constant frigate/events when a stationary object has been labeled as such.
I'll read the documentation again and confirm.
I don't believe there is currently a way to disable the Mqtt messages but keep stationary detection enabled. Just curious, why do you want to disable these messages? They should be able to be ignored along other updates to mqtt topic
Thx @NickM-27 for your guiding. I found the comment that I had over read:
` # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
# 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: 3000
# Optional: Object specific values
objects:
person: 1000`
The reason (at first) was because before the latest update, the only MQTT:frigate/events I was receiving were from actual detections (car, person and dog). These frigates/events were directly feeding my Node-Red automations.
Now with tracking of stationnary objects, I was getting the MQTT:frigate/events every 60 seconds when my car was parked and labeled as "stationary", sending me a PIX every 60 sec....
I have, in the mean time, modified my node-red to ignore messages containing : stationary: true That did fix my issue.
I have no use at the current time for updates about stationary objects, but might be better to keep em on and filter at node-red input.
Thx alot.
Describe the problem you are having
Hi, With the deployment of 0.10.0-BFECEE9 and the introduction of stationary object traking, I tried disabling this tracking by adding the following settings:
Unfortunately this seems to have no effect as I keep receiving regular updates (MQTT) when a stationary detection is present. When a car is detected is goes to stationary true, I then keep getting MQTT updates every 60 seconds about that stationnary car even-if my interval was set to zero.
Version
0.10.0-BFECEE9
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
amcrest
Any other information that may be helpful
FFprobe and Frigate stats will be provided shortly