From 7d12583ebc5b66271fb3a48b24946ba68e81d667 Mon Sep 17 00:00:00 2001 From: Blake Blackshear Date: Mon, 9 Nov 2026 06:49:43 -0600 Subject: [PATCH 1/9] update recommended camera list (#24919) --- docs/docs/frigate/hardware.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/docs/frigate/hardware.md b/docs/docs/frigate/hardware.md index d38d065443..f3d7405bd4 100644 --- a/docs/docs/frigate/hardware.md +++ b/docs/docs/frigate/hardware.md @@ -9,7 +9,7 @@ import CommunityBadge from '@site/src/components/CommunityBadge'; Cameras that output H.264 video and AAC audio will offer the most compatibility with all features of Frigate and Home Assistant. It is also helpful if your camera supports multiple substreams to allow different resolutions to be used for detection, streaming, and recordings without re-encoding. -I recommend Dahua, Hikvision, and Amcrest in that order. Dahua edges out Hikvision because they are easier to find and order, not because they are better cameras. I personally use Dahua cameras because they are easier to purchase directly. In my experience Dahua and Hikvision both have multiple streams with configurable resolutions and frame rates and rock solid streams. They also both have models with large sensors well known for excellent image quality at night. Not all the models are equal. Larger sensors are better than higher resolutions; especially at night. Amcrest is the fallback recommendation because they are rebranded Dahuas. They are rebranding the lower end models with smaller sensors or less configuration options. +I recommend Dahua and Hikvision. Dahua edges out Hikvision because they are easier to find and order, not because they are better cameras. I personally use Dahua cameras because they are easier to purchase directly. In my experience Dahua and Hikvision both have multiple streams with configurable resolutions and frame rates and rock solid streams. They also both have models with large sensors well known for excellent image quality at night. Not all the models are equal. Larger sensors are better than higher resolutions; especially at night. WiFi cameras are not recommended as [their streams are less reliable and cause connection loss and/or lost video data](https://ipcamtalk.com/threads/camera-conflicts.68142/#post-738821), especially when more than a few WiFi cameras will be used at the same time. @@ -17,10 +17,9 @@ Many users have reported various issues with 4K-plus Reolink cameras, it is best Here are some of the cameras I recommend: -- Loryta(Dahua) IPC-T549M-ALED-S3 (affiliate link) -- Loryta(Dahua) IPC-T54IR-AS (affiliate link) -- Amcrest IP5M-T1179EW-AI-V3 (affiliate link) -- HIKVISION DS-2CD2387G2P-LSU/SL ColorVu 8MP Panoramic Turret IP Camera (affiliate link) +- GemaVision(Dahua) IPC-T549M-ALED-S3 (affiliate link) +- GemaVision(Dahua) IPC-T54IR-AS (affiliate link) +- HIKVISION DS-2CD2387G2P-LSU/SL ColorVu 8MP Panoramic Turret IP Camera (affiliate link) I may earn a small commission for my endorsement, recommendation, testimonial, or link to any products or services from this website. From 2d25f9a8b5fbff74e0429fe41c02d2157b74860a Mon Sep 17 00:00:00 2001 From: yufretti <43564870+yufretti@users.noreply.github.com> Date: Wed, 11 Nov 2026 17:52:48 +0100 Subject: [PATCH 2/9] docs: add yuFriEye (iOS/macOS client) to third party extensions (#24942) --- docs/docs/integrations/third_party_extensions.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/docs/integrations/third_party_extensions.md b/docs/docs/integrations/third_party_extensions.md index 3e44c9d8ae..448d8c9eda 100644 --- a/docs/docs/integrations/third_party_extensions.md +++ b/docs/docs/integrations/third_party_extensions.md @@ -70,3 +70,7 @@ This is a fork (with fixed errors and new features) of [original Double Take](ht ## [Strix](https://github.com/eduard256/Strix) [Strix](https://github.com/eduard256/Strix) auto-discovers working stream URLs for IP cameras and generates ready-to-use Frigate configs. It tests thousands of URL patterns against your camera and supports cameras without RTSP or ONVIF. 67K+ camera models from 3.6K+ brands. + +## [yuFriEye](https://apps.apple.com/app/id6832456692) + +[yuFriEye](https://apps.apple.com/app/id6832456692) is a free native iOS, iPadOS and macOS client for Frigate. It shows the live camera grid with low-latency go2rtc streams, alerts and detections with clip playback and motion boxes, recordings by day with continuous playback, Frigate and go2rtc logs, and supports multiple servers with local and remote addresses. Works with or without Frigate authentication; no account or data collection. From cc94cbc2da93527b29439f5582d2f93cddf97263 Mon Sep 17 00:00:00 2001 From: Nicolas Mowen Date: Thu, 12 Nov 2026 11:41:09 -0700 Subject: [PATCH 3/9] Add mjpeg warning (#24954) --- docs/static/frigate-api.yaml | 5 ++++- frigate/api/media.py | 14 +++++++++++++- 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/docs/static/frigate-api.yaml b/docs/static/frigate-api.yaml index 7753ed7af3..fcbde123cb 100644 --- a/docs/static/frigate-api.yaml +++ b/docs/static/frigate-api.yaml @@ -5374,6 +5374,10 @@ paths: tags: - Media summary: Mjpeg Feed + description: |- + **Access:** Authenticated user with access to the referenced camera. + + An MJPEG stream of the camera's latest processed frame, intended for debugging only. Every frame of every open stream is color converted, annotated, resized, and JPEG encoded in Frigate's main process, which adds load to the system and can slow down Frigate's processing. It is strictly not recommended to view this stream continuously, such as on a dashboard. For live viewing, use a go2rtc restream instead. The frame rate and resolution can be raised with the fps and height parameters, for example ?fps=10&height=1080, at the cost of additional load. operationId: mjpeg_feed__camera_name__get parameters: - name: camera_name @@ -5461,7 +5465,6 @@ paths: security: - frigateUserAuth: [] x-required-role: camera - description: '**Access:** Authenticated user with access to the referenced camera.' /{camera_name}/ptz/info: get: tags: diff --git a/frigate/api/media.py b/frigate/api/media.py index d6e2a7f836..cd287f1667 100644 --- a/frigate/api/media.py +++ b/frigate/api/media.py @@ -74,7 +74,19 @@ def _resolve_cache_age(max_cache_age: int) -> int: return max_cache_age.default -@router.get("/{camera_name}", dependencies=[Depends(require_camera_access)]) +@router.get( + "/{camera_name}", + dependencies=[Depends(require_camera_access)], + description=( + "An MJPEG stream of the camera's latest processed frame, intended for debugging only. " + "Every frame of every open stream is color converted, annotated, resized, and JPEG " + "encoded in Frigate's main process, which adds load to the system and can slow down " + "Frigate's processing. It is strictly not recommended to view this stream " + "continuously, such as on a dashboard. For live viewing, use a go2rtc restream " + "instead. The frame rate and resolution can be raised with the fps and height " + "parameters, for example ?fps=10&height=1080, at the cost of additional load." + ), +) async def mjpeg_feed( request: Request, camera_name: str, From d3b7d4ea448536b46ea75229f6e54ff851b051bf Mon Sep 17 00:00:00 2001 From: Blake Blackshear Date: Sun, 15 Nov 2026 07:57:07 -0600 Subject: [PATCH 4/9] Add Frigate+ model selection guide (#24981) --- docs/docs/plus/choosing_a_model.md | 121 +++++++++++++++++++++++++++++ docs/docs/plus/first_model.md | 2 +- docs/docs/plus/index.md | 30 +++---- docs/sidebars.ts | 1 + 4 files changed, 138 insertions(+), 16 deletions(-) create mode 100644 docs/docs/plus/choosing_a_model.md diff --git a/docs/docs/plus/choosing_a_model.md b/docs/docs/plus/choosing_a_model.md new file mode 100644 index 0000000000..7447e39aa2 --- /dev/null +++ b/docs/docs/plus/choosing_a_model.md @@ -0,0 +1,121 @@ +--- +id: choosing_a_model +title: Choosing a model +--- + +Frigate+ offers several model types, sizes, and input resolutions. This page compares their accuracy and speed to help you decide which one to request. Make sure the model type you choose is supported by your detector, as shown in the [supported detector types](./index.md#supported-detector-types) table. + +## Recommendations + +- **YOLOv9-s at 320** is the balanced default if your hardware runs it well. It detects about twice as many objects as MobileDet, and 15 more per 100 than YOLO-NAS-s at 320, at the same false alarm rate. +- **Moving up a size at 320** helps more than moving to 640 for most cameras. YOLOv9-m at 320 detects more objects than YOLOv9-s at 640 (60% vs 59%) with lower GPU latency. +- **640 input** is rarely needed. Frigate doesn't run detection on the full frame. It crops a region around motion and resizes it to the model's input size, so with a 320 model it zooms in on a smaller area of the frame and small objects are no longer small to the model. 640 models detect small objects better within a large region, but not compared to a 320 model looking at a smaller, zoomed-in region. See [object size and input resolution](#object-size-and-input-resolution) for details. +- **YOLOv9-c** gains little over YOLOv9-m: about 2 points of detection rate at 320 and none at 640, with more latency. On CPU it takes 1.4 to 1.7 times as long as YOLOv9-m. +- **YOLOv9-t at 640** is no better than YOLOv9-s at 320 (55% vs 54%) and is slower on both GPU and CPU. +- **YOLO-NAS-s** and **MobileDet** are only worth considering on hardware that can't run YOLOv9. Everywhere else, a YOLOv9 model of similar speed is more accurate. + +Results on your own hardware and cameras will differ, so test with the base models before requesting a model. + +### Thresholds + +Each model's threshold for 95% precision is listed in the [accuracy](#accuracy) table. YOLOv9 models reach it at about 0.70 to 0.77. MobileDet (0.82) and YOLO-NAS-s (0.86 to 0.89) need higher thresholds, so with Frigate's default threshold they produce more false positives than the YOLOv9 models. See [object filters](../configuration/object_filters.md#object-scores) for how to adjust thresholds. + +## How these were measured + +The numbers on this page are for the 2026.3 base models. + +- **Images:** 10,947 images from the Frigate+ validation set, from real Frigate cameras. Images that share a source with training images are excluded. +- **Processing:** every model runs through Frigate's own detector code and post-processing (Frigate 0.18.2), exactly as deployed. +- **Labels:** results cover the 12 most common labels: `car`, `person`, `waste_bin`, `license_plate`, `dog`, `cat`, `face`, `bicycle`, `bird`, `deer`, `bbq_grill`, and `package`. +- **Single frames:** each image is scored on its own. In Frigate, an object has to score well across several frames before it becomes a tracked object, so brief one-frame mistakes rarely reach you. Use these numbers to compare models with each other, not as event rates. + +**Detection rate at 95% precision** is the main accuracy number. It's the share of real objects a model detects when its threshold is set so that 95% of its detections are correct (about 1 false detection in 20). Every model is held to the same false alarm rate, so the detection rates compare directly. The threshold that achieves this is shown too, because it differs between models. + +## Accuracy + +| Model | Input | Detection rate at 95% precision | Missed objects per 100 | Threshold for 95% precision | AP50 | +| ---------- | ----- | ------------------------------- | ---------------------- | --------------------------- | ---- | +| MobileDet | 320 | 24% | 76 | 0.82 | 0.47 | +| YOLO-NAS-s | 320 | 39% | 61 | 0.86 | 0.44 | +| YOLO-NAS-s | 640 | 48% | 52 | 0.89 | 0.55 | +| YOLOv9-t | 320 | 45% | 55 | 0.69 | 0.44 | +| YOLOv9-t | 640 | 55% | 45 | 0.70 | 0.54 | +| YOLOv9-s | 320 | 54% | 46 | 0.74 | 0.54 | +| YOLOv9-s | 640 | 59% | 41 | 0.75 | 0.61 | +| YOLOv9-m | 320 | 60% | 40 | 0.75 | 0.58 | +| YOLOv9-m | 640 | 64% | 36 | 0.77 | 0.64 | +| YOLOv9-c | 320 | 62% | 38 | 0.75 | 0.60 | +| YOLOv9-c | 640 | 63% | 37 | 0.77 | 0.64 | + +AP50 is the standard COCO metric (IoU 0.5) averaged over the 12 labels. It summarizes accuracy across every threshold, while the detection rate describes one realistic setting. + +:::note + +These AP50 numbers can't be compared to the COCO results published for YOLOv9, YOLO-NAS, and other models. Those results are measured on the COCO dataset, while these are measured on images from security cameras, with a different set of labels (several, such as `license_plate`, `face`, and `package`, aren't in COCO) and through Frigate's own post-processing. Published COCO results also usually report mAP averaged over IoU 0.5 to 0.95 rather than AP50. Use these numbers only to compare Frigate+ models with each other. + +::: + +### By object size + +AP50 by object size: + +| Model | Input | Small | Medium | Large | +| ---------- | ----- | ----- | ------ | ----- | +| MobileDet | 320 | 0.23 | 0.62 | 0.71 | +| YOLO-NAS-s | 320 | 0.23 | 0.57 | 0.60 | +| YOLO-NAS-s | 640 | 0.42 | 0.63 | 0.58 | +| YOLOv9-t | 320 | 0.22 | 0.60 | 0.67 | +| YOLOv9-t | 640 | 0.42 | 0.63 | 0.57 | +| YOLOv9-s | 320 | 0.35 | 0.70 | 0.73 | +| YOLOv9-s | 640 | 0.51 | 0.69 | 0.69 | +| YOLOv9-m | 320 | 0.40 | 0.73 | 0.74 | +| YOLOv9-m | 640 | 0.54 | 0.71 | 0.72 | +| YOLOv9-c | 320 | 0.44 | 0.73 | 0.77 | +| YOLOv9-c | 640 | 0.54 | 0.71 | 0.74 | + +In these single-image results, 640 input mostly helps small objects, such as distant people, license plates, and faces, and doesn't help medium and large objects. For example, license plate AP50 rises from 0.32 to 0.55 for YOLOv9-s. These numbers overstate the benefit of 640 in Frigate, as explained below. + +#### Object size and input resolution + +Frigate doesn't send the full camera frame to the model. It crops a region around motion or a tracked object and resizes that region to the model's input size. With a 320 model the regions are smaller, so Frigate effectively zooms in on that part of the frame, and an object that is small in the full frame is no longer small to the model. A 640 model detects small objects better than a 320 model when both look at the same large region, but not when compared to a 320 model looking at a smaller, zoomed-in region. + +640 input can still help in scenes with large objects in the foreground and small objects in the background at the same time, such as a doorbell camera that sees a person on the porch and another person across the street. The region has to be large enough to fit the nearby person, so the distant person is small within it. Frigate already handles much of this case: when an object is small relative to the region it was detected in, Frigate runs a separate detection on a smaller region around it. + +### By label + +AP50 by label: + +| Label | MobileDet 320 | YOLO-NAS-s 320 | YOLOv9-t 320 | YOLOv9-s 320 | YOLOv9-m 320 | YOLOv9-c 320 | YOLO-NAS-s 640 | YOLOv9-t 640 | YOLOv9-s 640 | YOLOv9-m 640 | YOLOv9-c 640 | +| --------------- | ------------- | -------------- | ------------ | ------------ | ------------ | ------------ | -------------- | ------------ | ------------ | ------------ | ------------ | +| `car` | 0.73 | 0.72 | 0.70 | 0.77 | 0.81 | 0.82 | 0.82 | 0.79 | 0.83 | 0.85 | 0.84 | +| `person` | 0.65 | 0.62 | 0.62 | 0.72 | 0.75 | 0.76 | 0.71 | 0.69 | 0.76 | 0.78 | 0.77 | +| `waste_bin` | 0.52 | 0.49 | 0.49 | 0.55 | 0.57 | 0.58 | 0.60 | 0.60 | 0.62 | 0.62 | 0.63 | +| `license_plate` | 0.31 | 0.31 | 0.23 | 0.32 | 0.36 | 0.39 | 0.55 | 0.46 | 0.55 | 0.60 | 0.61 | +| `dog` | 0.38 | 0.35 | 0.39 | 0.53 | 0.53 | 0.57 | 0.40 | 0.48 | 0.53 | 0.55 | 0.58 | +| `cat` | 0.41 | 0.37 | 0.39 | 0.51 | 0.57 | 0.59 | 0.43 | 0.46 | 0.58 | 0.61 | 0.62 | +| `face` | 0.39 | 0.41 | 0.23 | 0.33 | 0.42 | 0.45 | 0.60 | 0.43 | 0.57 | 0.63 | 0.63 | +| `bicycle` | 0.46 | 0.43 | 0.40 | 0.51 | 0.56 | 0.55 | 0.54 | 0.49 | 0.58 | 0.62 | 0.60 | +| `bird` | 0.30 | 0.18 | 0.33 | 0.42 | 0.47 | 0.50 | 0.23 | 0.30 | 0.39 | 0.43 | 0.38 | +| `deer` | 0.51 | 0.50 | 0.51 | 0.62 | 0.69 | 0.71 | 0.59 | 0.56 | 0.60 | 0.70 | 0.67 | +| `bbq_grill` | 0.68 | 0.60 | 0.69 | 0.77 | 0.78 | 0.81 | 0.74 | 0.74 | 0.81 | 0.83 | 0.84 | +| `package` | 0.35 | 0.28 | 0.34 | 0.46 | 0.47 | 0.49 | 0.39 | 0.43 | 0.50 | 0.48 | 0.50 | + +## Speed + +Average time per detection in milliseconds, measured through Frigate's detector code and including post-processing. Lower is better. A blank cell means that combination was not measured. + +| Model | Input | NVIDIA RTX 5060 Ti (ONNX, CUDA) | Intel i9-13900K (OpenVINO, CPU) | Intel i9-13900K (ONNX, CPU) | Intel i9-13900K (TFLite, CPU) | +| ---------- | ----- | ------------------------------- | ------------------------------- | --------------------------- | ----------------------------- | +| MobileDet | 320 | | | | 8.4 | +| YOLO-NAS-s | 320 | 4.9 | 8.4 | 8.9 | | +| YOLO-NAS-s | 640 | 7.1 | 29.6 | 28.6 | | +| YOLOv9-t | 320 | 2.9 | 4.3 | 6.5 | | +| YOLOv9-t | 640 | 5.0 | 12.9 | 17.0 | | +| YOLOv9-s | 320 | 3.9 | 9.3 | 11.5 | | +| YOLOv9-s | 640 | 6.3 | 33.1 | 32.6 | | +| YOLOv9-m | 320 | 5.2 | 23.2 | 19.8 | | +| YOLOv9-m | 640 | 10.1 | 88.1 | 69.5 | | +| YOLOv9-c | 320 | 5.4 | 38.8 | 27.5 | | +| YOLOv9-c | 640 | 11.1 | 147.8 | 99.5 | | + +CPU times vary by about ±15% between runs. Speeds on other hardware, such as Google Coral, Hailo, Intel iGPUs and NPUs, AMD GPUs, and Rockchip NPUs, are not included here. Test the base models on your own hardware to compare speeds. diff --git a/docs/docs/plus/first_model.md b/docs/docs/plus/first_model.md index 875e8200fc..0d19a50509 100644 --- a/docs/docs/plus/first_model.md +++ b/docs/docs/plus/first_model.md @@ -17,7 +17,7 @@ For more detailed recommendations, you can refer to the docs on [annotating](./a ## Step 2: Submit a model request -Once you have an initial set of verified images, you can request a model on the Models page. For guidance on choosing a model type, refer to [this part of the documentation](./index.md#available-model-types). If you are unsure which type to request, you can test the base model for each version from the "Base Models" tab. For most hardware, `yolov9` is recommended; `mobiledet` is a legacy model type and will be removed in 2027. Each model request requires 1 of the 12 trainings that you receive with your annual subscription. This model will support all [label types available](./index.md#available-label-types) even if you do not submit any examples for those labels. Model creation can take up to 36 hours. +Once you have an initial set of verified images, you can request a model on the Models page. For guidance on choosing a model type, refer to [available model types](./index.md#available-model-types) and [choosing a model](./choosing_a_model.md). If you are unsure which type to request, you can test the base model for each version from the "Base Models" tab. For most hardware, `yolov9` is recommended; `mobiledet` is a legacy model type and will be removed in 2027. Each model request requires 1 of the 12 trainings that you receive with your annual subscription. This model will support all [label types available](./index.md#available-label-types) even if you do not submit any examples for those labels. Model creation can take up to 36 hours. ![Plus Models Page](/img/plus/plus-models.jpg) ## Step 3: Set your model diff --git a/docs/docs/plus/index.md b/docs/docs/plus/index.md index a4aa098924..14849477f7 100644 --- a/docs/docs/plus/index.md +++ b/docs/docs/plus/index.md @@ -13,13 +13,13 @@ Information on how to integrate Frigate+ with Frigate can be found in the [integ There are three model types offered in Frigate+, `yolov9`, `yolonas`, and `mobiledet` (legacy). All of these models are object detection models and are trained to detect the same set of labels [listed below](#available-label-types). -Not all model types are supported by all detectors, so it's important to choose a model type to match your detector as shown in the table under [supported detector types](#supported-detector-types). You can test model types for compatibility and speed on your hardware by using the base models. +Not all model types are supported by all detectors, so it's important to choose a model type to match your detector as shown in the table under [supported detector types](#supported-detector-types). You can test model types for compatibility and speed on your hardware by using the base models. For accuracy and speed comparisons between model types, sizes, and resolutions, see [choosing a model](./choosing_a_model.md). -| Model Type | Description | -| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `yolov9` | A leading SOTA (state of the art) object detection model with similar performance to yolonas, but on a wider range of hardware options. Runs on most hardware. | -| `yolonas` | A newer architecture that offers slightly higher accuracy and improved detection of small objects. Runs on Intel, NVidia GPUs, and AMD GPUs. | -| `mobiledet` | Legacy. Based on the same architecture as the default model included with Frigate. Runs on Google Coral devices and CPUs. | +| Model Type | Description | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `yolov9` | A leading SOTA (state of the art) object detection model. More accurate than yolonas at similar speeds, and runs on a wider range of hardware. Runs on most hardware. | +| `yolonas` | An alternative architecture for hardware that can't run yolov9. Runs on Intel, NVidia GPUs, and AMD GPUs. | +| `mobiledet` | Legacy. Based on the same architecture as the default model included with Frigate. Runs on Google Coral devices and CPUs. | :::warning @@ -29,15 +29,15 @@ Not all model types are supported by all detectors, so it's important to choose ### YOLOv9 Details -YOLOv9 models are available in `t`, `s`, `c`, and `edgetpu` variants, and an `m` size is coming soon. When requesting a `yolov9` model, you will be prompted to choose a variant. If you want the model to be compatible with a Google Coral, you will need to choose the `edgetpu` variant, which requires Frigate 0.17 or later. If you are unsure what variant to choose, you should perform some tests with the base models to find the performance level that suits you. The `s` size is most similar to the current `yolonas` models in terms of inference times and accuracy, and a good place to start is the `320x320` resolution model for `yolov9s`. The `c` size is larger and offers higher accuracy at the cost of slower inference, so it is best suited to more powerful hardware such as GPUs. +YOLOv9 models are available in `t`, `s`, `m`, `c`, and `edgetpu` variants. When requesting a `yolov9` model, you will be prompted to choose a variant. If you want the model to be compatible with a Google Coral, you will need to choose the `edgetpu` variant, which requires Frigate 0.17 or later. If you are unsure what variant to choose, you should perform some tests with the base models to find the performance level that suits you. The `s` size has similar inference times to the current `yolonas` models with noticeably higher accuracy, and a good place to start is the `320x320` resolution model for `yolov9s`. The `m` size offers higher accuracy at the cost of slower inference, so it is best suited to more powerful hardware such as GPUs. The `c` size is slower still and offers little accuracy gain over `m`. See [choosing a model](./choosing_a_model.md) for detailed accuracy and speed comparisons. -| Variant | Size | Parameters | Speed and accuracy | Best suited for | -| --------- | -------------------- | ---------- | ----------------------------------------------------------- | -------------------------------------------------- | -| `t` | Tiny | ~2.0M | Fastest inference, lowest accuracy | Low power hardware or a large number of cameras | -| `s` | Small | ~7.1M | Balanced. Similar inference times and accuracy to `yolonas` | Most users. Start with `320x320` | -| `m` | Medium (coming soon) | ~20.0M | Slower than `s` with higher accuracy | Mid-range GPUs and NPUs | -| `c` | Compact | ~25.3M | Highest accuracy, slowest inference | More powerful hardware such as GPUs | -| `edgetpu` | N/A | N/A | Optimized to run on the Coral's Edge TPU | Google Coral devices only (requires Frigate 0.17+) | +| Variant | Size | Parameters | Speed and accuracy | Best suited for | +| --------- | ------- | ---------- | ------------------------------------------------------------- | -------------------------------------------------- | +| `t` | Tiny | ~2.0M | Fastest inference, lowest accuracy | Low power hardware or a large number of cameras | +| `s` | Small | ~7.1M | Balanced. Similar inference times to `yolonas`, more accurate | Most users. Start with `320x320` | +| `m` | Medium | ~20.0M | Slower than `s` with higher accuracy | Mid-range GPUs and NPUs | +| `c` | Compact | ~25.3M | Similar accuracy to `m`, slowest inference | More powerful hardware such as GPUs | +| `edgetpu` | N/A | N/A | Optimized to run on the Coral's Edge TPU | Google Coral devices only (requires Frigate 0.17+) | Parameter counts are for the standard YOLOv9 architectures. Actual inference times depend on your hardware and the input resolution you choose, so test with the base models before requesting a model. @@ -49,7 +49,7 @@ When switching to YOLOv9, you may need to adjust your thresholds for some object #### Hailo Support -If you have a Hailo device, you will need to specify the hardware you have when submitting a model request because they are not cross compatible. Hailo models are available for the `t`, `s`, and `c` variants on Hailo8, Hailo8L, and Hailo8R devices. Please test using the available base models before submitting your model request. +If you have a Hailo device, you will need to specify the hardware you have when submitting a model request because they are not cross compatible. Hailo models are available for the `t`, `s`, `m`, and `c` variants on Hailo8, Hailo8L, and Hailo8R devices. Please test using the available base models before submitting your model request. #### Rockchip (RKNN) Support diff --git a/docs/sidebars.ts b/docs/sidebars.ts index 4c656df8c2..ce105471fc 100644 --- a/docs/sidebars.ts +++ b/docs/sidebars.ts @@ -160,6 +160,7 @@ const sidebars: SidebarsConfig = { ], "Frigate+": [ "plus/index", + "plus/choosing_a_model", "plus/annotating", "plus/first_model", "plus/faq", From 190f4e0bd27309e2d5a6410cfbac1a390bd635e4 Mon Sep 17 00:00:00 2001 From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> Date: Sun, 15 Nov 2026 12:23:49 -0600 Subject: [PATCH 5/9] clarify region size in model guide (#24984) The guide said a 320 model gets smaller regions than a 640 model. Since 0.17 the minimum region is 320 px for any model, so both models get the same crops and a 640 model usually receives an upscaled one. --- docs/docs/plus/choosing_a_model.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/plus/choosing_a_model.md b/docs/docs/plus/choosing_a_model.md index 7447e39aa2..f80bf0262c 100644 --- a/docs/docs/plus/choosing_a_model.md +++ b/docs/docs/plus/choosing_a_model.md @@ -9,7 +9,7 @@ Frigate+ offers several model types, sizes, and input resolutions. This page com - **YOLOv9-s at 320** is the balanced default if your hardware runs it well. It detects about twice as many objects as MobileDet, and 15 more per 100 than YOLO-NAS-s at 320, at the same false alarm rate. - **Moving up a size at 320** helps more than moving to 640 for most cameras. YOLOv9-m at 320 detects more objects than YOLOv9-s at 640 (60% vs 59%) with lower GPU latency. -- **640 input** is rarely needed. Frigate doesn't run detection on the full frame. It crops a region around motion and resizes it to the model's input size, so with a 320 model it zooms in on a smaller area of the frame and small objects are no longer small to the model. 640 models detect small objects better within a large region, but not compared to a 320 model looking at a smaller, zoomed-in region. See [object size and input resolution](#object-size-and-input-resolution) for details. +- **640 input** is rarely needed. Frigate doesn't run detection on the full frame. It crops a region around motion, at least 320 pixels wide for any model, and resizes it to the model's input size. Most regions are small, so a 640 model usually receives an upscaled crop and does worse than a 320 model given the same crop at its native size. 640 models detect small objects better only within a large region. See [object size and input resolution](#object-size-and-input-resolution) for details. - **YOLOv9-c** gains little over YOLOv9-m: about 2 points of detection rate at 320 and none at 640, with more latency. On CPU it takes 1.4 to 1.7 times as long as YOLOv9-m. - **YOLOv9-t at 640** is no better than YOLOv9-s at 320 (55% vs 54%) and is slower on both GPU and CPU. - **YOLO-NAS-s** and **MobileDet** are only worth considering on hardware that can't run YOLOv9. Everywhere else, a YOLOv9 model of similar speed is more accurate. @@ -77,7 +77,7 @@ In these single-image results, 640 input mostly helps small objects, such as dis #### Object size and input resolution -Frigate doesn't send the full camera frame to the model. It crops a region around motion or a tracked object and resizes that region to the model's input size. With a 320 model the regions are smaller, so Frigate effectively zooms in on that part of the frame, and an object that is small in the full frame is no longer small to the model. A 640 model detects small objects better than a 320 model when both look at the same large region, but not when compared to a 320 model looking at a smaller, zoomed-in region. +Frigate doesn't send the full camera frame to the model. It crops a region around motion or a tracked object, at least 320 pixels wide for any model, and resizes it to the model's input size. Most regions are small, so a 640 model usually receives a crop upscaled from 320 pixels, which adds no detail and performs worse than a 320 model given the same crop at its native size. A 640 model detects small objects better only when the region is large. 640 input can still help in scenes with large objects in the foreground and small objects in the background at the same time, such as a doorbell camera that sees a person on the porch and another person across the street. The region has to be large enough to fit the nearby person, so the distant person is small within it. Frigate already handles much of this case: when an object is small relative to the region it was detected in, Frigate runs a separate detection on a smaller region around it. From 8e9607eccd0d06a6b505f45bf50c419bd26eea15 Mon Sep 17 00:00:00 2001 From: jey burrows <175012+jeyrb@users.noreply.github.com> Date: Mon, 16 Nov 2026 15:27:56 +0000 Subject: [PATCH 6/9] Update third_party_extensions.md with Home Assistant Marketplace integrations that support Frigate (#24965) * Update third_party_extensions.md with new integrations Added new integrations for Auto Arm and Camera AutoNotify to the documentation. * Enhance integration descriptions for clarity Updated descriptions for Auto Arm and Camera AutoNotify integrations to include additional features and synchronization options. --- docs/docs/integrations/third_party_extensions.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/docs/integrations/third_party_extensions.md b/docs/docs/integrations/third_party_extensions.md index 448d8c9eda..05cd3671e4 100644 --- a/docs/docs/integrations/third_party_extensions.md +++ b/docs/docs/integrations/third_party_extensions.md @@ -17,6 +17,14 @@ Please use your own knowledge to assess and vet them before you install anything The [Advanced Camera Card](https://card.camera/#/README) is a Home Assistant dashboard card with deep Frigate integration. +## [Auto Arm](https://autoarm.rhizomatics.org.uk) + +Home Assistant Marketplace integration to automatically manage alarm state based on time of day, occupancy, sun state, physical buttons etc. Can synchronize Frigate profiles to alarm state, so for example use `disarmed` profile to reduce noisy notifications when occupied during the day. + +## [Camera AutoNotify](https://camera-autonotify.rhizomatics.org.uk) + +Home Assistant Marketplace integration to set up notifications for Frigate cameras without use of blueprints or automations. Triggered by camera events and optionally by GenAI reviews, with option for daily/periodic GenAI Review Report emailed, and alerts if Frigate or any cameras are unavailable. Integration with [Supernotify](https://supernotify.rhizomatics.org.uk/) to auto configure mobile devices and customize notifications for alarm state, occupancy etc. + ## [cctvQL](https://github.com/arunrajiah/cctvql) [cctvQL](https://github.com/arunrajiah/cctvql) is a natural language query layer for Frigate and other CCTV systems. It connects to Frigate's REST API and MQTT broker to let you ask conversational questions about cameras and events (e.g. "Was there motion at the front door last night?"), with support for real-time event streaming, anomaly detection, PTZ control, alert rules, and a Home Assistant custom component. From d04ed58d8f97bff10991079ad4cdff70a7623c7c Mon Sep 17 00:00:00 2001 From: Nicolas Mowen Date: Mon, 16 Nov 2026 08:41:33 -0700 Subject: [PATCH 7/9] Organize extensions for Frigate (#24991) --- .../integrations/third_party_extensions.md | 96 +++++++++++-------- 1 file changed, 58 insertions(+), 38 deletions(-) diff --git a/docs/docs/integrations/third_party_extensions.md b/docs/docs/integrations/third_party_extensions.md index 05cd3671e4..f380c5a317 100644 --- a/docs/docs/integrations/third_party_extensions.md +++ b/docs/docs/integrations/third_party_extensions.md @@ -13,72 +13,92 @@ Please use your own knowledge to assess and vet them before you install anything ::: -## [Advanced Camera Card (formerly known as Frigate Card](https://card.camera/#/README) +## Cameras and Streaming -The [Advanced Camera Card](https://card.camera/#/README) is a Home Assistant dashboard card with deep Frigate integration. +Tools that help get video from your cameras into Frigate, or change how Frigate's video is delivered. -## [Auto Arm](https://autoarm.rhizomatics.org.uk) +### [frigate-abr](https://github.com/007hacky007/frigate-abr) -Home Assistant Marketplace integration to automatically manage alarm state based on time of day, occupancy, sun state, physical buttons etc. Can synchronize Frigate profiles to alarm state, so for example use `disarmed` profile to reduce noisy notifications when occupied during the day. +[frigate-abr](https://github.com/007hacky007/frigate-abr) is a drop-in Docker image of Frigate that adds adaptive bitrate (ABR) playback for recordings: a sidecar transcodes footage to lower quality tiers on demand, for reviewing over slow remote connections. Segments are transcoded when played and cached, so no additional stream is recorded. Frigate itself is not modified. -## [Camera AutoNotify](https://camera-autonotify.rhizomatics.org.uk) +### [reostream](https://github.com/VoltTech21/reostream) -Home Assistant Marketplace integration to set up notifications for Frigate cameras without use of blueprints or automations. Triggered by camera events and optionally by GenAI reviews, with option for daily/periodic GenAI Review Report emailed, and alerts if Frigate or any cameras are unavailable. Integration with [Supernotify](https://supernotify.rhizomatics.org.uk/) to auto configure mobile devices and customize notifications for alarm state, occupancy etc. +[reostream](https://github.com/VoltTech21/reostream) is a proxy for Reolink cameras that pulls video over Reolink's own protocol (the one the Reolink app and NVR use) instead of the camera's RTSP server, and serves it back as RTSP for go2rtc and Frigate. It helps models whose RTSP stream smears, drops frames or loses full resolution, and supports two-way talk. -## [cctvQL](https://github.com/arunrajiah/cctvql) +### [Scrypted - Frigate bridge plugin](https://github.com/apocaliss92/scrypted-frigate-bridge) + +[Scrypted - Frigate bridge](https://github.com/apocaliss92/scrypted-frigate-bridge) is a plugin that allows you to ingest Frigate detections, motion, videoclips on Scrypted as well as provide templates to export rebroadcast configurations on Frigate. + +### [Strix](https://github.com/eduard256/Strix) + +[Strix](https://github.com/eduard256/Strix) auto-discovers working stream URLs for IP cameras and generates ready-to-use Frigate configs. It tests thousands of URL patterns against your camera and supports cameras without RTSP or ONVIF. 67K+ camera models from 3.6K+ brands. + +## Events and Media + +Tools that enrich, query, or back up the events, snapshots, and reviews Frigate produces. + +### [cctvQL](https://github.com/arunrajiah/cctvql) [cctvQL](https://github.com/arunrajiah/cctvql) is a natural language query layer for Frigate and other CCTV systems. It connects to Frigate's REST API and MQTT broker to let you ask conversational questions about cameras and events (e.g. "Was there motion at the front door last night?"), with support for real-time event streaming, anomaly detection, PTZ control, alert rules, and a Home Assistant custom component. -## [Double Take](https://github.com/skrashevich/double-take) +### [Double Take](https://github.com/skrashevich/double-take) [Double Take](https://github.com/skrashevich/double-take) provides a unified UI and API for processing and training images for facial recognition. It supports automatically setting the sub labels in Frigate for person objects that are detected and recognized. This is a fork (with fixed errors and new features) of [original Double Take](https://github.com/jakowenko/double-take) project which, unfortunately, isn't being maintained by author. -## [frigate-abr](https://github.com/007hacky007/frigate-abr) - -[frigate-abr](https://github.com/007hacky007/frigate-abr) is a drop-in Docker image of Frigate that adds adaptive bitrate (ABR) playback for recordings: a sidecar transcodes footage to lower quality tiers on demand, for reviewing over slow remote connections. Segments are transcoded when played and cached, so no additional stream is recorded. Frigate itself is not modified. - -## [Frigate Notify](https://github.com/0x2142/frigate-notify) - -[Frigate Notify](https://github.com/0x2142/frigate-notify) is a simple app designed to send notifications from Frigate to your favorite platforms. Intended to be used with standalone Frigate installations - Home Assistant not required, MQTT is optional but recommended. - -## [Frigate Notify Alert](https://github.com/Sysoev86/frigate-notify-alert) - -[Frigate Notify Alert](https://github.com/Sysoev86/frigate-notify-alert) sends Frigate events to Telegram as a photo + video media group. It supports multiple camera groups (each notifying its own chat), optional zone filtering (notify only when an object enters a chosen zone), and in-chat buttons to pause notifications for a set time. Works with standalone Frigate over MQTT; Home Assistant not required. - -## [Frigate Snap-Sync](https://github.com/thequantumphysicist/frigate-snap-sync/) +### [Frigate Snap-Sync](https://github.com/thequantumphysicist/frigate-snap-sync/) [Frigate Snap-Sync](https://github.com/thequantumphysicist/frigate-snap-sync/) is a program that works in tandem with Frigate. It responds to Frigate when a snapshot or a review is made (and more can be added), and uploads them to one or more remote server(s) of your choice. -## [Frigate telegram](https://github.com/OldTyT/frigate-telegram) +## Notifications + +Standalone apps that send Frigate events to messaging platforms without requiring Home Assistant. For notifications through Home Assistant, see [Camera AutoNotify](#camera-autonotify). + +### [Frigate Notify](https://github.com/0x2142/frigate-notify) + +[Frigate Notify](https://github.com/0x2142/frigate-notify) is a simple app designed to send notifications from Frigate to your favorite platforms. Intended to be used with standalone Frigate installations - Home Assistant not required, MQTT is optional but recommended. + +### [Frigate Notify Alert](https://github.com/Sysoev86/frigate-notify-alert) + +[Frigate Notify Alert](https://github.com/Sysoev86/frigate-notify-alert) sends Frigate events to Telegram as a photo + video media group. It supports multiple camera groups (each notifying its own chat), optional zone filtering (notify only when an object enters a chosen zone), and in-chat buttons to pause notifications for a set time. Works with standalone Frigate over MQTT; Home Assistant not required. + +### [Frigate telegram](https://github.com/OldTyT/frigate-telegram) [Frigate telegram](https://github.com/OldTyT/frigate-telegram) makes it possible to send events from Frigate to Telegram. Events are sent as a message with a text description, video, and thumbnail. -## [FrigatePiP](https://github.com/maciejgornicz/frigate-pip) +## Clients and Viewers + +Apps and displays for viewing Frigate outside of its built-in web UI. + +### [FrigatePiP](https://github.com/maciejgornicz/frigate-pip) [FrigatePiP](https://github.com/maciejgornicz/frigate-pip) pops up a small picture-in-picture window with a camera's live video in a corner of the screen when Frigate detects an object, and closes it when the activity ends. It runs as a Windows tray app and on Linux (desktop windows, a console framebuffer, a terminal or tmux popups), receives events over Frigate's WebSocket or MQTT and plays the go2rtc RTSP stream with hardware decoding and camera audio. -## [kiosk-monitor](https://github.com/extremeshok/kiosk-monitor) +### [kiosk-monitor](https://github.com/extremeshok/kiosk-monitor) [kiosk-monitor](https://github.com/extremeshok/kiosk-monitor) is a Raspberry Pi watchdog that runs Chromium fullscreen on a Frigate dashboard (optionally with VLC on a second monitor for an RTSP camera stream), auto-restarts on frozen screens or unreachable URLs, and ships a Birdseye-aware Chromium helper that auto-sizes the grid to the display. -## [Periscope](https://github.com/maksz42/periscope) +### [Periscope](https://github.com/maksz42/periscope) [Periscope](https://github.com/maksz42/periscope) is a lightweight Android app that turns old devices into live viewers for Frigate. It works on Android 2.2 and above, including Android TV. It supports authentication and HTTPS. -## [reostream](https://github.com/VoltTech21/reostream) - -[reostream](https://github.com/VoltTech21/reostream) is a proxy for Reolink cameras that pulls video over Reolink's own protocol (the one the Reolink app and NVR use) instead of the camera's RTSP server, and serves it back as RTSP for go2rtc and Frigate. It helps models whose RTSP stream smears, drops frames or loses full resolution, and supports two-way talk. - -## [Scrypted - Frigate bridge plugin](https://github.com/apocaliss92/scrypted-frigate-bridge) - -[Scrypted - Frigate bridge](https://github.com/apocaliss92/scrypted-frigate-bridge) is a plugin that allows you to ingest Frigate detections, motion, videoclips on Scrypted as well as provide templates to export rebroadcast configurations on Frigate. - -## [Strix](https://github.com/eduard256/Strix) - -[Strix](https://github.com/eduard256/Strix) auto-discovers working stream URLs for IP cameras and generates ready-to-use Frigate configs. It tests thousands of URL patterns against your camera and supports cameras without RTSP or ONVIF. 67K+ camera models from 3.6K+ brands. - -## [yuFriEye](https://apps.apple.com/app/id6832456692) +### [yuFriEye](https://apps.apple.com/app/id6832456692) [yuFriEye](https://apps.apple.com/app/id6832456692) is a free native iOS, iPadOS and macOS client for Frigate. It shows the live camera grid with low-latency go2rtc streams, alerts and detections with clip playback and motion boxes, recordings by day with continuous playback, Frigate and go2rtc logs, and supports multiple servers with local and remote addresses. Works with or without Frigate authentication; no account or data collection. + +## Home Assistant + +Cards and Home Assistant Marketplace integrations that build on the [Frigate Home Assistant integration](/integrations/home-assistant). + +### [Advanced Camera Card (formerly known as Frigate Card)](https://card.camera/#/README) + +The [Advanced Camera Card](https://card.camera/#/README) is a Home Assistant dashboard card with deep Frigate integration. + +### [Auto Arm](https://autoarm.rhizomatics.org.uk) + +Home Assistant Marketplace integration to automatically manage alarm state based on time of day, occupancy, sun state, physical buttons etc. Can synchronize Frigate profiles to alarm state, so for example use `disarmed` profile to reduce noisy notifications when occupied during the day. + +### [Camera AutoNotify](https://camera-autonotify.rhizomatics.org.uk) + +Home Assistant Marketplace integration to set up notifications for Frigate cameras without use of blueprints or automations. Triggered by camera events and optionally by GenAI reviews, with option for daily/periodic GenAI Review Report emailed, and alerts if Frigate or any cameras are unavailable. Integration with [Supernotify](https://supernotify.rhizomatics.org.uk/) to auto configure mobile devices and customize notifications for alarm state, occupancy etc. From aadbda1104a3dc4805650bb8173f8f1131c14e52 Mon Sep 17 00:00:00 2001 From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> Date: Wed, 18 Nov 2026 10:52:28 -0600 Subject: [PATCH 8/9] Update nginx and backport module changes (#25009) * update nginx to 1.30.7 and backport nginx module changes from dev nginx 1.27.4 was vulnerable to CVE-2026-123007 (HTTP/2 flow control heap overflow) and CVE-2026-123633 (HTTP/2 use-after-free), both reachable before auth on the internal and external ports because http2 is on for the whole server block. Kaltura also deleted the nginx-vod-module and nginx-secure-token-module repos, so the build could no longer download either module. - Update nginx to 1.30.7 - Backport the switch to the maintained dio-az nginx-vod-module fork (#24123) - Backport the nginx-secure-token-module removal (#24893) * bump playwright to 1.65.0 for ubuntu 26.04 runners --- docker/main/build_nginx.sh | 25 ++++------ .../rootfs/usr/local/nginx/conf/nginx.conf | 22 +++++---- web/package-lock.json | 46 ++++++------------- .../components/player/GenericVideoPlayer.tsx | 4 +- 4 files changed, 37 insertions(+), 60 deletions(-) diff --git a/docker/main/build_nginx.sh b/docker/main/build_nginx.sh index 708a4cb45c..7809620dd2 100755 --- a/docker/main/build_nginx.sh +++ b/docker/main/build_nginx.sh @@ -2,9 +2,8 @@ set -euxo pipefail -NGINX_VERSION="1.27.4" -VOD_MODULE_VERSION="1.31" -SECURE_TOKEN_MODULE_VERSION="1.5" +NGINX_VERSION="1.30.7" +VOD_MODULE_VERSION="v1.9.1" SET_MISC_MODULE_VERSION="v0.33" NGX_DEVEL_KIT_VERSION="v0.3.3" @@ -31,32 +30,27 @@ wget -nv https://nginx.org/download/nginx-${NGINX_VERSION}.tar.gz tar -zxf nginx-${NGINX_VERSION}.tar.gz -C /tmp/nginx --strip-components=1 rm nginx-${NGINX_VERSION}.tar.gz mkdir /tmp/nginx-vod-module -wget -nv https://github.com/kaltura/nginx-vod-module/archive/refs/tags/${VOD_MODULE_VERSION}.tar.gz +wget -nv https://github.com/dio-az/nginx-vod-module/archive/refs/tags/${VOD_MODULE_VERSION}.tar.gz tar -zxf ${VOD_MODULE_VERSION}.tar.gz -C /tmp/nginx-vod-module --strip-components=1 rm ${VOD_MODULE_VERSION}.tar.gz # Patch MAX_CLIPS to allow more clips to be added than the default 128 sed -i 's/MAX_CLIPS (128)/MAX_CLIPS (1080)/g' /tmp/nginx-vod-module/vod/media_set.h patch -d /tmp/nginx-vod-module/ -p1 << 'EOF' ---- a/vod/avc_hevc_parser.c 2022-06-27 11:38:10.000000000 +0000 -+++ b/vod/avc_hevc_parser.c 2023-01-16 11:25:10.900521298 +0000 -@@ -3,6 +3,9 @@ +--- a/vod/avc_hevc_parser.c ++++ b/vod/avc_hevc_parser.c +@@ -2,6 +2,9 @@ + bool_t - avc_hevc_parser_rbsp_trailing_bits(bit_reader_state_t* reader) - { + avc_hevc_parser_rbsp_trailing_bits(bit_reader_state_t* reader) { + // https://github.com/blakeblackshear/frigate/issues/4572 + return TRUE; + uint32_t one_bit; - if (reader->stream.eof_reached) + if (reader->stream.eof_reached) { EOF -mkdir /tmp/nginx-secure-token-module -wget https://github.com/kaltura/nginx-secure-token-module/archive/refs/tags/${SECURE_TOKEN_MODULE_VERSION}.tar.gz -tar -zxf ${SECURE_TOKEN_MODULE_VERSION}.tar.gz -C /tmp/nginx-secure-token-module --strip-components=1 -rm ${SECURE_TOKEN_MODULE_VERSION}.tar.gz - mkdir /tmp/ngx_devel_kit wget https://github.com/vision5/ngx_devel_kit/archive/refs/tags/${NGX_DEVEL_KIT_VERSION}.tar.gz tar -zxf ${NGX_DEVEL_KIT_VERSION}.tar.gz -C /tmp/ngx_devel_kit --strip-components=1 @@ -80,7 +74,6 @@ cd /tmp/nginx --add-module=../ngx_devel_kit \ --add-module=../nginx-set-misc-module \ --add-module=../nginx-vod-module \ - --add-module=../nginx-secure-token-module \ --with-cc-opt="-O3 -Wno-error=implicit-fallthrough" make CC="ccache gcc" -j$(nproc) && make install diff --git a/docker/main/rootfs/usr/local/nginx/conf/nginx.conf b/docker/main/rootfs/usr/local/nginx/conf/nginx.conf index 34cfe966e5..956089a087 100644 --- a/docker/main/rootfs/usr/local/nginx/conf/nginx.conf +++ b/docker/main/rootfs/usr/local/nginx/conf/nginx.conf @@ -114,21 +114,23 @@ http { # Smaller segments, faster generation, better browser compatibility vod_hls_container_format fmp4; - secure_token $args; - secure_token_types application/vnd.apple.mpegurl; + # fMP4 playlists use EXT-X-MAP, which requires HLS protocol + # version 6 (RFC 8216 section 7); the module default is 4 + vod_hls_version 6; + + # Pass the playlist's query args (e.g. Home Assistant's authSig) on + # to every URL in it. These match the only URL endings vod writes + # with fmp4 and no subtitles. + sub_filter_types application/vnd.apple.mpegurl; + sub_filter_once off; + sub_filter '.m3u8' '.m3u8$is_args$args'; + sub_filter '.m4s' '.m4s$is_args$args'; + sub_filter '.mp4"' '.mp4$is_args$args"'; add_header Cache-Control "no-store"; expires off; keepalive_disable safari; - - # vod module returns 502 for non-existent media - # https://github.com/kaltura/nginx-vod-module/issues/468 - error_page 502 =404 /vod-not-found; - } - - location = /vod-not-found { - return 404; } location /stream/ { diff --git a/web/package-lock.json b/web/package-lock.json index 1497afb21f..5186f1ee23 100644 --- a/web/package-lock.json +++ b/web/package-lock.json @@ -1487,19 +1487,19 @@ } }, "node_modules/@playwright/test": { - "version": "1.59.1", - "resolved": "https://registry.npmjs.org/@playwright/test/-/test-1.59.1.tgz", - "integrity": "sha512-PG6q63nQg5c9rIi4/Z5lR5IVF7yU5MqmKaPOe0HSc0O2cX1fPi96sUQu5j7eo4gKCkB2AnNGoWt7y4/Xx3Kcqg==", + "version": "1.65.0", + "resolved": "https://registry.npmjs.org/@playwright/test/-/test-1.65.0.tgz", + "integrity": "sha512-iGURLGuKDLakSEl7Pgfv8h7f+XLT+V861Wfhz0zlEl5nyFuKUopdkFBPKqTllTUp06aOwPuH8iuUEb3yp3MpbQ==", "dev": true, "license": "Apache-2.0", "dependencies": { - "playwright": "1.59.1" + "playwright": "1.65.0" }, "bin": { "playwright": "cli.js" }, "engines": { - "node": ">=18" + "node": ">=20" } }, "node_modules/@radix-ui/number": { @@ -11558,50 +11558,32 @@ } }, "node_modules/playwright": { - "version": "1.59.1", - "resolved": "https://registry.npmjs.org/playwright/-/playwright-1.59.1.tgz", - "integrity": "sha512-C8oWjPR3F81yljW9o5OxcWzfh6avkVwDD2VYdwIGqTkl+OGFISgypqzfu7dOe4QNLL2aqcWBmI3PMtLIK233lw==", + "version": "1.65.0", + "resolved": "https://registry.npmjs.org/playwright/-/playwright-1.65.0.tgz", + "integrity": "sha512-F3AMWcR44qMBt4kq+6Kb6mX7bjGXshktKFOPULd7reED6ZJWevjbNRqysP7q+AATE9kdPEZBibex1BYsvpVoeA==", "dev": true, "license": "Apache-2.0", "dependencies": { - "playwright-core": "1.59.1" + "playwright-core": "1.65.0" }, "bin": { "playwright": "cli.js" }, "engines": { - "node": ">=18" - }, - "optionalDependencies": { - "fsevents": "2.3.2" + "node": ">=20" } }, "node_modules/playwright-core": { - "version": "1.59.1", - "resolved": "https://registry.npmjs.org/playwright-core/-/playwright-core-1.59.1.tgz", - "integrity": "sha512-HBV/RJg81z5BiiZ9yPzIiClYV/QMsDCKUyogwH9p3MCP6IYjUFu/MActgYAvK0oWyV9NlwM3GLBjADyWgydVyg==", + "version": "1.65.0", + "resolved": "https://registry.npmjs.org/playwright-core/-/playwright-core-1.65.0.tgz", + "integrity": "sha512-vNSKgH6YqtN7cdT/L334zo0a+YwkrpicyrHJlWWPIm/Q+Nn2SWInil01oT0mbu96U4GgoRtCYQD9CzJQgju+lA==", "dev": true, "license": "Apache-2.0", "bin": { "playwright-core": "cli.js" }, "engines": { - "node": ">=18" - } - }, - "node_modules/playwright/node_modules/fsevents": { - "version": "2.3.2", - "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz", - "integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==", - "dev": true, - "hasInstallScript": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": "^8.16.0 || ^10.6.0 || >=11.0.0" + "node": ">=20" } }, "node_modules/postcss": { diff --git a/web/src/components/player/GenericVideoPlayer.tsx b/web/src/components/player/GenericVideoPlayer.tsx index 25399771bf..71128106bb 100644 --- a/web/src/components/player/GenericVideoPlayer.tsx +++ b/web/src/components/player/GenericVideoPlayer.tsx @@ -32,8 +32,8 @@ export function GenericVideoPlayer({ const checkSourceExists = async (url: string) => { try { const response = await fetch(url, { method: "HEAD" }); - // nginx vod module returns 502 for non existent media - // https://github.com/kaltura/nginx-vod-module/issues/468 + // missing media is a 404; 502 still covers a failed or + // unreachable mapping request, which is equally unplayable setSourceExists(response.status !== 502 && response.status !== 404); } catch (error) { setSourceExists(false); From a19e23ae2dd3dd1082bf82a0ad5d2b62a5813676 Mon Sep 17 00:00:00 2001 From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> Date: Wed, 18 Nov 2026 11:11:18 -0600 Subject: [PATCH 9/9] bump version to 0.18.3 (#25011) --- Makefile | 2 +- docs/docs/frigate/updating.md | 14 +++++++------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/Makefile b/Makefile index 22b064aeed..4b488a139f 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ default_target: local COMMIT_HASH := $(shell git log -1 --pretty=format:"%h"|tail -1) -VERSION = 0.18.2 +VERSION = 0.18.3 IMAGE_REPO ?= ghcr.io/blakeblackshear/frigate GITHUB_REF_NAME ?= $(shell git rev-parse --abbrev-ref HEAD) BOARDS= #Initialized empty diff --git a/docs/docs/frigate/updating.md b/docs/docs/frigate/updating.md index 1cf26ad47d..1bdaf3cbea 100644 --- a/docs/docs/frigate/updating.md +++ b/docs/docs/frigate/updating.md @@ -5,7 +5,7 @@ title: Updating # Updating Frigate -The current stable version of Frigate is **0.18.2**. The release notes and any breaking changes for this version can be found on the [Frigate GitHub releases page](https://github.com/blakeblackshear/frigate/releases/tag/v0.18.2). +The current stable version of Frigate is **0.18.3**. The release notes and any breaking changes for this version can be found on the [Frigate GitHub releases page](https://github.com/blakeblackshear/frigate/releases/tag/v0.18.3). Keeping Frigate up to date ensures you benefit from the latest features, performance improvements, and bug fixes. The update process varies slightly depending on your installation method (Docker, Home Assistant App, etc.). Below are instructions for the most common setups. @@ -31,21 +31,21 @@ If you’re running Frigate via Docker (recommended method), follow these steps: 2. **Update and Pull the Latest Image**: - If using Docker Compose: - - Edit your `docker-compose.yml` file to specify the desired version tag (e.g., `0.18.2` instead of `0.17.1`). For example: + - Edit your `docker-compose.yml` file to specify the desired version tag (e.g., `0.18.3` instead of `0.17.1`). For example: ```yaml services: frigate: - image: ghcr.io/blakeblackshear/frigate:0.18.2 + image: ghcr.io/blakeblackshear/frigate:0.18.3 ``` - Then pull the image: ```bash - docker pull ghcr.io/blakeblackshear/frigate:0.18.2 + docker pull ghcr.io/blakeblackshear/frigate:0.18.3 ``` - **Note for `stable` Tag Users**: If your `docker-compose.yml` uses the `stable` tag (e.g., `ghcr.io/blakeblackshear/frigate:stable`), you don’t need to update the tag manually. The `stable` tag always points to the latest stable release after pulling. - If using `docker run`: - - Pull the image with the appropriate tag (e.g., `0.18.2`, `0.18.2-tensorrt`, or `stable`): + - Pull the image with the appropriate tag (e.g., `0.18.3`, `0.18.3-tensorrt`, or `stable`): ```bash - docker pull ghcr.io/blakeblackshear/frigate:0.18.2 + docker pull ghcr.io/blakeblackshear/frigate:0.18.3 ``` 3. **Start the Container**: @@ -100,7 +100,7 @@ If an update causes issues: 1. Stop Frigate. 2. Restore your backed-up config file and database. 3. Revert to the previous image version: - - For Docker: Specify an older tag (e.g., `ghcr.io/blakeblackshear/frigate:0.18.1`) in your `docker run` command. + - For Docker: Specify an older tag (e.g., `ghcr.io/blakeblackshear/frigate:0.18.2`) in your `docker run` command. - For Docker Compose: Edit your `docker-compose.yml`, specify the older version tag (e.g., `ghcr.io/blakeblackshear/frigate:0.16.4`), and re-run `docker compose up -d`. - For Home Assistant: Restore from the app/addon backup you took before you updated. 4. Verify the old version is running again.