Fixes (#18235)

* fix face library i18n

* Docs updates

docs/docs/configuration/license_plate_recognition.md

@@ -335,19 +335,37 @@ Use `match_distance` to allow small character mismatches. Alternatively, define
 
 ### How do I debug LPR issues?
 
-- View MQTT messages for `frigate/events` to verify detected plates.
-- If you are using a Frigate+ model or a model that detects license plates, watch the debug view (Settings --> Debug) to ensure that `license_plate` is being detected with a `car` or `motorcycle`.
-- Watch the debug view to see plates recognized in real-time. For non-dedicated LPR cameras, the `car` or `motorcycle` label will change to the recognized plate when LPR is enabled and working.
-- Adjust `detection_threshold` and `recognition_threshold` settings per the suggestions [above](#advanced-configuration).
-- Enable `debug_save_plates` to save images of detected text on plates to the clips directory (`/media/frigate/clips/lpr`). Ensure these images are readable and the text is clear.
-- Enable debug logs for LPR by adding `frigate.data_processing.common.license_plate: debug` to your `logger` configuration. These logs are _very_ verbose, so only enable this when necessary.
+Start with ["Why isn't my license plate being detected and recognized?"](#why-isnt-my-license-plate-being-detected-and-recognized). If you are still having issues, work through these steps.
 
-  ```yaml
-  logger:
-    default: info
-    logs:
-      frigate.data_processing.common.license_plate: debug
-  ```
+1. Enable debug logs to see exactly what Frigate is doing.
+
+   - Enable debug logs for LPR by adding `frigate.data_processing.common.license_plate: debug` to your `logger` configuration. These logs are _very_ verbose, so only keep this enabled when necessary.
+
+     ```yaml
+     logger:
+       default: info
+       logs:
+         frigate.data_processing.common.license_plate: debug
+     ```
+
+2. Ensure your plates are being _detected_.
+
+   If you are using a Frigate+ or `license_plate` detecting model:
+
+   - Watch the debug view (Settings --> Debug) to ensure that `license_plate` is being detected.
+   - View MQTT messages for `frigate/events` to verify detected plates.
+   - You may need to adjust your `min_score` and/or `threshold` for the `license_plate` object if your plates are not being detected.
+
+   If you are **not** using a Frigate+ or `license_plate` detecting model:
+
+   - Watch the debug logs for messages from the YOLOv9 plate detector.
+   - You may need to adjust your `detection_threshold` if your plates are not being detected.
+
+3. Ensure the characters on detected plates are being _recognized_.
+
+   - Enable `debug_save_plates` to save images of detected text on plates to the clips directory (`/media/frigate/clips/lpr`). Ensure these images are readable and the text is clear.
+   - Watch the debug view to see plates recognized in real-time. For non-dedicated LPR cameras, the `car` or `motorcycle` label will change to the recognized plate when LPR is enabled and working.
+   - Adjust `recognition_threshold` settings per the suggestions [above](#advanced-configuration).
 
 ### Will LPR slow down my system?
 

docs/docs/configuration/zones.md

@@ -136,7 +136,7 @@ Your zone must be defined with exactly 4 points and should be aligned to the gro
 
 ![Ground plane 4-point zone](/img/ground-plane.jpg)
 
-Speed estimation requires a minimum number of frames for your object to be tracked before a valid estimate can be calculated, so create your zone away from places where objects enter and exit for the best results. _Your zone should not take up the full frame._ An object's speed is tracked while it is in the zone and then saved to Frigate's database.
+Speed estimation requires a minimum number of frames for your object to be tracked before a valid estimate can be calculated, so create your zone away from places where objects enter and exit for the best results. The object's bounding box must be stable and remain a constant size as it enters and exits the zone. _Your zone should not take up the full frame, and the zone does **not** need to be the same size or larger than the objects passing through it._ An object's speed is tracked while it passes through the zone and then saved to Frigate's database.
 
 Accurate real-world distance measurements are required to estimate speeds. These distances can be specified in your zone config through the `distances` field.
 
@@ -165,8 +165,9 @@ These speed values are output as a number in miles per hour (mph) or kilometers
 
 #### Best practices and caveats
 
-- Speed estimation works best with a straight road or path when your object travels in a straight line across that path. Avoid creating your zone near intersections or anywhere that objects would make a turn. A large zone can be used, but it's not required and may even cause issues - if the object's bounding box changes shape (such as when it turns or becomes partially hidden), the speed estimate will be inaccurate. Generally it's best to make your zone large enough to capture a few frames, but small enough so that the bounding box doesn't change size as it travels through the zone.
-- Create a zone where the bottom center of your object's bounding box travels directly through it and does not become obscured at any time. See the photo example above.
+- Speed estimation works best with a straight road or path when your object travels in a straight line across that path. Avoid creating your zone near intersections or anywhere that objects would make a turn.
+- Create a zone where the bottom center of your object's bounding box travels directly through it and does not become obscured at any time.
+- A large zone can be used (as in the photo example above), but it may cause inaccurate estimation if the object's bounding box changes shape (such as when it turns or becomes partially hidden). Generally it's best to make your zone large enough to capture a few frames, but small enough so that the bounding box doesn't change size as it enters, travels through, and exits the zone.
 - Depending on the size and location of your zone, you may want to decrease the zone's `inertia` value from the default of 3.
 - 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.

web/public/locales/en/views/faceLibrary.json

@@ -69,6 +69,7 @@
     "maxSize": "Max size: {{size}}MB"
   },
   "nofaces": "No faces available",
+  "pixels": "{{area}}px",
   "readTheDocs": "Read the documentation",
   "trainFaceAs": "Train Face as:",
   "trainFace": "Train Face",

web/src/pages/FaceLibrary.tsx

@@ -791,7 +791,7 @@ function FaceAttemptGroup({
       <div className="flex flex-row justify-between">
         <div className="flex flex-col gap-1">
           <div className="select-none smart-capitalize">
-            Person
+            {t("details.person")}
             {event?.sub_label
               ? `: ${event.sub_label} (${Math.round((event.data.sub_label_score || 0) * 100)}%)`
               : ": " + t("details.unknown")}
@@ -974,7 +974,7 @@ function FaceAttempt({
           />
           {imageArea != undefined && (
             <div className="absolute bottom-1 right-1 z-10 rounded-lg bg-black/50 px-2 py-1 text-xs text-white">
-              {imageArea}px
+              {t("pixels", { area: imageArea })}
             </div>
           )}
         </div>