Fixes (#18625)

* Indicate disabling a camera and alerts/detections is temporary * generalize gasket driver docs * improve face rec faq * Update intel hardware recommendations * Update hardware acceleration * Add Hebrew and Catalan --------- Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com>
2025-07-26 13:47:03 +02:00 · 2025-06-11 13:08:46 -05:00 · 2025-06-11 13:08:46 -05:00 · 4a21b2f16d
commit 4a21b2f16d
parent 99e7533de2
8 changed files with 32 additions and 6 deletions
--- a/docs/docs/configuration/face_recognition.md
+++ b/docs/docs/configuration/face_recognition.md
@ -133,6 +133,27 @@ Once front-facing images are performing well, start choosing slightly off-angle

 ## FAQ

+### How do I debug Face Recognition issues?
+
+Start with the [Usage](#usage) section and re-read the [Model Requirements](#model-requirements) above.
+
+1. Ensure `person` is being _detected_. A `person` will automatically be scanned by Frigate for a face. Any detected faces will appear in the Train tab in the Frigate UI's Face Library.
+
+   If you are using a Frigate+ or `face` detecting model:
+
+   - Watch the debug view (Settings --> Debug) to ensure that `face` is being detected along with `person`.
+   - You may need to adjust the `min_score` for the `face` object if faces are not being detected.
+
+   If you are **not** using a Frigate+ or `face` detecting model:
+
+   - Check your `detect` stream resolution and ensure it is sufficiently high enough to capture face details on `person` objects.
+   - You may need to lower your `detection_threshold` if faces are not being detected.
+
+2. Any detected faces will then be _recognized_.
+
+   - Make sure you have trained at least one face per the recommendations above.
+   - Adjust `recognition_threshold` settings per the suggestions [above](#advanced-configuration).
+
 ### Detection does not work well with blurry images?

 Accuracy is definitely a going to be improved with higher quality cameras / streams. It is important to look at the DORI (Detection Observation Recognition Identification) range of your camera, if that specification is posted. This specification explains the distance from the camera that a person can be detected, observed, recognized, and identified. The identification range is the most relevant here, and the distance listed by the camera is the furthest that face recognition will realistically work.
--- a/docs/docs/configuration/hardware_acceleration_video.md
+++ b/docs/docs/configuration/hardware_acceleration_video.md
@ -71,7 +71,8 @@ Or map in all the `/dev/video*` devices.

 | CPU Generation | Intel Driver | Recommended Preset  | Notes                                |
 | -------------- | ------------ | ------------------- | ------------------------------------ |
-| gen1 - gen7    | i965         | preset-vaapi        | qsv is not supported                 |
+| gen1 - gen5    | i965         | preset-vaapi        | qsv is not supported                 |
+| gen6 - gen7    | iHD          | preset-vaapi        | qsv is not supported                 |
 | gen8 - gen12   | iHD          | preset-vaapi        | preset-intel-qsv-\* can also be used |
 | gen13+         | iHD / Xe     | preset-intel-qsv-\* |                                      |
 | Intel Arc GPU  | iHD / Xe     | preset-intel-qsv-\* |                                      |
--- a/docs/docs/frigate/hardware.md
+++ b/docs/docs/frigate/hardware.md
@ -116,7 +116,7 @@ Inference speeds vary greatly depending on the CPU or GPU used, some known examp
 | Intel HD 630   | ~ 15 ms                    | 320: ~ 30 ms              |                        |                                    |
 | Intel UHD 730  | ~ 10 ms                    | 320: ~ 19 ms 640: ~ 54 ms |                        |                                    |
 | Intel UHD 770  | ~ 15 ms                    | 320: ~ 20 ms 640: ~ 46 ms |                        |                                    |
-| Intel N100     | ~ 15 ms                    | 320: ~ 20 ms              |                        |                                    |
+| Intel N100     | ~ 15 ms                    | 320: ~ 25 ms              |                        | Can only run one detector instance |
 | Intel Iris XE  | ~ 10 ms                    | 320: ~ 18 ms 640: ~ 50 ms |                        |                                    |
 | Intel Arc A380 | ~ 6 ms                     | 320: ~ 10 ms 640: ~ 22 ms | 336: 20 ms 448: 27 ms  |                                    |
 | Intel Arc A750 | ~ 4 ms                     | 320: ~ 8 ms               |                        |                                    |
--- a/docs/docs/troubleshooting/edgetpu.md
+++ b/docs/docs/troubleshooting/edgetpu.md
@ -55,10 +55,10 @@ The USB Coral can become stuck and need to be restarted, this can happen for a n

 ## PCIe Coral Not Detected

-The most common reason for the PCIe Coral not being detected is that the driver has not been installed. This process varies based on what OS and kernel that is being run. 
+The most common reason for the PCIe Coral not being detected is that the driver has not been installed. This process varies based on what OS and kernel that is being run.

 - In most cases [the Coral docs](https://coral.ai/docs/m2/get-started/#2-install-the-pcie-driver-and-edge-tpu-runtime) show how to install the driver for the PCIe based Coral.
- For Ubuntu 22.04+ https://github.com/jnicolson/gasket-builder can be used to build and install the latest version of the driver.
+- For some newer Linux distros (for example, Ubuntu 22.04+), https://github.com/jnicolson/gasket-builder can be used to build and install the latest version of the driver.

 ## Attempting to load TPU as pci & Fatal Python error: Illegal instruction

--- a/web/public/locales/en/common.json
+++ b/web/public/locales/en/common.json
@ -163,6 +163,7 @@
      "sk": "Slovenčina (Slovak)",
      "yue": "粵語 (Cantonese)",
      "th": "ไทย (Thai)",
+      "ca": "Català (Catalan)",
      "withSystem": {
        "label": "Use the system settings for language"
      }
--- a/web/public/locales/en/views/settings.json
+++ b/web/public/locales/en/views/settings.json
@ -148,11 +148,11 @@
    "title": "Camera Settings",
    "streams": {
      "title": "Streams",
-      "desc": "Disabling a camera completely stops Frigate's processing of this camera's streams. Detection, recording, and debugging will be unavailable.<br /> <em>Note: This does not disable go2rtc restreams.</em>"
+      "desc": "Temporarily disable a camera until Frigate restarts. Disabling a camera completely stops Frigate's processing of this camera's streams. Detection, recording, and debugging will be unavailable.<br /> <em>Note: This does not disable go2rtc restreams.</em>"
    },
    "review": {
      "title": "Review",
-      "desc": "Enable/disable alerts and detections for this camera. When disabled, no new review items will be generated.",
+      "desc": "Temporarily enable/disable alerts and detections for this camera until Frigate restarts. When disabled, no new review items will be generated. ",
      "alerts": "Alerts ",
      "detections": "Detections "
    },
--- a/web/src/hooks/use-date-locale.ts
+++ b/web/src/hooks/use-date-locale.ts
@ -34,6 +34,7 @@ const localeMap: Record<string, () => Promise<Locale>> = {
  "yue-Hant": () =>
    import("date-fns/locale/zh-HK").then((module) => module.zhHK),
  th: () => import("date-fns/locale/th").then((module) => module.th),
+  ca: () => import("date-fns/locale/ca").then((module) => module.ca),
 };

 export function useDateLocale(): Locale {
--- a/web/src/lib/const.ts
+++ b/web/src/lib/const.ts
@ -5,11 +5,13 @@ export const supportedLanguageKeys = [
  "fr",
  "de",
  "it",
+  "ca",
  "nl",
  "nb-NO",
  "zh-CN",
  "yue-Hant",
  "th",
+  "he",
  "ru",
  "tr",
  "pl",