From a2a75b04f49f83d2e137e4430123e0b99d06fd22 Mon Sep 17 00:00:00 2001
From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com>
Date: Thu, 30 Jan 2025 09:44:03 -0600
Subject: [PATCH] docs for threshold

---
 docs/docs/configuration/zones.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/docs/docs/configuration/zones.md b/docs/docs/configuration/zones.md
index df254ed1f..c194913bb 100644
--- a/docs/docs/configuration/zones.md
+++ b/docs/docs/configuration/zones.md
@@ -163,3 +163,17 @@ The average speed of your object as it moved through your zone is saved in Friga
 - The more accurate your real-world dimensions can be measured, the more accurate speed estimation will be. However, due to the way Frigate's tracking algorithm works, you may need to tweak the real-world distance values so that estimated speeds better match real-world speeds.
 - Once an object leaves the zone, speed accuracy will likely decrease due to perspective distortion and misalignment with the calibrated area. Therefore, speed values will show as a zero through MQTT and will not be visible on the debug view when an object is outside of a speed tracking zone.
 - The speeds are only an _estimation_ and are highly dependent on camera position, zone points, and real-world measurements. This feature should not be used for law enforcement.
+
+### Speed Threshold
+
+Zones can be configured with a minimum speed requirement, meaning an object must be moving at or above this speed to be considered inside the zone. Zone `distances` must be defined as described above.
+
+```yaml
+cameras:
+  name_of_your_camera:
+    zones:
+      sidewalk:
+        coordinates: ...
+        distances: ...
+        speed_threshold: 20 # unit is in kph or mph, depending on how unit_system is set (see above)
+```