From 9379f81edf243e1b31c7ae89976ceba7d74d5e20 Mon Sep 17 00:00:00 2001 From: Nicolas Mowen Date: Mon, 2 Nov 2026 11:45:59 -0700 Subject: [PATCH] Adjust docs for new HA features for 0.19 (#24860) --- .cspell/frigate-dictionary.txt | 1 + docs/docs/configuration/object_detectors.md | 2 +- docs/docs/frigate/installation.md | 7 ++--- docs/docs/guides/ha_network_storage.md | 32 +++++++++++++-------- 4 files changed, 24 insertions(+), 18 deletions(-) diff --git a/.cspell/frigate-dictionary.txt b/.cspell/frigate-dictionary.txt index dcb77fbd4f..a82b905d8c 100644 --- a/.cspell/frigate-dictionary.txt +++ b/.cspell/frigate-dictionary.txt @@ -181,6 +181,7 @@ noninteractive noprint Norfair nptype +NTFS NTSC numpy nvenc diff --git a/docs/docs/configuration/object_detectors.md b/docs/docs/configuration/object_detectors.md index d8664c0a4a..84fddd0cad 100644 --- a/docs/docs/configuration/object_detectors.md +++ b/docs/docs/configuration/object_detectors.md @@ -361,7 +361,7 @@ The NPU firmware is loaded by the host kernel and is not part of the Frigate ima Frigate bundles a specific version of Intel's [linux-npu-driver](https://github.com/intel/linux-npu-driver/releases), and the host firmware must come from that release or a newer one. Firmware older than the bundled driver may fail with `MAPPED_INFERENCE_VERSION is NOT compatible with the ELF`, where `Expected` is the version the firmware supports and `received` is the version the bundled compiler produced. Distributions often package older firmware than the driver Frigate ships, so check the build date on the host with `sudo dmesg | grep -i vpu` and update it there if needed. -Intel NPUs cannot be used under Home Assistant OS, which does not include the NPU firmware. +Intel NPUs can be used under Home Assistant OS 18.4 or newer. ### Configuration {#configuration-openvino} diff --git a/docs/docs/frigate/installation.md b/docs/docs/frigate/installation.md index 27c862c845..c30956a4eb 100644 --- a/docs/docs/frigate/installation.md +++ b/docs/docs/frigate/installation.md @@ -763,20 +763,17 @@ The community supported docker image tags for the current stable version are: :::warning -As of Home Assistant Operating System 10.2 and Home Assistant 2023.6 defining separate network storage for media is supported. - There are important limitations in HA OS to be aware of: -- Separate local storage for media is not yet supported by Home Assistant - AMD GPUs are not supported because HA OS does not include the mesa driver. -- Intel NPUs are not supported because HA OS does not include the NPU firmware. +- Intel NPUs require Home Assistant OS 18.4 or newer. Earlier releases do not include the NPU firmware. - Nvidia GPUs are not supported because HA Apps do not support the Nvidia runtime. ::: :::tip -See [the network storage guide](/guides/ha_network_storage.md) for instructions to setup network storage for frigate. +Frigate's media can be kept on separate storage, either a network share (Home Assistant 2023.6 or newer) or a local disk such as a second internal drive or a USB drive (Home Assistant 2026.11 or newer). See [the storage guide](/guides/ha_network_storage.md) for setup instructions. ::: diff --git a/docs/docs/guides/ha_network_storage.md b/docs/docs/guides/ha_network_storage.md index 134e1952c8..c0b8899b94 100644 --- a/docs/docs/guides/ha_network_storage.md +++ b/docs/docs/guides/ha_network_storage.md @@ -1,40 +1,48 @@ --- id: ha_network_storage -title: Home Assistant network storage +title: Home Assistant storage --- -As of Home Assistant 2023.6, Network Mounted Storage is supported for Apps. +Frigate's media (`/media/frigate`) can be stored on a network share or a separate local disk (internal or USB) instead of the Home Assistant system disk. -## Setting Up Remote Storage For Frigate +## Prerequisites -### Prerequisites +### Network storage - Home Assistant 2023.6 or newer is installed - Running Home Assistant Operating System 10.2 or newer OR Running Supervised with latest os-agent installed (this is required for supervised install) +### Local disk + +- Home Assistant 2026.11 or newer is installed +- The disk is already formatted, ideally as ext4 (Home Assistant does not format disks). Avoid FAT32, exFAT, and NTFS, which do not support Linux file permissions. + +## Setting Up Storage For Frigate + ### Initial Setup 1. Stop the Frigate App ### Move current data -Keeping the current data is optional, but the data will need to be moved regardless so the share can be created successfully. +Keeping the current data is optional, but `/media/frigate` must be moved or deleted so Home Assistant can mount the storage there. The database and config are stored elsewhere and are not affected. #### If you want to keep the current data -1. Move the frigate.db, frigate.db-shm, frigate.db-wal files to the /config directory -2. Rename the /media/frigate folder to /media/frigate_tmp +1. Rename the /media/frigate folder to /media/frigate_tmp #### If you don't want to keep the current data 1. Delete the /media/frigate folder and all of its contents -### Create the media share +### Add the storage -1. Go to **Settings -> System -> Storage -> Add Network Storage** -2. Name the share `frigate` (this is required) -3. Choose type `media` -4. Fill out the additional required info for your particular NAS +1. Go to **Settings -> System -> Storage -> Add storage** +2. Name the storage `frigate` (this is required) +3. Choose usage `media` +4. Choose the type: + - For network storage, choose `Samba/Windows (CIFS)` or `Network File System (NFS)` and fill out the additional required info for your particular NAS + - For a local disk, choose `Local disk` and select the disk to use 5. Connect 6. Move files from `/media/frigate_tmp` to `/media/frigate` if they were kept in previous step 7. Start the Frigate App