scope classification attributes to allowed cameras

* pin genai review frames to the main stream

* retain previews as long as either stream has recordings

* watch sub stream recording health separately from main

* reject record_sub on the same input as record and document the role

* derive recording paths from the cache segment timestamp

Recording paths carry one second of resolution, but since sub stream recording start times are resolved to fractional wall clock, anchored to the cache file mtime and chained to the previous segment's end. A stream cutting segments faster than once a second resolves consecutive segments into the same second, so two rows collide on the unique path index and the batch insert fails. The cache segment name is unique per camera stream and second by construction because ffmpeg names segments with strftime, so the recording path is now built from that timestamp while the row keeps the resolved start time. This also restores the path semantics from before sub stream recording, when start times came straight from the cache filename.

Nothing derives times from recording paths: playback offsets, stream switching, and export all use the row's start time, which is unchanged, and the recordings sync matches files by exact path string.

* keep the rest of a recording batch when one row conflicts

* only publish record_sub status when a sub stream is configured

* don't shadow camera_cfg when publishing empty cache streams

* back off restarts when a recording stream goes stale

* give the shared sub stream grace on any capture thread reset

* include segment details in recording discard warnings

.cspell/frigate-dictionary.txt

@@ -55,6 +55,7 @@ Dahua
 datasheet
 debconf
 deci
+deepstack
 defragment
 devcontainer
 DEVICEMAP

.github/DISCUSSION_TEMPLATE/beta-support.yml

@@ -26,8 +26,8 @@ body:
     id: version
     attributes:
       label: Beta Version
-      description: Visible on the System Metrics page in the Web UI. Please include the full version including the build identifier (eg. 0.19.0-beta1, 0.19.0-8b72c7a, etc.)
-      placeholder: "0.19.0-beta1"
+      description: Visible on the System Metrics page in the Web UI. Please include the full version including the build identifier (eg. 0.18.0-beta1, 0.18.0-8b72c7a, etc.)
+      placeholder: "0.18.0-beta1"
     validations:
       required: true
   - type: dropdown

.github/DISCUSSION_TEMPLATE/report-a-bug.yml

@@ -6,9 +6,7 @@ body:
       value: |
         Use this form to submit a reproducible bug in Frigate or Frigate's UI.
 
-        If you are running on Proxmox, please see the [Proxmox FAQ](https://github.com/blakeblackshear/frigate/discussions/23916) and reproduce the issue on a standard Docker install first (bare metal, or a VM running plain Debian/Ubuntu) before submitting here.
-
-        **⚠️ If you are running a beta version (0.19.0-beta or similar), please use the [Beta Support template](https://github.com/blakeblackshear/frigate/discussions/new?category=beta-support) instead.**
+        **⚠️ If you are running a beta version (0.18.0-beta or similar), please use the [Beta Support template](https://github.com/blakeblackshear/frigate/discussions/new?category=beta-support) instead.**
 
         Before submitting your bug report, please ask the AI with the "Ask AI" button on the [official documentation site][ai] about your issue, [search the discussions][discussions], look at recent open and closed [pull requests][prs], read the [official Frigate documentation][docs], and read the [Frigate FAQ][faq] pinned at the Discussion page to see if your bug has already been fixed by the developers or reported by the community.
 

.github/workflows/ci.yml

@@ -23,7 +23,7 @@ jobs:
     name: AMD64 Build
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up QEMU and Buildx
@@ -49,7 +49,7 @@ jobs:
       - amd64_build
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up QEMU and Buildx
@@ -59,16 +59,10 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       - name: Start container
         run: |
-          mkdir -p /tmp/frigate-config /tmp/frigate-media
+          mkdir -p /tmp/frigate-config
           printf 'mqtt:\n  enabled: false\ncameras: {}\n' > /tmp/frigate-config/config.yml
-          # simulate a root-era install: root-owned 0600 jwt secret pre-exists
-          docker run --rm -v /tmp/frigate-config:/config --entrypoint bash \
-            ${{ steps.setup.outputs.image-name }}-amd64 \
-            -c "python3 -c 'import secrets; open(\"/config/.jwt_secret\",\"w\").write(secrets.token_hex(64))' && chmod 600 /config/.jwt_secret && chown 0:0 /config/.jwt_secret"
           docker run -d --name frigate --shm-size 256m \
             -v /tmp/frigate-config:/config \
-            -v /tmp/frigate-media:/media/frigate \
-            --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 \
             -p 5000:5000 -p 8971:8971 \
             ${{ steps.setup.outputs.image-name }}-amd64
       - name: Wait for API
@@ -97,183 +91,16 @@ jobs:
             echo "response carries frame-ancestors, which breaks cross-origin iframe embedding"
             exit 1
           fi
-          # -t as root would chown the live cache and temp dirs to the `user`
-          # directive user; stdout discarded because -t reopens the config's
-          # /dev/stdout logs and the docker exec pipe is root-owned
-          docker exec frigate /command/s6-setuidgid frigate bash -c '/usr/local/nginx/sbin/nginx -e stderr -t -c /tmp/nginx/conf/nginx.conf >/dev/null'
-          docker exec frigate stat -c %a /config/tls/privkey.pem | grep -qx 600
+          docker exec frigate /usr/local/nginx/sbin/nginx -t
+          docker exec frigate stat -c %a /etc/letsencrypt/live/frigate/privkey.pem | grep -qx 600
           docker exec frigate stat -c %a /dev/shm/go2rtc.yaml | grep -qx 640
-      - name: Assert services run as non-root
-        run: |
-          ps_out=$(docker exec frigate ps -eo user=,comm=)
-          echo "$ps_out"
-          assert_nonroot() {
-            # the process must exist AND no instance of it may run as root
-            echo "$ps_out" | grep -qw "$1" || { echo "$1 is not running"; exit 1; }
-            if echo "$ps_out" | grep -w "$1" | grep -q '^root'; then
-              echo "$1 is running as root"; exit 1
-            fi
-          }
-          assert_nonroot python3
-          assert_nonroot go2rtc
-          assert_nonroot nginx
-          # root-era jwt secret must have been captured by the sweep and the
-          # auth stack must be functional: wrong creds => clean 401, not 500
-          docker exec frigate stat -c %u /config/.jwt_secret | grep -qx "$(docker exec frigate id -u frigate)"
-          code=$(curl -s -o /dev/null -w '%{http_code}' -X POST http://127.0.0.1:5000/api/login \
-            -H 'content-type: application/json' -d '{"user":"admin","password":"definitely-wrong"}')
-          [ "$code" = "401" ] || { echo "login endpoint returned $code"; exit 1; }
-          # a root nginx -t above would have chowned the runtime dirs to root
-          owners=$(docker exec frigate stat -c %U /tmp/nginx /dev/shm/nginx_cache)
-          echo "$owners"
-          if echo "$owners" | grep -qvx frigate; then
-            echo "nginx runtime dirs are not owned by frigate"; exit 1
-          fi
-          # runtime user can write recordings storage
-          docker exec frigate /command/s6-setuidgid frigate touch /media/frigate/.write-probe
-          docker exec frigate rm /media/frigate/.write-probe
-          # tmpfs mount per the docs: arrives root-owned, holds the ZMQ IPC sockets
-          docker exec frigate /command/s6-setuidgid frigate touch /tmp/cache/.write-probe
-          docker exec frigate rm /tmp/cache/.write-probe
-          # models are baked in as root and archive members can carry root-only modes
-          docker exec frigate /command/s6-setuidgid frigate sh -c '
-            for f in /cpu_model.tflite /edgetpu_model.tflite /cpu_audio_model.tflite \
-                     /labelmap.txt /audio-labelmap.txt /openvino-model/*; do
-              [ -e "$f" ] || continue
-              test -r "$f" || { echo "$f is not readable by the runtime user"; exit 1; }
-            done'
-      - name: Assert device access grants
-        run: |
-          # a fake accelerator node created after boot, then the oneshot re-run.
-          # /command is on PATH only for s6-supervised services, and the
-          # with-contenv shebang resolves its execline helpers through PATH
-          docker exec frigate mknod /dev/apex_9 c 120 99
-          docker exec frigate sh -c 'export PATH=/command:$PATH; exec /etc/s6-overlay/s6-rc.d/init-devices/run'
-          acl=$(docker exec frigate getfacl -p /dev/apex_9)
-          echo "$acl"
-          echo "$acl" | grep -q "user:frigate:rw-"
-          echo "$acl" | grep -q "user:go2rtc:rw-"
-          # the usb tree gets recursive grants plus a default ACL that
-          # newly created nodes inherit (the Coral re-enumeration path)
-          docker exec frigate sh -c 'mkdir -p /dev/bus/usb/001 && mknod /dev/bus/usb/001/002 c 189 1'
-          docker exec frigate sh -c 'export PATH=/command:$PATH; exec /etc/s6-overlay/s6-rc.d/init-devices/run'
-          docker exec frigate getfacl -p /dev/bus/usb/001 | grep -q "user:frigate:rwx"
-          docker exec frigate sh -c 'mknod /dev/bus/usb/001/099 c 189 98 && chmod 664 /dev/bus/usb/001/099'
-          inherited=$(docker exec frigate getfacl -p /dev/bus/usb/001/099)
-          echo "$inherited"
-          echo "$inherited" | grep -q "user:frigate:rw-"
-          # getfacl prints granted perms even when the mask clamps them to
-          # nothing, with a trailing "#effective:" comment; a clamped ACL must
-          # fail this assertion, not sneak past it. The check is scoped to the
-          # runtime users because the inherited group:: entry is always clamped
-          # on a non-directory, so an unscoped grep could never pass.
-          if echo "$inherited" | grep -E "^user:(frigate|go2rtc):" | grep -q "effective"; then
-            echo "inherited ACL is mask-clamped and grants no real access"; exit 1
-          fi
-          # hardware that is absent must stay silent: the literal table entries
-          # are not globs, so nullglob does not drop them and only an existence
-          # check keeps them from warning on every boot
-          out=$(docker exec frigate sh -c 'export PATH=/command:$PATH; exec /etc/s6-overlay/s6-rc.d/init-devices/run')
-          echo "$out"
-          if echo "$out" | grep -q "WARN"; then
-            echo "grant warned about device nodes that do not exist"; exit 1
-          fi
-      - name: Assert escape hatch restores root
-        run: |
-          mkdir -p /tmp/frigate-config-root
-          printf 'mqtt:\n  enabled: false\ncameras: {}\n' > /tmp/frigate-config-root/config.yml
-          # pre-seed so the absence check proves the rm -f, not a vacuous pass
-          echo "2:1000:1000" > /tmp/frigate-config-root/.permissions_version
-          docker run -d --name frigate-root --shm-size 256m \
-            -e FRIGATE_RUN_AS_ROOT=true \
-            -v /tmp/frigate-config-root:/config \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          up=0
-          for i in $(seq 1 60); do
-            docker exec frigate-root curl -fs http://127.0.0.1:5000/api/version && up=1 && break
-            sleep 5
-          done
-          if [ "$up" -ne 1 ]; then echo "escape hatch container never healthy"; docker logs frigate-root; exit 1; fi
-          ps_out=$(docker exec frigate-root ps -eo user=,comm=)
-          echo "$ps_out"
-          echo "$ps_out" | grep -w python3 | grep -q '^root'
-          echo "$ps_out" | grep -w go2rtc  | grep -q '^root'
-          echo "$ps_out" | grep -w nginx   | grep -q '^root'
-          # an if, not ! test: bash exempts negated commands from set -e
-          if docker exec frigate-root test -f /config/.permissions_version; then
-            echo "escape hatch did not delete the sweep sentinel"; exit 1
-          fi
-          docker rm -f frigate-root
-      - name: Assert granular root services
-        run: |
-          mkdir -p /tmp/frigate-config-granular /tmp/frigate-media-granular
-          printf 'mqtt:\n  enabled: false\ncameras: {}\n' > /tmp/frigate-config-granular/config.yml
-          docker run -d --name frigate-granular --shm-size 256m \
-            -e FRIGATE_ROOT_SERVICES=frigate \
-            -v /tmp/frigate-config-granular:/config \
-            -v /tmp/frigate-media-granular:/media/frigate \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          up=0
-          for i in $(seq 1 60); do
-            docker exec frigate-granular curl -fs http://127.0.0.1:5000/api/version && up=1 && break
-            sleep 5
-          done
-          if [ "$up" -ne 1 ]; then echo "granular container never became healthy"; docker logs frigate-granular; exit 1; fi
-          ps_out=$(docker exec frigate-granular ps -eo user=,comm=)
-          echo "$ps_out"
-          # the listed service runs as root
-          echo "$ps_out" | grep -w python3 | grep -q '^root'
-          # unlisted services still drop; ifs because set -e exempts negated commands
-          if echo "$ps_out" | grep -w go2rtc | grep -q '^root'; then
-            echo "go2rtc is unexpectedly running as root"; exit 1
-          fi
-          if echo "$ps_out" | grep -w nginx | grep -q '^root'; then
-            echo "nginx is unexpectedly running as root"; exit 1
-          fi
-          # the sweep still ran and the sentinel records the mode
-          docker exec frigate-granular cat /config/.permissions_version | grep -qx "2:1000:1000:frigate"
-          # the root frigate process chowns the db it creates (first-boot immediacy)
-          docker exec frigate-granular stat -c %u /config/frigate.db | grep -qx 1000
-          # plant a root-owned straggler; the per-boot sweep must reclaim it on restart
-          docker exec frigate-granular sh -c 'mkdir -p /media/frigate/clips && touch /media/frigate/clips/straggler.webp'
-          docker restart frigate-granular
-          up=0
-          for i in $(seq 1 60); do
-            docker exec frigate-granular curl -fs http://127.0.0.1:5000/api/version && up=1 && break
-            sleep 5
-          done
-          if [ "$up" -ne 1 ]; then echo "granular container never came back after restart"; docker logs frigate-granular; exit 1; fi
-          docker exec frigate-granular stat -c %u /media/frigate/clips/straggler.webp | grep -qx 1000
-          docker rm -f frigate-granular
-      - name: Assert unknown root service fails fast
-        run: |
-          mkdir -p /tmp/frigate-config-badsvc
-          printf 'mqtt:\n  enabled: false\ncameras: {}\n' > /tmp/frigate-config-badsvc/config.yml
-          docker run -d --name frigate-badsvc --shm-size 256m \
-            -e FRIGATE_ROOT_SERVICES=frigatee \
-            -v /tmp/frigate-config-badsvc:/config \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          found=0
-          for i in $(seq 1 12); do
-            if docker logs frigate-badsvc 2>&1 | grep -q "unknown service 'frigatee'"; then found=1; break; fi
-            sleep 5
-          done
-          if [ "$found" -ne 1 ]; then
-            echo "no fail-fast error for an unknown service name"; docker logs frigate-badsvc; exit 1
-          fi
-          # the failed oneshot blocks startup through the dependency chain
-          if docker exec frigate-badsvc curl -fs http://127.0.0.1:5000/api/version; then
-            echo "container came up despite an invalid FRIGATE_ROOT_SERVICES"; exit 1
-          fi
-          docker rm -f frigate-badsvc
       - name: Assert PUID/PGID remapping
         run: |
-          mkdir -p /tmp/frigate-config-puid /tmp/frigate-media-puid
+          mkdir -p /tmp/frigate-config-puid
           printf 'mqtt:\n  enabled: false\ncameras: {}\n' > /tmp/frigate-config-puid/config.yml
           docker run -d --name frigate-puid --shm-size 256m \
             -e PUID=1500 -e PGID=1500 \
             -v /tmp/frigate-config-puid:/config \
-            -v /tmp/frigate-media-puid:/media/frigate \
             ${{ steps.setup.outputs.image-name }}-amd64
           up=0
           for i in $(seq 1 60); do
@@ -283,7 +110,7 @@ jobs:
           if [ "$up" -ne 1 ]; then echo "PUID container never became healthy"; docker logs frigate-puid; exit 1; fi
           docker exec frigate-puid id -u frigate | grep -qx 1500
           docker exec frigate-puid id -g frigate | grep -qx 1500
-          docker exec frigate-puid cat /config/.permissions_version | grep -qx "2:1500:1500"
+          docker exec frigate-puid cat /config/.permissions_version | grep -qx "1:1500:1500"
           # second boot must skip the sweep (sentinel hit). Poll rather than
           # sleep: the string can only come from the second boot (the first
           # had no sentinel), so grepping the full log is unambiguous.
@@ -295,129 +122,6 @@ jobs:
           done
           if [ "$ok" -ne 1 ]; then echo "sentinel skip never logged"; docker logs frigate-puid; exit 1; fi
           docker rm -f frigate-puid
-      - name: Assert read-only rootfs with --user works
-        run: |
-          mkdir -p /tmp/frigate-config-ro /tmp/frigate-media-ro
-          printf 'mqtt:\n  enabled: false\ncameras: {}\n' > /tmp/frigate-config-ro/config.yml
-          sudo chown -R 1000:1000 /tmp/frigate-config-ro /tmp/frigate-media-ro
-          # /run must allow exec: S6_READ_ONLY_ROOT has s6 copy its service
-          # scripts there and run them, and --tmpfs defaults to noexec
-          docker run -d --name frigate-ro --shm-size 256m \
-            --read-only --tmpfs /tmp:rw,size=1g --tmpfs /run:exec,nosuid,nodev,mode=0755,uid=1000,gid=1000 \
-            --user 1000:1000 \
-            --security-opt no-new-privileges:true \
-            -v /tmp/frigate-config-ro:/config \
-            -v /tmp/frigate-media-ro:/media/frigate \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          up=0
-          for i in $(seq 1 60); do
-            docker exec frigate-ro curl -fs http://127.0.0.1:5000/api/version && up=1 && break
-            sleep 5
-          done
-          if [ "$up" -ne 1 ]; then echo "read-only container never healthy"; docker logs frigate-ro; exit 1; fi
-          # an if, not "! grep": bash exempts a negated command from set -e and
-          # the assertion would never fail
-          if docker logs frigate-ro 2>&1 | grep -i "read-only file system"; then
-            echo "a service tried to write to the read-only rootfs"; exit 1
-          fi
-          # the self-signed cert has to land in /config, the only writable path
-          docker exec frigate-ro test -f /config/tls/privkey.pem
-          # and nginx must serve it, which is what proves the templated cert path
-          docker exec frigate-ro curl -ksSI https://127.0.0.1:8971/ >/dev/null
-          # logging must work via the s6-log fallback (no logutil-service as non-root)
-          docker exec frigate-ro test -s /dev/shm/logs/frigate/current
-          # runtime user can write recordings storage
-          docker exec frigate-ro touch /media/frigate/.write-probe
-          docker exec frigate-ro rm /media/frigate/.write-probe
-          docker rm -f frigate-ro
-      - name: Assert PUID with read-only fails fast with clear error
-        run: |
-          docker run -d --name frigate-ro-puid --shm-size 256m \
-            --read-only --tmpfs /tmp:rw,size=1g --tmpfs /run:exec,nosuid,nodev,mode=0755 \
-            -e PUID=1500 -e PGID=1500 \
-            -v /tmp/frigate-config-ro:/config \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          found=0
-          for i in $(seq 1 12); do
-            if docker logs frigate-ro-puid 2>&1 | grep -q "not compatible with read_only"; then found=1; break; fi
-            sleep 5
-          done
-          if [ "$found" -ne 1 ]; then
-            echo "no fail-fast error for PUID with a read-only rootfs"; docker logs frigate-ro-puid; exit 1
-          fi
-          docker rm -f frigate-ro-puid
-      - name: Assert EXTRA_GROUPS with read-only fails fast with clear error
-        run: |
-          docker run -d --name frigate-ro-groups --shm-size 256m \
-            --read-only --tmpfs /tmp:rw,size=1g --tmpfs /run:exec,nosuid,nodev,mode=0755 \
-            -e EXTRA_GROUPS=44 \
-            -v /tmp/frigate-config-ro:/config \
-            -v /tmp/frigate-media-ro:/media/frigate \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          found=0
-          for i in $(seq 1 12); do
-            if docker logs frigate-ro-groups 2>&1 | grep -q "EXTRA_GROUPS needs a writable /etc"; then found=1; break; fi
-            sleep 5
-          done
-          if [ "$found" -ne 1 ]; then
-            echo "no fail-fast error for EXTRA_GROUPS with a read-only rootfs"; docker logs frigate-ro-groups; exit 1
-          fi
-          docker rm -f frigate-ro-groups
-      - name: Assert read-only rootfs in the default mode works
-        run: |
-          mkdir -p /tmp/frigate-config-rod /tmp/frigate-media-rod
-          printf 'mqtt:\n  enabled: false\ncameras: {}\n' > /tmp/frigate-config-rod/config.yml
-          docker run -d --name frigate-rod --shm-size 256m \
-            --read-only --tmpfs /tmp:rw,size=1g --tmpfs /run:exec,nosuid,nodev,mode=0755 \
-            --security-opt no-new-privileges:true \
-            -v /tmp/frigate-config-rod:/config \
-            -v /tmp/frigate-media-rod:/media/frigate \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          up=0
-          for i in $(seq 1 60); do
-            docker exec frigate-rod curl -fs http://127.0.0.1:5000/api/version && up=1 && break
-            sleep 5
-          done
-          if [ "$up" -ne 1 ]; then echo "read-only default-mode container never healthy"; docker logs frigate-rod; exit 1; fi
-          if docker logs frigate-rod 2>&1 | grep -i "read-only file system"; then
-            echo "a service tried to write to the read-only rootfs"; exit 1
-          fi
-          # the point of this mode over docker's user:: the drop still happens
-          # and go2rtc still gets its own separate user
-          ps_out=$(docker exec frigate-rod ps -eo user=,comm=)
-          echo "$ps_out"
-          for svc in python3 nginx; do
-            if echo "$ps_out" | grep -w "$svc" | grep -q '^root'; then
-              echo "$svc is running as root"; exit 1
-            fi
-          done
-          echo "$ps_out" | grep -w go2rtc | grep -q '^go2rtc'
-          # the ownership sweep still ran and recorded itself in /config
-          docker exec frigate-rod cat /config/.permissions_version | grep -qx "2:1000:1000"
-          # setfacl under a read-only rootfs, which nothing else covers:
-          # init-devices exits early under --user, so that path is never reached
-          docker exec frigate-rod mknod /dev/apex_9 c 120 99
-          docker exec frigate-rod sh -c 'export PATH=/command:$PATH; exec /etc/s6-overlay/s6-rc.d/init-devices/run'
-          docker exec frigate-rod getfacl -p /dev/apex_9 | grep -q "user:frigate:rw-"
-          docker rm -f frigate-rod
-      - name: "Assert switching that install to user: still starts"
-        run: |
-          # the config dir above now holds a go2rtc-owned go2rtc_homekit.yml,
-          # which user: keeps readable but not writable (no supplementary groups)
-          docker run -d --name frigate-rod-user --shm-size 256m \
-            --read-only --tmpfs /tmp:rw,size=1g --tmpfs /run:exec,nosuid,nodev,mode=0755,uid=1000,gid=1000 \
-            --user 1000:1000 \
-            -v /tmp/frigate-config-rod:/config \
-            -v /tmp/frigate-media-rod:/media/frigate \
-            ${{ steps.setup.outputs.image-name }}-amd64
-          up=0
-          for i in $(seq 1 60); do
-            docker exec frigate-rod-user curl -fs http://127.0.0.1:5000/api/version && up=1 && break
-            sleep 5
-          done
-          if [ "$up" -ne 1 ]; then echo "container did not survive the switch to user:"; docker logs frigate-rod-user; exit 1; fi
-          docker logs frigate-rod-user 2>&1 | grep -q "HomeKit pairing changes will not persist"
-          docker rm -f frigate-rod-user
       - name: Teardown
         if: always()
         run: docker rm -f frigate || true
@@ -426,7 +130,7 @@ jobs:
     name: ARM Build
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up QEMU and Buildx
@@ -461,7 +165,7 @@ jobs:
     name: Jetson Jetpack 6
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up QEMU and Buildx
@@ -492,7 +196,7 @@ jobs:
       - amd64_build
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up QEMU and Buildx
@@ -533,7 +237,7 @@ jobs:
       - arm64_build
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up QEMU and Buildx
@@ -558,7 +262,7 @@ jobs:
       - arm64_build
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up QEMU and Buildx
@@ -590,7 +294,7 @@ jobs:
         with:
           string: ${{ github.repository }}
       - name: Log in to the Container registry
-        uses: docker/login-action@dbcb813823bdd20940b903addbd779551569679f
+        uses: docker/login-action@184bdaa0721073962dff0199f1fb9940f07167d1
         with:
           registry: ghcr.io
           username: ${{ github.actor }}

.github/workflows/pull_request.yml

@@ -16,10 +16,10 @@ jobs:
     name: Web - Lint
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
         with:
           persist-credentials: false
-      - uses: actions/setup-node@v7
+      - uses: actions/setup-node@v6
         with:
           node-version: 20.x
       - run: npm install
@@ -35,10 +35,10 @@ jobs:
     name: Web - Test
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
         with:
           persist-credentials: false
-      - uses: actions/setup-node@v7
+      - uses: actions/setup-node@v6
         with:
           node-version: 20.x
       - run: npm install
@@ -46,15 +46,18 @@ jobs:
       - name: Build web
         run: npm run build
         working-directory: ./web
+      # - name: Test
+      #   run: npm run test
+      #   working-directory: ./web
 
   web_e2e:
     name: Web - E2E Tests
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
         with:
           persist-credentials: false
-      - uses: actions/setup-node@v7
+      - uses: actions/setup-node@v6
         with:
           node-version: 20.x
       - run: npm install
@@ -83,11 +86,11 @@ jobs:
     name: Python Checks
     steps:
       - name: Check out the repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Set up Python ${{ env.DEFAULT_PYTHON }}
-        uses: actions/setup-python@v7.0.0
+        uses: actions/setup-python@v5.4.0
         with:
           python-version: ${{ env.DEFAULT_PYTHON }}
       - name: Install requirements
@@ -106,10 +109,10 @@ jobs:
     name: Python Tests
     steps:
       - name: Check out code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           persist-credentials: false
-      - uses: actions/setup-node@v7
+      - uses: actions/setup-node@v6
         with:
           node-version: 20.x
       - name: Install devcontainer cli
@@ -124,7 +127,5 @@ jobs:
         run: devcontainer exec --workspace-folder . bash -lc "python3 -u -m mypy --config-file frigate/mypy.ini frigate"
       - name: Check API spec is up to date
         run: devcontainer exec --workspace-folder . bash -lc "python3 generate_api_auth_spec.py --check"
-      - name: Check analytics schema is up to date
-        run: devcontainer exec --workspace-folder . bash -lc "python3 generate_analytics_schema.py --check"
       - name: Run unit tests in devcontainer
         run: devcontainer exec --workspace-folder . bash -lc "python3 -u -m unittest"

.github/workflows/release.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
         with:
           persist-credentials: false
       - id: lowercaseRepo
@@ -18,7 +18,7 @@ jobs:
         with:
           string: ${{ github.repository }}
       - name: Log in to the Container registry
-        uses: docker/login-action@dbcb813823bdd20940b903addbd779551569679f
+        uses: docker/login-action@184bdaa0721073962dff0199f1fb9940f07167d1
         with:
           registry: ghcr.io
           username: ${{ github.actor }}

.gitignore

@@ -28,7 +28,3 @@ core
 docs/src/components/DockerComposeGenerator/config/devices.ts
 docs/src/components/DockerComposeGenerator/config/hardware.ts
 docs/src/components/DockerComposeGenerator/config/ports.ts
-
-# GenAI review prompt tester local data (frames from real cameras)
-testing-scripts/genai-review-examples/*
-!testing-scripts/genai-review-examples/README.md

AGENTS.md

@@ -160,7 +160,7 @@ When reviewing code, do NOT comment on:
 
 ### Code Quality
 
-- **Linting**: ESLint (see `web/eslint.config.js`)
+- **Linting**: ESLint (see `web/.eslintrc.cjs`)
 - **Formatting**: Prettier with Tailwind CSS plugin
 - **Type Safety**: TypeScript strict mode enabled
 

CODEOWNERS

@@ -5,4 +5,3 @@
 /docker/rockchip/ @MarcA711
 /docker/rocm/ @harakas
 /docker/hailo8l/ @spanner3003
-/docker/deepx/ @sixfab

docker/deepx/user_installation.sh

@@ -1,131 +0,0 @@
-#!/bin/bash
-
-# Installs the DEEPX NPU kernel driver and the DX-RT runtime on the Docker host,
-# then enables the vendor's dxrt.service. A container cannot load kernel
-# modules, so this runs outside the image; the driver creates the /dev/dxrt*
-# nodes and the daemon multiplexes the NPU across host and container.
-#
-# Driver, runtime and firmware versions must agree or inference hangs instead
-# of failing at startup. The set this script installs is pinned in
-# driver_version, runtime_version and firmware_version below; move them
-# together, never one at a time.
-#
-# DEEPX NPU support in Frigate is maintained by Sixfab (https://sixfab.com).
-
-set -euo pipefail
-
-driver_version="v2.6.0"
-# the commit the tag resolves to, since DEEPX signs neither tags nor releases
-# and this is compiled and installed as root. Update both together
-driver_commit="7074748e7104f470b02f517583abba652b3f05fa"
-firmware_version="v2.7.4"
-
-sudo apt-get update
-sudo apt-get install -y git build-essential "linux-headers-$(uname -r)" pciutils wget
-
-if ! lspci -d 1ff4: | grep -q .; then
-    echo "No DEEPX device found on the PCIe bus (lspci -d 1ff4:)."
-    echo "Check that the module is seated correctly before continuing."
-    exit 1
-fi
-
-# fetch the pinned commit rather than cloning the tag, so a retag cannot swap
-# in different source. The build directory is reused so a second run after a
-# failure does not stop on the directory already being there
-mkdir -p dx_rt_npu_linux_driver
-cd dx_rt_npu_linux_driver
-git init -q
-git remote get-url origin > /dev/null 2>&1 ||
-    git remote add origin https://github.com/DEEPX-AI/dx_rt_npu_linux_driver.git
-git fetch --depth 1 origin "${driver_commit}"
-git checkout -q FETCH_HEAD
-
-fetched_commit=$(git rev-parse HEAD)
-if [[ "${fetched_commit}" != "${driver_commit}" ]]; then
-    echo "Fetched commit ${fetched_commit} does not match pinned driver_commit ${driver_commit}."
-    echo "Refusing to build unverified driver source."
-    exit 1
-fi
-
-cd modules
-
-sudo ./build.sh -c install --reload
-
-sudo depmod -A
-
-# dx_dma is the PCIe transport, dxrt_driver the NPU driver on top of it
-for module in dx_dma dxrt_driver; do
-    if ! sudo modprobe "${module}"; then
-        echo "Unable to load the ${module} kernel module, common reasons are:"
-        echo "- Secure Boot is enabled and is rejecting the unsigned module."
-        echo "- The running kernel does not match the installed linux-headers."
-        exit 1
-    fi
-done
-
-if ! compgen -G "/dev/dxrt*" > /dev/null; then
-    echo "Modules loaded but no /dev/dxrt* device node appeared."
-    echo "Run ./sanity_check.sh from the driver repo to diagnose."
-    exit 1
-fi
-
-runtime_version="v3.4.0"
-declare -A runtime_sha256=(
-    [amd64]="736cfef009ce9e974ab1ab610d867239d19d72a426a53e367ddcbd53297b6e20"
-    [arm64]="eb6107f5f02f2ad76ae89f414e8b5f346f34fbc6f0888236136853a26be6f6a0"
-)
-
-runtime_release="${runtime_version#v}"
-deb_arch=$(dpkg --print-architecture)
-deb_file="/tmp/libdxrt-bin_${runtime_release}_${deb_arch}.deb"
-
-wget -qO "${deb_file}" \
-    "https://raw.githubusercontent.com/DEEPX-AI/dx_rt/${runtime_version}/release/${runtime_release}/libdxrt-bin_${runtime_release}_${deb_arch}.deb"
-
-expected_sha256="${runtime_sha256[${deb_arch}]:-}"
-if [[ -z "${expected_sha256}" ]]; then
-    echo "No pinned SHA-256 for architecture ${deb_arch}; refusing to install."
-    exit 1
-fi
-if [[ "$(sha256sum "${deb_file}" | cut -d' ' -f1)" != "${expected_sha256}" ]]; then
-    echo "SHA-256 mismatch for ${deb_file}; refusing to install."
-    exit 1
-fi
-
-sudo dpkg -i "${deb_file}"
-sudo ldconfig
-rm -f "${deb_file}"
-
-sudo cp /usr/share/libdxrt-bin/service/dxrt.service /etc/systemd/system/
-
-# With an endpoint set, dxrtd binds that path only, so the socket goes in a
-# directory Frigate can mount (kept across restarts so the mount stays valid)
-# and a symlink at the default /tmp path keeps host tools that do not set the
-# variable working through their own fallback.
-sudo mkdir -p /etc/systemd/system/dxrt.service.d
-sudo tee /etc/systemd/system/dxrt.service.d/frigate.conf > /dev/null <<'UNIT'
-[Service]
-RuntimeDirectory=dxrt
-RuntimeDirectoryMode=0755
-RuntimeDirectoryPreserve=yes
-Environment=DXRT_DYNAMIC_IPC_ENDPOINT=/run/dxrt/dxrt_dynamic_ipc.sock
-ExecStartPost=/bin/ln -sfn /run/dxrt/dxrt_dynamic_ipc.sock /tmp/dxrt_dynamic_ipc.sock
-UNIT
-
-sudo systemctl daemon-reload
-sudo systemctl enable dxrt.service
-sudo systemctl restart dxrt.service
-
-if ! sudo systemctl is-active --quiet dxrt.service; then
-    echo "dxrt.service did not start. Check: sudo journalctl -u dxrt.service"
-    exit 1
-fi
-
-echo "DEEPX driver and runtime installation complete."
-echo "Driver version:   $(modinfo -F version dxrt_driver) (expected ${driver_version#v})"
-echo "Runtime version:  ${runtime_release}"
-echo "Device node(s):   $(echo /dev/dxrt*)"
-echo
-echo "This driver expects NPU firmware ${firmware_version}. Check it with:"
-echo "  dxrt-cli --status"
-echo "Update the module if it does not match before starting Frigate."

docker/main/Dockerfile

@@ -146,8 +146,6 @@ RUN wget -q https://github.com/openvinotoolkit/open_model_zoo/raw/master/data/da
 RUN wget -qO - https://www.kaggle.com/api/v1/models/google/yamnet/tfLite/classification-tflite/1/download | tar xvz && mv 1.tflite cpu_audio_model.tflite
 COPY audio-labelmap.txt .
 
-RUN chmod -R a+rX /rootfs
-
 
 FROM wget AS s6-overlay
 ARG TARGETARCH
@@ -202,6 +200,10 @@ RUN pip3 wheel --wheel-dir=/wheels -r /requirements-wheels.txt && \
         pip3 wheel --wheel-dir=/wheels -r /requirements-dev.txt; \
     fi
 
+# Install HailoRT & Wheels
+RUN --mount=type=bind,source=docker/main/install_hailort.sh,target=/deps/install_hailort.sh \
+    /deps/install_hailort.sh
+
 # Collect deps in a single layer
 FROM scratch AS deps-rootfs
 COPY --from=nginx /usr/local/nginx/ /usr/local/nginx/
@@ -212,6 +214,7 @@ COPY --from=libusb-build /usr/local/lib /usr/local/lib
 COPY --from=tempio /rootfs/ /
 COPY --from=s6-overlay /rootfs/ /
 COPY --from=models /rootfs/ /
+COPY --from=wheels /rootfs/ /
 COPY docker/main/rootfs/ /
 
 
@@ -289,12 +292,16 @@ RUN wget -q https://bootstrap.pypa.io/get-pip.py -O get-pip.py \
 RUN --mount=type=bind,from=wheels,source=/wheels,target=/deps/wheels \
     pip3 install -U /deps/wheels/*.whl
 
-# The Hailo, MemryX, and Axera runtimes are installed at first start by
-# frigate/util/runtime_deps.py, only when that detector is configured.
-# Axera's native libraries are bind mounted from the host.
+# Install Axera Engine
+RUN pip3 install https://github.com/AXERA-TECH/pyaxengine/releases/download/0.1.3-frigate/axengine-0.1.3-py3-none-any.whl
+
 ENV PATH="${PATH}:/usr/bin/axcl"
 ENV LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/lib/axcl"
 
+# Install MemryX runtime (requires libgomp (OpenMP) in the final docker image)
+RUN --mount=type=bind,source=docker/main/install_memryx.sh,target=/deps/install_memryx.sh \
+    bash -c "bash /deps/install_memryx.sh"
+
 COPY --from=deps-rootfs / /
 
 RUN ldconfig
@@ -307,9 +314,6 @@ EXPOSE 8555/tcp 8555/udp
 ENV S6_LOGGING_SCRIPT="T 1 n0 s10000000 T"
 # Do not fail on long-running download scripts
 ENV S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0
-# Allow running with a read-only root filesystem: s6 copies its scan dir into
-# /run and executes service scripts from there, so /run must allow exec
-ENV S6_READ_ONLY_ROOT=1
 
 ENTRYPOINT ["/init"]
 CMD []
@@ -381,8 +385,3 @@ FROM deps AS frigate
 
 WORKDIR /opt/frigate/
 COPY --from=rootfs / /
-ENV FRIGATE_IMAGE_VARIANT=standard
-
-# Pre-compile bytecode so a read-only rootfs doesn't force re-parsing the
-# source tree on every boot (pip-installed packages are already compiled)
-RUN python3 -m compileall -q -j0 /opt/frigate/frigate

docker/main/build_nginx.sh

@@ -3,7 +3,7 @@
 set -euxo pipefail
 
 NGINX_VERSION="1.27.4"
-VOD_MODULE_VERSION="v1.9.1"
+VOD_MODULE_VERSION="1.31"
 SECURE_TOKEN_MODULE_VERSION="1.5"
 SET_MISC_MODULE_VERSION="v0.33"
 NGX_DEVEL_KIT_VERSION="v0.3.3"
@@ -31,24 +31,24 @@ 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/dio-az/nginx-vod-module/archive/refs/tags/${VOD_MODULE_VERSION}.tar.gz
+wget -nv https://github.com/kaltura/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
-+++ b/vod/avc_hevc_parser.c
-@@ -2,6 +2,9 @@
-
+--- 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 @@
  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
 
 

docker/main/install_deps.sh

@@ -10,7 +10,7 @@ apt-get -qq install --no-install-recommends -y \
     gnupg \
     wget \
     lbzip2 \
-    procps vainfo acl \
+    procps vainfo \
     unzip locales tzdata libxml2 xz-utils \
     python3.11 \
     curl \

docker/main/install_hailort.sh

@@ -0,0 +1,32 @@
+#!/bin/bash
+
+set -euxo pipefail
+
+hailo_version="4.21.0"
+
+# sha256 digests of the release artifacts; update when bumping hailo_version.
+# The runtime tarball is keyed by TARGETARCH, the wheel by the python arch tag.
+declare -A hailort_checksums=(
+    ["amd64"]="0a57ac5f7cc8c2c3668133189d9285b55f498e8cb219797e203f6f5015fec4b3"
+    ["arm64"]="dd840548eb5d0d147c99aee2cb013d39d64be09c5bc63061171fcfacf4547b3f"
+    ["x86_64"]="8112a973ab48095399b29d883f31987828df5861b8553f614c89f098a67b3fb6"
+    ["aarch64"]="658432a43573280d472f6402d7934669effe7f163ba3dffa31c50bbeeaa7c01d"
+)
+
+if [[ "${TARGETARCH}" == "amd64" ]]; then
+    arch="x86_64"
+elif [[ "${TARGETARCH}" == "arm64" ]]; then
+    arch="aarch64"
+fi
+
+# downloaded rather than streamed into tar because streaming and verifying the
+# digest before extraction are mutually exclusive
+wget -qO /tmp/hailort.tar.gz "https://github.com/frigate-nvr/hailort/releases/download/v${hailo_version}/hailort-debian12-${TARGETARCH}.tar.gz"
+echo "${hailort_checksums[${TARGETARCH}]}  /tmp/hailort.tar.gz" | sha256sum -c -
+tar -C / -xzf /tmp/hailort.tar.gz
+rm -f /tmp/hailort.tar.gz
+
+wheel="/wheels/hailort-${hailo_version}-cp311-cp311-linux_${arch}.whl"
+mkdir -p /wheels
+wget -qO "${wheel}" "https://github.com/frigate-nvr/hailort/releases/download/v${hailo_version}/hailort-${hailo_version}-cp311-cp311-linux_${arch}.whl"
+echo "${hailort_checksums[${arch}]}  ${wheel}" | sha256sum -c -

docker/main/install_memryx.sh

@@ -0,0 +1,31 @@
+#!/bin/bash
+set -e
+
+# Download the MxAccl for Frigate github release
+wget https://github.com/memryx/mx_accl_frigate/archive/refs/tags/v2.1.0.zip -O /tmp/mxaccl.zip
+unzip /tmp/mxaccl.zip -d /tmp
+mv /tmp/mx_accl_frigate-2.1.0 /opt/mx_accl_frigate
+rm /tmp/mxaccl.zip
+
+# Install Python dependencies
+pip3 install -r /opt/mx_accl_frigate/freeze
+
+# Link the Python package dynamically
+SITE_PACKAGES=$(python3 -c "import site; print(site.getsitepackages()[0])")
+ln -s /opt/mx_accl_frigate/memryx "$SITE_PACKAGES/memryx"
+
+# Copy architecture-specific shared libraries
+ARCH=$(uname -m)
+if [[ "$ARCH" == "x86_64" ]]; then
+    cp /opt/mx_accl_frigate/memryx/x86/libmemx.so* /usr/lib/x86_64-linux-gnu/
+    cp /opt/mx_accl_frigate/memryx/x86/libmx_accl.so* /usr/lib/x86_64-linux-gnu/
+elif [[ "$ARCH" == "aarch64" ]]; then
+    cp /opt/mx_accl_frigate/memryx/arm/libmemx.so* /usr/lib/aarch64-linux-gnu/
+    cp /opt/mx_accl_frigate/memryx/arm/libmx_accl.so* /usr/lib/aarch64-linux-gnu/
+else
+    echo "Unsupported architecture: $ARCH"
+    exit 1
+fi
+
+# Refresh linker cache
+ldconfig

docker/main/requirements-dev.txt

@@ -1,4 +1,4 @@
 ruff == 0.15.20
 
 # types
-types-peewee == 4.0.*
+types-peewee == 3.17.*

docker/main/requirements-wheels.txt

@@ -1,17 +1,17 @@
-aiofiles == 25.1.*
-click == 8.5.*
+aiofiles == 24.1.*
+click == 8.1.*
 # FastAPI
 aiohttp == 3.12.*
 starlette == 0.47.*
-starlette-context == 0.5.*
+starlette-context == 0.4.*
 fastapi[standard-no-fastapi-cloud-cli] == 0.116.*
-uvicorn == 0.52.*
+uvicorn == 0.35.*
 slowapi == 0.1.*
-joserfc == 1.6.*
-cryptography == 46.0.*
+joserfc == 1.2.*
+cryptography == 44.0.*
 pathvalidate == 3.3.*
 markupsafe == 3.0.*
-python-multipart == 0.0.31
+python-multipart == 0.0.26
 # Classification Model Training
 tensorflow == 2.19.* ; platform_machine == 'aarch64'
 tensorflow-cpu == 2.19.* ; platform_machine == 'x86_64'
@@ -26,15 +26,15 @@ psutil == 7.1.*
 pydantic == 2.10.*
 git+https://github.com/fbcotter/py3nvml#egg=py3nvml
 pytz == 2025.*
-pyzmq == 27.1.*
+pyzmq == 26.2.*
 ruamel.yaml == 0.18.*
 tzlocal == 5.2
-requests == 2.33.*
+requests == 2.32.*
 types-requests == 2.32.*
 norfair == 2.3.*
 setproctitle == 1.3.*
 ws4py == 0.5.*
-unidecode == 1.4.*
+unidecode == 1.3.*
 titlecase == 2.4.*
 # Image Manipulation
 numpy == 1.26.*
@@ -51,26 +51,33 @@ google-genai == 1.58.*
 ollama == 0.6.*
 openai == 1.65.*
 # push notifications
-py-vapid == 1.9.4
+py-vapid == 1.9.*
 pywebpush == 2.0.*
 # alpr
-pyclipper == 1.4.*
+pyclipper == 1.3.*
 shapely == 2.0.*
 rapidfuzz==3.12.*
-# HailoRT
+# HailoRT Wheels
+appdirs==1.4.*
 argcomplete==2.0.*
 contextlib2==0.6.*
+distlib==0.3.*
+filelock==3.8.*
 future==0.18.*
-netaddr==1.3.*
+importlib-metadata==5.1.*
+importlib-resources==5.1.*
+netaddr==0.8.*
 netifaces==0.10.*
-prometheus-client == 0.26.*
+verboselogs==1.7.*
+virtualenv==20.17.*
+prometheus-client == 0.21.*
 # TFLite
 tflite_runtime @ https://github.com/frigate-nvr/TFlite-builds/releases/download/v2.17.1/tflite_runtime-2.17.1-cp311-cp311-linux_x86_64.whl; platform_machine == 'x86_64'
 tflite_runtime @ https://github.com/feranick/TFlite-builds/releases/download/v2.17.1/tflite_runtime-2.17.1-cp311-cp311-linux_aarch64.whl; platform_machine == 'aarch64'
 # audio transcription
-sherpa-onnx==1.13.*
-faster-whisper==1.2.*
+sherpa-onnx==1.12.*
+faster-whisper==1.1.*
 librosa==0.11.*
 soundfile==0.13.*
 # Memory profiling
-memray == 1.20.*
+memray == 1.15.*

docker/main/rootfs/etc/s6-overlay/s6-rc.d/certsync/run

@@ -6,35 +6,9 @@ set -o errexit -o nounset -o pipefail
 
 # Logs should be sent to stdout so that s6 can collect them
 
-# Not `nginx -s reload`: that has root parse /tmp/nginx/conf, which the
-# unprivileged nginx user can rewrite, and nginx chowns path directives on load.
-function reload_nginx() {
-    local pid
-
-    if ! pid=$(cat /tmp/nginx/nginx.pid 2>/dev/null); then
-        echo "[ERROR] No nginx pid file found, not reloading"
-        return 0
-    fi
-
-    if [[ ! "$pid" =~ ^[0-9]+$ ]] || [[ "$(cat "/proc/${pid}/comm" 2>/dev/null)" != "nginx" ]]; then
-        echo "[ERROR] nginx pid file does not name a running nginx process, not reloading"
-        return 0
-    fi
-
-    kill -HUP "$pid"
-}
-
 echo "[INFO] Starting certsync..."
 
-# Resolved once, and the condition must stay identical to the nginx run
-# script's. Testing only fullchain.pem here would pick the mounted cert on a
-# half-populated mount that nginx rejected, and the two fingerprints would then
-# never agree, reloading nginx every cycle forever.
-if [ -f /etc/letsencrypt/live/frigate/privkey.pem ] && [ -f /etc/letsencrypt/live/frigate/fullchain.pem ]; then
-    lefile="/etc/letsencrypt/live/frigate/fullchain.pem"
-else
-    lefile="/config/tls/fullchain.pem"
-fi
+lefile="/etc/letsencrypt/live/frigate/fullchain.pem"
 
 tls_enabled=`python3 /usr/local/nginx/get_nginx_settings.py | jq -r .tls.enabled`
 listen_external_port=`python3 /usr/local/nginx/get_nginx_settings.py | jq -r .listen.external_port`
@@ -75,7 +49,7 @@ do
     then
         echo "[INFO] Reloading nginx to refresh TLS certificate"
         echo "$lefile: $leprint"
-        reload_nginx
+        /usr/local/nginx/sbin/nginx -s reload
     fi
 
     sleep 60

docker/main/rootfs/etc/s6-overlay/s6-rc.d/frigate/run

@@ -4,24 +4,6 @@
 
 set -o errexit -o nounset -o pipefail
 
-runs_as_root=0
-if [[ "$(id -u)" -eq 0 ]]; then
-    if [[ "${FRIGATE_RUN_AS_ROOT:-false}" == "true" ]] || /usr/local/bin/service-runs-as-root frigate; then
-        runs_as_root=1
-    fi
-fi
-
-# /root survives s6-setuidgid and breaks cache writes after the drop; set
-# before opt_in_out so the opt-out marker lands where the service will look
-if [[ "$runs_as_root" -eq 0 ]]; then
-    export HOME=/config
-fi
-
-# detector runtimes installed at first start (pip install --user) live under
-# $HOME/.local; the dynamic loader only reads LD_LIBRARY_PATH at exec time
-export LD_LIBRARY_PATH="${LD_LIBRARY_PATH:+${LD_LIBRARY_PATH}:}${HOME}/.local/lib"
-export PATH="${PATH}:${HOME}/.local/bin"
-
 # opt out of openvino telemetry
 if [ -e /usr/local/bin/opt_in_out ]; then
   /usr/local/bin/opt_in_out --opt_out > /dev/null 2>&1
@@ -48,8 +30,4 @@ cd /opt/frigate || echo "[ERROR] Failed to change working directory to /opt/frig
 
 # Replace the bash process with the Frigate process, redirecting stderr to stdout
 exec 2>&1
-if [[ "$(id -u)" -ne 0 || "$runs_as_root" -eq 1 ]]; then
-    exec python3 -u -m frigate
-else
-    exec s6-setuidgid frigate python3 -u -m frigate
-fi
+exec python3 -u -m frigate

docker/main/rootfs/etc/s6-overlay/s6-rc.d/go2rtc/run

@@ -4,20 +4,6 @@
 
 set -o errexit -o nounset -o pipefail
 
-runs_as_root=0
-if [[ "$(id -u)" -eq 0 ]]; then
-    if [[ "${FRIGATE_RUN_AS_ROOT:-false}" == "true" ]] || /usr/local/bin/service-runs-as-root go2rtc; then
-        runs_as_root=1
-    fi
-fi
-
-# Root via FRIGATE_ROOT_SERVICES only; the escape hatch sweeps nothing and
-# leaves no unprivileged service, so /config/go2rtc stays as safe as pre-drop.
-granular_root=0
-if [[ "$runs_as_root" -eq 1 && "${FRIGATE_RUN_AS_ROOT:-false}" != "true" ]]; then
-    granular_root=1
-fi
-
 # Logs should be sent to stdout so that s6 can collect them
 
 function get_ip_and_port_from_supervisor() {
@@ -64,6 +50,42 @@ function set_libva_version() {
     export LIBAVFORMAT_VERSION_MAJOR
 }
 
+function setup_homekit_config() {
+    local config_path="$1"
+
+    if [[ ! -f "${config_path}" ]]; then
+        echo "[INFO] Creating empty config file for HomeKit..."
+        : > "${config_path}"
+    fi
+
+    # Convert YAML to JSON for jq processing
+    local temp_json="/tmp/cache/homekit_config.json"
+    yq eval -o=json "${config_path}" > "${temp_json}" 2>/dev/null || {
+        echo "[WARNING] Failed to convert HomeKit config to JSON, skipping cleanup"
+        return 0
+    }
+
+    # Use jq to extract the homekit section, if it exists
+    local homekit_json
+    homekit_json=$(jq '
+        if has("homekit") then {homekit: .homekit} else null end
+    ' "${temp_json}" 2>/dev/null) || homekit_json="null"
+
+    # If no homekit section, write an empty config file
+    if [[ "${homekit_json}" == "null" ]]; then
+        : > "${config_path}"
+    else
+        # Convert homekit JSON back to YAML and write to the config file
+        echo "${homekit_json}" | yq eval -P - > "${config_path}" 2>/dev/null || {
+            echo "[WARNING] Failed to convert cleaned config to YAML, creating minimal config"
+            : > "${config_path}"
+        }
+    fi
+
+    # Clean up temp files
+    rm -f "${temp_json}"
+}
+
 set_libva_version
 
 if [[ -f "/dev/shm/go2rtc.yaml" ]]; then
@@ -84,23 +106,13 @@ else
     echo "[WARNING] Unable to remove existing go2rtc config. Changes made to your frigate config file may not be recognized. Please remove the /dev/shm/go2rtc.yaml from your docker host manually."
 fi
 
-# HomeKit persistence. The helper is symlink-safe; hand off to go2rtc only when dropping.
+# HomeKit configuration persistence setup
 readonly homekit_config_path="/config/go2rtc_homekit.yml"
-if [[ "$(id -u)" -eq 0 && "$runs_as_root" -eq 0 ]]; then
-    python3 /usr/local/go2rtc/prepare_homekit.py "${homekit_config_path}" --chown
-    chown go2rtc:go2rtc /dev/shm/go2rtc.yaml 2>/dev/null || true
-else
-    python3 /usr/local/go2rtc/prepare_homekit.py "${homekit_config_path}"
-fi
+setup_homekit_config "${homekit_config_path}"
 
 readonly config_path="/config"
 
-# the sweep hands /config to uid 1000, so a root service must not exec from it
-if [[ "$granular_root" -eq 1 && -x "${config_path}/go2rtc" ]]; then
-  echo "[WARN] Ignoring '${config_path}/go2rtc' because FRIGATE_ROOT_SERVICES runs this service as root and /config is owned by the runtime user; using the embedded binary"
-  echo "[WARN] Use FRIGATE_RUN_AS_ROOT=true instead if you need both a custom go2rtc build and root"
-  readonly binary_path="/usr/local/go2rtc/bin/go2rtc"
-elif [[ -x "${config_path}/go2rtc" ]]; then
+if [[ -x "${config_path}/go2rtc" ]]; then
   readonly binary_path="${config_path}/go2rtc"
   echo "[WARN] Using go2rtc binary from '${binary_path}' instead of the embedded one"
 else
@@ -113,8 +125,4 @@ echo "[INFO] Starting go2rtc..."
 # Use HomeKit config as the primary config so writebacks go there
 # The main config from Frigate will be loaded as a secondary config
 exec 2>&1
-if [[ "$(id -u)" -ne 0 || "$runs_as_root" -eq 1 ]]; then
-    exec "${binary_path}" -config="${homekit_config_path}" -config=/dev/shm/go2rtc.yaml
-else
-    exec s6-setuidgid go2rtc "${binary_path}" -config="${homekit_config_path}" -config=/dev/shm/go2rtc.yaml
-fi
+exec "${binary_path}" -config="${homekit_config_path}" -config=/dev/shm/go2rtc.yaml

docker/main/rootfs/etc/s6-overlay/s6-rc.d/init-devices/run

@@ -1,105 +0,0 @@
-#!/command/with-contenv bash
-# shellcheck shell=bash
-# Grant the runtime users access to mapped-in device nodes with POSIX ACLs,
-# so --device works without host-side group or udev setup.
-# No-op when: started with --user (euid != 0), FRIGATE_RUN_AS_ROOT=true,
-# or FRIGATE_DEVICE_ACLS=false.
-
-set -o errexit -o nounset -o pipefail
-
-if [[ "$(id -u)" -ne 0 ]]; then
-    exit 0
-fi
-
-if [[ "${FRIGATE_RUN_AS_ROOT:-false}" == "true" ]]; then
-    exit 0
-fi
-
-if [[ "${FRIGATE_DEVICE_ACLS:-true}" == "false" ]]; then
-    echo "[INFO] FRIGATE_DEVICE_ACLS=false: skipping device access grants"
-    exit 0
-fi
-
-shopt -s nullglob
-
-device_globs=(
-    "/dev/dri/*"
-    "/dev/accel/*"
-    "/dev/apex_*"
-    "/dev/hailo*"
-    "/dev/video*"
-    "/dev/kfd"
-    "/dev/rknpu*"
-    "/dev/mpp_service"
-    "/dev/rga"
-    "/dev/dma_heap/*"
-    "/dev/nvhost*"
-    "/dev/nvmap"
-    "/dev/nvidia*"
-    "/dev/memx*"
-    "/dev/dxrt*"
-)
-
-IFS=',' read -ra extra_globs <<< "${DEVICE_ACL_PATHS:-}"
-for extra in "${extra_globs[@]}"; do
-    extra="${extra//[[:space:]]/}"
-    if [[ -z "$extra" ]]; then
-        continue
-    fi
-    if [[ "$extra" != /dev/* || "$extra" == *..* ]]; then
-        echo "[ERROR] DEVICE_ACL_PATHS entries must be under /dev, got '${extra}'" >&2
-        exit 1
-    fi
-    device_globs+=("$extra")
-done
-
-granted=0
-failed=0
-
-grant() {
-    local node="$1"
-    # nullglob only drops patterns that hold a metacharacter, so a literal
-    # table entry for absent hardware arrives here verbatim. Warn only about
-    # nodes that exist and could not be granted.
-    if [[ ! -e "$node" ]]; then
-        return 0
-    fi
-    local spec="u:frigate:rw,u:go2rtc:rw"
-    # directories need traverse or nothing under them is reachable
-    if [[ -d "$node" ]]; then
-        spec="u:frigate:rwx,u:go2rtc:rwx"
-    fi
-    if setfacl -m "$spec" "$node" 2>/dev/null; then
-        granted=$((granted + 1))
-    else
-        failed=$((failed + 1))
-        echo "[WARN] could not grant device access on ${node}; see EXTRA_GROUPS in the non-root docs for the fallback"
-    fi
-}
-
-for glob in "${device_globs[@]}"; do
-    # shellcheck disable=SC2231
-    for node in $glob; do
-        grant "$node"
-    done
-done
-
-# USB devices re-enumerate (the Coral uploads firmware and reattaches as a new
-# node), so the directories also get a default ACL new nodes inherit. The
-# inherited grant is clamped by the creating mode's group bits, which is rw on
-# udev hosts (0664) and nothing on raw devtmpfs (0600); hardware-verified.
-if [[ -d /dev/bus/usb ]]; then
-    while IFS= read -r -d '' node; do
-        grant "$node"
-    done < <(find /dev/bus/usb -mindepth 1 -print0)
-    while IFS= read -r -d '' dir; do
-        setfacl -d -m "u:frigate:rw,u:go2rtc:rw" "$dir" 2>/dev/null || \
-            echo "[WARN] could not set a default ACL on ${dir}; a re-enumerating USB device may lose access"
-    done < <(find /dev/bus/usb -type d -print0)
-fi
-
-if [[ "$failed" -gt 0 ]]; then
-    echo "[INFO] device access: granted ${granted} node(s), ${failed} failed"
-elif [[ "$granted" -gt 0 ]]; then
-    echo "[INFO] device access: granted ${granted} node(s) to the runtime users"
-fi

docker/main/rootfs/etc/s6-overlay/s6-rc.d/init-devices/type

@@ -1 +0,0 @@
-oneshot

docker/main/rootfs/etc/s6-overlay/s6-rc.d/init-devices/up

@@ -1 +0,0 @@
-/etc/s6-overlay/s6-rc.d/init-devices/run

docker/main/rootfs/etc/s6-overlay/s6-rc.d/init-usermod/run

@@ -2,7 +2,7 @@
 # shellcheck shell=bash
 # Remap the frigate user to PUID/PGID and register EXTRA_GROUPS.
 # No-op when: started with --user (euid != 0), FRIGATE_RUN_AS_ROOT=true,
-# or PUID/PGID already match. FRIGATE_ROOT_SERVICES is validated here too.
+# or PUID/PGID already match.
 
 set -o errexit -o nounset -o pipefail
 
@@ -12,31 +12,10 @@ if [[ "$(id -u)" -ne 0 ]]; then
 fi
 
 if [[ "${FRIGATE_RUN_AS_ROOT:-false}" == "true" ]]; then
-    if [[ -n "${FRIGATE_ROOT_SERVICES:-}" ]]; then
-        echo "[INFO] FRIGATE_RUN_AS_ROOT=true: ignoring FRIGATE_ROOT_SERVICES"
-    fi
     echo "[INFO] FRIGATE_RUN_AS_ROOT=true: skipping user remapping"
     exit 0
 fi
 
-# a typo must fail the boot, not silently drop a service to non-root
-if [[ -n "${FRIGATE_ROOT_SERVICES:-}" ]]; then
-    IFS=',' read -ra root_services <<< "${FRIGATE_ROOT_SERVICES}"
-    for entry in "${root_services[@]}"; do
-        entry="${entry//[[:space:]]/}"
-        if [[ -z "$entry" ]]; then
-            continue
-        fi
-        case "$entry" in
-            frigate|go2rtc|nginx) ;;
-            *)
-                echo "[ERROR] FRIGATE_ROOT_SERVICES contains unknown service '${entry}'; valid names are frigate, go2rtc, nginx" >&2
-                exit 1
-                ;;
-        esac
-    done
-fi
-
 puid="${PUID:-1000}"
 pgid="${PGID:-1000}"
 
@@ -53,15 +32,6 @@ if [[ "$puid" -eq 0 || "$pgid" -eq 0 ]]; then
     exit 1
 fi
 
-# Colliding with the go2rtc ids would merge the two users and collapse the
-# separation between the main process and the network-facing restreamer.
-go2rtc_uid="$(id -u go2rtc)"
-go2rtc_gid="$(id -g go2rtc)"
-if [[ "$puid" -eq "$go2rtc_uid" || "$pgid" -eq "$go2rtc_gid" ]]; then
-    echo "[ERROR] PUID/PGID must not equal the go2rtc service ids (${go2rtc_uid}:${go2rtc_gid})." >&2
-    exit 1
-fi
-
 current_uid="$(id -u frigate)"
 current_gid="$(id -g frigate)"
 
@@ -79,20 +49,7 @@ fi
 
 # EXTRA_GROUPS: numeric host GIDs granting device access (e.g. host render/video)
 if [[ -n "${EXTRA_GROUPS:-}" ]]; then
-    # groupadd and usermod -aG both write /etc/group. Checked up front so a
-    # read-only rootfs reports the real problem instead of dying mid-loop.
-    if [[ ! -w /etc/group ]]; then
-        echo "[ERROR] EXTRA_GROUPS needs a writable /etc and is not compatible with read_only: true." >&2
-        echo "[ERROR] Use docker's group_add: with the same GIDs instead; it needs no writes inside the container." >&2
-        echo "[ERROR] See https://docs.frigate.video/configuration/non_root for the compatibility matrix." >&2
-        exit 1
-    fi
-
     for gid in ${EXTRA_GROUPS//,/ }; do
-        if ! [[ "$gid" =~ ^[0-9]+$ ]] || [[ "$gid" -eq 0 ]]; then
-            echo "[ERROR] EXTRA_GROUPS must be nonzero numeric GIDs, got '${gid}'" >&2
-            exit 1
-        fi
         if ! getent group "$gid" >/dev/null; then
             groupadd -o -g "$gid" "frigate-extra-${gid}"
         fi

docker/main/rootfs/etc/s6-overlay/s6-rc.d/nginx/data/check

@@ -2,4 +2,4 @@
 set -e
 
 # Wait for PID file to exist.
-while ! test -f /tmp/nginx/nginx.pid; do sleep 1; done
+while ! test -f /run/nginx.pid; do sleep 1; done

docker/main/rootfs/etc/s6-overlay/s6-rc.d/nginx/run

@@ -4,13 +4,6 @@
 
 set -o errexit -o nounset -o pipefail
 
-runs_as_root=0
-if [[ "$(id -u)" -eq 0 ]]; then
-    if [[ "${FRIGATE_RUN_AS_ROOT:-false}" == "true" ]] || /usr/local/bin/service-runs-as-root nginx; then
-        runs_as_root=1
-    fi
-fi
-
 # Logs should be sent to stdout so that s6 can collect them
 
 echo "[INFO] Starting NGINX..."
@@ -66,105 +59,43 @@ function set_worker_processes() {
         cpus=4
     fi
 
-    sed -i "s/worker_processes auto;/worker_processes ${cpus};/" /tmp/nginx/conf/nginx.conf
+    # we need to catch any errors because sed will fail if user has bind mounted a custom nginx file
+    sed -i "s/worker_processes auto;/worker_processes ${cpus};/" /usr/local/nginx/conf/nginx.conf || true
 }
 
-# Rebuilt root-owned every start: a symlink planted by the previously
-# unprivileged nginx would redirect the root cp/tempio writes below onto any
-# root file. rm does not traverse symlinks; the bare mkdir fails closed if raced.
-rm -rf /tmp/nginx
-mkdir /tmp/nginx
-mkdir -p /tmp/nginx/conf /tmp/nginx/client_body /tmp/nginx/proxy \
-         /tmp/nginx/fastcgi /tmp/nginx/uwsgi /tmp/nginx/scgi
-cp -r /usr/local/nginx/conf/. /tmp/nginx/conf/
-
 set_worker_processes
 
-# TLS certs: user-mounted certs at /etc/letsencrypt/live/frigate (documented
-# contract) always win; otherwise fall back to a self-signed cert persisted in
-# /config/tls, which stays writable under a read-only root filesystem.
+# ensure the directory for ACME challenges exists
+mkdir -p /etc/letsencrypt/www
+
+# Create self signed certs if needed
 letsencrypt_path=/etc/letsencrypt/live/frigate
-selfsigned_path=/config/tls
+mkdir -p $letsencrypt_path
 
-if [ -f "$letsencrypt_path/privkey.pem" ] && [ -f "$letsencrypt_path/fullchain.pem" ]; then
-    cert_path="$letsencrypt_path"
-else
-    cert_path="$selfsigned_path"
-
-    # Root writing into /config follows any symlink planted there, and /config
-    # is owned by whoever the host mount says, not by root. Generate as the
-    # runtime user wherever we are going to drop to it; the escape hatch keeps
-    # root all the way through, so that path is refused rather than dropped.
-    gen=()
-    if [[ "$(id -u)" -eq 0 && "${FRIGATE_RUN_AS_ROOT:-false}" != "true" ]]; then
-        gen=(s6-setuidgid frigate)
-    elif [[ "$(id -u)" -eq 0 ]]; then
-        for link in "$cert_path" "$cert_path/privkey.pem" "$cert_path/fullchain.pem"; do
-            if [[ -L "$link" ]]; then
-                echo "[ERROR] ${link} is a symlink; refusing to write TLS material through it as root" >&2
-                exit 1
-            fi
-        done
-    fi
-
-    "${gen[@]}" mkdir -p "$cert_path"
-
-    if [ ! \( -f "$cert_path/privkey.pem" -a -f "$cert_path/fullchain.pem" \) ]; then
-        echo "[INFO] No TLS certificate found. Generating a self signed certificate..."
-        "${gen[@]}" openssl req -new -newkey rsa:4096 -days 365 -nodes -x509 \
-            -subj "/O=FRIGATE DEFAULT CERT/CN=*" \
-            -keyout "$cert_path/privkey.pem" -out "$cert_path/fullchain.pem" 2>/dev/null
-        "${gen[@]}" chmod 600 "$cert_path/privkey.pem"
-        "${gen[@]}" chmod 644 "$cert_path/fullchain.pem"
-    fi
+if [ ! \( -f "$letsencrypt_path/privkey.pem" -a -f "$letsencrypt_path/fullchain.pem" \) ]; then
+    echo "[INFO] No TLS certificate found. Generating a self signed certificate..."
+    openssl req -new -newkey rsa:4096 -days 365 -nodes -x509 \
+        -subj "/O=FRIGATE DEFAULT CERT/CN=*" \
+        -keyout "$letsencrypt_path/privkey.pem" -out "$letsencrypt_path/fullchain.pem" 2>/dev/null
+    chmod 600 "$letsencrypt_path/privkey.pem"
+    chmod 644 "$letsencrypt_path/fullchain.pem"
 fi
 
-# ACME challenges are only served from a writable rootfs; skipping the mkdir
-# under read_only leaves the location 404ing, which is the same as unused
-mkdir -p /etc/letsencrypt/www 2>/dev/null || true
-
 # nginx settings are read once; both templates consume them
 nginx_settings=$(python3 /usr/local/nginx/get_nginx_settings.py)
 
 # build templates for optional FRIGATE_BASE_PATH environment variable
 echo "$nginx_settings" | \
     tempio -template /usr/local/nginx/templates/base_path.gotmpl \
-           -out /tmp/nginx/conf/base_path.conf
+           -out /usr/local/nginx/conf/base_path.conf
 
-# build templates for additional network settings; listen.conf is the only
-# template that needs the resolved cert directory
+# build templates for additional network settings
 echo "$nginx_settings" | \
-    jq --arg p "$cert_path" '.tls.cert_path = $p' | \
     tempio -template /usr/local/nginx/templates/listen.gotmpl \
-           -out /tmp/nginx/conf/listen.conf
-
-if [[ "$(id -u)" -eq 0 && "$runs_as_root" -eq 0 ]]; then
-    chown -R frigate:frigate /tmp/nginx
-    # heal the cache: a root `nginx -t` chowns every cycle path to the `user` directive user
-    if [ -d /dev/shm/nginx_cache ]; then
-        chown -R frigate:frigate /dev/shm/nginx_cache
-    fi
-    # nginx reopens /dev/stdout by path for its logs, and s6 made the pipe
-    # root-owned 0600; without this the non-root master exits EACCES
-    chown frigate /dev/stdout
-    # Only mounted certs need handing over; the self-signed pair is already
-    # owned by the runtime user that generated it. Never chown the /config copy:
-    # chown follows symlinks, so it would retarget onto any root file the
-    # runtime user pointed it at. Tolerant because mounted certs may be :ro.
-    if [ "$cert_path" = "$letsencrypt_path" ] && [ -f "$cert_path/privkey.pem" ]; then
-        chown frigate:frigate "$cert_path/privkey.pem" "$cert_path/fullchain.pem" 2>/dev/null || true
-    fi
-fi
+           -out /usr/local/nginx/conf/listen.conf
 
 # Replace the bash process with the NGINX process, redirecting stderr to stdout
 exec 2>&1
-# -e stderr: the compiled-in error log path is not writable by the runtime user
-if [[ "$(id -u)" -ne 0 || "$runs_as_root" -eq 1 ]]; then
-    exec \
-        s6-notifyoncheck -t 30000 -n 1 \
-        nginx -e stderr -c /tmp/nginx/conf/nginx.conf
-else
-    exec \
-        s6-notifyoncheck -t 30000 -n 1 \
-        s6-setuidgid frigate nginx -e stderr -c /tmp/nginx/conf/nginx.conf
-fi
+exec \
+    s6-notifyoncheck -t 30000 -n 1 \
+    nginx

docker/main/rootfs/etc/s6-overlay/s6-rc.d/prepare/run

@@ -153,57 +153,7 @@ if [[ "$(id -u)" -eq 0 ]]; then
     if [[ "${FRIGATE_RUN_AS_ROOT:-false}" == "true" ]]; then
         rm -f /config/.permissions_version
     else
-        # Only when a mount backs /media/frigate itself: under a parent /media
-        # mount, a dedicated volume added later would be shadowed and skipped
-        sentinel_args=(--sentinel /config/.permissions_version)
-        root_services_mode=""
-        if [[ -n "${FRIGATE_ROOT_SERVICES:-}" ]]; then
-            # || true: an all-empty list (",") fails grep -v and errexit would kill the boot
-            root_services_mode=$(tr ',' '\n' <<< "${FRIGATE_ROOT_SERVICES//[[:space:]]/}" | grep -v '^$' | sort -u | paste -sd, - || true)
-            if [[ -n "$root_services_mode" ]]; then
-                sentinel_args+=(--mode "$root_services_mode")
-            fi
-        fi
-        if ! awk '$2 == "/media/frigate" || $2 ~ /^\/media\/frigate\//' /proc/mounts | grep -q .; then
-            sentinel_args=()
-        fi
-        /usr/local/bin/fix-ownership "${sentinel_args[@]}" \
+        /usr/local/bin/fix-ownership --sentinel /config/.permissions_version \
             "${PUID:-1000}" "${PGID:-1000}" /config /media/frigate
-
-        # Root services write clips stragglers and caches mid-run; realign the
-        # small trees every boot. Recordings are chowned at create instead.
-        if [[ -n "$root_services_mode" ]]; then
-            # only sweep what exists; clips and exports appear after the first run
-            boot_sweep_paths=(/config)
-            for extra in /media/frigate/clips /media/frigate/exports; do
-                if [[ -d "$extra" ]]; then
-                    boot_sweep_paths+=("$extra")
-                fi
-            done
-            /usr/local/bin/fix-ownership \
-                "${PUID:-1000}" "${PGID:-1000}" "${boot_sweep_paths[@]}"
-        fi
     fi
 fi
-
-# Must stay after the sweep, which reads an absent /media/frigate as an
-# unmounted volume rather than a swept one
-if [[ "$(id -u)" -eq 0 && ! -d /media/frigate ]]; then
-    # The image does not ship this directory, so on a read-only rootfs it can
-    # only come from a mount. Report that rather than failing under errexit.
-    if ! mkdir -p /media/frigate 2>/dev/null; then
-        echo "[ERROR] /media/frigate does not exist and could not be created, which is what happens with read_only: true and no recordings volume." >&2
-        echo "[ERROR] Mount a volume at /media/frigate." >&2
-        echo "[ERROR] See https://docs.frigate.video/configuration/non_root for the compatibility matrix." >&2
-        exit 1
-    fi
-    if [[ "${FRIGATE_RUN_AS_ROOT:-false}" != "true" ]]; then
-        chown "${PUID:-1000}:${PGID:-1000}" /media/frigate
-    fi
-fi
-
-# usually a tmpfs mount: root-owned on arrival and outside the swept volumes
-if [[ "$(id -u)" -eq 0 && "${FRIGATE_RUN_AS_ROOT:-false}" != "true" ]]; then
-    mkdir -p /tmp/cache
-    chown "${PUID:-1000}:${PGID:-1000}" /tmp/cache
-fi

docker/main/rootfs/usr/local/bin/fix-ownership

@@ -1,17 +1,15 @@
 #!/bin/bash
 # Single source of truth for aligning volume ownership with the runtime user.
 #
-# Usage: fix-ownership [--dry-run] [--sentinel FILE] [--mode STRING] UID GID PATH [PATH...]
+# Usage: fix-ownership [--dry-run] [--sentinel FILE] UID GID PATH [PATH...]
 #
 #   --dry-run    report what would change, touch nothing
 #   --sentinel   skip entirely when FILE already records "SCHEMA:UID:GID";
 #                write it after a successful run (used by the boot path so
 #                multi-TB volumes are swept once per UID/schema change, not
 #                on every boot)
-#   --mode       append STRING to the sentinel, so changing it re-sweeps once
 #
 # Only files whose uid OR gid differs are touched, so re-runs are cheap.
-# lost+found is skipped: fsck fills it with root-only recovered fragments.
 # Top-level /config additionally grants group frigate-data TRAVERSE ONLY
 # (g+rx) so the separate go2rtc user can reach its pre-created HomeKit file
 # on hosts where /config is mounted 0700. Never g+w: directory write means
@@ -24,11 +22,10 @@ set -o errexit -o nounset -o pipefail
 # Permissions-layout epoch. Bump to force a one-time re-sweep on upgrade
 # (e.g. when the privilege-drop release must capture files created as root
 # since the previous sweep).
-schema=2
+schema=1
 
 dry_run=0
 sentinel=""
-mode=""
 
 while [[ "${1:-}" == --* ]]; do
     case "$1" in
@@ -39,18 +36,12 @@ while [[ "${1:-}" == --* ]]; do
                 exit 2
             fi
             sentinel="$2"; shift 2 ;;
-        --mode)
-            if [[ -z "${2:-}" ]]; then
-                echo "[ERROR] fix-ownership: --mode requires a value" >&2
-                exit 2
-            fi
-            mode="$2"; shift 2 ;;
         *) echo "[ERROR] fix-ownership: unknown option $1" >&2; exit 2 ;;
     esac
 done
 
 if [[ $# -lt 3 ]]; then
-    echo "Usage: fix-ownership [--dry-run] [--sentinel FILE] [--mode STRING] UID GID PATH..." >&2
+    echo "Usage: fix-ownership [--dry-run] [--sentinel FILE] UID GID PATH..." >&2
     exit 2
 fi
 
@@ -63,21 +54,11 @@ if [[ "$(id -u)" -ne 0 ]]; then
     exit 0
 fi
 
-# The list folds into the sentinel so entering or leaving a granular root mode
-# re-sweeps once, catching whatever the other ownership mechanisms missed.
-sentinel_content="${schema}:${target_uid}:${target_gid}"
-if [[ -n "$mode" ]]; then
-    sentinel_content="${sentinel_content}:${mode}"
-fi
-
-# safe-sentinel reports only a root-owned regular file, so a forged or
-# symlinked sentinel in the runtime-user-owned /config can't suppress the sweep
-if [[ "$dry_run" -eq 0 && -n "$sentinel" ]]; then
-    if existing=$(/usr/local/bin/safe-sentinel read "$sentinel" 2>/dev/null) && \
-        [[ "$existing" == "$sentinel_content" ]]; then
-        echo "[INFO] fix-ownership: ${target_uid}:${target_gid} (schema ${schema}) already applied, skipping"
-        exit 0
-    fi
+# A dry run always inspects: the sentinel records what a past sweep did, not
+# what the volume looks like now, and reporting from it would hide later drift.
+if [[ "$dry_run" -eq 0 && -n "$sentinel" && -f "$sentinel" && "$(cat "$sentinel")" == "${schema}:${target_uid}:${target_gid}" ]]; then
+    echo "[INFO] fix-ownership: ${target_uid}:${target_gid} (schema ${schema}) already applied, skipping"
+    exit 0
 fi
 
 # A sweep that could not chown everything must not be recorded as complete:
@@ -85,26 +66,6 @@ fi
 # unreachable once services run unprivileged.
 swept_clean=1
 
-# Entries another mechanism deliberately owns. Chowning them undoes that work
-# and leaves the same "mismatch" waiting for the next boot, so /config could
-# never report itself clean: /config is chgrp'd to frigate-data below so go2rtc
-# can traverse it, and the HomeKit file is handed to the go2rtc user by the
-# go2rtc service. Only the GROUP on /config is exempt; a root-owned /config
-# must still be chowned or the runtime user cannot write there at all.
-# Shared by the counting and the chowning walk so the two cannot disagree.
-mismatch_expr=(
-    "(" -not -uid "$target_uid"
-        -o "(" -not -gid "$target_gid" -a ! -path /config ")"
-    ")"
-    -a ! -path /config/go2rtc_homekit.yml
-)
-if [[ -n "$sentinel" ]]; then
-    # safe-sentinel keeps the sentinel root-owned on purpose and rejects one
-    # owned by anybody else, so chowning it here would suppress the skip and
-    # make every boot re-sweep. Only the trailing write puts it back today.
-    mismatch_expr+=(-a ! -path "$sentinel")
-fi
-
 for path in "$@"; do
     # An absent root is an incomplete sweep, not a finished one: /media/frigate
     # is not in the image, so a boot before the volume is mounted would
@@ -115,13 +76,11 @@ for path in "$@"; do
         continue
     fi
 
-    echo "[INFO] fix-ownership: scanning ${path} for ownership mismatches; this may take a while on large filesystems"
-
     # find may fail mid-walk on a live volume (file deleted under it) or on a
     # stale mount. Tolerate it rather than aborting under errexit, but never
     # read a failed scan as "nothing to do": that would record the sweep as
     # complete without having looked.
-    if ! count=$(find "$path" -name lost+found -prune -o "${mismatch_expr[@]}" -printf '.' 2>/dev/null | wc -c); then
+    if ! count=$(find "$path" \( -not -uid "$target_uid" -o -not -gid "$target_gid" \) -printf '.' 2>/dev/null | wc -c); then
         swept_clean=0
         echo "[WARN] fix-ownership: could not scan ${path}; will retry on next boot"
         continue
@@ -139,41 +98,17 @@ for path in "$@"; do
         echo "[WARN] fix-ownership: ${path} contains symlinked directories; ownership behind them is not managed and must be aligned by hand"
     fi
 
-    echo "[WARN] fix-ownership: adjusting ownership of ${count} entries under ${path}"
+    echo "[WARN] fix-ownership: adjusting ownership of ${count} entries under ${path}; on large recordings volumes this can take a long time"
     if [[ "$dry_run" -eq 1 ]]; then
         echo "[INFO] fix-ownership: dry run, not changing ${path}"
         continue
     fi
 
-    # -execdir chowns from the entry's own directory, so a parent swapped for a
-    # symlink mid-walk can't redirect the chown out of the volume
-    started=$SECONDS
-    if find "$path" -name lost+found -prune -o "${mismatch_expr[@]}" \
-        -print -execdir chown -h "${target_uid}:${target_gid}" {} + \
-        | awk -v total="$count" -v path="$path" '
-            BEGIN { next_pct = 5 }
-            {
-                pct = int(NR * 100 / total)
-                if (pct > 100) pct = 100
-                if (pct >= next_pct) {
-                    printf "[INFO] fix-ownership: %s %d%% (%d/%d entries)\n", path, pct, NR, total
-                    # mawk block-buffers to a pipe; without fflush the whole
-                    # progress log arrives at once
-                    fflush()
-                    while (next_pct <= pct) next_pct += 5
-                }
-            }'; then
-        elapsed=$((SECONDS - started))
-        if [[ "$elapsed" -ge 60 ]]; then
-            elapsed="$((elapsed / 60))m $((elapsed % 60))s"
-        else
-            elapsed="${elapsed}s"
-        fi
-        echo "[INFO] fix-ownership: finished ${path} in ${elapsed}"
-    else
+    find "$path" \( -not -uid "$target_uid" -o -not -gid "$target_gid" \) \
+        -exec chown -h "${target_uid}:${target_gid}" {} + || {
         swept_clean=0
         echo "[WARN] fix-ownership: some entries under ${path} could not be updated (deleted mid-sweep or chown denied); will retry on next mismatch"
-    fi
+    }
 done
 
 # go2rtc (separate user) must be able to REACH its HomeKit state in /config.
@@ -189,6 +124,6 @@ if [[ "$dry_run" -eq 0 && -d /config ]]; then
 fi
 
 if [[ "$dry_run" -eq 0 && -n "$sentinel" && "$swept_clean" -eq 1 ]]; then
-    /usr/local/bin/safe-sentinel write "$sentinel" "$sentinel_content" || \
+    echo "${schema}:${target_uid}:${target_gid}" > "$sentinel" || \
         echo "[WARN] fix-ownership: could not write ${sentinel}; the sweep will run again on next boot"
 fi

docker/main/rootfs/usr/local/bin/safe-sentinel

@@ -1,74 +0,0 @@
-#!/usr/bin/env python3
-"""Read or write the ownership sweep sentinel without following symlinks.
-
-The sentinel lives in /config, which the unprivileged runtime user owns, so it
-can be swapped for a symlink. read trusts only a root-owned regular file; write
-never follows a symlink or fifo onto another file.
-
-Usage:
-  safe-sentinel read PATH            print content, exit 0 only if root-owned regular file
-  safe-sentinel write PATH CONTENT   write CONTENT to a regular file at PATH
-"""
-
-import errno
-import os
-import stat
-import sys
-
-MODE = 0o644
-
-
-def do_read(path: str) -> int:
-    try:
-        fd = os.open(path, os.O_RDONLY | os.O_NOFOLLOW)
-    except OSError:
-        return 1
-    try:
-        st = os.fstat(fd)
-        if not stat.S_ISREG(st.st_mode) or st.st_uid != 0:
-            return 1
-        sys.stdout.buffer.write(os.read(fd, 4096))
-    finally:
-        os.close(fd)
-    return 0
-
-
-def do_write(path: str, content: str) -> int:
-    # O_NONBLOCK so a fifo fails fast (ENXIO) instead of blocking the open.
-    flags = os.O_WRONLY | os.O_CREAT | os.O_NOFOLLOW | os.O_NONBLOCK
-    replace = (errno.ELOOP, errno.ENXIO)
-    try:
-        fd = os.open(path, flags, MODE)
-        if not stat.S_ISREG(os.fstat(fd).st_mode):
-            os.close(fd)
-            raise OSError(errno.ELOOP, "not a regular file")
-    except OSError as err:
-        if err.errno not in replace:
-            raise
-        os.unlink(path)
-        fd = os.open(path, flags | os.O_EXCL, MODE)
-    try:
-        os.ftruncate(fd, 0)
-        os.write(fd, content.encode())
-        # keep it root-owned so a later sweep that chowned the old sentinel to
-        # the runtime user can't make the next read reject and re-sweep
-        os.fchown(fd, 0, 0)
-    finally:
-        os.close(fd)
-    return 0
-
-
-def main(argv: list[str]) -> int:
-    if len(argv) == 3 and argv[1] == "read":
-        return do_read(argv[2])
-    if len(argv) == 4 and argv[1] == "write":
-        try:
-            return do_write(argv[2], argv[3])
-        except OSError:
-            return 1
-    print("usage: safe-sentinel read PATH | write PATH CONTENT", file=sys.stderr)
-    return 2
-
-
-if __name__ == "__main__":
-    sys.exit(main(sys.argv))

docker/main/rootfs/usr/local/bin/service-runs-as-root

@@ -1,18 +0,0 @@
-#!/bin/bash
-# Exit 0 when FRIGATE_ROOT_SERVICES names the given service. Membership only:
-# the euid and FRIGATE_RUN_AS_ROOT checks stay in the callers.
-#
-# Usage: service-runs-as-root SERVICE
-
-set -o nounset
-
-service="${1:?usage: service-runs-as-root SERVICE}"
-
-IFS=',' read -ra entries <<< "${FRIGATE_ROOT_SERVICES:-}"
-for entry in "${entries[@]}"; do
-    entry="${entry//[[:space:]]/}"
-    if [[ "$entry" == "$service" ]]; then
-        exit 0
-    fi
-done
-exit 1

docker/main/rootfs/usr/local/go2rtc/prepare_homekit.py

@@ -1,107 +0,0 @@
-"""Normalize the go2rtc HomeKit file and hand it to go2rtc, as root.
-
-Runs before the drop. The file is in the runtime-user-owned /config, so a
-planted symlink could redirect the root write or chown onto another file;
-every operation goes through an O_NOFOLLOW fd to prevent that.
-
-Usage: prepare_homekit.py PATH [--chown]
-"""
-
-import errno
-import grp
-import io
-import os
-import pwd
-import stat
-import sys
-
-from ruamel.yaml import YAML
-
-RUNTIME_OWNER = "go2rtc"
-SHARED_GROUP = "frigate-data"
-MODE = 0o664
-MAX_BYTES = 10 * 1024 * 1024
-
-
-def open_nofollow(path: str) -> int:
-    """Return an fd to a regular file at path, never following a symlink."""
-    flags = os.O_RDWR | os.O_CREAT | os.O_NOFOLLOW
-    try:
-        fd = os.open(path, flags, MODE)
-    except OSError as err:
-        if err.errno != errno.ELOOP:
-            raise
-        os.unlink(path)
-        return os.open(path, flags | os.O_EXCL, MODE)
-
-    # A fifo or other non-regular file would hang or misbehave on read; replace it.
-    if not stat.S_ISREG(os.fstat(fd).st_mode):
-        os.close(fd)
-        os.unlink(path)
-        return os.open(path, flags | os.O_EXCL, MODE)
-    return fd
-
-
-def normalize(content: str) -> str:
-    """Keep only the homekit section, matching the previous yq/jq behavior."""
-    yaml = YAML(typ="safe")
-    try:
-        data = yaml.load(content)
-    except Exception:
-        return ""
-
-    if not isinstance(data, dict) or "homekit" not in data:
-        return ""
-
-    buf = io.StringIO()
-    yaml.dump({"homekit": data["homekit"]}, buf)
-    return buf.getvalue()
-
-
-def main() -> int:
-    if len(sys.argv) < 2:
-        print("[ERROR] prepare_homekit: PATH is required", file=sys.stderr)
-        return 2
-
-    path = sys.argv[1]
-    do_chown = "--chown" in sys.argv[2:]
-
-    try:
-        fd = open_nofollow(path)
-    except PermissionError:
-        print(
-            f"[WARN] {path} is not writable by uid {os.geteuid()}, so HomeKit "
-            "pairing changes will not persist. It is owned by the go2rtc user "
-            "from an earlier run in the default mode. To fix, on the host run: "
-            f"chown {os.geteuid()}:{os.getegid()} <your config dir>/{os.path.basename(path)}"
-        )
-        return 0
-
-    try:
-        content = os.read(fd, MAX_BYTES).decode("utf-8", "replace")
-        normalized = normalize(content)
-        os.ftruncate(fd, 0)
-        os.lseek(fd, 0, os.SEEK_SET)
-        os.write(fd, normalized.encode("utf-8"))
-
-        if do_chown:
-            # tolerate a chown-refusing mount (NFS root_squash): pairing
-            # persistence degrades, the service does not
-            try:
-                uid = pwd.getpwnam(RUNTIME_OWNER).pw_uid
-                gid = grp.getgrnam(SHARED_GROUP).gr_gid
-                os.fchown(fd, uid, gid)
-                os.fchmod(fd, MODE)
-            except (KeyError, OSError):
-                print(
-                    f"[WARN] Could not hand {path} to the go2rtc user; "
-                    "HomeKit pairing changes may not persist"
-                )
-    finally:
-        os.close(fd)
-
-    return 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())

docker/main/rootfs/usr/local/nginx/conf/nginx.conf

@@ -1,13 +1,9 @@
-# Loaded with -c from the /tmp/nginx/conf copy: relative includes follow the -c
-# file, all other path directives follow --prefix and must stay absolute.
-
 daemon off;
-# ignored by a non-root master; keeps workers root under FRIGATE_RUN_AS_ROOT
 user root;
 worker_processes auto;
 
 error_log /dev/stdout warn;
-pid /tmp/nginx/nginx.pid;
+pid /var/run/nginx.pid;
 
 events {
     worker_connections 1024;
@@ -17,12 +13,6 @@ http {
     map_hash_bucket_size 256;
     server_tokens off;
 
-    client_body_temp_path /tmp/nginx/client_body;
-    proxy_temp_path /tmp/nginx/proxy;
-    fastcgi_temp_path /tmp/nginx/fastcgi;
-    uwsgi_temp_path /tmp/nginx/uwsgi;
-    scgi_temp_path /tmp/nginx/scgi;
-
     include mime.types;
     default_type application/octet-stream;
 
@@ -132,10 +122,6 @@ http {
             # Smaller segments, faster generation, better browser compatibility
             vod_hls_container_format fmp4;
 
-            # 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;
-
             secure_token $args;
             secure_token_types application/vnd.apple.mpegurl;
 
@@ -144,6 +130,14 @@ http {
             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/ {
@@ -166,9 +160,7 @@ http {
             include auth_request.conf;
             types {
                 video/mp4 mp4;
-                image/jpeg jpg jpeg;
-                image/png png;
-                image/webp webp;
+                image/jpeg jpg;
             }
 
             expires 7d;
@@ -343,6 +335,13 @@ http {
                 add_header Cache-Control "public";
             }
 
+            location /fonts/ {
+                access_log off;
+                expires 1y;
+                include security_headers.conf;
+                add_header Cache-Control "public";
+            }
+
             location /locales/ {
                 access_log off;
                 include security_headers.conf;
@@ -369,7 +368,7 @@ http {
             sub_filter '"/BASE_PATH/assets/' '"$http_x_ingress_path/assets/';
             sub_filter '"/BASE_PATH/locales/' '"$http_x_ingress_path/locales/';
             sub_filter '"/BASE_PATH/monacoeditorwork/' '"$http_x_ingress_path/assets/';
-            sub_filter 'return`/BASE_PATH/`' 'return window.baseUrl';
+            sub_filter 'return"/BASE_PATH/"' 'return window.baseUrl';
             sub_filter '<body>' '<body><script>window.baseUrl="$http_x_ingress_path/";</script>';
             sub_filter_types text/css application/javascript;
             sub_filter_once off;

docker/main/rootfs/usr/local/nginx/templates/listen.gotmpl

@@ -8,8 +8,8 @@ listen {{ .listen.internal }};
     listen {{ .listen.external }} ssl;
     {{ if .ipv6.enabled }}listen [::]:{{ .listen.external_port }} ssl;{{ end }}
 
-    ssl_certificate {{ .tls.cert_path }}/fullchain.pem;
-    ssl_certificate_key {{ .tls.cert_path }}/privkey.pem;
+    ssl_certificate /etc/letsencrypt/live/frigate/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/frigate/privkey.pem;
 
     # generated 2024-06-01, Mozilla Guideline v5.7, nginx 1.25.3, OpenSSL 1.1.1w, modern configuration, no OCSP
     # https://ssl-config.mozilla.org/#server=nginx&version=1.25.3&config=modern&openssl=1.1.1w&ocsp=false&guideline=5.7

docker/migration/fix-permissions.sh

@@ -36,16 +36,6 @@ if ! [[ "$puid" =~ ^[0-9]+$ && "$pgid" =~ ^[0-9]+$ ]]; then
 fi
 
 echo "[INFO] Using image ${IMAGE} (override with FRIGATE_IMAGE=...)"
-if ! docker image inspect "${IMAGE}" >/dev/null 2>&1; then
-    echo "[INFO] ${IMAGE} is not present locally and has to be pulled first; this may take a while"
-fi
-
-if [[ -n "$dry_run_flag" ]]; then
-    echo "[INFO] Dry run: reporting what would change under ${config_dir} and ${media_dir}, changing nothing"
-else
-    echo "[INFO] Aligning ${config_dir} and ${media_dir} to ${puid}:${pgid}; this may take a while on large filesystems"
-fi
-
 # shellcheck disable=SC2086
 docker run --rm \
     -v "${config_dir}:/config" \

docker/rockchip/Dockerfile

@@ -25,7 +25,6 @@ RUN --mount=type=bind,from=rk-wheels,source=/rk-wheels,target=/deps/rk-wheels \
 
 WORKDIR /opt/frigate/
 COPY --from=rootfs / /
-ENV FRIGATE_IMAGE_VARIANT=rk
 COPY docker/rockchip/COCO /COCO
 COPY docker/rockchip/conv2rknn.py /opt/conv2rknn.py
 

docker/rocm/Dockerfile

@@ -44,7 +44,6 @@ RUN echo "deb http://deb.debian.org/debian trixie main" > /etc/apt/sources.list.
 
 WORKDIR /opt/frigate
 COPY --from=rootfs / /
-ENV FRIGATE_IMAGE_VARIANT=rocm
 
 RUN wget -q https://bootstrap.pypa.io/get-pip.py -O get-pip.py \
     && sed -i 's/args.append("setuptools")/args.append("setuptools==77.0.3")/' get-pip.py \

docker/rpi/Dockerfile

@@ -15,4 +15,3 @@ ENV INCLUDED_FFMPEG_VERSIONS="${DEFAULT_FFMPEG_VERSION}:${INCLUDED_FFMPEG_VERSIO
 
 WORKDIR /opt/frigate/
 COPY --from=rootfs / /
-ENV FRIGATE_IMAGE_VARIANT=rpi

docker/synaptics/Dockerfile

@@ -22,7 +22,6 @@ pip3 install --no-deps -U /deps/synap-wheels/*.whl
 
 WORKDIR /opt/frigate/
 COPY --from=rootfs / /
-ENV FRIGATE_IMAGE_VARIANT=synaptics
 
 COPY --from=synap1680-wheels /rootfs/usr/local/lib/*.so /usr/lib
 

docker/tensorrt/Dockerfile.amd64

@@ -25,7 +25,6 @@ RUN --mount=type=bind,from=trt-wheels,source=/trt-wheels,target=/deps/trt-wheels
     && pip3 install -U /deps/trt-wheels/*.whl
 
 COPY --from=rootfs / /
-ENV FRIGATE_IMAGE_VARIANT=tensorrt
 COPY docker/tensorrt/detector/rootfs/etc/ld.so.conf.d /etc/ld.so.conf.d
 RUN ldconfig
 

docker/tensorrt/Dockerfile.arm64

@@ -151,7 +151,6 @@ RUN --mount=type=bind,from=trt-wheels,source=/trt-wheels,target=/deps/trt-wheels
 
 WORKDIR /opt/frigate/
 COPY --from=rootfs / /
-ENV FRIGATE_IMAGE_VARIANT=tensorrt-jp6
 
 # Fixes "Error importing detector runtime: /usr/lib/aarch64-linux-gnu/libstdc++.so.6: cannot allocate memory in static TLS block"
 ENV LD_PRELOAD /usr/lib/aarch64-linux-gnu/libstdc++.so.6

docker/tensorrt/detector/rootfs/etc/s6-overlay/s6-rc.d/trt-model-prepare/run

@@ -13,16 +13,6 @@ TRT_VER=${TRT_VER:-$(cat /etc/TENSORRT_VER)}
 OUTPUT_FOLDER="${MODEL_CACHE_DIR}/${TRT_VER}"
 YOLO_MODELS=${YOLO_MODELS:-""}
 
-# This runs as root after prepare's sentinel-guarded sweep, so the dirs and
-# engines it creates below are the runtime user's to fix up, on every exit path
-function hand_off_ownership() {
-    if [[ "$(id -u)" -eq 0 && "${FRIGATE_RUN_AS_ROOT:-false}" != "true" ]]; then
-        /usr/local/bin/fix-ownership "${PUID:-1000}" "${PGID:-1000}" \
-            /config/model_cache "${MODEL_CACHE_DIR}"
-    fi
-}
-trap hand_off_ownership EXIT
-
 # Create output folder
 mkdir -p ${OUTPUT_FOLDER}
 

docker/tensorrt/requirements-amd64.txt

@@ -1,5 +1,6 @@
 # Nvidia ONNX Runtime GPU Support
 --extra-index-url 'https://pypi.nvidia.com'
+cython==3.0.*; platform_machine == 'x86_64'
 nvidia-cuda-cupti-cu12==12.8.90; platform_machine == 'x86_64'
 nvidia-cublas-cu12==12.8.4.1; platform_machine == 'x86_64'
 nvidia-cudnn-cu12==9.8.0.87; platform_machine == 'x86_64'

docs/data/object_detectors_models.yaml

@@ -36,13 +36,13 @@ edgeTPU:
             height: 320 # <--- should match the imgsize of the model, typically 320
             path: /config/model_cache/yolov9-s-relu6-best_320_int8_edgetpu.tflite
             labelmap_path: /config/labels-coco17.txt
-hailo:
-  title: Hailo
+hailo8l:
+  title: Hailo-8/Hailo-8L
   models:
     - key: yolo
       label: YOLO
       recommended: true
-      download: If no custom model path or URL is provided, the Hailo detector automatically downloads the default model (YOLOv6n) from the Hailo Model Zoo on first startup, choosing the build that matches the attached device. Once cached under `/config/model_cache`, the model works fully offline.
+      download: If no custom model path or URL is provided, the Hailo detector automatically downloads the default model (YOLOv6n) from the Hailo Model Zoo on first startup based on the detected hardware. Once cached under `/config/model_cache/hailo`, the model works fully offline.
       ui: |-
         Navigate to **Settings > System > Detection models** and select **Hailo** from the **Hardware** dropdown. Then, on the same model, open the **Custom Model** tab and configure the model settings:
 
@@ -60,7 +60,7 @@ hailo:
       yaml: |-
         models:
           - devices:
-              - hailo:PCIe
+              - hailo8l:PCIe
             width: 320
             height: 320
             input_tensor: nhwc
@@ -101,7 +101,7 @@ hailo:
       yaml: |-
         models:
           - devices:
-              - hailo:PCIe
+              - hailo8l:PCIe
             width: 300
             height: 300
             input_tensor: nhwc
@@ -824,6 +824,24 @@ cpu:
         models:
           - devices:
               - cpu:3
+deepstack:
+  title: DeepStack / CodeProject.AI
+  models:
+    - key: yolo
+      label: YOLO
+      recommended: true
+      download: This detector runs object detection over the network against a CodeProject.AI or DeepStack server, so no model is downloaded into Frigate itself. Visit the [CodeProject.AI official website](https://www.codeproject.com/Articles/5322557/CodeProject-AI-Server-AI-the-easy-way) to download and install the AI server on your preferred device (e.g. Raspberry Pi, Nvidia Jetson, or other compatible hardware) before configuring the detector.
+      ui: |-
+        Navigate to **Settings > System > Detection models** and add a model. The CodeProject.AI server is not reported by the hardware probe, so set `devices` to `deepstack:http://<your_codeproject_ai_server_ip>:<port>/v1/vision/detection` in YAML.
+
+        | Field         | Value                                                                  |
+        | ------------- | ---------------------------------------------------------------------- |
+        | **API URL**   | `http://<your_codeproject_ai_server_ip>:<port>/v1/vision/detection`    |
+        | **API Timeout** | `0.1` (seconds)                                                      |
+      yaml: |-
+        models:
+          - devices:
+              - deepstack:http://<your_codeproject_ai_server_ip>:<port>/v1/vision/detection
 memryx:
   title: MemryX
   models:
@@ -967,65 +985,6 @@ memryx:
             # The .zip file must contain:
             # ├── ssdlite_mobilenet.dfp          (a file ending with .dfp)
             # └── ssdlite_mobilenet_post.onnx    (optional; only if the model includes a cropped post-processing network)
-deepx:
-  title: DEEPX NPU
-  models:
-    - key: yolo
-      label: YOLO
-      recommended: true
-      download: No model is bundled with Frigate. Download a pre-compiled YOLO `.dxnn` model from the [DEEPX ModelZoo](https://developer.deepx.ai/modelzoo) or compile your own with DX-COM, then bind-mount it into the container and point the model's `path` at it. The recommended model is `yolox-s_640x640_ppu.dxnn`. Its Post-Processing Unit (PPU) compile moves candidate selection onto the NPU, which makes it the fastest ModelZoo model measured through Frigate (about 13 ms on a DX-M1). The output layout is read from the compiled model, so anchor-based, anchor-free, NMS-in-head and PPU models (anchor-based or anchor-free) all need no extra configuration; prefer a `PPU` variant whenever the ModelZoo offers one. PPU models must be compiled with DX-COM 2.4.0 or later, which writes the head layout Frigate reads into the file.
-      ui: |-
-        Navigate to **Settings > System > Detection models** and select **DEEPX NPU** from the **Hardware** dropdown. Then, on the same model, open the **Custom Model** tab and configure:
-
-        | Field                                    | Value                                                |
-        | ---------------------------------------- | ---------------------------------------------------- |
-        | **Custom object detector model path**    | `/config/model_cache/deepx/yolox-s_640x640_ppu.dxnn` |
-        | **Label map for custom object detector** | `/labelmap/coco-80.txt`                              |
-        | **Object detection model input width**   | `640`                                                |
-        | **Object detection model input height**  | `640`                                                |
-        | **Model Input Pixel Color Format**       | `rgb` (Frigate's default value)                      |
-        | **Model Input Tensor Shape**             | `nhwc` (Frigate's default value)                     |
-        | **Model Input D Type**                   | `int` (Frigate's default value)                      |
-        | **Object Detection Model Type**          | `yolo-generic`                                       |
-
-        Quantization is baked into the compiled model, so no normalization is applied on the host and the input defaults do not need to be overridden.
-      yaml: |-
-        models:
-          - devices:
-              - deepx:PCIe:0
-            path: /config/model_cache/deepx/yolox-s_640x640_ppu.dxnn
-            labelmap_path: /labelmap/coco-80.txt
-            model_type: yolo-generic
-            width: 640
-            height: 640
-    - key: yolox
-      label: YOLOX
-      recommended: false
-      download: No model is bundled with Frigate. Download a pre-compiled YOLOX `.dxnn` model from the [DEEPX ModelZoo](https://developer.deepx.ai/modelzoo), then bind-mount it into the container and point the model's `path` at it. The `_ppu` variant is faster and also works with the `yolo-generic` model type; the plain export needs `yolox` so its raw head is decoded.
-      ui: |-
-        Navigate to **Settings > System > Detection models** and select **DEEPX NPU** from the **Hardware** dropdown. Then, on the same model, open the **Custom Model** tab and configure:
-
-        | Field                                    | Value                                    |
-        | ---------------------------------------- | ---------------------------------------- |
-        | **Custom object detector model path**    | `/config/model_cache/deepx/yolox-s_640x640.dxnn`|
-        | **Label map for custom object detector** | `/labelmap/coco-80.txt`                  |
-        | **Object detection model input width**   | `640`                                    |
-        | **Object detection model input height**  | `640`                                    |
-        | **Model Input Pixel Color Format**       | `rgb` (Frigate's default value)          |
-        | **Model Input Tensor Shape**             | `nhwc` (Frigate's default value)         |
-        | **Model Input D Type**                   | `int` (Frigate's default value)          |
-        | **Object Detection Model Type**          | `yolox`                                  |
-
-        The width and height must match the resolution the `.dxnn` file was compiled for.
-      yaml: |-
-        models:
-          - devices:
-              - deepx:PCIe:0
-            path: /config/model_cache/deepx/yolox-s_640x640.dxnn
-            labelmap_path: /labelmap/coco-80.txt
-            model_type: yolox
-            width: 640
-            height: 640
 tensorrt:
   title: TensorRT
   models:
@@ -1074,7 +1033,7 @@ synaptics:
     - key: ssd
       label: SSD MobileNet
       recommended: true
-      download: A synap model is provided in the container at `/synaptics/mobilenet.synap` and is used by this detector type by default. The model comes from the [Synap-release Github](https://github.com/synaptics-astra/synap-release/tree/v1.5.0/models/dolphin/object_detection/coco/model/mobilenet224_full80).
+      download: A synap model is provided in the container at `/mobilenet.synap` and is used by this detector type by default. The model comes from the [Synap-release Github](https://github.com/synaptics-astra/synap-release/tree/v1.5.0/models/dolphin/object_detection/coco/model/mobilenet224_full80).
       ui: |-
         Navigate to **Settings > System > Detection models** and select **Synaptics NPU** from the **Hardware** dropdown. Then, on the same model, open the **Custom Model** tab and configure:
 

docs/docs/configuration/advanced/analytics.md

@@ -1,41 +0,0 @@
----
-id: analytics
-title: Anonymous Analytics
----
-
-import AnalyticsFields from "@site/src/components/AnalyticsFields";
-import NavPath from "@site/src/components/NavPath";
-
-Frigate can send one anonymous usage report a day. The reports show the maintainers which hardware to support, which features people use, and how releases perform. Sharing is off until you turn it on.
-
-## Turning it on
-
-Enable **Share anonymous analytics** at <NavPath path="Settings > System > Telemetry" />, or set it in your config:
-
-```yaml
-telemetry:
-  analytics: true
-```
-
-The same page has a **Preview the report** button that shows exactly what the next report contains.
-
-## How it's sent
-
-- Once a day, as a JSON POST to `https://analytics.frigate.video/report`
-- The server looks up your country and region from your IP address and never stores the address
-- Raw reports are kept for 60 days; only aggregate totals are published
-- A random install ID, stored in `/config/.analytics.json`, keeps your install from being counted twice. Turning sharing off deletes it
-
-## What's never sent
-
-- Camera, zone, group, profile, or user names
-- Object labels, face names, or license plate text
-- IP addresses, hostnames, URLs, or stream paths
-- Credentials or API keys
-- Events, recordings, or anything from them
-
-## Every field
-
-Fields marked public appear in the published totals. The machine-readable schema is [frigate-analytics-schema.json](pathname:///frigate-analytics-schema.json).
-
-<AnalyticsFields />

docs/docs/configuration/advanced/reference.md

@@ -496,11 +496,6 @@ review:
       - Animals in the garden
     # Optional: Preferred response language (default: English)
     preferred_language: English
-    # Optional: Writing style preset for generated descriptions (default: shown below)
-    # Options: "default", "natural", "concise", "detailed"
-    # Presets adjust the tone and level of detail of the user-facing title,
-    # summary, and scene description; "default" leaves the built-in prompt unchanged.
-    response_style: default
     # Optional: Save thumbnails sent to the GenAI provider for review/debugging purposes (default: shown below)
     debug_save_thumbnails: False
 
@@ -800,7 +795,7 @@ lpr:
 # to Google or OpenAI's LLMs to generate descriptions. GenAI features can be configured at
 # the camera level to enhance privacy for indoor cameras.
 # NOTE: genai is a map of named providers. Each key is a name you choose for the provider,
-#       and each role (chat, descriptions, embeddings, transcribe) may be assigned to exactly one provider.
+#       and each role (chat, descriptions, embeddings) may be assigned to exactly one provider.
 genai:
   # Required: name of the provider (chosen by you, used to reference it elsewhere)
   my_provider:
@@ -813,13 +808,11 @@ genai:
     # Required: The model to use with the provider.
     model: gemini-1.5-flash
     # Optional: Roles this provider handles (default: shown below)
-    # Each role (chat, descriptions, embeddings, transcribe) must be assigned to exactly
-    # one provider.
+    # Each role (chat, descriptions, embeddings) must be assigned to exactly one provider.
     roles:
       - chat
       - descriptions
       - embeddings
-      - transcribe
     # Optional additional args to pass to the GenAI Provider (default: None)
     provider_options:
       keep_alive: -1
@@ -832,19 +825,13 @@ genai:
 audio_transcription:
   # Optional: Enable live and speech event audio transcription (default: shown below)
   enabled: False
-  # Optional: The transcription backend (default: shown below)
-  # Either 'whisper' for Frigate's built-in local models, or the name of a genai
-  # provider that has 'transcribe' in its roles. device and model_size are ignored
-  # when a genai provider is named.
-  model: whisper
   # Optional: The device to run the models on for live transcription. (default: shown below)
   device: CPU
   # Optional: Set the model size used for live transcription. (default: shown below)
   model_size: small
   # Optional: Set the language used for transcription translation. (default: shown below)
-  # Use 'auto' to let the model detect the language, or a language code from
-  # https://github.com/openai/whisper/blob/main/whisper/tokenizer.py#L10
-  language: auto
+  # List of language codes: https://github.com/openai/whisper/blob/main/whisper/tokenizer.py#L10
+  language: en
 
 # Optional: Configuration for classification models
 classification:
@@ -1194,9 +1181,6 @@ ui:
 
 # Optional: Telemetry configuration
 telemetry:
-  # Optional: Share one anonymous usage report a day (default: shown below)
-  # NOTE: See https://docs.frigate.video/configuration/advanced/analytics for what is sent
-  analytics: False
   # Optional: Enabled network interfaces for bandwidth stats monitoring (default: empty list, let nethogs search all)
   network_interfaces:
     - eth

docs/docs/configuration/advanced/system.md

@@ -397,10 +397,6 @@ To do this:
 2. Update the `ffmpeg.path` in your Frigate config to `/config/custom-ffmpeg`.
 3. Restart Frigate and the custom version will be used if the steps above were done correctly.
 
-Both binaries have to be executable by Frigate's unprivileged runtime user, so `chmod 755` them after extracting. The startup ownership sweep runs only once, so anything you add to `/config` later keeps whatever ownership and mode you gave it.
-
-There is one exception, and it only affects [`FRIGATE_ROOT_SERVICES`](/configuration/non_root#keeping-individual-services-root) listing `frigate`. That mode runs Frigate as root while still handing `/config` to the unprivileged runtime user, so anything running as that user could swap the binary and gain root. A build inside any of Frigate's writable volumes (`/config`, `/media/frigate`, the cache and shm dirs) is ignored there and the bundled one is used, with a warning in the log. Keep the build somewhere root-owned (any absolute `ffmpeg.path` works, so a read-only bind mount such as `/opt/custom-ffmpeg` is enough) if you need both. The default mode and `FRIGATE_RUN_AS_ROOT=true` are unaffected and behave exactly as they always have.
-
 ### Custom go2rtc version
 
 Frigate currently includes go2rtc v1.9.14, there may be certain cases where you want to run a different version of go2rtc.
@@ -409,11 +405,9 @@ To do this:
 
 1. Download the go2rtc build to the `/config` folder.
 2. Rename the build to `go2rtc`.
-3. Give `go2rtc` execute permission for all users (`chmod 755`). It runs as its own `go2rtc` user, which doesn't own the file, so owner-only execute permission isn't enough.
+3. Give `go2rtc` execute permission.
 4. Restart Frigate and the custom version will be used, you can verify by checking go2rtc logs.
 
-The same exception applies, and again only to [`FRIGATE_ROOT_SERVICES`](/configuration/non_root#keeping-individual-services-root) listing `go2rtc`: the binary is ignored there and the embedded one is used, with a warning in the log. Unlike `ffmpeg.path`, the go2rtc binary location is not configurable, so there is no outside-`/config` alternative. Use `FRIGATE_RUN_AS_ROOT=true` instead if you need both a custom go2rtc build and root. The default mode and the escape hatch both honor `/config/go2rtc` exactly as they always have.
-
 ## Validating your config.yml file updates
 
 When frigate starts up, it checks whether your config file is valid, and if it is not, the process exits. To minimize interruptions when updating your config, you have three options -- you can edit the config via the WebUI which has built in validation, use the config API, or you can validate on the command line using the frigate docker container.

docs/docs/configuration/audio_detectors.md

@@ -204,7 +204,7 @@ Frequently-heard labels like `speech` can generate a lot of events, and each eve
 
 ### Audio Transcription
 
-Frigate supports fully local audio transcription using either `sherpa-onnx` or OpenAI's open-source Whisper models via `faster-whisper`, and can alternatively offload transcription to a [GenAI provider](#genai-provider). The goal of this feature is to support Semantic Search for `speech` audio events. Frigate is not intended to act as a continuous, fully-automatic speech transcription service. Automatically transcribing all speech (or queuing many audio events for transcription) requires substantial CPU (or GPU) resources and is impractical on most systems. For this reason, transcriptions for events are initiated manually from the UI or the API rather than being run continuously in the background.
+Frigate supports fully local audio transcription using either `sherpa-onnx` or OpenAI's open-source Whisper models via `faster-whisper`. The goal of this feature is to support Semantic Search for `speech` audio events. Frigate is not intended to act as a continuous, fully-automatic speech transcription service. Automatically transcribing all speech (or queuing many audio events for transcription) requires substantial CPU (or GPU) resources and is impractical on most systems. For this reason, transcriptions for events are initiated manually from the UI or the API rather than being run continuously in the background.
 
 :::info
 
@@ -224,7 +224,6 @@ To enable transcription, configure it globally and optionally disable for specif
 **Global:** Navigate to <NavPath path="Settings > Enrichments > Audio transcription" />.
 
 - Set **Enable audio transcription** to on
-- Set **Audio transcription model or GenAI provider name** to `whisper` for Frigate's built-in local models, or to the name of a GenAI provider
 - Set **Transcription device** to the desired device
 - Set **Model size** to the desired size
 
@@ -236,7 +235,6 @@ To enable transcription, configure it globally and optionally disable for specif
 ```yaml
 audio_transcription:
   enabled: True
-  model: whisper
   device: ...
   model_size: ...
 ```
@@ -265,88 +263,20 @@ The optional config parameters that can be set at the global level include:
 - **`enabled`**: Enable or disable the audio transcription feature.
   - Default: `False`
   - It is recommended to only configure the features at the global level, and enable it at the individual camera level.
-- **`model`**: The transcription backend.
-  - Default: `whisper`
-  - `whisper` uses Frigate's built-in local models, described by `device` and `model_size` below.
-  - Any other value must name a key in your `genai` config whose entry has `transcribe` in its `roles`. See [GenAI Provider](#genai-provider).
 - **`device`**: Device to use to run transcription and translation models.
   - Default: `CPU`
   - This can be `CPU` or `GPU`. The `sherpa-onnx` models are lightweight and run on the CPU only. The `whisper` models can run on GPU but are only supported on CUDA hardware.
-  - Ignored when `model` names a GenAI provider.
 - **`model_size`**: The size of the model used for live transcription.
   - Default: `small`
   - This can be `small` or `large`. The `small` setting uses `sherpa-onnx` models that are fast, lightweight, and always run on the CPU but are not as accurate as the `whisper` model.
-  - This config option applies to **live transcription only**. With `model: whisper`, recorded `speech` events always use a different `whisper` model (and can be accelerated for CUDA hardware if available with `device: GPU`).
-  - Ignored when `model` names a GenAI provider.
-- **`language`**: Defines the language used to transcribe and translate `speech` audio events (and live audio only if using the `large` model or a GenAI provider).
-  - Default: `auto`
-  - `auto` lets the model detect the language itself, which most models do well. Set an explicit language only if detection is picking the wrong one.
-  - Otherwise you must use a valid [language code](https://github.com/openai/whisper/blob/main/whisper/tokenizer.py#L10).
+  - This config option applies to **live transcription only**. Recorded `speech` events will always use a different `whisper` model (and can be accelerated for CUDA hardware if available with `device: GPU`).
+- **`language`**: Defines the language used by `whisper` to translate `speech` audio events (and live audio only if using the `large` model).
+  - Default: `en`
+  - You must use a valid [language code](https://github.com/openai/whisper/blob/main/whisper/tokenizer.py#L10).
   - Transcriptions for `speech` events are translated.
   - Live audio is translated only if you are using the `large` model. The `small` `sherpa-onnx` model is English-only.
 
-The only field that is valid at the camera level is `enabled`. In particular `model` is global only: the transcription backend is a process-wide resource shared by every camera.
-
-#### GenAI Provider
-
-Frigate can send audio to a GenAI provider for transcription when that provider has the `transcribe` role. This is useful if you already run a GenAI provider, or if you do not have the CPU/GPU headroom for a local whisper model. Supported providers are **OpenAI**, **Azure OpenAI**, **Gemini**, and **llama.cpp** with an audio-capable model (a dedicated ASR model such as Qwen3-ASR, or a general multimodal model that accepts audio). Ollama is not supported as it has no audio input.
-
-To use a GenAI provider for audio transcription:
-
-1. Configure a GenAI provider with `transcribe` in its `roles`.
-2. Set the audio transcription model to that GenAI config key (e.g. `whisper_cloud`).
-
-<ConfigTabs>
-<TabItem value="ui">
-
-Navigate to <NavPath path="Settings > Enrichments > Audio transcription" />.
-
-| Field                                                | Description                                                                                              |
-| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
-| **Audio transcription model or GenAI provider name** | Set to the GenAI config key (e.g. `whisper_cloud`) to use a configured GenAI provider for transcription |
-
-The GenAI provider must also be configured with the `transcribe` role under <NavPath path="Settings > Enrichments > Generative AI" />.
-
-</TabItem>
-<TabItem value="yaml">
-
-```yaml
-genai:
-  whisper_cloud:
-    provider: openai
-    api_key: your-api-key
-    model: gpt-transcribe
-    roles:
-      - transcribe
-
-audio_transcription:
-  enabled: True
-  model: whisper_cloud
-  language: en
-```
-
-</TabItem>
-</ConfigTabs>
-
-:::warning
-
-**Give `transcribe` its own `genai` entry.** A `genai` entry has a single `model` string that is shared by every role it holds, so `roles: [descriptions, transcribe]` would send the same model name to both the chat endpoint and the transcription endpoint. Transcription models and chat models are almost never the same model, so define a dedicated entry as shown above.
-
-:::
-
-:::warning
-
-**Live transcription against a metered provider is billed continuously.** In live mode Frigate uploads an overlapping ~2 second window of audio roughly once per second, per camera, for as long as audio stays above that camera's `audio.min_volume`. Windows below that threshold are never uploaded, which is what keeps a quiet camera near zero requests, but a camera pointed at a busy street will keep sending.
-
-Three things keep this opt-in: `transcribe` is not one of the default roles, live transcription is off by default, and the volume gate suppresses silence. Transcription of recorded `speech` events is unaffected - it remains a manual, one-request-per-event action.
-
-:::
-
-`device` and `model_size` have no effect on this path and no local model is ever downloaded.
-
-`language` defaults to `auto`, which sends no language hint and lets the model detect it. Most audio models detect language well, so leave it on `auto` unless detection is picking the wrong one.
-
-When set explicitly, it is sent as the transcription endpoint's native `language` parameter for OpenAI, Azure, and llama.cpp, and as part of the prompt for Gemini. This matters for dedicated ASR models such as Qwen3-ASR: they read the prompt as contextual biasing rather than as an instruction, so a language named in the prompt is ignored, while the endpoint parameter is honored.
+The only field that is valid at the camera level is `enabled`.
 
 #### Live transcription
 
@@ -362,8 +292,6 @@ Results can be error-prone due to a number of factors, including:
 
 For speech sources close to the camera with minimal background noise, use the `small` model.
 
-A [GenAI provider](#genai-provider) is generally the most accurate option for live transcription, at the cost of a network round trip per window. That round trip has to stay under about a second to keep up with the audio; if it does not, Frigate drops the oldest buffered audio rather than letting the backlog grow.
-
 If you have CUDA hardware, you can experiment with the `large` `whisper` model on GPU. Performance is not quite as fast as the `sherpa-onnx` `small` model, but live transcription is far more accurate. Using the `large` model with CPU will likely be too slow for real-time transcription.
 
 #### Transcription and translation of `speech` audio events
@@ -380,7 +308,7 @@ Only one `speech` event may be transcribed at a time. Frigate does not automatic
 
 :::
 
-With `model: whisper`, recorded `speech` events always use a `whisper` model, regardless of the `model_size` config setting. Without a supported Nvidia GPU, generating transcriptions for longer `speech` events may take a fair amount of time, so be patient. With a [GenAI provider](#genai-provider), the recorded clip is sent to the provider instead and no local model is used.
+Recorded `speech` events will always use a `whisper` model, regardless of the `model_size` config setting. Without a supported Nvidia GPU, generating transcriptions for longer `speech` events may take a fair amount of time, so be patient.
 
 #### FAQ
 

docs/docs/configuration/authentication.md

@@ -22,9 +22,7 @@ The following ports are available to access the Frigate web UI.
 
 ## Onboarding
 
-On startup, an admin user and password are generated and printed in the logs. It is recommended to set a new password for the admin account after logging in for the first time.
-
-On a new install the [setup wizard](../guides/getting_started.md#configuring-frigate) offers this as its first step, along with creating accounts for anyone else who needs access. You can also do both at any time under <NavPath path="Settings > Users" />.
+On startup, an admin user and password are generated and printed in the logs. It is recommended to set a new password for the admin account after logging in for the first time under Settings > Users.
 
 ## Resetting admin password
 
@@ -216,9 +214,9 @@ A default role can be provided. Any value in the mapped `role` header will overr
 
 Navigate to <NavPath path="Settings > System > Proxy" /> and set the default role.
 
-| Field            | Description                                                                                          |
-| ---------------- | ---------------------------------------------------------------------------------------------------- |
-| **Default role** | Fallback role when no role header is present (e.g., `viewer`), or `None (deny access)` to reject unmapped users |
+| Field            | Description                                                   |
+| ---------------- | ------------------------------------------------------------- |
+| **Default role** | Fallback role when no role header is present (e.g., `viewer`) |
 
 </TabItem>
 <TabItem value="yaml">
@@ -232,14 +230,6 @@ proxy:
 </TabItem>
 </ConfigTabs>
 
-Setting `default_role` to `none` denies access instead of falling back to a role. Any proxy-authenticated user whose headers do not match an explicit `role_map` entry receives a 403 response. This is useful when the upstream proxy authenticates a broader set of users than should reach Frigate, so that only mapped groups are allowed in.
-
-```yaml
-proxy:
-  ...
-  default_role: none
-```
-
 ## Role mapping
 
 In some environments, upstream identity providers (OIDC, SAML, LDAP, etc.) do not pass a Frigate-compatible role directly, but instead pass one or more group claims. To handle this, Frigate supports a `role_map` that translates upstream group names into Frigate's internal roles (`admin`, `viewer`, or custom). This is configurable via YAML in the configuration file:
@@ -265,7 +255,7 @@ In this example:
 - If the proxy passes a role header containing `sysadmins` or `access-level-security`, the user is assigned the `admin` role.
 - If the proxy passes a role header containing `camera-viewer`, the user is assigned the `viewer` role.
 - If the proxy passes a role header containing `operators`, the user is assigned the `operator` custom role.
-- If no mapping matches, Frigate falls back to `default_role` if configured, or denies access if `default_role` is `none`.
+- If no mapping matches, Frigate falls back to `default_role` if configured.
 - If `role_map` is not defined, Frigate assumes the role header directly contains `admin`, `viewer`, or a custom role name.
 
 **Note on matching semantics:**
@@ -339,7 +329,7 @@ Frigate supports user roles to control access to certain features in the UI and
 
 - **admin**: Full access to all features, including user management and configuration.
 - **viewer**: Read-only access to the UI and API, including viewing cameras, review items, and historical footage. Configuration editor and settings in the UI are inaccessible.
-- **Custom Roles**: Arbitrary role names (alphanumeric, dots/underscores) with specific camera permissions. These extend the system for granular access (e.g., "operator" for select cameras). The names `admin`, `viewer`, and `none` are reserved and cannot be used.
+- **Custom Roles**: Arbitrary role names (alphanumeric, dots/underscores) with specific camera permissions. These extend the system for granular access (e.g., "operator" for select cameras).
 
 ### Custom Roles and Camera Access
 

docs/docs/configuration/cameras.md

@@ -9,7 +9,7 @@ import NavPath from "@site/src/components/NavPath";
 
 ## Adding a camera with the Add Camera Wizard
 
-The Add Camera Wizard is the recommended way to add a camera. Click **Add Camera** in <NavPath path="Settings > Global configuration > Camera management" />, or use it from the [setup wizard](../guides/getting_started.md#configuring-frigate) on a new install. The wizard connects to your camera, tests each stream, and writes the camera's configuration for you, including the [go2rtc](go2rtc.md) restream and the live view stream mapping, so a standard setup needs no hand-written YAML.
+The Add Camera Wizard is the recommended way to add a camera. Click **Add Camera** in <NavPath path="Settings > Global configuration > Camera management" />. The wizard connects to your camera, tests each stream, and writes the camera's configuration for you, including the [go2rtc](go2rtc.md) restream and the live view stream mapping, so a standard setup needs no hand-written YAML.
 
 ### Step 1: Name and connection
 

docs/docs/configuration/genai/config.md

@@ -43,7 +43,7 @@ genai:
 
 The examples on this page all use `my_provider`, but the name is arbitrary and is only used to reference the provider elsewhere in the config (for example, `semantic_search.model`).
 
-Each provider handles one or more **roles**: `chat`, `descriptions`, `embeddings`, and `transcribe`. A provider handles the first three by default; `transcribe` must always be listed explicitly, and is not available on Ollama, which has no audio input. Each role may be assigned to exactly one provider. Define a single provider if you want it to do everything, or split the roles across several providers using the `roles` option.
+Each provider handles one or more **roles**: `chat`, `descriptions`, and `embeddings`. A provider handles all three by default, and each role may be assigned to exactly one provider. Define a single provider if you want it to do everything, or split the roles across several providers using the `roles` option.
 
 If the provider you choose requires an API key, you may either directly paste it in your configuration, or store it in an environment variable prefixed with `FRIGATE_`.
 
@@ -63,11 +63,11 @@ Running Generative AI models on CPU is not recommended, as high inference times
 
 You must use a vision-capable model with Frigate. The following models are recommended for local deployment of the `descriptions` and `chat` roles:
 
-| Model               | Review [frame mode](/configuration/genai/genai_review#frame-mode) | Notes                                                                                                                                                                |
-| ------------------- | --------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `qwen3-vl`          | `frames`                                                              | Strong visual and situational understanding, enhanced ability to identify smaller objects and interactions with object. Follows a sequence of frames on its own.     |
-| `qwen3.6`/`qwen3.8` | `frames`                                                              | Strong situational understanding, but missing DeepStack from qwen3-vl leading to worse performance for identifying objects in people's hand and other small details. |
-| `gemma4`            | `annotated_frames`                                                    | Strong situational understanding, sometimes resorts to more vague terms like 'interacts' instead of assigning a specific action. Loses track of activity that repeats or reverses, so it benefits from annotated frames. |
+| Model               | Notes                                                                                                                                                                |
+| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `qwen3-vl`          | Strong visual and situational understanding, enhanced ability to identify smaller objects and interactions with object.                                              |
+| `qwen3.6`/`qwen3.8` | Strong situational understanding, but missing DeepStack from qwen3-vl leading to worse performance for identifying objects in people's hand and other small details. |
+| `gemma4`            | Strong situational understanding, sometimes resorts to more vague terms like 'interacts' instead of assigning a specific action.                                     |
 
 #### Embedding models
 
@@ -77,17 +77,6 @@ The `embeddings` role needs a different kind of model. Text queries are matched
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `qwen3-vl-embedding` | Multimodal embeddings for [Semantic Search](/configuration/semantic_search#genai-provider). Must be served by llama.cpp started with `--embeddings` and `--mmproj`. |
 
-#### Transcription models
-
-The `transcribe` role needs a model that accepts audio input. A text-only or vision-only model cannot serve this role. The following are recommended for local deployment of the `transcribe` role:
-
-| Model       | Notes                                                                                                                                                                                                      |
-| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `qwen3-asr` | Dedicated speech recognition model covering 30 languages, and the better choice for transcription quality. It only transcribes, so it cannot be shared with the `descriptions` or `chat` roles.            |
-| `gemma4`    | General multimodal model that accepts audio as well as images, so one served model can cover `transcribe` alongside the other roles. Transcript quality is below `qwen3-asr`, particularly on noisy audio. |
-
-Both must be served by llama.cpp started with the matching audio `--mmproj`. llama.cpp only reports audio support when an audio projector is loaded. Without it Frigate sees the model as text-only and the `transcribe` role is unavailable in the UI. Frigate transcribes through the server's `/v1/audio/transcriptions` route, which llama.cpp serves for any audio-capable model.
-
 :::info
 
 Each model is available in multiple parameter sizes (3b, 4b, 8b, etc.). Larger sizes are more capable of complex tasks and understanding of situations, but requires more memory and computational resources. It is recommended to try multiple models and experiment to see which performs best.
@@ -528,6 +517,6 @@ objects:
 7. If descriptions are generated but the results are poor or inconsistent, look at the model and the context window.
    - Empty fields, missing `shortSummary` values, or `Failed to parse review description` errors usually mean the model is not following the requested JSON schema. Smaller models struggle with structured output. Try a larger parameter size or one of the [recommended models](#recommended-local-models).
    - Frigate calculates how many frames to send from the context size the provider reports. If your server reports a different value than it is actually running with, frames will be truncated or the request will fail. Pin the value by adding `context_size` under <NavPath path="Settings > Enrichments > Generative AI > Provider options" /> (`genai.<provider>.provider_options`), and for Ollama also confirm `options.num_ctx` there matches the context you have configured.
-   - Check **Review Description Speed** and **Object Description Speed** in <NavPath path="Health and Metrics > Enrichments" />. If inference takes tens of seconds, requests will queue behind each other and descriptions will appear to stop. For Ollama, review `OLLAMA_NUM_PARALLEL`, `OLLAMA_MAX_QUEUE`, and `OLLAMA_MAX_LOADED_MODELS` so that concurrent requests from Frigate are handled the way you expect.
+   - Check **Review Description Speed** and **Object Description Speed** in <NavPath path="System metrics > Enrichments" />. If inference takes tens of seconds, requests will queue behind each other and descriptions will appear to stop. For Ollama, review `OLLAMA_NUM_PARALLEL`, `OLLAMA_MAX_QUEUE`, and `OLLAMA_MAX_LOADED_MODELS` so that concurrent requests from Frigate are handled the way you expect.
 
 </FaqItem>

docs/docs/configuration/genai/review_summaries.md

@@ -192,76 +192,6 @@ review:
 </TabItem>
 </ConfigTabs>
 
-### Frame Mode
-
-Review items are sent to the model as a sequence of still frames. Some models follow that sequence well on their own; others lose track of activity that repeats or reverses, and describe a single trip when the subject actually made several. The `frame_mode` option controls how those frames are presented.
-
-- `frames` (default): the prompt followed by the frames, exactly as earlier versions of Frigate sent them.
-- `annotated_frames`: each frame is preceded by its frame number and elapsed time, along with notes describing what the object tracker recorded at that moment, such as an object being first detected, starting to move, turning around, stopping, or no longer being detected.
-
-The notes come from tracking data rather than from the images, so they describe activity the model may not have picked up on its own. In testing with a person carrying three waste bins to the curb one at a time, `gemma4` described a single trip on every attempt with `frames`, and consistently described multiple trips with `annotated_frames`. Models that already handle these sequences well, such as the `qwen3-vl` family, gain little and should stay on `frames`.
-
-Annotated mode also caps the number of frames, since the notes already establish the order of events and extra near-duplicate frames tend to crowd out the middle of a clip. Longer review items are sampled more sparsely as a result, and typically use fewer tokens than `frames` mode for the same item.
-
-:::note
-
-Annotated mode needs tracking data for the review item. If none is available, Frigate falls back to sending plain frames for that item.
-
-:::
-
-<ConfigTabs>
-<TabItem value="ui">
-
-Navigate to <NavPath path="Settings > Global configuration > Review" />.
-
-- Set **GenAI config > Frame mode** to the desired mode (e.g., `annotated_frames`)
-
-</TabItem>
-<TabItem value="yaml">
-
-```yaml {4}
-review:
-  genai:
-    enabled: true
-    frame_mode: annotated_frames
-```
-
-</TabItem>
-</ConfigTabs>
-
-### Response Style
-
-Different models respond to the built-in prompt with very different writing styles: some produce natural narration while others sound short and mechanical. The `response_style` option selects a writing style preset that rewords the prompt's instructions for the user-facing fields (the title, short summary, and scene description). Presets replace those instructions rather than adding extra ones, so the model never receives competing style directions.
-
-Available presets:
-
-- `default`: The built-in prompt, unchanged. This already reads like a neutral security report.
-- `natural`: Plain, everyday narration with flowing sentences and sentence-style headline titles. Useful when a model's output sounds robotic.
-- `concise`: As brief as possible while still covering each significant action, with terse two-to-four word titles.
-- `detailed`: Thorough descriptions and titles that include the most identifying specifics, like colors, clothing, and carried items.
-
-Style presets only adjust how the user-facing text reads; the model's step-by-step observations and threat level scoring guidance are unaffected. Results vary by model, so it is worth comparing presets against saved debug output using `testing-scripts/genai_review_tester.py` in the Frigate repository.
-
-<ConfigTabs>
-<TabItem value="ui">
-
-Navigate to <NavPath path="Settings > Global configuration > Review" />.
-
-- Set **GenAI config > Response style** to the desired preset (e.g., `natural`)
-
-</TabItem>
-<TabItem value="yaml">
-
-```yaml {4}
-review:
-  genai:
-    enabled: true
-    response_style: natural
-```
-
-</TabItem>
-</ConfigTabs>
-
 ## Review Reports
 
 Along with individual review item summaries, Generative AI can also produce a single report of review items from all cameras marked "suspicious" over a specified time period (for example, a daily summary of suspicious activity while you're on vacation).

docs/docs/configuration/hardware_acceleration_video.md

@@ -499,7 +499,7 @@ cameras:
 
 ## Synaptics
 
-Hardware accelerated video de-/encoding is supported on Synaptics SL-series SoC.
+Hardware accelerated video de-/encoding is supported on Synpatics SL-series SoC.
 
 ### Prerequisites
 

docs/docs/configuration/license_plate_recognition.md

@@ -8,7 +8,7 @@ import TabItem from "@theme/TabItem";
 import NavPath from "@site/src/components/NavPath";
 import FaqItem from "@site/src/components/FaqItem";
 
-Frigate can recognize license plates on vehicles and automatically add the detected characters to the `recognized_license_plate` field or a [known](#matching) name as a `sub_label` to tracked objects of type `car`, `motorcycle`, `bus`, `truck`, `school_bus`, or `garbage_truck`, depending on which of those labels your model detects. A common use case may be to read the license plates of cars pulling into a driveway or cars passing by on a street.
+Frigate can recognize license plates on vehicles and automatically add the detected characters to the `recognized_license_plate` field or a [known](#matching) name as a `sub_label` to tracked objects of type `car` or `motorcycle`. A common use case may be to read the license plates of cars pulling into a driveway or cars passing by on a street.
 
 LPR works best when the license plate is clearly visible to the camera. For moving vehicles, Frigate continuously refines the recognition process, keeping the most confident result. When a vehicle becomes stationary, LPR continues to run for a short time after to attempt recognition.
 
@@ -24,7 +24,7 @@ When a plate is recognized, the details are:
 - Viewable in the Details pane in Review/History.
 - Viewable in the Tracked Object Details pane in Explore (sub labels and recognized license plates).
 - Filterable through the More Filters menu in Explore.
-- Published via the `frigate/events` MQTT topic as a `sub_label` ([known](#matching)) or `recognized_license_plate` (unknown) for the vehicle tracked object.
+- Published via the `frigate/events` MQTT topic as a `sub_label` ([known](#matching)) or `recognized_license_plate` (unknown) for the `car` or `motorcycle` tracked object.
 - Published via the `frigate/tracked_object_update` MQTT topic with `name` (if [known](#matching)) and `plate`.
 
 ## Model Requirements
@@ -35,7 +35,7 @@ Users without a model that detects license plates can still run LPR. Frigate use
 
 :::note
 
-In the default mode, Frigate's LPR needs to first detect a vehicle before it can recognize a license plate. If you're using a dedicated LPR camera and have a zoomed-in view where a vehicle will not be detected, you can still run LPR, but the configuration parameters will differ from the default mode. See the [Dedicated LPR Cameras](#dedicated-lpr-cameras) section below.
+In the default mode, Frigate's LPR needs to first detect a `car` or `motorcycle` before it can recognize a license plate. If you're using a dedicated LPR camera and have a zoomed-in view where a `car` or `motorcycle` will not be detected, you can still run LPR, but the configuration parameters will differ from the default mode. See the [Dedicated LPR Cameras](#dedicated-lpr-cameras) section below.
 
 :::
 
@@ -86,7 +86,7 @@ cameras:
 </TabItem>
 </ConfigTabs>
 
-For non-dedicated LPR cameras, ensure that your camera is configured to detect vehicle objects, and that a vehicle is actually being detected by Frigate. Otherwise, LPR will not run. The object types that can carry a plate are defined by your model's `attributes_map`, so if your model detects other vehicle labels, you can add them there.
+For non-dedicated LPR cameras, ensure that your camera is configured to detect objects of type `car` or `motorcycle`, and that a car or motorcycle is actually being detected by Frigate. Otherwise, LPR will not run.
 
 Like the other real-time processors in Frigate, license plate recognition runs on the camera stream defined by the `detect` role in your config. To ensure optimal performance, select a suitable resolution for this stream in your camera's firmware that fits your specific scene and requirements.
 
@@ -158,7 +158,7 @@ lpr:
 
 Navigate to <NavPath path="Settings > Enrichments > License plate recognition" />.
 
-- **Known plates**: Assign custom `sub_label` values to vehicle objects when a recognized plate matches a known value. These labels appear in the UI, filters, and notifications. Unknown plates are still saved but are added to the `recognized_license_plate` field rather than the `sub_label`.
+- **Known plates**: Assign custom `sub_label` values to `car` and `motorcycle` objects when a recognized plate matches a known value. These labels appear in the UI, filters, and notifications. Unknown plates are still saved but are added to the `recognized_license_plate` field rather than the `sub_label`.
 - **Match distance**: Allows for minor variations (missing/incorrect characters) when matching a detected plate to a known plate. For example, setting to `1` allows a plate `ABCDE` to match `ABCBE` or `ABCD`. This parameter will _not_ operate on known plates that are defined as regular expressions.
 
 </TabItem>
@@ -316,7 +316,7 @@ lpr:
 
 :::note
 
-If a camera is configured to detect vehicles but you don't want Frigate to run LPR for that camera, disable LPR at the camera level:
+If a camera is configured to detect `car` or `motorcycle` but you don't want Frigate to run LPR for that camera, disable LPR at the camera level:
 
 <ConfigTabs>
 <TabItem value="ui">
@@ -456,7 +456,7 @@ With this setup:
 - Snapshots will have license plate bounding boxes on them.
 - The `frigate/events` MQTT topic will publish tracked object updates.
 - Debug view will display `license_plate` bounding boxes.
-- If you are using a Frigate+ model and want to submit images from your dedicated LPR camera for model training and fine-tuning, annotate both the vehicle and the `license_plate` in the snapshots on the Frigate+ website, even if the vehicle is barely visible.
+- If you are using a Frigate+ model and want to submit images from your dedicated LPR camera for model training and fine-tuning, annotate both the `car` / `motorcycle` and the `license_plate` in the snapshots on the Frigate+ website, even if the car is barely visible.
 
 ### Using the Secondary LPR Pipeline (Without Frigate+)
 
@@ -611,9 +611,9 @@ If you are still having issues detecting plates, start with a basic configuratio
 
 </FaqItem>
 
-<FaqItem id="can-i-run-lpr-without-detecting-car-or-motorcycle-objects" question={<>Can I run LPR without detecting vehicle objects?</>}>
+<FaqItem id="can-i-run-lpr-without-detecting-car-or-motorcycle-objects" question={<>Can I run LPR without detecting <code>car</code> or <code>motorcycle</code> objects?</>}>
 
-In normal LPR mode, Frigate requires a vehicle to be detected first before recognizing a license plate. If you have a dedicated LPR camera, you can change the camera `type` to `"lpr"` to use the Dedicated LPR Camera algorithm. This comes with important caveats, though. See the [Dedicated LPR Cameras](#dedicated-lpr-cameras) section above.
+In normal LPR mode, Frigate requires a `car` or `motorcycle` to be detected first before recognizing a license plate. If you have a dedicated LPR camera, you can change the camera `type` to `"lpr"` to use the Dedicated LPR Camera algorithm. This comes with important caveats, though. See the [Dedicated LPR Cameras](#dedicated-lpr-cameras) section above.
 
 </FaqItem>
 
@@ -697,9 +697,9 @@ lpr:
    - You may need to adjust your `detection_threshold` if your plates are not being detected.
 
 4. Ensure the characters on detected plates are being _recognized_.
-   - Check the **Plate recognition** inference time in Enrichment metrics (<NavPath path="Health and Metrics > Enrichments" />). High inference times (> 100ms) could lead to poor recognition results, especially for dedicated LPR cameras where the plate crosses the frame quickly.
+   - Check the **Plate recognition** inference time in Enrichment metrics (<NavPath path="System metrics > Enrichments" />). High inference times (> 100ms) could lead to poor recognition results, especially for dedicated LPR cameras where the plate crosses the frame quickly.
    - 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 vehicle's label will change to the recognized plate when LPR is enabled and working.
+   - 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).
 
 </FaqItem>
@@ -714,13 +714,13 @@ LPR's performance impact depends on your hardware. Ensure you have at least 4GB
 
 The YOLOv9 license plate detector model will run (and the metric will appear) if you've enabled LPR but haven't defined `license_plate` as an object to track, either at the global or camera level.
 
-If you are detecting vehicles on cameras where you don't want to run LPR, make sure you disable LPR it at the camera level. And if you do want to run LPR on those cameras, make sure you define `license_plate` as an object to track.
+If you are detecting `car` or `motorcycle` on cameras where you don't want to run LPR, make sure you disable LPR it at the camera level. And if you do want to run LPR on those cameras, make sure you define `license_plate` as an object to track.
 
 </FaqItem>
 
 <FaqItem id="it-looks-like-frigate-picked-up-my-cameras-timestamp-or-overlay-text-as-the-license-plate-how-can-i-prevent-this" question="It looks like Frigate picked up my camera's timestamp or overlay text as the license plate. How can I prevent this?">
 
-This could happen if vehicles travel close to your camera's timestamp or overlay text. You could either move the text through your camera's firmware, or apply a mask to it in Frigate.
+This could happen if cars or motorcycles travel close to your camera's timestamp or overlay text. You could either move the text through your camera's firmware, or apply a mask to it in Frigate.
 
 If you are using a model that natively detects `license_plate`, add an _object mask_ of type `license_plate` and a _motion mask_ over your text.
 

docs/docs/configuration/live.md

@@ -28,24 +28,6 @@ WebRTC may use an external STUN server for NAT traversal. MSE and HLS streaming
 
 :::
 
-### Selecting a streaming technology
-
-Frigate [defaults to MSE](#why-does-frigate-prefer-mse-over-webrtc-for-live-view) for restreamed cameras by design. To use WebRTC, select it explicitly from a camera's single-camera Live view settings (the settings menu in the camera's Live view header on desktop, or the settings drawer on mobile). Three related controls work together:
-
-- **Stream**: _what_ to play. This lists the [streams you've configured](#setting-streams-for-live-ui) (for example `Main Stream` and `Sub Stream`).
-- **Force low-bandwidth mode**: a switch that always plays Frigate's built-in low-bandwidth feed (the stream assigned the `detect` role, using JSMpeg) instead of the selected stream. It works anywhere without go2rtc and is useful on slow or metered connections. While it is enabled, the stream and streaming technology selectors are disabled; your stream and technology choices are restored when you turn it off.
-- **Streaming Technology**: _how_ to play the selected stream, listing **MSE** and **WebRTC**. It is only shown for a restreamed stream.
-
-- The choices are saved **per device, per camera** in your browser's local storage.
-- **WebRTC is only selectable when it can actually work for that stream.** When it can't, the option is shown disabled with the reason inline, and a more detailed reason (the failing codecs, or why the connectivity check failed) is logged to your browser's console. Common reasons:
-  - **Not configured**: no `candidates` or `ice_servers` are set under `go2rtc.webrtc` (see [WebRTC extra configuration](#webrtc-extra-configuration)).
-  - **Could not connect**: e.g. port `8555` isn't reachable, or a STUN/TURN server is misconfigured. Frigate runs a one-time WebRTC connectivity check when the Live view opens; the option may briefly show as "checking" while it runs.
-  - **Unsupported video codec**: the stream's video codec can't be played over WebRTC in your browser, most commonly H.265/HEVC in Firefox or Edge.
-  - **Unsupported audio codec**: WebRTC needs opus or G.711 audio, so a stream whose playback audio is only AAC (without an added opus/G.711 track) can't carry audio over WebRTC. See [Audio Support](#audio-support) for how to add one.
-  - **Unsupported browser**: the browser doesn't support WebRTC.
-
-When WebRTC isn't available, Frigate automatically uses MSE (or falls back to JSMpeg), so live view keeps working regardless of the selection.
-
 ### Camera Settings Recommendations
 
 If you are using go2rtc, you should adjust the following settings in your camera's firmware for the best experience with Live view:
@@ -175,17 +157,6 @@ WebRTC works by creating a TCP or UDP connection on port `8555`. However, it req
         - stun:8555
   ```
 
-- The web UI uses the STUN and TURN servers in `ice_servers` and falls back to Google's public STUN server when none are set:
-
-  ```yaml title="config.yml"
-  go2rtc:
-    webrtc:
-      ice_servers:
-        - urls: [turn:turn.example.com:3478]
-          username: frigate
-          credential: password
-  ```
-
 - For access through Tailscale, the Frigate system's Tailscale IP must be added as a WebRTC candidate. Tailscale IPs all start with `100.`, and are reserved within the `100.64.0.0/10` CIDR block.
 
 - Note that some browsers may not support H.265 (HEVC). You can check your browser's current version for H.265 compatibility [here](https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#codecs-madness).
@@ -235,8 +206,6 @@ For devices that support two way talk, Frigate can be configured to use the feat
 - Ensure you access Frigate via https (may require [opening port 8971](/frigate/installation/#ports)).
 - For the Home Assistant Frigate card, [follow the docs](http://card.camera/#/usage/2-way-audio) for the correct source.
 
-The two-way talk control in the single-camera Live view is only enabled when WebRTC is available; if WebRTC isn't configured or can't connect, the control is shown disabled.
-
 To use the Reolink Doorbell with two way talk, you should use the [recommended Reolink configuration](/configuration/camera_specific#reolink-cameras)
 
 As a starting point to check compatibility for your camera, view the list of cameras supported for two-way talk on the [go2rtc repository](https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#two-way-audio). For cameras in the category `ONVIF Profile T`, you can use the [ONVIF Conformant Products Database](https://www.onvif.org/conformant-products/)'s FeatureList to check for the presence of `AudioOutput`. A camera that supports `ONVIF Profile T` _usually_ supports this, but due to inconsistent support, a camera that explicitly lists this feature may still not work. If no entry for your camera exists on the database, it is recommended not to buy it or to consult with the manufacturer's support on the feature availability.

docs/docs/configuration/non_root.md

@@ -1,395 +0,0 @@
----
-id: non_root
-title: Running as a non-root user
----
-
-# Running as a non-root user
-
-Frigate's services run as an unprivileged user inside the container. The main Frigate process and nginx run as `frigate`, and go2rtc runs as its own more restricted `go2rtc` user. Only the s6 init system and the certsync helper stay root.
-
-The runtime user is uid/gid `1000:1000` by default. You can change it with `PUID`/`PGID`, or bypass Frigate's user handling entirely with Docker's own `user:`.
-
-Most upgrades need nothing. Frigate aligns your volume ownership on the first boot and grants access to your hardware at startup. The sections below cover the cases that need attention: large storage volumes, network storage, and hardware the automatic grant can't reach.
-
-## Run modes
-
-| Mode                | How to enable                   | Ownership of `/config` and `/media/frigate`            | `read_only: true` |
-| ------------------- | ------------------------------- | ------------------------------------------------------ | ----------------- |
-| Default             | nothing, this is the default    | Aligned to `1000:1000` on first boot                   | Supported         |
-| `PUID`/`PGID`       | `PUID=1001`, `PGID=1001`        | Aligned to the values you set, on first boot           | Not supported     |
-| Docker-native user  | `user: "1001:1001"`             | You own it, Frigate never changes ownership            | Supported         |
-| Root (escape hatch) | `FRIGATE_RUN_AS_ROOT=true`      | Never touched                                          | Not supported     |
-| Granular root       | `FRIGATE_ROOT_SERVICES=frigate` | Aligned at boot; recordings and exports also at create | Not supported     |
-
-`PUID`/`PGID` remapping runs `usermod` at startup, which writes to `/etc/passwd`, so it can't work with a read-only root filesystem. That combination stops at startup with a message pointing here. `EXTRA_GROUPS` writes to `/etc/group` and stops the same way; use Docker's `group_add:` instead, which needs no writes inside the container. The default mode and Docker's `user:` mode both work with `read_only: true`; see [Hardened deployment](#hardened-deployment).
-
-`FRIGATE_RUN_AS_ROOT` is matched against the exact lowercase string `true`. `True`, `TRUE`, and `1` are all ignored. `FRIGATE_DEVICE_ACLS` works the same way: only the lowercase string `false` turns off the automatic device grants.
-
-### Keeping individual services root
-
-`FRIGATE_ROOT_SERVICES` takes a comma separated list of `frigate`, `go2rtc`, and `nginx`. A listed service keeps running as root, and everything else about non-root operation still applies: `PUID`/`PGID` remapping, the ownership sweep, and ownership of the files those services create.
-
-There are two reasons to use it:
-
-- Your detector hardware won't work as an unprivileged user, even after reading [Hardware device access](#hardware-device-access). `FRIGATE_ROOT_SERVICES=frigate` keeps the main process and its detectors as root while nginx and go2rtc stay unprivileged.
-- You want everything to run as root but still want your files owned by `PUID`/`PGID` instead of root. `FRIGATE_ROOT_SERVICES=frigate,go2rtc,nginx` does that.
-
-Try the device grants and `EXTRA_GROUPS` first. The `frigate` service runs the API and every ffmpeg process that decodes your camera streams, so listing it puts those back on root as well, not just your detectors.
-
-A listed service also stops honoring a [custom ffmpeg or go2rtc build](/configuration/advanced/system#custom-dependencies) kept in `/config`, since that directory stays owned by the unprivileged user and a binary there would run as root. `FRIGATE_RUN_AS_ROOT=true` has no such restriction.
-
-Recordings and exports are owned by `PUID`/`PGID` as soon as they're written, even by a root service. Snapshots, thumbnails, and other files under `clips/` are corrected on each restart, so they can show as root-owned from the host until then. A listed service also keeps root's home directory, so library caches go to the container layer instead of `/config`. The same applies to the [detector runtimes](/frigate/network_requirements#detector-runtimes) Frigate installs at first start (Hailo, MemryX, AXEngine): a root `frigate` service installs them into `/root/.local`, which is lost when the container is recreated, and never loads a copy left behind in `/config/.local`.
-
-Listing all three services is not the same as `FRIGATE_RUN_AS_ROOT=true`. The escape hatch never touches ownership; the list keeps the ownership handling active. A few more details:
-
-- An unknown name in the list stops the container at startup, rather than silently leaving a service unprivileged.
-- Changing the list runs the full ownership sweep once on the next boot.
-- If both are set, `FRIGATE_RUN_AS_ROOT=true` wins and the list is ignored.
-- With Docker's `user:`, the list does nothing, since the container never has root to keep.
-
-## Migrating an existing install
-
-Volumes from earlier versions of Frigate are owned by root, so ownership has to be aligned with the runtime user once. This happens automatically on the first boot after upgrading.
-
-On large recordings volumes, do it from the host beforehand instead. The boot sweep runs before any service starts, so a multi-terabyte `/media/frigate` can hold the container in startup long enough for Docker's healthcheck to mark it unhealthy, and orchestrators that watch health will restart it mid-sweep. If you'd rather not run the script, raise the healthcheck start period instead (`--start-period=1800s`, or `start_period: 1800s` under `healthcheck:` in compose).
-
-Grab [`fix-permissions.sh`](https://github.com/blakeblackshear/frigate/blob/dev/docker/migration/fix-permissions.sh) from the Frigate repo and dry run it first:
-
-```bash
-./fix-permissions.sh --dry-run /path/to/your/config /path/to/your/storage
-```
-
-That reports how many entries would change and touches nothing. When it looks right, run it without `--dry-run`:
-
-```bash
-./fix-permissions.sh /path/to/your/config /path/to/your/storage
-```
-
-Pass `PUID` and `PGID` as the third and fourth arguments if you're not using the default `1000:1000`. The script wraps the same helper the container uses, so the result is identical either way. Override the image it pulls with `FRIGATE_IMAGE=...` if you're not on `stable`.
-
-Both the script and the boot sweep report progress, so you can tell a slow sweep from a stuck one:
-
-```
-[INFO] fix-ownership: scanning /media/frigate for ownership mismatches; this may take a while on large filesystems
-[WARN] fix-ownership: adjusting ownership of 4823941 entries under /media/frigate
-[INFO] fix-ownership: /media/frigate 5% (241197/4823941 entries)
-[INFO] fix-ownership: /media/frigate 10% (482394/4823941 entries)
-[INFO] fix-ownership: finished /media/frigate in 12m 4s
-```
-
-The scan has no percentage because the total isn't known until it finishes. Watch the boot sweep with `docker logs -f frigate`.
-
-Once the volumes are aligned, start Frigate normally. A file at `/config/.permissions_version` records what was done, so later boots skip the sweep unless you change `PUID`/`PGID`.
-
-If something under your volumes can't be chowned, a read-only btrfs snapshot directory for example, the sweep warns and names the path and doesn't record the migration as finished. It retries on the next boot instead. Either move those paths outside `/media/frigate` or expect the scan to repeat.
-
-### Network storage
-
-Recordings on a NAS behave differently, so check what you have before migrating:
-
-```bash
-findmnt -T /path/to/your/storage -o TARGET,FSTYPE,OPTIONS
-```
-
-**SMB and CIFS** don't store per-file ownership at all. It's synthesized from the mount options, so a per-file `chown` fails and isn't needed. Mount the share as the uid and gid Frigate runs as, and every file already looks correct to the sweep:
-
-```
-//nas/frigate /media/frigate cifs credentials=/root/.smb,uid=1000,gid=1000,file_mode=0664,dir_mode=0775 0 0
-```
-
-**NFS** exports default to `root_squash` on most servers, which maps the container's root to `nobody`. The chown then fails, you get `[WARN] fix-ownership: some entries under /media/frigate could not be updated`, and since the sweep didn't finish it doesn't record the migration, so it retries on every boot.
-
-The best fix is to not chown over NFS at all. Do it on the server, where there's no squash and no network round trip per file:
-
-```bash
-# on the NAS itself, against the exported directory
-chown -R 1000:1000 /export/frigate
-```
-
-Frigate's sweep then finds nothing to change and records the migration normally. If you can't get a shell on the server, you can export temporarily with `no_root_squash`, migrate, and put it back, or leave ownership alone and set `PUID`/`PGID` to whichever uid already owns the files.
-
-Either way the uid has to mean the same thing on both machines. NFS sends numeric uids, so container uid 1000 is uid 1000 on the server no matter what the usernames are.
-
-Expect the first boot to be slow even when nothing needs changing, because checking ownership costs a round trip per file. That's a one-time cost. **If the sweep runs on every boot rather than once, ownership isn't actually being applied**, and the warning above will say so.
-
-Keep `/config` on local storage either way. Frigate's database is SQLite and network shares handle its locking poorly. That's a long-standing recommendation, not something running non-root introduces.
-
-## Rolling back
-
-Set `FRIGATE_RUN_AS_ROOT=true` and restart. Everything runs as root again, exactly as it did before. This is the fastest way to get a broken install running while you sort out a device permission problem.
-
-The escape hatch never changes ownership, and it clears the record of the last sweep on startup, so switching back to non-root later corrects whatever root created in the meantime. Toggling in either direction is safe.
-
-## Hardware device access
-
-Frigate grants the runtime user access to your devices at startup. Pass your hardware with `--device` (or `devices:` in compose) and detection and hardware acceleration work with no group or udev setup on the host.
-
-The grant covers the common accelerator and camera nodes: GPU render nodes, Intel/AMD NPUs (`/dev/accel`), Coral, Hailo, Rockchip, Jetson, `/dev/video*`, and the USB bus. For hardware it misses, add your own paths with `DEVICE_ACL_PATHS`, a comma separated list of globs:
-
-```yaml
-environment:
-  DEVICE_ACL_PATHS: "/dev/mydev*"
-```
-
-Set `FRIGATE_DEVICE_ACLS=false` if you manage device permissions yourself and want Frigate to leave them alone.
-
-Frigate grants access by adding an ACL entry for the runtime users. The device's owner and mode are unchanged, and nothing is made world accessible. One thing to know: `--device` nodes belong to the container, but a bind mounted `/dev/bus/usb` (the usual Coral USB setup) shares the host's device nodes, so the entry is visible on the host until udev recreates the node.
-
-### Manual setup
-
-You only need this for hardware the automatic grant can't reach, or for Docker's `user:` mode, where there's no root startup to do the granting.
-
-Your accelerator most likely worked in older versions because Frigate ran as root. Device nodes are usually owned by `root:root`, and root either matches the group or skips the check entirely. The runtime user does neither, so a device that worked before can become unreadable with no change to your Frigate config.
-
-#### Read what your device requires
-
-Find the node and look at its owner, group, and mode:
-
-```bash
-ls -ln /dev/dri/renderD128
-crw-rw---- 1 0 105 226, 128 Jul  5 10:12 /dev/dri/renderD128
-#          ^ ^  ^
-#          | |  group GID 105
-#          | owner UID 0 (root)
-#          mode: owner rw, group rw, other none
-```
-
-Then work out which of the three permission sets applies to the runtime user. It isn't the owner, since that's root, so it gets the group bits if it belongs to that GID and otherwise falls through to "other". In the example above "other" is empty, so without membership in group 105 the runtime user can't open the node.
-
-Watch for a node that looks permissive but isn't. A USB Coral defaults to this:
-
-```bash
-ls -ln /dev/bus/usb/004/003
-crw-rw-r-- 1 0 0 189, 386 Jul  5 10:12 /dev/bus/usb/004/003
-```
-
-The group is `0`, so "other" applies to the runtime user, and "other" here is read only. `libedgetpu` needs to write to the node, so detection fails with `No EdgeTPU was detected` as though no Coral were attached. Read access alone isn't enough for most accelerators.
-
-#### Grant access
-
-Give the runtime user the GID with `EXTRA_GROUPS`, a comma separated list of numeric host GIDs. They're added to both the `frigate` and `go2rtc` users, which matters because go2rtc needs its own render and video access for hardware accelerated restreams.
-
-```yaml
-environment:
-  EXTRA_GROUPS: "105,44" # host render and video GIDs
-```
-
-Use numeric GIDs from the host, not names. Group names don't have to match between the host and the container, and the kernel only checks the number. If the GID doesn't exist in the image, Frigate creates a placeholder group for it.
-
-Two things that look like they should work but don't:
-
-- Docker's `group_add` has no effect in the default or `PUID` modes. Frigate rebuilds the supplementary group list from `/etc/group` when it drops privileges, which discards what Docker passed in. It is the right tool with Docker's `user:`, where no privilege drop happens and `EXTRA_GROUPS` does nothing.
-- `privileged: true` doesn't help. It grants capabilities to root, and the runtime user isn't root, so the file permissions on the node still apply.
-
-If the node's group is `root` or the mode denies the group, no `EXTRA_GROUPS` value will help. You need a udev rule first.
-
-#### Verify access
-
-Check the group landed, then check the runtime user can open the node. Test for write, not just read:
-
-```bash
-docker exec frigate id frigate
-docker exec frigate /command/s6-setuidgid frigate sh -c 'test -w /dev/dri/renderD128 && echo ok'
-docker exec frigate /command/s6-setuidgid go2rtc  sh -c 'test -w /dev/dri/renderD128 && echo ok'
-```
-
-A permission check is only a proxy for the driver working. These exercise the real libraries as the runtime user:
-
-```bash
-docker exec frigate /command/s6-setuidgid frigate vainfo
-docker exec frigate /command/s6-setuidgid frigate python3 -c "import openvino as ov; print(ov.Core().available_devices)"
-```
-
-`vainfo` should reach `va_openDriver() returns 0` and list profiles. Complaints about `XDG_RUNTIME_DIR` or an X server above that are normal. OpenVINO should list `GPU`; if it returns only `CPU`, detection has fallen back and inference will be much slower without an error in the log.
-
-To tell a permissions problem from anything else, start the container once with `FRIGATE_RUN_AS_ROOT=true`. If the device works as root and not otherwise, it's node permissions and a udev rule is the fix. If it's missing either way, the problem is your device mapping or the host, and isn't related to running non-root.
-
-#### udev rules by device
-
-Rules go in `/etc/udev/rules.d/` on the host and take effect after:
-
-```bash
-sudo udevadm control --reload-rules && sudo udevadm trigger
-```
-
-A device that's already connected sometimes keeps its original ownership through a trigger. If `ls -ln` doesn't show the new group, replug it, or reboot for a built-in device.
-
-**Coral USB** needs two rules, because the device re-enumerates after loading firmware. It appears as Global Unichip `1a6e` before and Google `18d1` after, with a different node each time. A rule covering only `1a6e` gives you a Coral that starts up once and then disappears mid-run.
-
-```
-SUBSYSTEM=="usb", ATTRS{idVendor}=="1a6e", GROUP="plugdev", MODE="0664"
-SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev", MODE="0664"
-```
-
-Map the whole `/dev/bus/usb` rather than a single node, for the same reason. Most hosts put `plugdev` at GID 46 and the image agrees, so a USB Coral often needs no `EXTRA_GROUPS` entry. Confirm with `getent group plugdev` and add the number if your host differs.
-
-**Coral PCIe** is often `crw------- root root`, which only root can open:
-
-```
-SUBSYSTEM=="apex", MODE="0660", GROUP="apex"
-```
-
-Create the group with `sudo groupadd -f apex`, then add its GID to `EXTRA_GROUPS`.
-
-**Hailo** works the same way. Grant `/dev/hailo0` a group and add that GID:
-
-```
-SUBSYSTEM=="hailo_chardev", MODE="0660", GROUP="hailo"
-```
-
-**Intel and AMD GPUs** usually need nothing beyond `EXTRA_GROUPS`, since most distributions ship a `render` group that owns `/dev/dri/renderD128`. The GID often differs between the host and the image, so pass the host's number rather than assuming the name resolves. Debian based images have no `render` group at all.
-
-#### Quick reference
-
-What each device needs when you're setting it up by hand. The automatic grant covers most of these already, so start here only if it didn't.
-
-| Hardware                  | Device(s)                                                   | What non-root needs                                                                                              |
-| ------------------------- | ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| Intel/AMD GPU (VAAPI/QSV) | `/dev/dri/renderD128`                                       | Host render GID in `EXTRA_GROUPS`, from `getent group render`                                                    |
-| Intel/AMD NPU             | `/dev/accel`                                                | udev rule granting a group, then that GID in `EXTRA_GROUPS`                                                      |
-| Coral USB                 | `/dev/bus/usb`                                              | udev rules for both `1a6e` and `18d1`; usually already covered by `plugdev` 46                                   |
-| Coral PCIe                | `/dev/apex_0`                                               | udev rule granting a group, then that GID in `EXTRA_GROUPS`                                                      |
-| Hailo                     | `/dev/hailo0`                                               | udev rule granting a group, then that GID in `EXTRA_GROUPS`                                                      |
-| NVIDIA                    | nvidia runtime                                              | Nothing, works with the nvidia-container-toolkit defaults                                                        |
-| AMD ROCm                  | `/dev/kfd`, `/dev/dri`                                      | Host `video` and `render` GIDs in `EXTRA_GROUPS`                                                                 |
-| Raspberry Pi              | `/dev/video11`                                              | Host `video` GID in `EXTRA_GROUPS`                                                                               |
-| Rockchip                  | `/dev/dri`, `/dev/dma_heap`, `/dev/rga`, `/dev/mpp_service` | Commonly `root:root` `0600`, so all four need udev rules. If you can't grant all four, use `FRIGATE_RUN_AS_ROOT` |
-| Axera (AXCL)              | `/dev/ax_*` per the AXCL driver docs                        | Unverified. Check node ownership on your hardware before assuming this works                                     |
-| Synaptics SL1680          | per the Synaptics docs                                      | Unverified                                                                                                       |
-| MemryX                    | per the MemryX docs                                         | Still requires `privileged: true`, which means root. Out of scope for non-root operation                         |
-| Nvidia Jetson             | nvidia runtime plus Jetson nodes                            | Unverified. The nvidia runtime handles mapping, but check `/dev/nvhost-*` ownership on your board                |
-| VeriSilicon NPU (Teflon)  | per the driver, commonly `/dev/galcore`                     | Unverified. Check node ownership on your hardware before assuming this works                                     |
-| CPU detector              | none                                                        | Nothing, no device is opened                                                                                     |
-| ZMQ detector              | none                                                        | Nothing, inference happens over a socket                                                                         |
-| Apple Silicon             | none                                                        | Nothing, the NPU client runs on the host and Frigate reaches it over the network                                 |
-
-## Hardened deployment
-
-A read-only root filesystem means the container can't modify itself, only the volumes you give it. It works in the default mode and under Docker's `user:`, but not with `PUID`/`PGID` or `EXTRA_GROUPS`, which both need to write to `/etc`.
-
-Start with the default mode. It keeps go2rtc on its own restricted user and still grants your hardware automatically, at the cost of a short root startup that finishes before any service runs.
-
-```yaml
-services:
-  frigate:
-    container_name: frigate
-    image: ghcr.io/blakeblackshear/frigate:stable
-    restart: unless-stopped
-    stop_grace_period: 30s
-    read_only: true
-    security_opt:
-      - no-new-privileges:true
-    shm_size: "512mb" # size for your cameras, see the shm-size calculation
-    devices:
-      - /dev/dri/renderD128:/dev/dri/renderD128 # your hardware, granted at startup
-    volumes:
-      - /etc/localtime:/etc/localtime:ro
-      - /path/to/your/config:/config
-      - /path/to/your/storage:/media/frigate
-    tmpfs:
-      - /tmp:size=256m
-      - /tmp/cache:size=1000000000 # recording segments, sized as before
-      - /run:exec,nosuid,nodev,mode=0755,size=16m
-    ports:
-      - "8971:8971"
-      - "8554:8554" # RTSP feeds
-      - "8555:8555/tcp" # WebRTC over tcp
-      - "8555:8555/udp" # WebRTC over udp
-```
-
-`/run` has to allow `exec`. With a read-only root filesystem s6 copies its service scripts into `/run` and runs them from there, and tmpfs mounts default to `noexec`. The equivalent for `docker run` is `--tmpfs /run:exec,nosuid,nodev,mode=0755`. Spelling out `nosuid` and `nodev` matters: passing any tmpfs options replaces Docker's defaults instead of adjusting them, so asking for `exec` alone would drop those two as well.
-
-Size `/tmp` deliberately. It now carries nginx's config copy and its five proxy temp directories as well as the recording cache. Keeping `/tmp/cache` as its own nested tmpfs, as above, leaves your existing [cache sizing](/frigate/installation#storage) untouched and adds a small allowance for nginx. If you'd rather use one tmpfs over all of `/tmp`, size it as your cache budget plus roughly 50MB, or recordings begin failing once the cache fills.
-
-The self signed certificate is written to `/config/tls`, which stays writable. Certificates you mount at `/etc/letsencrypt/live/frigate` work unchanged and still take precedence.
-
-[Detector runtimes](/frigate/network_requirements#detector-runtimes) that Frigate installs at first start (Hailo, MemryX, AXEngine) are staged in `/tmp` and installed into `/config/.local`, so they work with a read-only root filesystem in the default mode and under `user:`. A root `frigate` service installs into `/root/.local` instead, which a read-only root filesystem prevents; either leave `frigate` out of `FRIGATE_ROOT_SERVICES` or drop `read_only`.
-
-Soak a hardened deployment for 24 hours against real cameras before relying on it. A read-only root filesystem turns an occasional write into a failure that startup won't reveal.
-
-### Never starting as root
-
-To remove root from the container entirely, add Docker's `user:`:
-
-```yaml
-    user: "1000:1000" # NOT compatible with PUID/PGID, see the run modes table
-    tmpfs:
-      - /tmp:size=256m
-      - /tmp/cache:size=1000000000
-      - /run:exec,nosuid,nodev,mode=0755,uid=1000,gid=1000,size=16m # uid must match user:
-```
-
-`/run` has to be owned by that uid as well. s6 writes its runtime state there before anything else starts, and with no root in the container a root-owned `/run` stops it during init with `cannot create /run/test of writability`. Keep `uid` and `gid` in the tmpfs options matching `user:`, and don't carry that pair back into the default mode, where a root-owned `/run` is what keeps the unprivileged services out of s6's runtime state.
-
-This only bites once root is genuinely gone. s6's init helper is setuid, so `user:` on its own still lets init regain root and correct `/run` itself. The `no-new-privileges:true` above is what blocks that, which is also what makes the `/run` ownership mandatory. Dropping it would hide the problem by handing init root again.
-
-Two things change, and the first one will break a working install if you skip it. The startup device grants can't run, because there is no root left to run them, so every device you pass stops working until you grant that uid access yourself with `group_add:` or a udev rule; see [Manual setup](#manual-setup). Expect this to surface as a driver error rather than a permission error, like `No VA display found` from VAAPI. And every service then runs as that one uid, so go2rtc no longer gets its own restricted user. `/config` and `/media/frigate` have to be owned by that uid already, since Frigate never adjusts ownership in this mode. Switching an existing install over also leaves `/config/go2rtc_homekit.yml` owned by the go2rtc user, which this mode can't write; `chown` it to your uid or HomeKit pairing changes stop persisting. Frigate warns and starts either way.
-
-This mode can also take `cap_drop: [ALL]`, which the default mode cannot: starting as root needs `CAP_CHOWN` for the ownership sweep, `CAP_SETUID` and `CAP_SETGID` to drop to the runtime user, and `CAP_FOWNER` for the device grants.
-
-### Per-variant exceptions
-
-- **Rockchip** needs `- /sys/:/sys/:ro` alongside its device nodes, in addition to everything above.
-- **MemryX** and **QNAP Container Station** still require `privileged: true` per their own documentation, which gives back most of what this layout removes. MemryX also downloads its models to `/memryx_models` on the root filesystem, so it can't run read-only regardless. Its SDK is installed into `/config/.local` like the other detector runtimes.
-
-## Network isolation
-
-Everything above limits what a compromised container can do to the host. It doesn't limit what your cameras can do to your network. Camera firmware is closed source, rarely patched, and not something you can audit, and none of it needs internet access for Frigate to work.
-
-Put the cameras on their own VLAN or subnet, give the Frigate host a route into it, and deny that VLAN any route out. Frigate reaches in to pull streams, the cameras reach nothing. A second NIC on the Frigate host is the simplest version of this, and a tagged VLAN on the NIC you already have works just as well.
-
-Here's the deny as nftables on the router, with cameras on `vlan20` and the Frigate host at `192.168.10.5`:
-
-```
-table inet cameras {
-  chain forward {
-    type filter hook forward priority filter; policy accept;
-
-    ct state established,related accept
-    iifname "vlan20" ip daddr 192.168.10.5 accept
-    iifname "vlan20" drop
-  }
-}
-```
-
-It's in its own table so it can sit alongside an existing ruleset without touching it. Streams keep working because Frigate opens those connections and the return traffic is `established`. Cameras can still reach each other on their own VLAN, since that traffic never reaches the router, so use client isolation on the switch if that matters to you.
-
-Two things break when you do this. The manufacturer's phone app stops working, which is the point, and camera clocks drift, because most of them set their time over NTP and are bad at it. Point them at an NTP server on your own network rather than opening the VLAN back up, or their timestamps and Frigate's will disagree.
-
-Frigate itself needs some outbound access, though nearly all of it is optional. The startup version check is the only piece that's on by default, and `telemetry.version_check: false` turns it off. Everything else (model downloads for the enrichment features, push notifications, Frigate+, and cloud GenAI providers) only reaches out once you enable that feature. See [Network Requirements](/frigate/network_requirements) for the full list and how to run fully offline.
-
-For containers that only talk to each other, an internal compose network gets you the same isolation without involving the router:
-
-```yaml
-services:
-  frigate:
-    networks: [default, iot]
-    # the rest of your frigate service
-  mosquitto:
-    image: eclipse-mosquitto
-    networks: [iot]
-
-networks:
-  iot:
-    internal: true
-```
-
-`internal: true` gives that network no route off the host, so the broker isn't reachable from anywhere else on your LAN. Frigate sits on both networks and keeps its normal outbound path.
-
-One Docker specific trap: published ports are inserted ahead of the host firewall, so `ufw deny 8971` doesn't do what it looks like it does. Bind the port to the interface you want instead, like `127.0.0.1:8971:8971` for a reverse proxy on the same host, or your LAN address for everything else.
-
-## Known limitations
-
-`telemetry.stats.network_bandwidth` uses nethogs, which needs `CAP_NET_ADMIN` and `CAP_NET_RAW` and therefore root. The stat is turned off automatically when Frigate isn't running as root, with one warning in the log. Use `FRIGATE_ROOT_SERVICES=frigate` (or `FRIGATE_RUN_AS_ROOT=true`) if you need it.
-
-go2rtc's ffmpeg processes no longer appear in Intel GPU stats. Frigate reads per-process GPU usage from `/proc/<pid>/fdinfo`, which the kernel won't let one user read for another user's processes, so anything go2rtc spawns is invisible to it. Overall GPU utilization is unaffected.
-
-If you mount your own TLS certificate at `/etc/letsencrypt/live/frigate`, the private key has to be readable by the runtime user, which runs nginx. Frigate hands the key to that user at startup if the mount is writable; on a read-only mount, make the key readable by uid 1000 (or your `PUID`) yourself.
-
-If you're debugging nginx, run the config check as the runtime user with stdout discarded:
-
-```bash
-docker exec frigate /command/s6-setuidgid frigate bash -c 'nginx -t -c /tmp/nginx/conf/nginx.conf >/dev/null'
-```
-
-Running `nginx -t` as root hands nginx's runtime directories to root as a side effect, which breaks the running workers until the service restarts, and the config's `/dev/stdout` logs can't be reopened through a root-owned `docker exec` pipe. The results print on stderr either way.

docs/docs/configuration/object_detectors.md

@@ -22,9 +22,8 @@ Frigate supports multiple different detectors that work on different types of ha
 **Most Hardware**
 
 - [Coral EdgeTPU](#edge-tpu-detector): The Google Coral EdgeTPU is available in USB, Mini PCIe, and m.2 formats allowing for a wide range of compatibility with devices.
-- [Hailo](#hailo): The Hailo-8, Hailo-8L and Hailo-8R AI Acceleration modules are available in m.2 format with a HAT for RPi devices, offering a wide range of compatibility with devices.
+- [Hailo](#hailo-8): The Hailo8 and Hailo8L AI Acceleration module is available in m.2 format with a HAT for RPi devices, offering a wide range of compatibility with devices.
 - <CommunityBadge /> [MemryX](#memryx-mx3): The MX3 Acceleration module is available in m.2 format, offering broad compatibility across various platforms.
-- <CommunityBadge /> [DEEPX](#deepx-npu): The DEEPX NPU is available in m.2 format and as a HAT+ for the Raspberry Pi 5, offering broad compatibility across various platforms.
 
 **AMD**
 
@@ -135,7 +134,7 @@ Along with picking a detector for your hardware, you will choose a model's **inp
 
 **Resolution (320x320 vs 640x640):** Frigate is optimized for `320x320` models, and `320x320` is the best choice for the vast majority of setups. Frigate is specifically designed to compensate for the smaller model by cropping a region of motion from the full frame and zooming into it before running detection, so a `320x320` model is actually _better_ at small and distant objects, not worse. A `640x640` model is slower and uses more resources, and its main benefit is fitting more objects into a single inference when many objects are spread across a large area. Recent versions of Frigate have improved support for `640x640` models, but `320x320` remains the recommended starting point for nearly all setups.
 
-**Variant size (tiny/small/medium):** Larger variants are gradually more accurate but slower. Whether the difference is noticeable depends on your specific cameras and scenes. A good rule of thumb is to use the largest model your hardware can run without skipping detections, which you can monitor on the <NavPath path="Health and Metrics > Cameras" /> page in the UI. Better accuracy only helps if your detector keeps up with the detection load across all cameras.
+**Variant size (tiny/small/medium):** Larger variants are gradually more accurate but slower. Whether the difference is noticeable depends on your specific cameras and scenes. A good rule of thumb is to use the largest model your hardware can run without skipping detections, which you can monitor on the <NavPath path="System > Metrics > Cameras" /> page in the UI. Better accuracy only helps if your detector keeps up with the detection load across all cameras.
 
 **Acceptable inference time depends on your hardware.** Inference time alone does not tell the whole story, because different hardware has different capacity. A GPU can run multiple instances of the same model concurrently, so an inference time around 30ms can still keep up with several cameras. A Google Coral runs only a single instance of the model, so it needs a much lower inference time (around 10ms) to keep up.
 
@@ -286,9 +285,9 @@ models:
 
 ---
 
-## Hailo
+## Hailo-8
 
-This detector is available for use with the Hailo-8, Hailo-8L and Hailo-8R AI Acceleration Modules. The integration identifies which of them is attached and selects the matching default model if no custom model is specified.
+This detector is available for use with both Hailo-8 and Hailo-8L AI Acceleration Modules. The integration automatically detects your hardware architecture via the Hailo CLI and selects the appropriate default model if no custom model is specified.
 
 See the [installation docs](../frigate/installation.md#hailo-8) for information on configuring the Hailo hardware.
 
@@ -298,22 +297,16 @@ If no custom model is provided, the Hailo detector downloads a default model fro
 
 :::
 
-:::info
-
-The HailoRT runtime is not part of the Frigate image. It is downloaded and installed into `/config/.local` the first time a Hailo detector is configured, verified against pinned checksums, and updated automatically when a Frigate release pins a new version. If the container has no internet access, see [Detector runtimes](/frigate/network_requirements#detector-runtimes) for how to provide the files yourself.
-
-:::
-
 ### Configuration {#configuration-hailo}
 
 When configuring the Hailo detector, you have two options to specify the model: a local **path** or a **URL**.
 If both are provided, the detector will first check for the model at the given local path. If the file is not found, it will download the model from the specified URL. The model file is cached under `/config/model_cache/hailo`.
 
-<ModelConfigDropdown detectorTitle="Hailo" models={objectDetectorsModels.hailo.models} />
+<ModelConfigDropdown detectorTitle="Hailo-8/Hailo-8L" models={objectDetectorsModels.hailo8l.models} />
 
 For additional ready-to-use models, please visit: https://github.com/hailo-ai/hailo_model_zoo
 
-Hailo supports all models in the Hailo Model Zoo that include HailoRT post-processing. You're welcome to choose any of these pre-configured models for your implementation.
+Hailo8 supports all models in the Hailo Model Zoo that include HailoRT post-processing. You're welcome to choose any of these pre-configured models for your implementation.
 
 > **Note:**
 > The config.path parameter can accept either a local file path or a URL ending with .hef. When provided, the detector will first check if the path is a local file path. If the file exists locally, it will use it directly. If the file is not found locally or if a URL was provided, it will attempt to download the model from the specified URL.
@@ -345,8 +338,6 @@ models:
 
 ### Intel NPU host requirements {#intel-npu-requirements}
 
-The NPU device must be passed into the container by adding `/dev/accel:/dev/accel` to the `devices` section of your compose file. Frigate grants the runtime user access to the device automatically; see [hardware device access](/configuration/non_root#hardware-device-access) if you manage device permissions yourself.
-
 The NPU firmware is loaded by the host kernel and is not part of the Frigate image. Everything else the NPU needs is bundled in the container, so host NPU libraries should never be mounted in.
 
 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.
@@ -363,7 +354,7 @@ Intel NPUs cannot be used under Home Assistant OS, which does not include the NP
 
 :::warning
 
-The Apple Silicon detector client is being reworked. Its extra options no longer have a place in the config, so only the endpoint carried in the device string is honored right now, and `request_timeout_ms` and `linger_ms` are ignored. Anything else is dropped when your config is migrated.
+The network-based detectors (Deepstack and the Apple Silicon client) are being reworked. Their extra options no longer have a place in the config, so only the endpoint carried in the device string is honored right now: Deepstack ignores `api_key` and `api_timeout`, and the Apple Silicon client ignores `request_timeout_ms` and `linger_ms`. Anything else is dropped when your config is migrated.
 
 :::
 
@@ -541,6 +532,30 @@ A TensorFlow Lite model is provided in the container at `/cpu_model.tflite` and
 
 When using CPU detectors, you can add one CPU detector per camera. Adding more detectors than the number of cameras should not improve performance.
 
+## Deepstack / CodeProject.AI Server Detector
+
+:::warning
+
+The network-based detectors (Deepstack and the Apple Silicon client) are being reworked. Their extra options no longer have a place in the config, so only the endpoint carried in the device string is honored right now: Deepstack ignores `api_key` and `api_timeout`, and the Apple Silicon client ignores `request_timeout_ms` and `linger_ms`. Anything else is dropped when your config is migrated.
+
+:::
+
+The Deepstack / CodeProject.AI Server detector for Frigate allows you to integrate Deepstack and CodeProject.AI object detection capabilities into Frigate. CodeProject.AI and DeepStack are open-source AI platforms that can be run on various devices such as the Raspberry Pi, Nvidia Jetson, and other compatible hardware. It is important to note that the integration is performed over the network, so the inference times may not be as fast as native Frigate detectors, but it still provides an efficient and reliable solution for object detection and tracking.
+
+### Setup {#setup-deepstack}
+
+To get started with CodeProject.AI, visit their [official website](https://www.codeproject.com/Articles/5322557/CodeProject-AI-Server-AI-the-easy-way) to follow the instructions to download and install the AI server on your preferred device. Detailed setup instructions for CodeProject.AI are outside the scope of the Frigate documentation.
+
+To integrate CodeProject.AI into Frigate, configure the detector as follows:
+
+### Configuration {#configuration-deepstack}
+
+<ModelConfigDropdown detectorTitle="DeepStack" models={objectDetectorsModels.deepstack.models} />
+
+Replace `<your_codeproject_ai_server_ip>` and `<port>` with the IP address and port of your CodeProject.AI server.
+
+To verify that the integration is working correctly, start Frigate and observe the logs for any error messages related to CodeProject.AI. Additionally, you can check the Frigate web interface to see if the objects detected by CodeProject.AI are being displayed and tracked properly.
+
 # Community Supported Detectors
 
 ## MemryX MX3
@@ -551,12 +566,6 @@ See the [installation docs](../frigate/installation.md#memryx-mx3) for informati
 
 To configure a MemryX detector, simply set the `type` attribute to `memryx` and follow the configuration guide below.
 
-:::info
-
-The MemryX SDK is not part of the Frigate image. It is downloaded and installed into `/config/.local` the first time a MemryX detector is configured, verified against pinned checksums, and updated automatically when a Frigate release pins a new version. If the container has no internet access, see [Detector runtimes](/frigate/network_requirements#detector-runtimes) for how to provide the files yourself.
-
-:::
-
 ### Configuration {#configuration-memryx}
 
 <ModelConfigDropdown detectorTitle="MemryX" models={objectDetectorsModels.memryx.models} />
@@ -613,63 +622,6 @@ For detailed instructions on compiling models, refer to the [MemryX Compiler](ht
 
 ---
 
-## DEEPX NPU
-
-This detector is available for use with the DEEPX NPU, both the DX-M1 M.2 module and the DX-M1M on the Sixfab AI HAT+ for the Raspberry Pi 5. The configuration below applies unchanged to either form factor. DEEPX NPU support in Frigate is developed and maintained by [Sixfab](https://sixfab.com).
-
-See the [installation docs](../frigate/installation.md#deepx-npu) for information on installing the DEEPX kernel driver and runtime on the host and passing the NPU through to the container.
-
-To run a model on a DEEPX NPU, list a `deepx` device on that model.
-
-:::info
-
-The DX-RT Python bindings are not part of the Frigate image. They are downloaded and installed into `/config/.local` the first time a DEEPX device is configured, verified against pinned checksums, and updated automatically when a Frigate release pins a new version. If the container has no internet access, see [Detector runtimes](/frigate/network_requirements#detector-runtimes) for how to provide the files yourself.
-
-:::
-
-### Configuration {#configuration-deepx}
-
-<ModelConfigDropdown detectorTitle="DEEPX" models={objectDetectorsModels.deepx.models} />
-
-Frigate does not bundle a model for this detector. Models must be compiled to DEEPX's `.dxnn` format. Two model types are supported:
-
-- `yolo-generic` for YOLO object detection models, the recommended default. The detector reads the model's output layout from the compiled file, so anchor-based, anchor-free and NMS-in-head models all work with the same configuration, as do models compiled with DEEPX's Post-Processing Unit (PPU) support.
-- `yolox` for YOLOX models compiled without PPU support, whose raw head needs Frigate's YOLOX decoder. A YOLOX model compiled with PPU support works under either `yolox` or `yolo-generic`.
-
-The quickest way to get one is the [DEEPX ModelZoo](https://developer.deepx.ai/modelzoo), which publishes pre-compiled `.dxnn` files for a range of YOLO object detection models. Download the `.dxnn`, bind-mount it into the container, and point the model's `path` at it. Alternatively, compile your own model with the DX-COM compiler. The recommended starting point is `yolox-s_640x640_ppu.dxnn`, the fastest ModelZoo model measured through Frigate:
-
-```yaml
-models:
-  - devices:
-      - deepx:PCIe:0
-    path: /config/model_cache/deepx/yolox-s_640x640_ppu.dxnn
-    labelmap_path: /labelmap/coco-80.txt
-    model_type: yolo-generic
-    width: 640
-    height: 640
-```
-
-For PPU models, use a `.dxnn` compiled with DX-COM 2.4.0 or later. Frigate reads the PPU head layout the compiler writes into the file and refuses to load a PPU model without it.
-
-`model_type` must be set to `yolo-generic` or `yolox` to match the model; `yolo-generic` is the recommended default unless the model is a raw YOLOX export. Frigate defaults it to `ssd`, which this detector does not support, so the detector refuses to start on a model that leaves it unset.
-
-`width` and `height` must match the resolution the model was compiled for. Quantization parameters are baked into the `.dxnn` file at compile time, so no normalization is applied on the host and Frigate's default `input_tensor`, `input_pixel_format`, and `input_dtype` values do not need to be overridden.
-
-A DEEPX device is `PCIe:<index>`, as reported on the detector settings page. The NPU daemon multiplexes across processes, so the same device may be listed more than once to run additional inference processes against it:
-
-```yaml
-models:
-  - devices:
-      - deepx:PCIe:0
-      - deepx:PCIe:0
-```
-
-#### Label maps
-
-The object detection models in the DEEPX ModelZoo are trained on the standard 80-class COCO label set, so `labelmap_path` must be set to `/labelmap/coco-80.txt`. Frigate's default label map uses an extended 91-class COCO scheme, and leaving it in place will cause detections to be reported as the wrong object type. For `yolo-generic` models the label map is also what the detector uses to tell the output layout, so a label map with the wrong number of classes is reported as an error at startup.
-
----
-
 ## NVidia TensorRT Detector
 
 Nvidia Jetson devices may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the `-tensorrt-jp6` tag suffix, e.g. `ghcr.io/blakeblackshear/frigate:stable-tensorrt-jp6`. This detector is designed to work with Yolo models for object detection.
@@ -874,12 +826,6 @@ The AXEngine detector downloads its default model from HuggingFace on first star
 
 :::
 
-:::info
-
-The AXEngine python package is not part of the Frigate image. It is downloaded and installed into `/config/.local` the first time an AXEngine detector is configured, verified against a pinned checksum, and updated automatically when a Frigate release pins a new version. If the container has no internet access, see [Detector runtimes](/frigate/network_requirements#detector-runtimes) for how to provide the file yourself.
-
-:::
-
 ### Configuration {#configuration-axengine}
 
 When configuring the AXEngine detector, you have to specify the model name.

docs/docs/configuration/record.md

@@ -9,7 +9,7 @@ import NavPath from "@site/src/components/NavPath";
 
 Recordings can be enabled and are stored at `/media/frigate/recordings`. The folder structure for the recordings is `YYYY-MM-DD/HH/<camera_name>/MM.SS.mp4` in **UTC time**. These recordings are written directly from your camera stream without re-encoding. Each camera supports a configurable retention policy. Frigate chooses the largest matching retention value between the recording retention and the tracked object retention when determining if a recording should be removed.
 
-New recording segments are written from the camera stream to cache, they are only moved to disk if they pass a validation check and match the setup recording retention policy.
+New recording segments are written from the camera stream to cache, they are only moved to disk if they match the setup recording retention policy.
 
 :::tip
 
@@ -280,7 +280,6 @@ This configuration will retain recording segments that overlap with alerts and d
 In addition to the main recording stream, Frigate can record a second, lower quality stream for each camera. This serves two purposes:
 
 - **Quality selection during playback**: A quality selector (`Auto`, `Original`, or `Low`) appears in History view for cameras with sub stream recording enabled. `Original` and `Low` play only that stream's recordings. Time ranges where the selected stream has no footage are skipped during playback, and the selector notes when the selected stream has no recordings at all in the viewed time range. With `Auto` (the default), playback prefers the original quality and automatically falls back to the low quality stream when the connection cannot keep up, or for time ranges where the original recordings have expired. The selector shows each stream's video codec and audio details beneath the options; footage recorded by older Frigate versions shows no details.
-- **Quality selection when exporting**: A `Quality` selector (`Auto`, `Original`, or `Low`) is available for cameras with sub stream recording enabled. See [exporting](#exporting-a-camera-that-records-two-streams) for details on each option.
 - **Extended retention**: Sub stream recordings have their own retention settings, fully independent of the main recordings. By giving the low quality recordings a longer retention period, you can keep weeks or months of low quality history using a fraction of the storage, and that history remains playable after the main recordings expire. Playback falls back to the low quality recordings automatically, and the timeline shows a muted treatment for time ranges where only low quality footage remains. Timeline previews are kept for as long as either stream still has recordings, so scrubbing works across the whole retained history.
 
 ### Configuring sub stream recording
@@ -417,8 +416,7 @@ As a general rule, features that read recordings prefer the main stream and fall
 | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
 | Recording playback (History and Review)                                                  | Both (main preferred with sub fallback by default), or exactly one stream when a quality is selected manually |
 | Tracking details and Explore clip playback                                               | Main, falling back to sub where the main recordings have expired                                              |
-| Exports                                                                                  | Both (main preferred with sub fallback by default), or exactly one stream when a quality is selected in the export dialog |
-| Clip downloads                                                                           | Main; sub is used when no main recordings remain in the range (streams are never mixed in one file)           |
+| Exports and clip downloads                                                               | Main; sub is used when no main recordings remain in the range (streams are never mixed in one file)           |
 | Frames grabbed from a recording in History (download snapshot, submit frame to Frigate+) | Main preferred, sub fallback                                                                                  |
 | Audio extraction (e.g., transcription)                                                   | Main preferred, sub fallback                                                                                  |
 | Motion search                                                                            | Main only                                                                                                     |
@@ -450,7 +448,7 @@ For advanced use cases, the [custom export HTTP API](../integrations/api/export-
 POST /export/custom/{camera_name}/start/{start_time}/end/{end_time}
 ```
 
-The request body accepts `ffmpeg_input_args` and `ffmpeg_output_args` to control encoding, frame rate, filters, and other FFmpeg options. If neither is provided, Frigate defaults to time-lapse output settings (25x speed, 30 FPS) with audio removed (`-an`). When providing your own `ffmpeg_input_args`, include `-an` if you want audio stripped from the export.
+The request body accepts `ffmpeg_input_args` and `ffmpeg_output_args` to control encoding, frame rate, filters, and other FFmpeg options. If neither is provided, Frigate defaults to time-lapse output settings (25x speed, 30 FPS).
 
 The following example exports a time-lapse at 60x speed with 25 FPS:
 
@@ -501,7 +499,7 @@ Media files (event snapshots, event thumbnails, review thumbnails, previews, exp
 
 Normal operation may leave small numbers of orphaned files until Frigate's scheduled cleanup, but crashes, configuration changes, or upgrades may cause more orphaned files that Frigate does not clean up. This feature checks the file system for media files and removes any that are not referenced in the database.
 
-The Maintenance pane in the Frigate UI or an API endpoint `POST /api/media/sync` can be used to trigger a media sync. When using the API, a job ID is returned and the operation continues on the server. Status can be checked with the `/api/media/sync/status/{job_id}` endpoint. Results include the disk space reclaimed, or with `dry_run: true`, the space that would be reclaimed.
+The Maintenance pane in the Frigate UI or an API endpoint `POST /api/media/sync` can be used to trigger a media sync. When using the API, a job ID is returned and the operation continues on the server. Status can be checked with the `/api/media/sync/status/{job_id}` endpoint.
 
 Setting `verbose: true` writes a detailed report of every orphaned file and database entry to `/config/media_sync/<job_id>.txt`. For recordings, the report separates orphaned database entries (DB records whose files are missing from disk) from orphaned files (files on disk with no corresponding database record).
 
@@ -517,7 +515,7 @@ The storage usage Frigate reports will not exactly match what the operating syst
 
 ### How Frigate measures recording usage
 
-The **Recordings** value on the Storage Metrics page (<NavPath path="Health and Metrics > Storage" />), and the per-camera **Camera Storage** breakdown, is the sum of the recording segment sizes Frigate has written, taken from Frigate's database. It is **not** computed by a scan of the disk. Frigate tracks usage this way by design: repeatedly walking the entire drive to total its size would keep hard drives spun up and add unnecessary I/O.
+The **Recordings** value on the Storage Metrics page (<NavPath path="System > Storage" />), and the per-camera **Camera Storage** breakdown, is the sum of the recording segment sizes Frigate has written, taken from Frigate's database. It is **not** computed by a scan of the disk. Frigate tracks usage this way by design: repeatedly walking the entire drive to total its size would keep hard drives spun up and add unnecessary I/O.
 
 The disk **total** shown beside it, and the free-space figure Frigate uses to decide when to delete recordings, instead come from the operating system's report for the whole filesystem mounted at `/media/frigate`. As a result, the **Unused** value on the page is _total disk capacity minus Frigate's recordings_, not the drive's real free space, which will be lower whenever anything else is stored on the disk.
 

docs/docs/configuration/restream.md

@@ -197,7 +197,7 @@ For cameras that support two-way talk, go2rtc will automatically establish an au
 To prevent this, you must configure two separate stream instances:
 
 1. One stream instance with `#backchannel=0` for Frigate's viewing, recording, and detection (prevents go2rtc from establishing the blocking backchannel)
-2. A second stream instance with no `#` parameters at all for two-way talk functionality (can be used by Frigate's WebRTC viewer or other applications)
+2. A second stream instance without `#backchannel=0` for two-way talk functionality (can be used by Frigate's WebRTC viewer or other applications)
 
 Configuration example:
 
@@ -215,8 +215,6 @@ In this configuration:
 - `front_door` stream is used by Frigate for viewing, recording, and detection. The `#backchannel=0` parameter prevents go2rtc from establishing the audio output backchannel, so it won't block two-way talk access.
 - `front_door_twoway` stream is used for two-way talk functionality. This stream can be used by Frigate's WebRTC viewer when two-way talk is enabled, or by other applications (like Home Assistant Advanced Camera Card) that need access to the camera's audio output channel.
 
-Any `#` parameter on a bare `rtsp://` source disables the backchannel unless the URL explicitly contains `#backchannel=1`. A two-way talk stream with something like `#video=h264` on it silently loses two-way audio, and Frigate will report that two-way talk is unavailable for that stream.
-
 ## Security: Restricted Stream Sources
 
 For security reasons, the `echo:`, `expr:`, and `exec:` stream sources are disabled by default in go2rtc. These sources allow arbitrary command execution and can pose security risks if misconfigured.

docs/docs/configuration/tls.md

@@ -9,7 +9,7 @@ import NavPath from "@site/src/components/NavPath";
 
 # TLS
 
-Frigate's integrated NGINX server supports TLS certificates. By default Frigate will generate a self signed certificate that will be used for port 8971, stored in `/config/tls` so it survives container recreation. Frigate is designed to make it easy to use whatever tool you prefer to manage certificates.
+Frigate's integrated NGINX server supports TLS certificates. By default Frigate will generate a self signed certificate that will be used for port 8971. Frigate is designed to make it easy to use whatever tool you prefer to manage certificates.
 
 Frigate is often running behind a reverse proxy that manages TLS certificates for multiple services. You will likely need to set your reverse proxy to allow self signed certificates or you can disable TLS in Frigate's config. However, if you are running on a dedicated device that's separate from your proxy or if you expose Frigate directly to the internet, you may want to configure TLS with valid certificates.
 
@@ -45,9 +45,7 @@ frigate:
   ...
 ```
 
-Within the folder, the private key is expected to be named `privkey.pem` and the certificate is expected to be named `fullchain.pem`. Mounted certificates take precedence over the self signed pair in `/config/tls`.
-
-`privkey.pem` must be readable by the runtime user that runs NGINX. Frigate hands it over at startup when the mount is writable; on a `:ro` mount, make it readable by uid 1000 (or your `PUID`) yourself. See [Running as a non-root user](/configuration/non_root).
+Within the folder, the private key is expected to be named `privkey.pem` and the certificate is expected to be named `fullchain.pem`.
 
 Note that certbot uses symlinks, and those can't be followed by the container unless it has access to the targets as well, so if using certbot you'll also have to mount the `archive` folder for your domain, e.g.:
 
@@ -61,7 +59,7 @@ frigate:
 
 ```
 
-Frigate automatically compares the fingerprint of the certificate it loaded, from either location, against the fingerprint of the TLS cert in NGINX every minute. If these differ, the NGINX config is reloaded to pick up the updated certificate.
+Frigate automatically compares the fingerprint of the certificate at `/etc/letsencrypt/live/frigate/fullchain.pem` against the fingerprint of the TLS cert in NGINX every minute. If these differ, the NGINX config is reloaded to pick up the updated certificate.
 
 If you issue Frigate valid certificates you will likely want to configure it to run on port 443 so you can access it without a port number like `https://your-frigate-domain.com` by mapping 8971 to 443.
 
@@ -75,4 +73,4 @@ frigate:
 
 ## ACME Challenge
 
-Frigate also supports hosting the acme challenge files for the HTTP challenge method if needed. The challenge files should be mounted at `/etc/letsencrypt/www`. With a read-only root filesystem this has to be a mounted volume, since Frigate cannot create the directory itself.
+Frigate also supports hosting the acme challenge files for the HTTP challenge method if needed. The challenge files should be mounted at `/etc/letsencrypt/www`.

docs/docs/development/contributing.md

@@ -204,20 +204,11 @@ Light guidelines and advice:
 npm run lint
 ```
 
-- Ensure the backend [unit tests](#unit-tests) pass. Your PR cannot be merged unless tests pass.
-
-```shell
-python3 -u -m unittest
-```
-
-- Ensure the end-to-end tests pass. They run in Playwright against a production build with mocked API data, so they don't need a running Frigate instance. Add or update tests in `web/e2e/specs/` when you change UI behavior.
+- Add to unit tests and ensure they pass. As much as possible, you should strive to _increase_ test coverage whenever making changes. This will help ensure features do not accidentally become broken in the future.
+- If you run into error messages like "TypeError: Cannot read properties of undefined (reading 'context')" when running tests, this may be due to these issues (https://github.com/vitest-dev/vitest/issues/1910, https://github.com/vitest-dev/vitest/issues/1652) in vitest, but I haven't been able to resolve them.
 
 ```console
-# First-time setup
-npx playwright install chromium
-
-# Build the app and run all tests
-npm run e2e:build && npm run e2e
+npm run test
 ```
 
 - Test in different browsers. Firefox, Chrome, and Safari all have different quirks that make them unique targets to interact with.

docs/docs/frigate/hardware.md

@@ -54,7 +54,7 @@ Frigate supports multiple different detectors that work on different types of ha
 
 **Most Hardware**
 
-- [Hailo](#hailo-8): The Hailo-8, Hailo-8L and Hailo-8R AI Acceleration modules are available in m.2 format with a HAT for RPi devices offering a wide range of compatibility with devices.
+- [Hailo](#hailo-8): The Hailo8 and Hailo8L AI Acceleration module is available in m.2 format with a HAT for RPi devices offering a wide range of compatibility with devices.
   - [Supports many model architectures](../../configuration/object_detectors#configuration-hailo)
   - Runs best with tiny or small size models
 
@@ -65,11 +65,6 @@ Frigate supports multiple different detectors that work on different types of ha
   - [Supports many model architectures](../../configuration/object_detectors#memryx-mx3)
   - Runs best with tiny, small, or medium-size models
 
-- <CommunityBadge /> [DEEPX](#deepx-npu): The DEEPX NPU is available in m.2 format and as a HAT+ for the Raspberry Pi 5, allowing for a wide range of compatibility with devices.
-  - [Supports YOLO model architectures](../../configuration/object_detectors#deepx-npu)
-  - Runs best with tiny or small size models
-  - Runs efficiently on low power hardware
-
 **AMD**
 
 - [ROCm](#rocm---amd-gpu): ROCm can run on AMD Discrete GPUs to provide efficient object detection
@@ -116,13 +111,12 @@ Frigate supports multiple different detectors that work on different types of ha
 
 ### Hailo-8
 
-Frigate supports the Hailo-8, Hailo-8L and Hailo-8R AI Acceleration Modules on compatible hardware platforms, including the Raspberry Pi 5 with the PCIe hat from the AI kit. The Hailo detector integration in Frigate identifies which of them is attached and selects the matching default model when a custom model isn’t provided.
+Frigate supports both the Hailo-8 and Hailo-8L AI Acceleration Modules on compatible hardware platforms, including the Raspberry Pi 5 with the PCIe hat from the AI kit. The Hailo detector integration in Frigate automatically identifies your hardware type and selects the appropriate default model when a custom model isn’t provided.
 
 **Default Model Configuration:**
 
-- **Hailo-8L:** Default model is **YOLOv6n**, compiled for the Hailo-8L.
-- **Hailo-8:** Default model is **YOLOv6n**, compiled for the Hailo-8.
-- **Hailo-8R:** Default model is the **Hailo-8** build of **YOLOv6n**, since the Hailo Model Zoo publishes no Hailo-8R build.
+- **Hailo-8L:** Default model is **YOLOv6n**.
+- **Hailo-8:** Default model is **YOLOv6n**.
 
 In real-world deployments, even with multiple cameras running concurrently, Frigate has demonstrated consistent performance. Testing on x86 platforms, with dual PCIe lanes, yields further improvements in FPS, throughput, and latency compared to the Raspberry Pi setup.
 
@@ -262,32 +256,6 @@ The MX3 is a pipelined architecture, where the maximum frames per second support
 
 Inference speeds may vary depending on the host platform. The above data was measured on an **Intel 13700 CPU**. Platforms like Raspberry Pi, Orange Pi, and other ARM-based SBCs have different levels of processing capability, which may limit total FPS.
 
-### DEEPX NPU
-
-Frigate supports the DEEPX NPU in both of its form factors: the **DX-M1** M.2 module, which works on x86 (Intel/AMD) and ARM-based SBCs such as the Raspberry Pi 5, and the **DX-M1M** on the [Sixfab AI HAT+](https://docs.sixfab.com/docs/ai-hat-plus-raspberry-pi-5-quickstart) for the Raspberry Pi 5. Both use the same driver and runtime, so the configuration is identical for either one. DEEPX NPU support in Frigate is developed and maintained by [Sixfab](https://sixfab.com).
-
-The DEEPX driver and runtime run on the Docker host rather than inside the Frigate container and must be installed before the NPU can be used. See the [installation docs](installation.md#deepx-npu) for the setup steps and [the detector docs](/configuration/object_detectors#deepx-npu) for the configuration.
-
-Frigate does not bundle a model for this detector. Models use DEEPX's `.dxnn` format, and pre-compiled YOLO models can be downloaded from the [DEEPX ModelZoo](https://developer.deepx.ai/modelzoo). Prefer a model with a `_ppu` suffix whenever one is available for the architecture you want: these run part of the post-processing on the NPU itself and are considerably faster, roughly 2.5x for the same architecture and input size. **YOLOX-S with PPU is the recommended starting point.**
-
-Inference times for a few recommended models, measured through Frigate's own stats on a DX-M1:
-
-| Model             | Input Size | DX-M1 Inference Time |
-| ----------------- | ---------- | -------------------- |
-| YOLOX-S (PPU)     | 640        | ~ 13 ms              |
-| YOLOv9-t (PPU)    | 640        | ~ 18 ms              |
-| YOLOv4 (PPU)      | 512        | ~ 20 ms              |
-| YOLOX-S           | 640        | ~ 34 ms              |
-| YOLOv9-s          | 640        | ~ 39 ms              |
-
-Other ModelZoo YOLO variants are also supported but have not been measured. Inference speeds vary with the host platform, so a slower host such as a Raspberry Pi 5 will report higher times than those above.
-
-:::note
-
-A few ModelZoo models can not be used with Frigate: SSD models (they are trained on Pascal VOC, so their labels do not match Frigate's), DAMO-YOLO models, face and pose models, and the PPU builds of YOLOv7.
-
-:::
-
 ### Nvidia Jetson
 
 Jetson devices are supported via the TensorRT or ONNX detectors when running Jetpack 6. It will [make use of the Jetson's hardware media engine](/configuration/hardware_acceleration_video#nvidia-jetson) when configured with the [appropriate presets](/configuration/ffmpeg_presets#hwaccel-presets), and will make use of the Jetson's GPU and DLA for object detection when configured with the [TensorRT detector](/configuration/object_detectors#nvidia-tensorrt-detector).

docs/docs/frigate/installation.md

@@ -122,9 +122,7 @@ Additionally, the USB Coral draws a considerable amount of power. If using any o
 
 ### Hailo-8
 
-The Hailo-8, Hailo-8L and Hailo-8R AI accelerators are available in both M.2 and HAT form factors for the Raspberry Pi. The M.2 version typically connects to a carrier board for PCIe, which then interfaces with the Raspberry Pi 5 as part of the AI Kit. The HAT version can be mounted directly onto compatible Raspberry Pi models. Both form factors have been successfully tested on x86 platforms as well, making them versatile options for various computing environments.
-
-The HailoRT runtime is not part of the Frigate image; Frigate downloads and installs it at first start once a Hailo detector is configured. Containers without internet access can provide the files themselves, see [Detector runtimes](/frigate/network_requirements#detector-runtimes).
+The Hailo-8 and Hailo-8L AI accelerators are available in both M.2 and HAT form factors for the Raspberry Pi. The M.2 version typically connects to a carrier board for PCIe, which then interfaces with the Raspberry Pi 5 as part of the AI Kit. The HAT version can be mounted directly onto compatible Raspberry Pi models. Both form factors have been successfully tested on x86 platforms as well, making them versatile options for various computing environments.
 
 #### Installation
 
@@ -300,7 +298,7 @@ If you are using `docker run`, add this option to your command `--device /dev/ha
 
 #### Configuration
 
-Finally, configure [hardware object detection](/configuration/object_detectors#hailo) to complete the setup.
+Finally, configure [hardware object detection](/configuration/object_detectors#hailo-8) to complete the setup.
 
 ### MemryX MX3
 
@@ -317,8 +315,6 @@ The MemryX MX3 Accelerator is available in the M.2 2280 form factor (like an NVM
 
 To get started with MX3 hardware setup for your system, refer to the [Hardware Setup Guide](https://developer.memryx.com/2p1/get_started/install_hardware.html).
 
-The MemryX SDK used inside the container is not part of the Frigate image; Frigate downloads and installs it at first start once a MemryX detector is configured. Containers without internet access can provide the file themselves, see [Detector runtimes](/frigate/network_requirements#detector-runtimes). The host side driver still has to be installed as described below.
-
 Then follow these steps for installing the correct driver/runtime configuration:
 
 1. Copy or download [this script](https://github.com/blakeblackshear/frigate/blob/dev/docker/memryx/user_installation.sh).
@@ -381,99 +377,6 @@ If you can't use Docker Compose, you can run the container with something simila
 
 Finally, configure [hardware object detection](/configuration/object_detectors#memryx-mx3) to complete the setup.
 
-### DEEPX NPU
-
-The DEEPX NPU is available in two form factors, and Frigate supports both:
-
-- **DX-M1** in the M.2 2280 form factor (like an NVMe SSD), for x86 (Intel/AMD) PCs, the Raspberry Pi 5, and other ARM SBCs with an exposed PCIe M.2 slot.
-- **DX-M1M** on the [Sixfab AI HAT+](https://docs.sixfab.com/docs/ai-hat-plus-raspberry-pi-5-quickstart), a HAT+ board that connects to the Raspberry Pi 5 over PCIe Gen 3 x1.
-
-Both present the NPU through the same PCIe driver and DX-RT runtime, so the setup below and the detector configuration are identical for either one. Nothing needs to change when moving between them.
-
-DEEPX NPU support in Frigate is developed and maintained by [Sixfab](https://sixfab.com).
-
-#### Versions
-
-A DEEPX install has several separately versioned pieces, and they all have to agree. The driver, the runtime, and the daemon live on the Docker host; Frigate itself carries only the Python bindings, which it downloads on first start:
-
-| Component      | Version  | Installed on | Installed by              |
-| -------------- | -------- | ------------ | ------------------------- |
-| Kernel driver  | `v2.6.0` | Host  | `user_installation.sh`    |
-| DX-RT runtime  | `v3.4.0` | Host  | `user_installation.sh`    |
-| NPU firmware   | `v2.7.4` | The module   | Flashed from the host     |
-| DX-RT bindings | `v3.4.0` | Frigate      | Downloaded at first start |
-
-:::warning
-
-A version mismatch does not produce a startup error. It typically shows up as inference requests that are accepted but never return a result, so detections simply stop appearing while Frigate looks healthy. If that happens after a Frigate upgrade, check every version in the table before anything else.
-
-:::
-
-The installation script installs the DX-RT runtime on the host and enables `dxrt.service`, so the daemon starts at boot and any other program on the host can share the NPU with Frigate. Check the firmware version with `dxrt-cli --status` and update the module if it does not match the table above.
-
-#### Installation
-
-The DEEPX kernel driver must be installed on the host rather than in the container, because containers share the host kernel and cannot load kernel modules. Installing it creates the `/dev/dxrt*` device nodes that are passed through to Frigate. The same script installs the DX-RT runtime and enables `dxrt.service`, the daemon that owns the NPU and hands work to it on behalf of Frigate and anything else on the host.
-
-1. Copy or download [this script](https://github.com/blakeblackshear/frigate/blob/dev/docker/deepx/user_installation.sh).
-2. Ensure it has execution permissions with `sudo chmod +x user_installation.sh`
-3. Run the script with `./user_installation.sh`
-4. **Restart your computer** to complete driver installation.
-
-Confirm the NPU is visible before continuing:
-
-```bash
-ls /dev/dxrt*
-```
-
-Then confirm the daemon is running and listening in `/run/dxrt`:
-
-```bash
-systemctl is-active dxrt.service
-ls /run/dxrt/
-```
-
-#### Setup
-
-To set up Frigate, follow the default installation instructions, for example: `ghcr.io/blakeblackshear/frigate:stable`
-
-#### Docker configuration
-
-Frigate needs the NPU device node and the directory holding the daemon's socket:
-
-```yaml
-services:
-  frigate:
-    devices:
-      - /dev/dxrt0:/dev/dxrt0
-    volumes:
-      - /run/dxrt:/run/dxrt
-```
-
-If you can't use Docker Compose, add `--device /dev/dxrt0:/dev/dxrt0 -v /run/dxrt:/run/dxrt` to your `docker run` command.
-
-Add one `--device` per NPU, contiguously from `/dev/dxrt0`, since the client stops enumerating at the first gap.
-
-The installation script configures `dxrt.service` to place its socket in `/run/dxrt` through a systemd drop-in. Mounting the directory rather than the socket file means the container sees the new socket after `dxrt.service` is restarted, rather than holding on to a deleted one.
-
-`dxrtd` listens on an abstract socket as well, but that one does not cross into a container, so Frigate names the filesystem socket through `DXRT_DYNAMIC_IPC_ENDPOINT` on your behalf. Set that variable on the container yourself only if the daemon listens somewhere else, which means you also set it for `dxrtd` through its own systemd drop-in. The script writes `/etc/systemd/system/dxrt.service.d/frigate.conf` for exactly that, and has `dxrt.service` link the socket to `/tmp/dxrt_dynamic_ipc.sock` when it starts, so the host's own `dxrt-cli` and `dxtop` keep finding it at the default path they fall back to.
-
-:::note
-
-The DX-RT client exits when `dxrt.service` stops, so restart the Frigate container after restarting `dxrt.service`.
-
-:::
-
-The device node is needed as well as the socket, because the client opens the NPU directly even though the daemon arbitrates access. Without it, inference fails with `Device not found`.
-
-`/dev/shm` does not need sharing.
-
-The DX-RT python bindings are not shipped in the Frigate image. Frigate downloads them on first start when a DEEPX detector is configured, and caches them under `/config`.
-
-#### Configuration
-
-Finally, configure [hardware object detection](/configuration/object_detectors#deepx-npu) to complete the setup.
-
 ### Rockchip platform
 
 Make sure that you use a linux distribution that comes with the rockchip BSP kernel 5.10 or 6.1 and necessary drivers (especially rkvdec2 and rknpu). To check, enter the following commands:
@@ -576,8 +479,6 @@ Follow these steps for installation:
 
 To set up Frigate, follow the default installation instructions, for example: `ghcr.io/blakeblackshear/frigate:stable`
 
-The AXEngine python package is not part of the Frigate image; Frigate downloads and installs it at first start once an AXEngine detector is configured. Containers without internet access can provide the file themselves, see [Detector runtimes](/frigate/network_requirements#detector-runtimes).
-
 Next, grant Docker permissions to access your hardware by adding the following lines to your `docker-compose.yml` file:
 
 ```yaml
@@ -647,7 +548,9 @@ services:
 
 ### Recommended security options
 
-Frigate does not need elevated container privileges for most setups. The following hardens the container; add the `devices`/`group_add` entries your hardware requires (see the hardware acceleration docs):
+Frigate does not need elevated container privileges for most setups. The
+following hardens the container; add the `devices`/`group_add` entries your
+hardware requires (see the hardware acceleration docs):
 
 ```yaml
 services:
@@ -661,14 +564,15 @@ services:
 
 :::note
 
-`telemetry.stats.network_bandwidth` uses nethogs, which requires root with NET_ADMIN/NET_RAW capabilities. If you enable that stat, omit `cap_drop: [ALL]` or add `cap_add: [NET_ADMIN, NET_RAW]`.
+`telemetry.stats.network_bandwidth` uses nethogs, which requires root with
+NET_ADMIN/NET_RAW capabilities. If you enable that stat, omit `cap_drop: [ALL]`
+or add `cap_add: [NET_ADMIN, NET_RAW]`.
 
-Platforms that genuinely require `privileged: true` (MemryX, some QNAP setups) are called out in their own sections and are unaffected by this guidance.
+Platforms that genuinely require `privileged: true` (MemryX, some QNAP setups)
+are called out in their own sections and are unaffected by this guidance.
 
 :::
 
-Frigate's services run as an unprivileged user inside the container. See [Running as a non-root user](../configuration/non_root.md) for the run modes, the one time volume ownership migration, what each accelerator needs on the host, and the [hardened deployment](../configuration/non_root.md#hardened-deployment) layout with a read-only root filesystem.
-
 **Docker CLI**
 
 If you can't use Docker Compose, you can run the container with something similar to this:

docs/docs/frigate/network_requirements.md

@@ -47,7 +47,7 @@ If you are using one of the following hardware detectors and have not provided y
 | Detector                                                           | Model Downloaded     | Source                   |
 | ------------------------------------------------------------------ | -------------------- | ------------------------ |
 | [Rockchip RKNN](/configuration/object_detectors#rockchip-platform) | RKNN detection model | GitHub                   |
-| [Hailo 8 / 8L / 8R](/configuration/object_detectors#hailo)         | YOLOv6n (.hef)       | Hailo Model Zoo (AWS S3) |
+| [Hailo 8 / 8L](/configuration/object_detectors#hailo-8)            | YOLOv6n (.hef)       | Hailo Model Zoo (AWS S3) |
 | [AXERA AXEngine](/configuration/object_detectors)                  | Detection model      | HuggingFace              |
 
 :::note
@@ -56,24 +56,6 @@ The default CPU, EdgeTPU, and OpenVINO object detection models are bundled into
 
 :::
 
-### Detector Runtimes
-
-The SDKs for a few hardware detectors are not shipped in the Frigate image. They are downloaded the first time that detector is configured, verified against checksums pinned in the Frigate release, and installed into the Frigate user's home directory (`/config/.local` by default). Once installed they are not downloaded again until a Frigate release pins a new version.
-
-| Detector                                                   | Version | Files                                                                                                                                                                                 | Source                                                                                   |
-| ---------------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
-| [Hailo 8 / 8L / 8R](/configuration/object_detectors#hailo) | 4.21.0  | `hailort-debian12-amd64.tar.gz` and `hailort-4.21.0-cp311-cp311-linux_x86_64.whl` on x86, `hailort-debian12-arm64.tar.gz` and `hailort-4.21.0-cp311-cp311-linux_aarch64.whl` on arm64 | [GitHub release](https://github.com/frigate-nvr/hailort/releases/tag/v4.21.0)            |
-| [MemryX MX3](/configuration/object_detectors#memryx-mx3)   | 2.1.0   | `mx_accl_frigate-2.1.0.zip` (the release source archive, renamed)                                                                                                                     | [GitHub archive](https://github.com/memryx/mx_accl_frigate/archive/refs/tags/v2.1.0.zip) |
-| [AXERA AXEngine](/configuration/object_detectors#axera)    | 0.1.3   | `axengine-0.1.3-py3-none-any.whl`                                                                                                                                                     | [GitHub release](https://github.com/AXERA-TECH/pyaxengine/releases/tag/0.1.3-frigate)    |
-
-If the container cannot reach GitHub, provide the files yourself:
-
-1. Download the files for your architecture on a machine with internet access.
-2. Place them, with exactly the file names listed above, in `/config/model_cache/runtimes/<detector>/`, where `<detector>` is the detector named in your config's `devices` (`hailo`, `memryx`, or `axengine`).
-3. Start Frigate. Files whose checksum matches are installed without any download; a file with the wrong checksum is discarded and downloaded again, so a failed startup log names the file to replace.
-
-The `GITHUB_ENDPOINT` mirror variable below applies to these downloads as well.
-
 ### Preventing Model Downloads
 
 If you have already downloaded all required models and want to prevent Frigate from attempting any outbound connections to HuggingFace or the Transformers library, set the following environment variables on your Frigate container:
@@ -97,7 +79,7 @@ If your Frigate instance has restricted internet access, you can point model dow
 | Environment Variable                | Default                             | Used By                                       |
 | ----------------------------------- | ----------------------------------- | --------------------------------------------- |
 | `HF_ENDPOINT`                       | `https://huggingface.co`            | Semantic search, Sherpa-ONNX, AXEngine models |
-| `GITHUB_ENDPOINT`                   | `https://github.com`                | Face recognition, LPR, RKNN models, detector runtimes |
+| `GITHUB_ENDPOINT`                   | `https://github.com`                | Face recognition, LPR, RKNN models            |
 | `GITHUB_RAW_ENDPOINT`               | `https://raw.githubusercontent.com` | Bird classification                           |
 | `TF_KERAS_MOBILENET_V2_WEIGHTS_URL` | Unset (Keras uses its own default)  | Custom classification training                |
 
@@ -134,15 +116,6 @@ telemetry:
   version_check: false
 ```
 
-### Anonymous Analytics
-
-If [anonymous analytics](/configuration/advanced/analytics) sharing is turned on, Frigate sends one report a day to `https://analytics.frigate.video`. It's off by default, so no outbound connection happens unless you enable it:
-
-```yaml
-telemetry:
-  analytics: true
-```
-
 ### Push Notifications
 
 When [notifications](/configuration/notifications) are enabled and users have registered for push notifications in the web UI, Frigate sends push messages through the browser vendor's push service (e.g., Google FCM, Mozilla autopush). This requires internet access from the Frigate server to these push endpoints.
@@ -151,12 +124,16 @@ When [notifications](/configuration/notifications) are enabled and users have re
 
 If an [MQTT broker](/integrations/mqtt) is configured, Frigate maintains a connection to the broker's host and port. This is typically a local network connection, but will require internet if you use a cloud-hosted MQTT broker.
 
+### DeepStack / CodeProject.AI
+
+When using the [DeepStack detector plugin](/configuration/object_detectors), Frigate sends images to the configured API endpoint for inference. This is typically local but depends on where the service is hosted.
+
 ## WebRTC (STUN)
 
 For [WebRTC live streaming](/configuration/live), Frigate uses STUN for NAT traversal:
 
 - **go2rtc** defaults to a local STUN listener (`stun:8555`), no internet required.
-- **The web UI** uses the servers in `go2rtc.webrtc.ice_servers` for its WebRTC player and for the WebRTC connectivity check it runs when the Live view loads. If none are set, it uses Google's public STUN server (`stun:stun.l.google.com:19302`), which requires internet access from the browser. Set `ice_servers` to a STUN or TURN server on your network to avoid this.
+- **The web UI's WebRTC player** includes a fallback to Google's public STUN server (`stun:stun.l.google.com:19302`), which requires internet.
 
 ## Home Assistant Supervisor
 
@@ -179,7 +156,7 @@ To run Frigate in an air-gapped or offline environment:
 2. **Pre-download the training base weights**: If you plan to train custom classification models, set `TF_KERAS_MOBILENET_V2_WEIGHTS_URL` before training, then run one training job while online. Without this variable the base weights are cached outside `/config/` and are lost whenever the container is recreated, so a later training run will fail offline. If the machine never has internet access, copy the weights in manually as described below.
 3. **Disable version check**: Set `telemetry.version_check: false` in your configuration.
 4. **Block outbound model requests**: Set the `HF_HUB_OFFLINE=1` and `TRANSFORMERS_OFFLINE=1` environment variables to prevent HuggingFace and Transformers from attempting any network requests.
-5. **Avoid cloud features**: Do not configure Frigate+, Generative AI providers that require internet, or cloud MQTT brokers, and leave anonymous analytics off (its default).
+5. **Avoid cloud features**: Do not configure Frigate+, Generative AI providers that require internet, or cloud MQTT brokers.
 6. **Use local model mirrors**: If limited internet is available, set the `HF_ENDPOINT`, `GITHUB_ENDPOINT`, `GITHUB_RAW_ENDPOINT`, and `TF_KERAS_MOBILENET_V2_WEIGHTS_URL` environment variables to point to local mirrors.
 
 After these steps, Frigate will operate with no outbound internet connections.

docs/docs/frigate/updating.md

@@ -60,7 +60,7 @@ If you’re running Frigate via Docker (recommended method), follow these steps:
      ```bash
      docker logs frigate
      ```
-   - Visit the Frigate Web UI (default: `http://<your-ip>:5000`) to confirm the new version is running. The version number is displayed at the top of the Health and Metrics page.
+   - Visit the Frigate Web UI (default: `http://<your-ip>:5000`) to confirm the new version is running. The version number is displayed at the top of the System Metrics page.
 
 ### Notes
 

docs/docs/guides/getting_started.md

@@ -4,7 +4,6 @@ title: Getting started
 ---
 
 import ConfigTabs from "@site/src/components/ConfigTabs";
-import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 import NavPath from "@site/src/components/NavPath";
 
@@ -133,68 +132,21 @@ services:
       - "8554:8554" # RTSP feeds
 ```
 
-Now you should be able to start Frigate by running `docker compose up -d` from within the folder containing `docker-compose.yml`. On startup, an admin user and password will be created and outputted in the logs. You can see this by running `docker logs frigate`. Frigate should now be accessible at `https://server_ip:8971` where you can login with the `admin` user. With no cameras configured yet, the setup wizard runs on first login and walks you through the rest.
+Now you should be able to start Frigate by running `docker compose up -d` from within the folder containing `docker-compose.yml`. On startup, an admin user and password will be created and outputted in the logs. You can see this by running `docker logs frigate`. Frigate should now be accessible at `https://server_ip:8971` where you can login with the `admin` user and finish configuration using the Settings UI.
 
 ## Configuring Frigate
 
 This section assumes that you already have an environment setup as described in [Installation](../frigate/installation.md). You should also configure your cameras according to the [camera setup guide](/frigate/camera_setup). Pay particular attention to the section on choosing a detect resolution.
 
-<Tabs
-groupId="setup-method"
-defaultValue="wizard"
-values={[
-{ label: "Setup wizard", value: "wizard" },
-{ label: "Manual", value: "manual" },
-]}
-
-> <TabItem value="wizard">
-
-The first time you open Frigate with no cameras configured, the setup wizard walks you through the basics. Every step can be skipped, everything it sets can be changed later in Settings, and once you finish or dismiss it, it doesn't come back.
-
-:::note
-
-Frigate only sees hardware that has been passed into the container. If you plan to use a GPU, a Coral, or another accelerator, add the device to your `docker-compose.yml` and restart before running the wizard, otherwise it won't appear in the detection or hardware acceleration steps. The Manual tab shows the device entries for an Intel or AMD GPU and for a Coral, and the [hardware acceleration](../configuration/hardware_acceleration_video.md) and [object detectors](../configuration/object_detectors.md) docs cover the rest.
-
-:::
-
-**Account**
-
-Set a password for the `admin` account to replace the generated one from the logs, and add accounts for anyone else who needs access. This step is hidden if you have turned authentication off.
-
-**Add a camera**
-
-Opens the [Add Camera Wizard](../configuration/cameras.md#adding-a-camera-with-the-add-camera-wizard), which connects to the camera, tests each stream, and writes its configuration for you. You can add more than one before moving on.
-
-**Object detection**
-
-Lists the detection hardware Frigate found on your system, such as a Coral, an Intel GPU or NPU, or a discrete GPU, and configures the one you pick. NVIDIA and AMD GPUs need a model before detection can start, so the wizard offers your Frigate+ models if you have them, or lets you finish setup and add one later under <NavPath path="Settings > System > Detection models" />.
-
-**Hardware acceleration**
-
-Offers only the decoding methods your hardware supports. Auto picks one based on that hardware and the codec your camera sends, so a mixed h264 and h265 setup gets the right preset per camera.
-
-**Recording**
-
-Choose whether to record only when something is detected or around the clock, and how long to keep it.
-
-The last screen summarizes what was set up. If a step changed something that needs a restart, the button restarts Frigate and returns you to the Live view once it is back.
-
-The wizard configures the essentials only. Motion masks are not included and should be set up afterward, once you can identify the areas of the frame that trigger unwanted motion. See the [masks documentation](../configuration/masks.md). Zones, tracked object types, notifications, and MQTT are also configured in Settings.
-
-</TabItem>
-<TabItem value="manual">
-
-On a new install the setup wizard opens first. Click **Skip setup and configure manually** on its welcome screen to dismiss it, and the steps below apply. The wizard won't come back once dismissed.
-
-**Step 1: Start Frigate**
+### Step 1: Start Frigate
 
 At this point you should be able to start Frigate and a basic config will be created automatically.
 
-**Step 2: Add a camera**
+### Step 2: Add a camera
 
 Click the **Add Camera** button in <NavPath path="Settings > Global configuration > Camera management" /> to use the camera setup wizard to get your first camera added into Frigate. See [Adding a camera with the Add Camera Wizard](../configuration/cameras.md#adding-a-camera-with-the-add-camera-wizard) for a walkthrough of each step.
 
-**Step 3: Configure hardware acceleration (recommended)**
+### Step 3: Configure hardware acceleration (recommended)
 
 Now that you have a working camera configuration, set up hardware acceleration to minimize the CPU required to decode your video streams. See the [hardware acceleration](../configuration/hardware_acceleration_video.md) docs for examples applicable to your hardware.
 
@@ -238,7 +190,7 @@ cameras:
 </TabItem>
 </ConfigTabs>
 
-**Step 4: Configure detectors**
+### Step 4: Configure detectors
 
 By default, Frigate will use a single OpenVINO detector running on the CPU.
 
@@ -347,7 +299,7 @@ More details on available detectors can be found [here](../configuration/object_
 
 Restart Frigate and you should start seeing detections for `person`. If you want to track other objects, they can be configured in <NavPath path="Settings > Global configuration > Objects" /> or via the [configuration file reference](../configuration/advanced/reference.md).
 
-**Step 5: Setup motion masks**
+### Step 5: Setup motion masks
 
 Now that you have optimized your configuration for decoding the video stream, you will want to check to see where to implement motion masks. Click on the camera from the main dashboard, then select the gear icon in the top right, enable the [Debug view](/usage/live#the-single-camera-view), and finally enable the switch for Motion Boxes. Watch for areas that continuously trigger unwanted motion to be detected. Common areas to mask include camera timestamps and trees that frequently blow in the wind. The goal is to avoid wasting object detection cycles looking at these areas.
 
@@ -384,7 +336,7 @@ cameras:
           coordinates: "0,461,3,0,1919,0,1919,843,1699,492,1344,458,1346,336,973,317,869,375,866,432"
 ```
 
-**Step 6: Enable recordings**
+### Step 6: Enable recordings
 
 In order to review activity in the Frigate UI, recordings need to be enabled.
 
@@ -433,10 +385,7 @@ If you only plan to use Frigate for recording, it is still recommended to define
 
 By default, Frigate will retain video of all tracked objects for 10 days. The full set of options for recording can be found [here](../configuration/advanced/reference.md).
 
-</TabItem>
-</Tabs>
-
-### Complete config
+### Step 7: Complete config
 
 At this point you have a complete config with basic functionality.
 

docs/docs/plus/index.md

@@ -41,7 +41,7 @@ Rockchip models are automatically converted as of 0.17. For 0.16, YOLOv9 onnx mo
 
 ## Supported detector types
 
-Currently, Frigate+ models support CPU (`cpu`), Google Coral (`edgetpu`), OpenVino (`openvino`), ONNX (`onnx`), Hailo (`hailo`), and Rockchip (`rknn`) detectors.
+Currently, Frigate+ models support CPU (`cpu`), Google Coral (`edgetpu`), OpenVino (`openvino`), ONNX (`onnx`), Hailo (`hailo8l`), and Rockchip (`rknn`) detectors.
 
 | Hardware                                                                         | Recommended Detector Type | Recommended Model Type |
 | -------------------------------------------------------------------------------- | ------------------------- | ---------------------- |
@@ -50,7 +50,7 @@ Currently, Frigate+ models support CPU (`cpu`), Google Coral (`edgetpu`), OpenVi
 | [Intel](/configuration/object_detectors.md#openvino-detector)                    | `openvino`                | `yolov9`               |
 | [NVidia GPU](/configuration/object_detectors#onnx)                               | `onnx`                    | `yolov9`               |
 | [AMD ROCm GPU](/configuration/object_detectors#amdrocm-gpu-detector)             | `onnx`                    | `yolov9`               |
-| [Hailo8/Hailo8L/Hailo8R](/configuration/object_detectors#hailo)                  | `hailo`                   | `yolov9`               |
+| [Hailo8/Hailo8L/Hailo8R](/configuration/object_detectors#hailo-8)                | `hailo8l`                 | `yolov9`               |
 | [Rockchip NPU](/configuration/object_detectors#rockchip-platform)                | `rknn`                    | `yolov9`               |
 
 ## Improving your model

docs/docs/troubleshooting/common_errors.md

@@ -66,19 +66,17 @@ An FFmpeg message meaning it probed the stream but never saw enough decodable vi
 
 ## Recording
 
-<FaqItem id="no-new-recording-segments" question="No new recording segments were created (or: No new valid recording segments were created / No valid segments created since last invalid segment) for <camera> in the last 120s">
+<FaqItem id="no-new-recording-segments" question="No new recording segments were created for <camera> in the last 120s">
 
-Frigate's record watchdog is restarting the record FFmpeg process because the camera stopped producing usable recordings. The wording distinguishes the cases: `No new recording segments` means no new segment file reached the cache, so ffmpeg isn't getting video out of the record stream; the two `valid` variants mean recordings are arriving but keep failing validation. Either way the fault is on the camera or network side, and the restart is Frigate trying to recover.
+Frigate's record watchdog is restarting the record FFmpeg process because no valid segment has reached the cache. This means the record stream is not connecting or the segments are being rejected (see the audio-codec entry below).
 
-See [Recordings: no new recording segments were created](/troubleshooting/recordings#no-new-recording-segments-were-created).
+See [Recordings: the record stream isn't connecting](/troubleshooting/recordings#the-record-stream-isnt-connecting).
 
 </FaqItem>
 
-<FaqItem id="invalid-or-missing-video-stream-in-segment" question="Invalid or missing video stream in segment. Discarding. / Discarding a corrupt recording segment / Failed to probe corrupt segment / Invalid recording segment detected">
+<FaqItem id="invalid-or-missing-video-stream-in-segment" question="Invalid or missing video stream in segment. Discarding.">
 
-A cached recording segment failed validation and was deleted, either because it had no readable video stream or because its length was impossible. This nearly always means the camera stopped sending usable video partway through the segment: a camera that rebooted, dropped the connection, or ran out of simultaneous connections, or an unreliable link such as WiFi or a failing switch port. Broken camera timestamps (a "Smart Codec" / H.264+ mode) cause the corrupt-segment variants. The same stream failure trips the record watchdog, so the restarts above usually appear alongside these messages.
-
-See [Recordings: invalid or missing video stream in segment](/troubleshooting/recordings#invalid-or-missing-video-stream-in-segment).
+A cached recording segment failed validation (no readable video stream) and was deleted. The most common cause is a segment that was truncated because the record FFmpeg process was killed mid-write, so this often appears alongside, and as a consequence of, the record-stream restarts above. A segment containing only audio triggers it too.
 
 </FaqItem>
 

docs/docs/troubleshooting/faqs.md

@@ -39,20 +39,6 @@ To do this efficiently the following setup is required:
 
 When this is done correctly, the GPU will do the decoding and scaling which will result in a small increase in CPU usage but with better results.
 
-### How can I rotate my camera's video feed?
-
-Rotation is best done in the camera's firmware settings (usually called rotate, flip, or corridor mode) so the video arrives already rotated and no extra processing is needed. Check there first.
-
-If your camera does not support rotation, go2rtc's ffmpeg module can rotate the stream with the `#rotate` parameter (`90`, `180`, `270`, or `-90`), but this is not recommended: rotation requires transcoding (re-encoding) the video, which significantly increases CPU usage, especially for high resolution streams.
-
-```yaml
-go2rtc:
-  streams:
-    my_camera: "ffmpeg:rtsp://user:password@192.168.1.10:554/stream#video=h264#hardware#rotate=90"
-```
-
-Point the camera's inputs at the restream as described in the [restream docs](/configuration/restream.md), and swap `detect -> width` and `detect -> height` to match the rotated resolution.
-
 ### My mjpeg stream or snapshots look green and crazy
 
 This almost always means that the width/height defined for your camera are not correct. Double check the resolution with VLC or another player. Also make sure you don't have the width and height values backwards.
@@ -135,7 +121,7 @@ You can still configure Frigate to use UDP by using ffmpeg input args or the pre
 
 ### Frigate is slow to start up with a "probing detect stream" message in the logs
 
-When `detect.width` and `detect.height` are not set, Frigate probes each camera's detect stream on startup (and when saving the config) to auto-detect its resolution. For RTSP streams Frigate probes with ffprobe and automatically retries over TCP if UDP doesn't respond, with a 5 second timeout per attempt. A camera that cannot be reached over either transport will add up to ~10 seconds to startup before Frigate falls through with default dimensions, which may show up as width `0` and height `0` in Camera Probe Info under Health and Metrics.
+When `detect.width` and `detect.height` are not set, Frigate probes each camera's detect stream on startup (and when saving the config) to auto-detect its resolution. For RTSP streams Frigate probes with ffprobe and automatically retries over TCP if UDP doesn't respond, with a 5 second timeout per attempt. A camera that cannot be reached over either transport will add up to ~10 seconds to startup before Frigate falls through with default dimensions, which may show up as width `0` and height `0` in Camera Probe Info under System Metrics.
 
 To skip the probe entirely and make startup instant, set `detect.width` and `detect.height` explicitly in your camera config:
 
@@ -181,9 +167,3 @@ Frigate's object detection relies on a machine learning [model](../frigate/gloss
 - If the false positive is always in the same fixed spot (like a statue or mailbox that reads as a person), add an [object filter mask](../configuration/masks.md#object-filter-masks) over that location.
 
 Filters and masks only hide the incorrect result - they don't teach Frigate what the object actually is. For that, fine-tune your own model or use Frigate+.
-
-### Where do I see problems Frigate has detected?
-
-Open System > Health. The Notices list keeps a record of problems Frigate has found, and you can dismiss any entry to acknowledge it. Ongoing conditions, such as an offline camera or recordings deleted before their retention period, appear in the status bar for admins until they clear, and the status bar links to the Notices list while it has undismissed entries. On mobile, tap the warning icon in the bottom navigation bar to see them.
-
-The Hardware section below the notices shows whether the detection hardware, hardware acceleration, and enrichment devices in your config were found and are being used, so a GPU that silently fell back to the CPU shows up as a warning. Run stream checks to probe every camera's streams for the same problems the camera wizard reports.

docs/docs/troubleshooting/go2rtc.md

@@ -15,7 +15,7 @@ When a stream won't play or behaves oddly, the most important first step is to f
 
 ### 1. Read the go2rtc logs
 
-Access the go2rtc logs in the Frigate UI under <NavPath path="Logs" /> in the sidebar (select the **go2rtc** tab). If go2rtc cannot connect to your camera you will usually see a clear error here: `401 Unauthorized` (bad or incorrectly encoded credentials), `Connection refused` / `timeout` (wrong IP, port, or the camera is at its connection limit), or `404 Not Found` (wrong RTSP path, or the referenced stream name does not exist).
+Access the go2rtc logs in the Frigate UI under <NavPath path="System Logs" /> in the sidebar (select the **go2rtc** tab). If go2rtc cannot connect to your camera you will usually see a clear error here: `401 Unauthorized` (bad or incorrectly encoded credentials), `Connection refused` / `timeout` (wrong IP, port, or the camera is at its connection limit), or `404 Not Found` (wrong RTSP path, or the referenced stream name does not exist).
 
 ### 2. Test the stream in the go2rtc web interface
 
@@ -78,9 +78,7 @@ go2rtc:
 
 :::warning
 
-The transcoding modifiers (`#video=`, `#audio=`, `#hardware`, …) **only take effect on a source that is prefixed with `ffmpeg:`**. Adding them to a bare `rtsp://…#audio=opus` source does nothing: go2rtc ignores them. Likewise, when a source references another stream by name (e.g. `ffmpeg:back#audio=aac`), the name must match the stream key **exactly** (it is case sensitive), or the transcode is silently never produced. This is the single most common configuration mistake. In the Frigate UI, the **Use compatibility mode (ffmpeg)** toggle adds the `ffmpeg:` prefix for you.
-
-A bare `rtsp://` source reads a different set of modifiers: `#backchannel=`, `#media=`, `#timeout=`, and `#transport=`. These do nothing on an `ffmpeg:` source. Adding **any** modifier to a bare `rtsp://` source also disables the camera's backchannel unless the URL explicitly contains `#backchannel=1`, so a stream dedicated to two-way talk should carry no modifiers at all.
+The `#`-modifiers (`#video=`, `#audio=`, `#hardware`, `#backchannel=0`, …) **only take effect on a source that is prefixed with `ffmpeg:`**. Adding them to a bare `rtsp://…#audio=opus` source does nothing: go2rtc ignores them. Likewise, when a source references another stream by name (e.g. `ffmpeg:back#audio=aac`), the name must match the stream key **exactly** (it is case sensitive), or the transcode is silently never produced. This is the single most common configuration mistake. In the Frigate UI, the **Use compatibility mode (ffmpeg)** toggle adds the `ffmpeg:` prefix for you.
 
 :::
 
@@ -155,7 +153,7 @@ WebRTC is only attempted when MSE fails or when using a camera's two-way talk fe
 
 - **Codec mismatch**: WebRTC cannot carry H.265 or AAC. The stream backing the WebRTC view must provide Opus (or PCMA/PCMU) audio and H.264 video. Add an `ffmpeg:back#audio=opus` source as shown above.
 - **Port `8555` not reachable, or no candidates set**: WebRTC needs port `8555` (both TCP and UDP) open and a reachable candidate advertised. On Docker installs running on a custom/overlay network, go2rtc may advertise unreachable container IPs as ICE candidates; setting `webrtc.filters.candidates: []` and supplying only your host's LAN IP resolves this. See [WebRTC extra configuration](/configuration/live#webrtc-extra-configuration).
-- **Two-way talk** additionally requires a secure context (HTTPS or the authenticated port `8971`, because browsers block microphone access on plain HTTP). The camera's RTSP backchannel must also be handled correctly: go2rtc seizes the backchannel by default, which blocks two-way audio for other consumers and can inject static. Disable it on the primary stream with `#backchannel=0` and use a separate dedicated stream for talk, carrying no `#` modifiers of any kind, as documented in [preventing go2rtc from blocking two-way audio](/configuration/restream#two-way-talk-restream).
+- **Two-way talk** additionally requires a secure context (HTTPS or the authenticated port `8971`, because browsers block microphone access on plain HTTP). The camera's RTSP backchannel must also be handled correctly: go2rtc seizes the backchannel by default, which blocks two-way audio for other consumers and can inject static. Disable it on the primary stream with `#backchannel=0` and use a separate dedicated stream for talk, as documented in [preventing go2rtc from blocking two-way audio](/configuration/restream#two-way-talk-restream).
 
 ## High CPU usage
 

docs/docs/troubleshooting/recordings.md

@@ -209,50 +209,6 @@ If the record stream uses a "Smart Codec"/H.264+ mode or changes encoding parame
 
 </FaqItem>
 
-<FaqItem id="invalid-or-missing-video-stream-in-segment" question="I see the message: WARNING : Invalid or missing video stream in segment ... Discarding.">
-
-Every recording segment is validated before it leaves the cache. Frigate probes each finished `.mp4` in `/tmp/cache` and requires a readable video stream and a valid duration before moving to storage. A segment that fails is deleted, so those ~10 seconds of footage are lost. Three messages come from this check:
-
-- `Invalid or missing video stream in segment <path>. Discarding.` The segment holds no video, or could not be read at all.
-- `Failed to probe corrupt segment <path>` followed by `Discarding a corrupt recording segment: <path>`. The segment was read, but its length could not be determined.
-- `Discarding a corrupt recording segment: <path>` on its own. The segment's length is impossible (empty, or longer than ten minutes), which points at broken timestamps coming from the camera.
-
-For each one, the camera watchdog also logs `Invalid recording segment detected for <camera> at <timestamp>`.
-
-:::warning
-
-This is almost always a **camera or network problem**, not a Frigate one. A segment is only complete once ffmpeg has finished writing it, so anything that interrupts the stream partway through leaves behind a file that cannot be saved. Frigate is reporting the interruption, not causing it.
-
-:::
-
-#### Start with the camera and the network
-
-- **The camera dropped the connection.** Cameras reboot, reinitialize their stream when switching to night mode, and cut clients off when they are overloaded or out of simultaneous connections. Count everything pulling from the camera at once: Frigate's detect and record streams, go2rtc, a phone app, and any other NVR each use one. Routing all roles through a single [RTSP restream](/configuration/restream#reduce-connections-to-camera) so the camera only ever sees one connection often resolves this by itself.
-- **The link to the camera is unreliable.** WiFi cameras, powerline adapters, a saturated uplink, a failing switch port, or a marginal cable all produce this pattern, and usually only on one camera at a time. WiFi cameras are [not recommended](https://ipcamtalk.com/threads/multiple-cameras-high-bandwidth.77100/#post-861110).
-- **The camera cannot reliably send what it is being asked for.** A high bitrate 4K stream can be more than the camera's own hardware can encode and push out under load. Lower the bitrate, or record a lower-resolution profile.
-- **The camera is using a "Smart Codec", H.264+, or H.265+ mode.** These change encoding parameters mid-stream and produce the broken timestamps behind the corrupt-segment variant. Turn the mode off and set the camera's keyframe interval equal to its frame rate. See [Segments are only ~1 second long](#segments-are-only-1-second-long).
-
-Read the rest of the Frigate and/or go2rtc log around the **first** occurrence. When the camera or the network is at fault, other messages show up with it, such as `No frames received from <camera> in 20 seconds`, `Non-monotonic DTS`, `RTP: PT=xx: bad cseq`, `error while decoding MB`, or a connection timeout. Each of those is explained in [Common error messages](/troubleshooting/common_errors). To confirm the camera is the source, open its stream in the [go2rtc web interface](/troubleshooting/go2rtc) on port `1984` or play the same URL in VLC, and leave it running long enough for the failures to happen again.
-
-#### If the camera and network check out
-
-- **Audio the recording cannot store.** Some cameras send G.711 audio, which cannot be saved in an MP4 and stops segments from finalizing. See [Incompatible audio codec](#incompatible-audio-codec-recordings-silently-fail-to-save).
-- **Frigate itself was stopped or restarted.** A single warning per camera around a restart is expected and needs no action.
-- **The system ran out of room or memory.** A full `/tmp/cache`, or the host killing Frigate for using too much memory, cuts off the segment being written. Both leave other errors in the log alongside this one. See [No space left on device](#errno-28-no-space-left-on-device).
-
-</FaqItem>
-
-<FaqItem id="no-new-recording-segments-were-created" question="I see the message: ERROR : No new recording segments were created for <camera> in the last 120s. Restarting the ffmpeg record process...">
-
-When a camera stops producing usable recordings for two minutes, Frigate restarts that camera's record process to try to recover. The wording tells you how far the recordings got:
-
-- **`No new recording segments were created`**: no new segment file showed up in the cache at all, so ffmpeg isn't getting video out of the record stream. The camera is unreachable or refusing the connection, the stream URL, path, or credentials are wrong, or the camera accepted the connection and then sent nothing. See [The record stream isn't connecting](#the-record-stream-isnt-connecting).
-- **`No new valid recording segments were created`** and **`No valid segments created since last invalid segment`**: recordings are arriving, but they keep failing validation, so the camera is sending video that cannot be saved. See [Invalid or missing video stream in segment](#invalid-or-missing-video-stream-in-segment) above.
-
-The restart is Frigate recovering from a problem, not causing one. One of these after a camera reboot or a brief network drop is normal. Seeing them repeat every couple of minutes means the camera or the network is still failing, and the restarts can extend the damage, because each one cuts off the segment that was being written. Work from the earliest failure in that camera's log rather than from the restarts.
-
-</FaqItem>
-
 <FaqItem id="i-see-the-message-warning--unable-to-keep-up-with-recording-segments-in-cache-for-camera-keeping-the-5-most-recent-segments-out-of-6-and-discarding-the-rest" question="I see the message: WARNING : Unable to keep up with recording segments in cache for camera. Keeping the 5 most recent segments out of 6 and discarding the rest...">
 
 This warning means the recording maintainer cannot move recording segments from the RAM cache to disk fast enough. When the cache fills up, Frigate discards the oldest segments to avoid running out of memory and crashing, so you lose recorded footage. This is almost always a storage throughput or system resource problem. Work through the steps below to identify which.
@@ -374,7 +330,7 @@ If segments are only ~1 second instead of ~10 seconds, the camera is sending cor
 
 :::tip
 
-You don't have to run `ffprobe` by hand to catch this. Open a camera's **Camera Probe Info** dialog (the info icon on the Health and Metrics → Cameras page) and check the **Keyframe analysis** section. It probes the record stream and flags sparse or variable keyframes, which is what smart/"+" codecs (H.264+/H.265+) and long keyframe intervals produce.
+You don't have to run `ffprobe` by hand to catch this. Open a camera's **Camera Probe Info** dialog (the info icon on the System → Metrics → Cameras page) and check the **Keyframe analysis** section. It probes the record stream and flags sparse or variable keyframes, which is what smart/"+" codecs (H.264+/H.265+) and long keyframe intervals produce.
 
 :::
 

docs/package.json

@@ -18,17 +18,17 @@
     "write-heading-ids": "docusaurus write-heading-ids"
   },
   "dependencies": {
-    "@docusaurus/core": "^3.10.2",
-    "@docusaurus/plugin-content-docs": "^3.10.2",
-    "@docusaurus/preset-classic": "^3.10.2",
-    "@docusaurus/theme-mermaid": "^3.10.2",
+    "@docusaurus/core": "^3.7.0",
+    "@docusaurus/plugin-content-docs": "^3.7.0",
+    "@docusaurus/preset-classic": "^3.7.0",
+    "@docusaurus/theme-mermaid": "^3.7.0",
     "@inkeep/docusaurus": "^2.0.16",
     "@mdx-js/react": "^3.1.0",
     "@types/js-yaml": "^4.0.9",
     "clsx": "^2.1.1",
-    "docusaurus-plugin-openapi-docs": "^5.2.0",
-    "docusaurus-theme-openapi-docs": "^5.2.0",
-    "js-yaml": "^4.3.2",
+    "docusaurus-plugin-openapi-docs": "^4.5.1",
+    "docusaurus-theme-openapi-docs": "^4.5.1",
+    "js-yaml": "^4.1.1",
     "marked": "^16.4.2",
     "prism-react-renderer": "^2.4.1",
     "raw-loader": "^4.0.2",
@@ -48,11 +48,11 @@
     ]
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "^3.10.2",
-    "@docusaurus/types": "^3.10.2",
+    "@docusaurus/module-type-aliases": "^3.7.0",
+    "@docusaurus/types": "^3.7.0",
     "@types/react": "^18.3.27"
   },
   "engines": {
-    "node": ">=20.19"
+    "node": ">=18.0"
   }
 }

docs/sidebars.ts

@@ -122,7 +122,6 @@ const sidebars: SidebarsConfig = {
           "configuration/ffmpeg_presets",
           "configuration/pwa",
           "configuration/tls",
-          "configuration/non_root",
         ],
       },
       {
@@ -130,7 +129,6 @@ const sidebars: SidebarsConfig = {
         label: "Advanced Configuration",
         items: [
           "configuration/advanced/system",
-          "configuration/advanced/analytics",
           "configuration/advanced/reference",
           {
             type: "link",

docs/src/components/AnalyticsFields/index.jsx

@@ -1,60 +0,0 @@
-import React from "react";
-import schema from "@site/static/frigate-analytics-schema.json";
-
-function resolve(node) {
-  if (!node) return node;
-  if (node.$ref) return schema.$defs[node.$ref.split("/").pop()];
-  if (node.anyOf) {
-    const inner = node.anyOf.find((option) => option.type !== "null");
-    return inner ? resolve(inner) : node;
-  }
-  return node;
-}
-
-function rows(properties, prefix = "") {
-  return Object.entries(properties).flatMap(([name, field]) => {
-    const path = prefix ? `${prefix}.${name}` : name;
-    const row = {
-      path,
-      description: field.description,
-      isPublic: field["x-public"],
-    };
-    const target = resolve(field);
-
-    if (target?.properties) return [row, ...rows(target.properties, path)];
-
-    const values = resolve(target?.additionalProperties);
-    if (values?.properties)
-      return [row, ...rows(values.properties, `${path}.<key>`)];
-
-    const items = resolve(target?.items);
-    if (items?.properties) return [row, ...rows(items.properties, `${path}[]`)];
-
-    return [row];
-  });
-}
-
-export default function AnalyticsFields() {
-  return (
-    <table>
-      <thead>
-        <tr>
-          <th>Field</th>
-          <th>Description</th>
-          <th>Public</th>
-        </tr>
-      </thead>
-      <tbody>
-        {rows(schema.properties).map((row) => (
-          <tr key={row.path}>
-            <td>
-              <code>{row.path}</code>
-            </td>
-            <td>{row.description}</td>
-            <td>{row.isPublic ? "Yes" : "No"}</td>
-          </tr>
-        ))}
-      </tbody>
-    </table>
-  );
-}

docs/static/frigate-api.yaml

@@ -10,25 +10,6 @@ servers:
   - url: https://demo.frigate.video/api
   - url: http://localhost:5001/api
 paths:
-  /analytics/preview:
-    get:
-      tags:
-        - Analytics
-      summary: Get Analytics Preview
-      description: |-
-        **Access:** Admin role required.
-
-        Get the analytics report Frigate would send next, without sending it.
-      operationId: get_analytics_preview_analytics_preview_get
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema: {}
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
   /auth/first_time_login:
     get:
       tags:
@@ -81,9 +62,6 @@ paths:
                 type: string
         '401':
           description: Authentication Failed
-        '403':
-          description: Access Denied (proxy user resolved to a default role of 
-            'none')
       security: []
       x-required-role: public
   /profile:
@@ -1498,10 +1476,12 @@ paths:
         - Classification
       summary: Get custom classification attributes
       description: |-
-        **Access:** Authenticated user with access to all cameras.
+        **Access:** Any authenticated user.
 
         Returns custom classification attributes for a given object type.
             Only includes models with classification_type set to 'attribute'.
+            Callers without access to every camera only receive values that have been
+            recorded on the cameras they can access.
             By default returns a flat sorted list of all attribute labels.
             If group_by_model is true, returns attributes grouped by model name.
       operationId: get_custom_attributes_classification_attributes_get
@@ -1533,7 +1513,7 @@ paths:
                 $ref: '#/components/schemas/HTTPValidationError'
       security:
         - frigateUserAuth: []
-      x-required-role: all_cameras
+      x-required-role: any
   /classification/{name}/train:
     get:
       tags:
@@ -2302,42 +2282,6 @@ paths:
         - frigateUserAuth: []
       x-required-role: camera
       description: '**Access:** Authenticated user with access to the referenced camera.'
-  /review/{review_id}/regenerate_description:
-    put:
-      tags:
-        - Review
-      summary: Generate a review item description
-      description: |-
-        **Access:** Admin role required.
-
-        Re-runs a review item through the GenAI descriptions process.
-            Frames are always taken from recordings, and both alerts and detections are
-            accepted regardless of the camera's GenAI alerts/detections toggles.
-      operationId: 
-        regenerate_review_description_review__review_id__regenerate_description_put
-      parameters:
-        - name: review_id
-          in: path
-          required: true
-          schema:
-            type: string
-            title: Review Id
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/GenericResponse'
-        '422':
-          description: Validation Error
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/HTTPValidationError'
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
   /review/{review_id}/viewed:
     delete:
       tags:
@@ -2537,25 +2481,6 @@ paths:
       security:
         - frigateAdminAuth: []
       x-required-role: admin
-  /genai/roles:
-    get:
-      tags:
-        - App
-      summary: Get the model assigned to each GenAI role
-      description: |-
-        **Access:** Admin role required.
-
-        Returns the selected model and its context size for each configured GenAI role. Reads only what the client saved when it initialized, so the provider is not queried for its model list.
-      operationId: genai_roles_genai_roles_get
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema: {}
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
   /genai/probe:
     post:
       tags:
@@ -4130,188 +4055,6 @@ paths:
       security:
         - frigateAdminAuth: []
       x-required-role: admin
-  /hardware/hwaccel:
-    get:
-      tags:
-        - Hardware
-      summary: Hwaccel Recommendation
-      description: |-
-        **Access:** Admin role required.
-
-        Get the hardware decoding this system can do.
-
-        Args:
-            detector: Hardware key of the detection hardware in use, which biases
-                the recommendation toward that hardware's GPU
-            codecs: Comma separated codecs of the streams that will be decoded,
-                used to drop families that cannot decode one of them
-
-        Returns:
-            The recommended family (empty when none fits) and every usable family
-      operationId: hwaccel_recommendation_hardware_hwaccel_get
-      parameters:
-        - name: detector
-          in: query
-          required: false
-          schema:
-            anyOf:
-              - type: string
-              - type: 'null'
-            title: Detector
-        - name: codecs
-          in: query
-          required: false
-          schema:
-            anyOf:
-              - type: string
-              - type: 'null'
-            title: Codecs
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/HwaccelRecommendation'
-        '422':
-          description: Validation Error
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/HTTPValidationError'
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
-  /notices:
-    get:
-      tags:
-        - Notices
-      summary: Get Notices
-      description: |-
-        **Access:** Admin role required.
-
-        Get notices, most severe first.
-
-        Args:
-            include_dismissed: Also return dismissed notices, for the history view
-
-        Returns:
-            The notices
-      operationId: get_notices_notices_get
-      parameters:
-        - name: include_dismissed
-          in: query
-          required: false
-          schema:
-            type: boolean
-            default: false
-            title: Include Dismissed
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema: {}
-        '422':
-          description: Validation Error
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/HTTPValidationError'
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
-  /notices/stats:
-    get:
-      tags:
-        - Notices
-      summary: Get Notice Stats
-      description: |-
-        **Access:** Admin role required.
-
-        Get lifetime occurrence counts per notice kind.
-      operationId: get_notice_stats_notices_stats_get
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema: {}
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
-  /notices/dismissed_checks:
-    get:
-      tags:
-        - Notices
-      summary: Get Dismissed Checks
-      description: |-
-        **Access:** Admin role required.
-
-        Get the dismissed config and stream check rows, newest first.
-      operationId: get_dismissed_checks_notices_dismissed_checks_get
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema: {}
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
-  /notices/dismissed:
-    delete:
-      tags:
-        - Notices
-      summary: Purge Dismissed
-      description: |-
-        **Access:** Admin role required.
-
-        Delete every dismissed notice and check row so each can show again.
-      operationId: purge_dismissed_notices_dismissed_delete
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema: {}
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
-  /notices/{notice_id}/dismiss:
-    post:
-      tags:
-        - Notices
-      summary: Dismiss Notice
-      description: |-
-        **Access:** Admin role required.
-
-        Hide a notice or a config or stream check row.
-
-        It stays hidden if the same problem happens again.
-      operationId: dismiss_notice_notices__notice_id__dismiss_post
-      parameters:
-        - name: notice_id
-          in: path
-          required: true
-          schema:
-            type: string
-            title: Notice Id
-      responses:
-        '200':
-          description: Successful Response
-          content:
-            application/json:
-              schema: {}
-        '422':
-          description: Validation Error
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/HTTPValidationError'
-      security:
-        - frigateAdminAuth: []
-      x-required-role: admin
   /events:
     get:
       tags:
@@ -7401,17 +7144,13 @@ paths:
           in: query
           required: false
           schema:
-            anyOf:
-              - type: number
-              - type: 'null'
+            type: number
             title: After
         - name: before
           in: query
           required: false
           schema:
-            anyOf:
-              - type: number
-              - type: 'null'
+            type: number
             title: Before
       responses:
         '200':
@@ -7785,14 +7524,6 @@ components:
             - type: 'null'
           title: New case description
           description: Optional description for a newly created export case
-        stream:
-          $ref: '#/components/schemas/ExportStreamEnum'
-          title: Recorded stream to export
-          description: Which recorded stream every item in the batch is exported
-            from. 'auto' uses the merged timeline, preferring the main stream 
-            and falling back to the sub stream where main has aged out. 'main' 
-            or 'sub' pins the exports to that stream.
-          default: auto
       type: object
       required:
         - items
@@ -7974,18 +7705,6 @@ components:
           description: Per-request thinking toggle. None means use the provider 
             default. Ignored by providers that do not expose a per-request 
             thinking switch.
-        tool_decisions:
-          additionalProperties:
-            type: string
-            enum:
-              - approve
-              - reject
-          type: object
-          title: Tool Decisions
-          description: Decisions for tool calls that paused for approval, keyed 
-            by tool call ID. Send these with the conversation chain returned 
-            alongside an approval request; rejected calls are reported to the 
-            model as declined instead of being executed.
       type: object
       required:
         - messages
@@ -8730,14 +8449,6 @@ components:
           title: Chapter mode
           description: Optional chapter metadata to embed in the export. When 
             omitted, the camera's configured export chapter mode is used.
-        stream:
-          $ref: '#/components/schemas/ExportStreamEnum'
-          title: Recorded stream to export
-          description: Which recorded stream to export. 'auto' uses the merged 
-            timeline, preferring the main stream and falling back to the sub 
-            stream where main has aged out. 'main' or 'sub' pins the export to 
-            that stream alone.
-          default: auto
       type: object
       title: ExportRecordingsBody
     ExportRecordingsCustomBody:
@@ -8792,20 +8503,6 @@ components:
       required:
         - name
       title: ExportRenameBody
-    ExportStreamEnum:
-      type: string
-      enum:
-        - auto
-        - main
-        - sub
-      title: ExportStreamEnum
-      description: |-
-        Which recorded stream an export should be built from.
-
-        ``auto`` keeps the merged timeline: main where it exists, sub filling
-        the gaps main has already aged out of. Pinning to one stream trades
-        that coverage for a uniform source, which is always a plain stream
-        copy since nothing hands off mid-export.
     Extension:
       type: string
       enum:
@@ -8975,43 +8672,6 @@ components:
         - label
       title: HardwareUnit
       description: One physical piece of hardware.
-    HwaccelFamily:
-      properties:
-        key:
-          type: string
-          title: Family key
-          description: Stable identifier for this kind of hardware decoding.
-        presets:
-          additionalProperties:
-            type: string
-          type: object
-          title: Presets
-          description: The ffmpeg preset for each codec this family decodes, or 
-            a single 'any' preset when it decodes every codec.
-      type: object
-      required:
-        - key
-        - presets
-      title: HwaccelFamily
-      description: A kind of hardware decoding, and the presets that drive it.
-    HwaccelRecommendation:
-      properties:
-        recommended:
-          type: string
-          title: Recommended family
-          description: Key of the family that fits this system best, or an empty
-            string when none does.
-        available:
-          items:
-            $ref: '#/components/schemas/HwaccelFamily'
-          type: array
-          title: Available families
-          description: Every family this system's hardware can use, best first.
-      type: object
-      required:
-        - recommended
-      title: HwaccelRecommendation
-      description: The hardware decoding this system can do.
     Last24HoursReview:
       properties:
         reviewed_alert:

frigate/__main__.py

@@ -99,10 +99,6 @@ def main() -> None:
         print("***    End Config Validation Errors                       ***")
         print("*************************************************************")
 
-        # force a non-zero exit code for config failures
-        if args.validate_config:
-            sys.exit(1)
-
         # attempt to start Frigate in recovery mode
         try:
             config = FrigateConfig.load(install=True, safe_load=True)

frigate/analytics/__init__.py

@@ -1 +0,0 @@
-"""Opt-in anonymous analytics reports."""

frigate/analytics/collectors/__init__.py

@@ -1 +0,0 @@
-"""One collector per report section."""

frigate/analytics/collectors/cameras.py

@@ -1,223 +0,0 @@
-"""Cameras section: counts and histograms across cameras, never per camera."""
-
-from collections import Counter
-from typing import Any
-from urllib.parse import urlsplit
-
-from frigate.analytics.collectors.common import closed, histogram
-from frigate.analytics.context import ReportContext
-from frigate.analytics.schema import (
-    CamerasSection,
-    ConnectionQuality,
-    FpsBucket,
-    HeightBucket,
-    HwaccelKey,
-    InputPresetKey,
-    RetainBucket,
-    RetainDays,
-)
-from frigate.config import CameraConfig
-from frigate.config.camera.camera import CameraTypeEnum
-from frigate.config.camera.ffmpeg import CameraInput, CameraRoleEnum
-from frigate.const import REPLAY_CAMERA_PREFIX
-
-# the upper edge of every height bucket but the last
-HEIGHT_BUCKETS = (
-    (360, HeightBucket.le_360),
-    (540, HeightBucket.h480),
-    (900, HeightBucket.h720),
-    (1260, HeightBucket.h1080),
-    (1800, HeightBucket.h1440),
-)
-RESTREAM_HOSTS = frozenset({"127.0.0.1", "localhost"})
-RESTREAM_PORT = 8554
-QUALITIES = frozenset(ConnectionQuality)
-
-
-def height_bucket(height: int) -> HeightBucket:
-    for limit, bucket in HEIGHT_BUCKETS:
-        if height <= limit:
-            return bucket
-
-    return HeightBucket.ge_2160
-
-
-def fps_bucket(fps: int) -> FpsBucket:
-    if fps <= 5:
-        return FpsBucket.le_5
-
-    if fps <= 10:
-        return FpsBucket.f6_10
-
-    return FpsBucket.gt_10
-
-
-def retain_bucket(days: float) -> RetainBucket:
-    if days <= 0:
-        return RetainBucket.zero
-
-    if days <= 7:
-        return RetainBucket.d1_7
-
-    if days <= 30:
-        return RetainBucket.d8_30
-
-    return RetainBucket.gt_30
-
-
-def preset_key(args: str | list[str], enum: Any) -> Any:
-    """The preset's name, custom for hand written args, or none."""
-    if not args:
-        return enum("none")
-
-    if isinstance(args, str) and args.startswith("preset-"):
-        return closed(enum, args.removeprefix("preset-"), enum("custom"))
-
-    return enum("custom")
-
-
-def is_restream(path: str) -> bool:
-    try:
-        url = urlsplit(path)
-        return url.hostname in RESTREAM_HOSTS and url.port == RESTREAM_PORT
-    except ValueError:
-        return False
-
-
-def role_input(camera: CameraConfig, role: CameraRoleEnum) -> CameraInput | None:
-    return next((i for i in camera.ffmpeg.inputs if role in i.roles), None)
-
-
-def object_masks(camera: CameraConfig) -> int:
-    # parsing copies camera-wide masks into every filter as global_<id>
-    own = sum(1 for mask in camera.objects.mask.values() if mask is not None)
-    per_label = sum(
-        1
-        for label_filter in camera.objects.filters.values()
-        for mask_id, mask in label_filter.mask.items()
-        if mask is not None and not mask_id.startswith("global_")
-    )
-    return own + per_label
-
-
-def collect(ctx: ReportContext) -> CamerasSection:
-    cameras = {
-        name: camera
-        for name, camera in ctx.config.cameras.items()
-        if not name.startswith(REPLAY_CAMERA_PREFIX)
-    }
-    camera_stats = ctx.stats.get("cameras", {})
-
-    flags: Counter[str] = Counter()
-    types: Counter[CameraTypeEnum] = Counter()
-    heights: Counter[HeightBucket] = Counter()
-    fps: Counter[FpsBucket] = Counter()
-    hwaccel: Counter[Any] = Counter()
-    input_presets: Counter[Any] = Counter()
-    quality: Counter[ConnectionQuality] = Counter()
-    retain: dict[str, Counter[RetainBucket]] = {
-        period: Counter() for period in ("continuous", "motion", "alerts", "detections")
-    }
-
-    for name, camera in cameras.items():
-        detect_input = role_input(camera, CameraRoleEnum.detect)
-        record_input = role_input(camera, CameraRoleEnum.record)
-
-        # config validation requires a detect input, so this never skips
-        if detect_input is None:
-            continue
-
-        types[camera.type] += 1
-        fps[fps_bucket(camera.detect.fps)] += 1
-        hwaccel[
-            preset_key(
-                detect_input.hwaccel_args or camera.ffmpeg.hwaccel_args, HwaccelKey
-            )
-        ] += 1
-        input_presets[
-            preset_key(
-                detect_input.input_args or camera.ffmpeg.input_args, InputPresetKey
-            )
-        ] += 1
-
-        if camera.detect.height:
-            heights[height_bucket(camera.detect.height)] += 1
-
-        state = camera_stats.get(name, {}).get("connection_quality")
-
-        if state in QUALITIES:
-            quality[ConnectionQuality(state)] += 1
-
-        if camera.record.enabled:
-            retain["continuous"][retain_bucket(camera.record.continuous.days)] += 1
-            retain["motion"][retain_bucket(camera.record.motion.days)] += 1
-            retain["alerts"][retain_bucket(camera.record.alerts.retain.days)] += 1
-            retain["detections"][
-                retain_bucket(camera.record.detections.retain.days)
-            ] += 1
-
-        zones = len(camera.zones)
-        flags["enabled"] += camera.enabled
-        flags["go2rtc_restream"] += any(
-            is_restream(i.path) for i in camera.ffmpeg.inputs
-        )
-        flags["separate_detect_stream"] += (
-            record_input is not None and record_input.path != detect_input.path
-        )
-        flags["detect"] += camera.detect.enabled
-        flags["record"] += camera.record.enabled
-        flags["sub_stream_record"] += camera.record.sub.enabled
-        flags["snapshots"] += camera.snapshots.enabled
-        flags["audio"] += camera.audio.enabled
-        flags["audio_transcription"] += camera.audio_transcription.enabled
-        flags["birdseye"] += camera.birdseye.enabled
-        flags["onvif"] += bool(camera.onvif.host)
-        flags["autotracking"] += camera.onvif.autotracking.enabled
-        flags["face_recognition"] += camera.face_recognition.enabled
-        flags["lpr"] += camera.lpr.enabled
-        flags["review_genai"] += camera.review.genai.enabled
-        flags["object_genai"] += camera.objects.genai.enabled
-        flags["notifications"] += camera.notifications.enabled
-        flags["zones"] += zones
-        flags["cameras_with_zones"] += zones > 0
-        flags["motion_masks"] += sum(
-            1 for mask in camera.motion.mask.values() if mask is not None
-        )
-        flags["object_masks"] += object_masks(camera)
-
-    return CamerasSection(
-        total=len(cameras),
-        enabled=flags["enabled"],
-        types=histogram(types),
-        detect_height=histogram(heights),
-        detect_fps=histogram(fps),
-        hwaccel=histogram(hwaccel),
-        input_preset=histogram(input_presets),
-        go2rtc_restream=flags["go2rtc_restream"],
-        separate_detect_stream=flags["separate_detect_stream"],
-        detect=flags["detect"],
-        record=flags["record"],
-        sub_stream_record=flags["sub_stream_record"],
-        snapshots=flags["snapshots"],
-        audio=flags["audio"],
-        audio_transcription=flags["audio_transcription"],
-        birdseye=flags["birdseye"],
-        onvif=flags["onvif"],
-        autotracking=flags["autotracking"],
-        face_recognition=flags["face_recognition"],
-        lpr=flags["lpr"],
-        review_genai=flags["review_genai"],
-        object_genai=flags["object_genai"],
-        notifications=flags["notifications"],
-        zones=flags["zones"],
-        cameras_with_zones=flags["cameras_with_zones"],
-        motion_masks=flags["motion_masks"],
-        object_masks=flags["object_masks"],
-        connection_quality=histogram(quality),
-        retain_days=RetainDays(
-            continuous=histogram(retain["continuous"]),
-            motion=histogram(retain["motion"]),
-            alerts=histogram(retain["alerts"]),
-            detections=histogram(retain["detections"]),
-        ),
-    )

frigate/analytics/collectors/common.py

@@ -1,37 +0,0 @@
-"""Helpers the section collectors share."""
-
-import math
-from collections import Counter
-from enum import Enum
-from typing import Any, TypeVar
-
-E = TypeVar("E", bound=Enum)
-
-
-def closed(enum: type[E], value: Any, fallback: E) -> E:
-    """The member for a value, or the fallback for one the enum doesn't know."""
-    try:
-        return enum(str(value))
-    except ValueError:
-        return fallback
-
-
-def rate(value: Any) -> float:
-    """A finite, non-negative number rounded to 2 decimals, else 0.
-
-    A NaN would serialize as null and fail the schema's number type.
-    """
-    try:
-        number = float(value)
-    except (TypeError, ValueError):
-        return 0.0
-
-    if not math.isfinite(number):
-        return 0.0
-
-    return round(max(number, 0.0), 2)
-
-
-def histogram(counter: "Counter[E]") -> dict[E, int]:
-    """Drop the empty buckets, since an absent key means zero."""
-    return {key: total for key, total in counter.items() if total > 0}

frigate/analytics/collectors/detection.py

@@ -1,65 +0,0 @@
-"""Detection section: models, the detectors they run on, and inference speed."""
-
-import os
-
-from frigate.analytics.collectors.common import rate
-from frigate.analytics.context import ReportContext
-from frigate.analytics.schema import DetectionModel, DetectionSection, ModelSource
-from frigate.config.config import DEFAULT_MODEL
-from frigate.const import MODEL_CACHE_DIR
-from frigate.detectors.detector_config import SceneEnum
-from frigate.detectors.detector_types import DetectorTypeEnum
-from frigate.detectors.device import runner_names
-
-# the paths FrigateConfig fills in for a model that sets none
-BUNDLED_MODEL_PATHS = frozenset(
-    {"/cpu_model.tflite", "/edgetpu_model.tflite", str(DEFAULT_MODEL["path"])}
-)
-
-
-def model_source(path: str | None) -> ModelSource:
-    """Default, Frigate+ (a cached model next to its info file), or custom.
-
-    Parsing rewrites plus://<id> to the model cache, so the prefix is gone by now.
-    """
-    if path is None or path in BUNDLED_MODEL_PATHS:
-        return ModelSource.default
-
-    if path.startswith(f"{MODEL_CACHE_DIR}/") and os.path.isfile(f"{path}.json"):
-        return ModelSource.plus
-
-    return ModelSource.custom
-
-
-def collect(ctx: ReportContext) -> DetectionSection:
-    config = ctx.config
-    detectors = ctx.stats.get("detectors", {})
-    model_specs = [(model, config.devices_for_model(model)) for model in config.models]
-
-    # FrigateApp.start_detectors names the processes in this same order
-    names = iter(runner_names([spec for _, specs in model_specs for spec in specs]))
-    models: dict[SceneEnum, DetectionModel] = {}
-
-    for model, specs in model_specs:
-        speeds: list[float] = []
-
-        for _ in specs:
-            speed = detectors.get(next(names), {}).get("inference_speed")
-
-            if isinstance(speed, int | float) and speed > 0:
-                speeds.append(float(speed))
-
-        models[model.scene] = DetectionModel(
-            detector=DetectorTypeEnum(specs[0].detector),
-            devices=len(specs),
-            model_type=model.model_type,
-            input=f"{model.width}x{model.height}",
-            source=model_source(model.path),
-            inference_ms=rate(sum(speeds) / len(speeds)) if speeds else None,
-        )
-
-    return DetectionSection(
-        models=models,
-        detection_fps=rate(ctx.stats.get("detection_fps")),
-        skipped_fps=rate(ctx.stats.get("skipped_fps")),
-    )

frigate/analytics/collectors/features.py

@@ -1,145 +0,0 @@
-"""Features section: enrichments, GenAI, integrations, and users."""
-
-from collections import Counter
-
-from frigate.analytics.collectors.common import closed, histogram
-from frigate.analytics.context import ReportContext
-from frigate.analytics.schema import (
-    BirdseyeUsage,
-    ClassificationUsage,
-    EnrichmentDevice,
-    EnrichmentUsage,
-    FeaturesSection,
-    GenAIUsage,
-    SemanticSearchModel,
-    SemanticSearchUsage,
-    TranscriptionModel,
-    TranscriptionUsage,
-    UserRole,
-)
-from frigate.config.camera.genai import GenAIProviderEnum, GenAIRoleEnum
-from frigate.const import REPLAY_CAMERA_PREFIX
-from frigate.models import User
-
-RUNTIME_DEVICES = {
-    "cpu": EnrichmentDevice.cpu,
-    "cuda": EnrichmentDevice.cuda,
-    "tensorrt": EnrichmentDevice.tensorrt,
-    "migraphx": EnrichmentDevice.migraphx,
-}
-OPENVINO_DEVICES = {
-    "cpu": EnrichmentDevice.openvino_cpu,
-    "gpu": EnrichmentDevice.openvino_gpu,
-    "npu": EnrichmentDevice.openvino_npu,
-}
-
-
-def enrichment_device(label: object) -> EnrichmentDevice | None:
-    """Map a runner's device label, like "CUDA" or "OpenVINO GPU.0,CPU"."""
-    if not isinstance(label, str) or not label:
-        return None
-
-    runtime, _, target = label.partition(" ")
-
-    if runtime == "OpenVINO":
-        first = target.split(",")[0].split(".")[0].strip().lower()
-        return OPENVINO_DEVICES.get(first, EnrichmentDevice.other)
-
-    return RUNTIME_DEVICES.get(label.lower(), EnrichmentDevice.other)
-
-
-def model_name(model: object) -> str | None:
-    if model is None:
-        return None
-
-    return str(getattr(model, "value", model))
-
-
-def semantic_model(model: object) -> SemanticSearchModel | None:
-    # any string that isn't a built-in model names a GenAI provider
-    name = model_name(model)
-
-    if name is None:
-        return None
-
-    if name in ("jinav1", "jinav2"):
-        return SemanticSearchModel(name)
-
-    return SemanticSearchModel.genai
-
-
-def transcription_model(model: object) -> TranscriptionModel | None:
-    name = model_name(model)
-
-    if name is None:
-        return None
-
-    return TranscriptionModel.whisper if name == "whisper" else TranscriptionModel.genai
-
-
-def users() -> dict[UserRole, int]:
-    roles: Counter[UserRole] = Counter(
-        closed(UserRole, user.role, UserRole.custom) for user in User.select(User.role)
-    )
-    return histogram(roles)
-
-
-def collect(ctx: ReportContext) -> FeaturesSection:
-    config = ctx.config
-    devices = ctx.stats.get("embeddings", {}).get("devices", {})
-    cameras = [
-        camera
-        for name, camera in config.cameras.items()
-        if not name.startswith(REPLAY_CAMERA_PREFIX)
-    ]
-    providers: Counter[GenAIProviderEnum] = Counter(
-        genai.provider for genai in config.genai.values()
-    )
-    roles: Counter[GenAIRoleEnum] = Counter(
-        role for genai in config.genai.values() for role in genai.roles
-    )
-    custom = list(config.classification.custom.values())
-
-    return FeaturesSection(
-        face_recognition=EnrichmentUsage(
-            enabled=config.face_recognition.enabled,
-            model_size=config.face_recognition.model_size,
-            device=enrichment_device(devices.get("face_recognition")),
-        ),
-        lpr=EnrichmentUsage(
-            enabled=config.lpr.enabled,
-            model_size=config.lpr.model_size,
-            device=enrichment_device(devices.get("lpr")),
-        ),
-        semantic_search=SemanticSearchUsage(
-            enabled=config.semantic_search.enabled,
-            model=semantic_model(config.semantic_search.model),
-            model_size=config.semantic_search.model_size,
-            device=enrichment_device(devices.get("semantic_search")),
-            triggers=sum(len(camera.semantic_search.triggers) for camera in cameras),
-        ),
-        audio_transcription=TranscriptionUsage(
-            enabled=config.audio_transcription.enabled,
-            model=transcription_model(config.audio_transcription.model),
-            model_size=config.audio_transcription.model_size,
-        ),
-        genai=GenAIUsage(providers=histogram(providers), roles=histogram(roles)),
-        classification_models=ClassificationUsage(
-            state=sum(1 for model in custom if model.state_config is not None),
-            object=sum(1 for model in custom if model.object_config is not None),
-        ),
-        birdseye=BirdseyeUsage(
-            enabled=config.birdseye.enabled,
-            modes=list(config.birdseye.modes),
-            restream=config.birdseye.restream,
-        ),
-        mqtt=config.mqtt.enabled,
-        notifications=config.notifications.enabled,
-        auth=config.auth.enabled,
-        proxy_auth=config.proxy.header_map.user is not None,
-        tls=config.tls.enabled,
-        users=users(),
-        camera_groups=len(config.camera_groups),
-        profiles=len(config.profiles),
-        plus_api_key=config.plus_api.is_active(),
-    )

frigate/analytics/collectors/hardware.py

@@ -1,107 +0,0 @@
-"""Hardware section: CPU, memory, GPUs, decode and detection hardware, storage."""
-
-import os
-from collections import Counter
-from typing import Any
-
-import psutil
-
-from frigate.analytics.collectors.common import closed, histogram
-from frigate.analytics.context import ReportContext
-from frigate.analytics.schema import (
-    DecodeFamily,
-    GpuInfo,
-    GpuVendor,
-    HardwareKey,
-    HardwareSection,
-    StorageInfo,
-)
-from frigate.const import RECORD_DIR
-from frigate.detectors.hardware import hardware_prober
-from frigate.util.hwaccel import hwaccel_options
-
-DEVICE_TREE_MODEL = "/proc/device-tree/model"
-CPUINFO = "/proc/cpuinfo"
-
-
-def cpu_model() -> str:
-    """The board model on ARM boards, else the CPU's model name."""
-    try:
-        with open(DEVICE_TREE_MODEL) as f:
-            board = f.read().strip("\x00\n ")
-
-        if board:
-            return board[:64]
-    except OSError:
-        pass
-
-    try:
-        with open(CPUINFO) as f:
-            for line in f:
-                key, _, value = line.partition(":")
-
-                if key.strip() == "model name" and value.strip():
-                    return value.strip()[:64]
-    except OSError:
-        pass
-
-    return "unknown"
-
-
-def gpus(stats: dict[str, Any]) -> list[GpuInfo]:
-    found: list[GpuInfo] = []
-
-    for name, entry in stats.get("gpu_usages", {}).items():
-        vendor = entry.get("vendor") if isinstance(entry, dict) else None
-        found.append(
-            GpuInfo(
-                vendor=closed(GpuVendor, vendor, GpuVendor.other),
-                name=str(name)[:64],
-            )
-        )
-
-    return found
-
-
-def decode_families() -> list[DecodeFamily]:
-    _, available = hwaccel_options()
-    families = [
-        closed(DecodeFamily, family.key, DecodeFamily.other) for family in available
-    ]
-    return list(dict.fromkeys(families))
-
-
-def detection_hardware() -> dict[HardwareKey, int]:
-    units: Counter[HardwareKey] = Counter()
-
-    for found in hardware_prober.probe():
-        units[closed(HardwareKey, found.key, HardwareKey.other)] += found.count
-
-    return histogram(units)
-
-
-def storage(stats: dict[str, Any]) -> StorageInfo:
-    # stats report sizes in MB
-    entry = stats.get("service", {}).get("storage", {}).get(RECORD_DIR) or {}
-    total_mb = float(entry.get("total") or 0)
-    used_mb = float(entry.get("used") or 0)
-
-    return StorageInfo(
-        record_fs=str(entry.get("mount_type") or "unknown")[:16],
-        record_total_gb=round(total_mb / 1024),
-        record_used_pct=min(round(used_mb / total_mb * 100), 100)
-        if total_mb > 0
-        else 0,
-    )
-
-
-def collect(ctx: ReportContext) -> HardwareSection:
-    return HardwareSection(
-        cpu_model=cpu_model(),
-        cpu_cores=os.cpu_count() or 0,
-        memory_gb=round(psutil.virtual_memory().total / 2**30),
-        gpus=gpus(ctx.stats),
-        decode_families=decode_families(),
-        detection_hardware=detection_hardware(),
-        storage=storage(ctx.stats),
-    )

frigate/analytics/collectors/health.py

@@ -1,59 +0,0 @@
-"""Health section: uptime, CPU, enrichment speed, and notice counts."""
-
-from typing import Any
-
-from frigate.analytics.collectors.common import rate
-from frigate.analytics.context import ReportContext
-from frigate.analytics.schema import (
-    EnrichmentTiming,
-    HealthSection,
-    NoticeCounts,
-    NoticeKindKey,
-)
-
-TIMING_STATS = {
-    EnrichmentTiming.face: "face_recognition_speed",
-    EnrichmentTiming.lpr: "plate_recognition_speed",
-    EnrichmentTiming.plate_detection: "yolov9_plate_detection_speed",
-    EnrichmentTiming.image_embedding: "image_embedding_speed",
-    EnrichmentTiming.text_embedding: "text_embedding_speed",
-    EnrichmentTiming.review_description: "review_description_speed",
-    EnrichmentTiming.object_description: "object_description_speed",
-}
-REPORTABLE_KINDS = frozenset(key.value for key in NoticeKindKey)
-
-
-def notice_deltas(notice_stats: list[dict[str, Any]]) -> dict[Any, NoticeCounts]:
-    """What changed since the last accepted report, per reportable kind."""
-    deltas: dict[Any, NoticeCounts] = {}
-
-    for row in notice_stats:
-        if row["kind"] not in REPORTABLE_KINDS:
-            continue
-
-        occurrences = max(row["occurrences"] - row["reported_occurrences"], 0)
-        dismissals = max(row["dismissals"] - row["reported_dismissals"], 0)
-
-        if occurrences or dismissals:
-            deltas[NoticeKindKey(row["kind"])] = NoticeCounts(
-                occurrences=occurrences, dismissals=dismissals
-            )
-
-    return deltas
-
-
-def collect(ctx: ReportContext) -> HealthSection:
-    service = ctx.stats.get("service", {})
-    embeddings = ctx.stats.get("embeddings", {})
-    cpu = ctx.stats.get("cpu_usages", {}).get("frigate.full_system", {}).get("cpu")
-    timings = {
-        timing: rate(embeddings.get(key)) for timing, key in TIMING_STATS.items()
-    }
-
-    return HealthSection(
-        uptime_hours=int(rate(service.get("uptime")) // 3600),
-        cpu_percent=min(round(rate(cpu)), 100),
-        enrichment_ms={timing: value for timing, value in timings.items() if value > 0},
-        retention_unmet=bool(service.get("retention_unmet", False)),
-        notices=notice_deltas(ctx.notice_stats),
-    )

frigate/analytics/collectors/install.py

@@ -1,63 +0,0 @@
-"""Install section: version, image variant, install type, platform."""
-
-import os
-import platform
-import re
-
-from frigate.analytics.collectors.common import closed
-from frigate.analytics.context import ReportContext
-from frigate.analytics.schema import Arch, ImageVariant, InstallSection, InstallType
-from frigate.version import VERSION
-
-KERNEL_PATTERN = re.compile(r"^(\d{1,3})\.(\d{1,3})")
-
-
-def image_variant(value: str | None) -> ImageVariant:
-    """The published image from the build-time FRIGATE_IMAGE_VARIANT, dev when unset."""
-    if not value:
-        return ImageVariant.dev
-
-    return closed(ImageVariant, value, ImageVariant.other)
-
-
-def install_type() -> InstallType:
-    # the add-on is a container too, so it has to be checked first
-    if os.path.isfile("/data/options.json"):
-        return InstallType.ha_addon
-
-    if os.environ.get("KUBERNETES_SERVICE_HOST"):
-        return InstallType.kubernetes
-
-    if os.path.exists("/run/.containerenv"):
-        return InstallType.podman
-
-    if os.path.exists("/.dockerenv"):
-        return InstallType.docker
-
-    return InstallType.unknown
-
-
-def arch(machine: str) -> Arch:
-    match machine.lower():
-        case "x86_64" | "amd64":
-            return Arch.x86_64
-        case "aarch64" | "arm64":
-            return Arch.aarch64
-        case _:
-            return Arch.other
-
-
-def kernel(release: str) -> str:
-    match = KERNEL_PATTERN.match(release)
-    return f"{match.group(1)}.{match.group(2)}" if match else "unknown"
-
-
-def collect(ctx: ReportContext) -> InstallSection:
-    return InstallSection(
-        version=VERSION[:32],
-        image_variant=image_variant(os.environ.get("FRIGATE_IMAGE_VARIANT")),
-        install_type=install_type(),
-        arch=arch(platform.machine()),
-        kernel=kernel(platform.release()),
-        run_as_root=os.geteuid() == 0,
-    )

frigate/analytics/context.py

@@ -1,13 +0,0 @@
-"""What the collectors read, gathered once per report."""
-
-from dataclasses import dataclass, field
-from typing import Any
-
-from frigate.config import FrigateConfig
-
-
-@dataclass(frozen=True)
-class ReportContext:
-    config: FrigateConfig
-    stats: dict[str, Any]
-    notice_stats: list[dict[str, Any]] = field(default_factory=list)

frigate/analytics/report.py

@@ -1,88 +0,0 @@
-"""Build a report from the section collectors."""
-
-import logging
-import time
-from collections.abc import Callable
-from typing import TYPE_CHECKING, Any
-from uuid import uuid4
-
-from pydantic import BaseModel
-
-from frigate.analytics.collectors import (
-    cameras,
-    detection,
-    features,
-    hardware,
-    health,
-    install,
-)
-from frigate.analytics.context import ReportContext
-from frigate.analytics.schema import SCHEMA_VERSION, AnalyticsReport
-from frigate.analytics.state import load_state
-from frigate.config import FrigateConfig
-
-if TYPE_CHECKING:
-    from frigate.notices.registry import NoticeRegistry
-    from frigate.stats.emitter import StatsEmitter
-
-logger = logging.getLogger(__name__)
-
-COLLECTORS: dict[str, Callable[[ReportContext], BaseModel | None]] = {
-    "install": install.collect,
-    "hardware": hardware.collect,
-    "detection": detection.collect,
-    "cameras": cameras.collect,
-    "features": features.collect,
-    "health": health.collect,
-}
-
-# shown in the preview until the first report creates a real ID
-PREVIEW_INSTALL_ID = "0" * 32
-
-
-def build_report(
-    ctx: ReportContext, install_id: str, sent_at: int | None = None
-) -> AnalyticsReport:
-    """Run every collector; one that fails sends its section as null."""
-    sections: dict[str, Any] = {}
-
-    for name, collect in COLLECTORS.items():
-        try:
-            sections[name] = collect(ctx)
-        except Exception:
-            # a collector bug must cost one section, never the whole report
-            logger.warning("Analytics %s section failed", name, exc_info=True)
-            sections[name] = None
-
-    return AnalyticsReport.model_validate(
-        {
-            "schema_version": SCHEMA_VERSION,
-            "install_id": install_id,
-            "report_id": str(uuid4()),
-            "sent_at": int(time.time()) if sent_at is None else sent_at,
-            **sections,
-        }
-    )
-
-
-def gather_context(
-    config: FrigateConfig,
-    stats_emitter: "StatsEmitter | None",
-    notice_registry: "NoticeRegistry | None",
-) -> ReportContext:
-    return ReportContext(
-        config=config,
-        stats=stats_emitter.get_latest_stats() if stats_emitter is not None else {},
-        notice_stats=notice_registry.stats() if notice_registry is not None else [],
-    )
-
-
-def preview_report(
-    config: FrigateConfig,
-    stats_emitter: "StatsEmitter | None",
-    notice_registry: "NoticeRegistry | None",
-) -> AnalyticsReport:
-    """The report the next send would carry, without sending it."""
-    state = load_state()
-    ctx = gather_context(config, stats_emitter, notice_registry)
-    return build_report(ctx, state.install_id if state else PREVIEW_INSTALL_ID)

frigate/analytics/reporter.py

@@ -1,177 +0,0 @@
-"""Send one analytics report a day while the admin has opted in."""
-
-import logging
-import random
-import threading
-import time
-from collections.abc import Callable
-from multiprocessing.synchronize import Event as MpEvent
-from typing import TYPE_CHECKING
-
-from frigate.analytics.context import ReportContext
-from frigate.analytics.report import build_report
-from frigate.analytics.state import (
-    STATE_PATH,
-    AnalyticsState,
-    delete_state,
-    load_state,
-    new_state,
-    save_state,
-)
-from frigate.analytics.transport import SendOutcome, send_report
-from frigate.config import FrigateConfig
-from frigate.config.holder import ConfigHolder
-from frigate.const import ANALYTICS_URL
-from frigate.notices import raise_notice, resolve_notice
-
-if TYPE_CHECKING:
-    from frigate.notices.registry import NoticeRegistry
-    from frigate.stats.emitter import StatsEmitter
-
-logger = logging.getLogger(__name__)
-
-WAKE_S = 10 * 60
-INTERVAL_S = 24 * 60 * 60
-JITTER_S = 60 * 60
-FIRST_DELAY_S = (15 * 60, 45 * 60)
-PROMPT_KIND = "analytics_prompt"
-
-
-class AnalyticsReporter(threading.Thread):
-    """Follows the live config, so a settings save needs no restart."""
-
-    def __init__(
-        self,
-        config_holder: ConfigHolder,
-        stats_emitter: "StatsEmitter",
-        notice_registry: "NoticeRegistry",
-        stop_event: MpEvent | threading.Event,
-        *,
-        state_path: str = STATE_PATH,
-        url: str = ANALYTICS_URL,
-        send: Callable[[str, str], SendOutcome] = send_report,
-        clock: Callable[[], float] = time.time,
-        rng: random.Random | None = None,
-    ) -> None:
-        super().__init__(name="analytics_reporter", daemon=True)
-        self.config_holder = config_holder
-        self.stats_emitter = stats_emitter
-        self.notice_registry = notice_registry
-        self.stop_event = stop_event
-        self.state_path = state_path
-        self.url = url
-        self.send = send
-        self.clock = clock
-        self.rng = rng or random.Random()
-        self.first_due = clock() + self.rng.uniform(*FIRST_DELAY_S)
-        self.interval = self._next_interval()
-        self.opted_in: bool | None = None
-        self.warned_unwritable = False
-        # a settings save runs on an API thread while a wake may be mid-attempt
-        self._lock = threading.Lock()
-        config_holder.subscribe(self._on_config)
-
-    def _next_interval(self) -> float:
-        return INTERVAL_S + self.rng.uniform(-JITTER_S, JITTER_S)
-
-    def run(self) -> None:
-        while True:
-            try:
-                self.tick()
-            except Exception:
-                logger.exception("Analytics reporter failed")
-
-            if self.stop_event.wait(WAKE_S):
-                break
-
-    def _on_config(self, config: FrigateConfig) -> None:
-        # a save can turn sharing off and back on between two wakes, so an
-        # opt-out is handled when it's saved rather than at the next wake
-        with self._lock:
-            if not config.safe_mode:
-                self._apply_consent(config.telemetry.analytics)
-
-    def _apply_consent(self, opted_in: bool) -> None:
-        # called with the lock held
-        if opted_in == self.opted_in:
-            return
-
-        self.opted_in = opted_in
-
-        if opted_in:
-            resolve_notice(PROMPT_KIND)
-        else:
-            raise_notice(PROMPT_KIND)
-            delete_state(self.state_path)
-
-    def tick(self) -> None:
-        with self._lock:
-            config = self.config_holder.config
-
-            # safe mode parses a default config where analytics reads as off,
-            # and handling that as an opt-out would delete the install ID
-            if config.safe_mode:
-                return
-
-            self._apply_consent(config.telemetry.analytics)
-
-            if not config.telemetry.analytics:
-                return
-
-            now = self.clock()
-
-            if now < self.first_due:
-                return
-
-            state = load_state(self.state_path) or new_state()
-
-            if not self._due(state.last_attempt_at, now):
-                return
-
-            # saved before sending, so a failing endpoint or a crash mid-send
-            # still waits a full interval; without saved state every boot would
-            # send under a new install ID
-            if not save_state(AnalyticsState(state.install_id, now), self.state_path):
-                if not self.warned_unwritable:
-                    logger.warning(
-                        "Analytics is on, but %s isn't writable, so no report is sent",
-                        self.state_path,
-                    )
-                    self.warned_unwritable = True
-
-                return
-
-            self.interval = self._next_interval()
-
-        # the lock stays free during the request, so a save never waits on it
-        self._send(state.install_id, now)
-
-    def _due(self, last_attempt_at: float, now: float) -> bool:
-        # a last attempt stamped in the future came from a wrong clock
-        return (
-            now >= last_attempt_at + self.interval or last_attempt_at > now + INTERVAL_S
-        )
-
-    def _send(self, install_id: str, now: float) -> None:
-        notice_stats = self.notice_registry.stats()
-        ctx = ReportContext(
-            config=self.config_holder.config,
-            stats=self.stats_emitter.get_latest_stats(),
-            notice_stats=notice_stats,
-        )
-        report = build_report(ctx, install_id, sent_at=int(now))
-        body = report.model_dump_json()
-
-        # consent can be withdrawn while the report builds
-        if not self.config_holder.config.telemetry.analytics:
-            return
-
-        if self.send(self.url, body) is not SendOutcome.accepted:
-            return
-
-        # a failed health section sent no notice counts, so they stay pending
-        if report.health is not None:
-            self.notice_registry.mark_reported(notice_stats)
-
-        logger.info("Sent the daily analytics report")
-        logger.debug("Analytics report: %s", body)

frigate/analytics/schema.py

@@ -1,407 +0,0 @@
-"""Models for the analytics report, the contract with the ingest endpoint.
-
-Every field carries a description and an x-public flag, and no field accepts
-user-entered text, so a report can't carry camera names or other free text.
-"""
-
-from enum import StrEnum
-from typing import Any
-
-from pydantic import BaseModel, ConfigDict, Field
-
-from frigate.config.camera.birdseye import BirdseyeModeEnum
-from frigate.config.camera.camera import CameraTypeEnum
-from frigate.config.camera.genai import GenAIProviderEnum, GenAIRoleEnum
-from frigate.config.classification import ModelSizeEnum
-from frigate.detectors.detector_config import ModelTypeEnum, SceneEnum
-from frigate.detectors.detector_types import DetectorTypeEnum
-from frigate.ffmpeg_presets import PRESETS_HW_ACCEL_DECODE, PRESETS_INPUT
-from frigate.notices.types import NOTICE_KINDS
-
-SCHEMA_VERSION = 1
-
-
-class ImageVariant(StrEnum):
-    standard = "standard"
-    rpi = "rpi"
-    tensorrt = "tensorrt"
-    tensorrt_jp6 = "tensorrt-jp6"
-    rocm = "rocm"
-    rk = "rk"
-    synaptics = "synaptics"
-    dev = "dev"
-    other = "other"
-
-
-class InstallType(StrEnum):
-    ha_addon = "ha_addon"
-    docker = "docker"
-    podman = "podman"
-    kubernetes = "kubernetes"
-    unknown = "unknown"
-
-
-class Arch(StrEnum):
-    x86_64 = "x86_64"
-    aarch64 = "aarch64"
-    other = "other"
-
-
-class GpuVendor(StrEnum):
-    intel = "intel"
-    amd = "amd"
-    nvidia = "nvidia"
-    rockchip = "rockchip"
-    rpi = "rpi"
-    other = "other"
-
-
-class DecodeFamily(StrEnum):
-    nvidia = "nvidia"
-    vaapi = "vaapi"
-    rkmpp = "rkmpp"
-    intel_qsv = "intel-qsv"
-    jetson = "jetson"
-    rpi = "rpi"
-    other = "other"
-
-
-class HardwareKey(StrEnum):
-    edgetpu_pci = "edgetpu:pci"
-    edgetpu_usb = "edgetpu:usb"
-    openvino_gpu = "openvino:GPU"
-    openvino_npu = "openvino:NPU"
-    onnx_amd = "onnx:amd"
-    onnx_nvidia = "onnx:nvidia"
-    tensorrt = "tensorrt"
-    hailo = "hailo"
-    memryx = "memryx"
-    deepx = "deepx"
-    rknn = "rknn"
-    axengine = "axengine"
-    synaptics = "synaptics"
-    cpu = "cpu"
-    other = "other"
-
-
-class ModelSource(StrEnum):
-    default = "default"
-    plus = "plus"
-    custom = "custom"
-
-
-class HeightBucket(StrEnum):
-    le_360 = "le_360"
-    h480 = "480"
-    h720 = "720"
-    h1080 = "1080"
-    h1440 = "1440"
-    ge_2160 = "ge_2160"
-
-
-class FpsBucket(StrEnum):
-    le_5 = "le_5"
-    f6_10 = "6_10"
-    gt_10 = "gt_10"
-
-
-class RetainBucket(StrEnum):
-    zero = "0"
-    d1_7 = "1_7"
-    d8_30 = "8_30"
-    gt_30 = "gt_30"
-
-
-class ConnectionQuality(StrEnum):
-    excellent = "excellent"
-    fair = "fair"
-    poor = "poor"
-    unusable = "unusable"
-
-
-class EnrichmentDevice(StrEnum):
-    cpu = "cpu"
-    cuda = "cuda"
-    tensorrt = "tensorrt"
-    migraphx = "migraphx"
-    openvino_cpu = "openvino_cpu"
-    openvino_gpu = "openvino_gpu"
-    openvino_npu = "openvino_npu"
-    other = "other"
-
-
-class SemanticSearchModel(StrEnum):
-    jinav1 = "jinav1"
-    jinav2 = "jinav2"
-    genai = "genai"
-
-
-class TranscriptionModel(StrEnum):
-    whisper = "whisper"
-    genai = "genai"
-
-
-class UserRole(StrEnum):
-    admin = "admin"
-    viewer = "viewer"
-    custom = "custom"
-
-
-class EnrichmentTiming(StrEnum):
-    face = "face"
-    lpr = "lpr"
-    plate_detection = "plate_detection"
-    image_embedding = "image_embedding"
-    text_embedding = "text_embedding"
-    review_description = "review_description"
-    object_description = "object_description"
-
-
-def _preset_keys(presets: dict[str, Any]) -> dict[str, str]:
-    keys = [name.removeprefix("preset-") for name in presets]
-    return {key: key for key in [*keys, "custom", "none"]}
-
-
-# built from the registries they mirror, so a new preset or notice kind reaches
-# the schema through generate_analytics_schema.py instead of a hand edit
-HwaccelKey = StrEnum("HwaccelKey", _preset_keys(PRESETS_HW_ACCEL_DECODE))  # type: ignore[misc]
-InputPresetKey = StrEnum("InputPresetKey", _preset_keys(PRESETS_INPUT))  # type: ignore[misc]
-NoticeKindKey = StrEnum(  # type: ignore[misc]
-    "NoticeKindKey",
-    {key: key for key, kind in NOTICE_KINDS.items() if kind.reportable},
-)
-
-
-class AnalyticsModel(BaseModel):
-    model_config = ConfigDict(extra="forbid")
-
-
-def metric(description: str, *, public: bool = True, **kwargs: Any) -> Any:
-    """Declare a report field; the description and flag land in the schema."""
-    return Field(
-        description=description, json_schema_extra={"x-public": public}, **kwargs
-    )
-
-
-def count(description: str) -> Any:
-    return metric(description, ge=0)
-
-
-class InstallSection(AnalyticsModel):
-    version: str = metric("Frigate version string", max_length=32)
-    image_variant: ImageVariant = metric("Published image the install runs")
-    install_type: InstallType = metric("How Frigate is installed")
-    arch: Arch = metric("CPU architecture")
-    kernel: str = metric(
-        "Host kernel as major.minor", pattern=r"^(\d{1,3}\.\d{1,3}|unknown)$"
-    )
-    run_as_root: bool = metric("Whether the main process runs as root")
-
-
-class GpuInfo(AnalyticsModel):
-    vendor: GpuVendor = metric("GPU vendor")
-    name: str = metric("GPU name as the hardware reports it", max_length=64)
-
-
-class StorageInfo(AnalyticsModel):
-    record_fs: str = metric("Filesystem of the recordings volume", max_length=16)
-    record_total_gb: int = count("Size of the recordings volume in GB")
-    record_used_pct: int = metric(
-        "Percent of the recordings volume in use", ge=0, le=100
-    )
-
-
-class HardwareSection(AnalyticsModel):
-    cpu_model: str = metric(
-        "CPU or board model as the hardware reports it", max_length=64
-    )
-    cpu_cores: int = count("Logical CPU count")
-    memory_gb: int = count("Total memory in GB")
-    gpus: list[GpuInfo] = metric("GPUs the stats collector found")
-    decode_families: list[DecodeFamily] = metric(
-        "Hardware decode families this system can use"
-    )
-    detection_hardware: dict[HardwareKey, int] = metric(
-        "Detection hardware found, as unit counts by kind"
-    )
-    storage: StorageInfo = metric("Recordings storage")
-
-
-class DetectionModel(AnalyticsModel):
-    detector: DetectorTypeEnum = metric("Detector type the model runs on")
-    devices: int = count("Devices the model runs on")
-    model_type: ModelTypeEnum = metric("Model architecture")
-    input: str = metric("Model input size as WxH", pattern=r"^\d{1,5}x\d{1,5}$")
-    source: ModelSource = metric("Where the model came from", public=False)
-    inference_ms: float | None = metric(
-        "Mean inference time across the model's detector processes, null before the first stats",
-        ge=0,
-    )
-
-
-class DetectionSection(AnalyticsModel):
-    models: dict[SceneEnum, DetectionModel] = metric("Detection models keyed by scene")
-    detection_fps: float = metric("Detections per second across cameras", ge=0)
-    skipped_fps: float = metric("Frames per second skipped across cameras", ge=0)
-
-
-class RetainDays(AnalyticsModel):
-    continuous: dict[RetainBucket, int] = metric(
-        "Recording cameras by continuous retention in days"
-    )
-    motion: dict[RetainBucket, int] = metric(
-        "Recording cameras by motion retention in days"
-    )
-    alerts: dict[RetainBucket, int] = metric(
-        "Recording cameras by alert retention in days"
-    )
-    detections: dict[RetainBucket, int] = metric(
-        "Recording cameras by detection retention in days"
-    )
-
-
-class CamerasSection(AnalyticsModel):
-    total: int = count("Configured cameras")
-    enabled: int = count("Enabled cameras")
-    types: dict[CameraTypeEnum, int] = metric("Cameras by type")
-    detect_height: dict[HeightBucket, int] = metric(
-        "Cameras by detect resolution height"
-    )
-    detect_fps: dict[FpsBucket, int] = metric("Cameras by detect fps")
-    hwaccel: dict[HwaccelKey, int] = metric(
-        "Cameras by the resolved hwaccel preset of the detect input"
-    )
-    input_preset: dict[InputPresetKey, int] = metric(
-        "Cameras by the input preset of the detect input"
-    )
-    go2rtc_restream: int = count("Cameras with an input from the go2rtc restream")
-    separate_detect_stream: int = count(
-        "Cameras whose detect input differs from their record input"
-    )
-    detect: int = count("Cameras with detection on")
-    record: int = count("Cameras with recording on")
-    sub_stream_record: int = count("Cameras with sub stream recording on")
-    snapshots: int = count("Cameras with snapshots on")
-    audio: int = count("Cameras with audio detection on")
-    audio_transcription: int = count("Cameras with audio transcription on")
-    birdseye: int = count("Cameras in birdseye")
-    onvif: int = count("Cameras with an ONVIF host")
-    autotracking: int = count("Cameras with PTZ autotracking on")
-    face_recognition: int = count("Cameras with face recognition on")
-    lpr: int = count("Cameras with license plate recognition on")
-    review_genai: int = count("Cameras with GenAI review summaries on")
-    object_genai: int = count("Cameras with GenAI object descriptions on")
-    notifications: int = count("Cameras with notifications on")
-    zones: int = count("Zones across cameras")
-    cameras_with_zones: int = count("Cameras with at least one zone")
-    motion_masks: int = count("Motion masks across cameras")
-    object_masks: int = count("Object masks across cameras")
-    connection_quality: dict[ConnectionQuality, int] = metric(
-        "Cameras by connection quality at send time"
-    )
-    retain_days: RetainDays = metric("Recording retention")
-
-
-class EnrichmentUsage(AnalyticsModel):
-    enabled: bool = metric("Whether the enrichment is on")
-    model_size: ModelSizeEnum = metric("Configured model size")
-    device: EnrichmentDevice | None = metric(
-        "Device the model loaded on, null when it isn't loaded"
-    )
-
-
-class SemanticSearchUsage(AnalyticsModel):
-    enabled: bool = metric("Whether semantic search is on")
-    model: SemanticSearchModel | None = metric(
-        "Embedding model, genai for a GenAI provider"
-    )
-    model_size: ModelSizeEnum = metric("Configured model size")
-    device: EnrichmentDevice | None = metric(
-        "Device the model loaded on, null when it isn't loaded"
-    )
-    triggers: int = count("Semantic search triggers across cameras")
-
-
-class TranscriptionUsage(AnalyticsModel):
-    enabled: bool = metric("Whether audio transcription is on")
-    model: TranscriptionModel | None = metric(
-        "Transcription model, genai for a GenAI provider"
-    )
-    model_size: ModelSizeEnum = metric("Configured model size")
-
-
-class GenAIUsage(AnalyticsModel):
-    providers: dict[GenAIProviderEnum, int] = metric(
-        "Configured GenAI providers by type"
-    )
-    roles: dict[GenAIRoleEnum, int] = metric("Configured GenAI providers by role")
-
-
-class ClassificationUsage(AnalyticsModel):
-    state: int = count("Custom state classification models")
-    object: int = count("Custom object classification models")
-
-
-class BirdseyeUsage(AnalyticsModel):
-    enabled: bool = metric("Whether birdseye is on")
-    modes: list[BirdseyeModeEnum] = metric("Birdseye modes")
-    restream: bool = metric("Whether birdseye is restreamed")
-
-
-class FeaturesSection(AnalyticsModel):
-    face_recognition: EnrichmentUsage = metric("Face recognition")
-    lpr: EnrichmentUsage = metric("License plate recognition")
-    semantic_search: SemanticSearchUsage = metric("Semantic search")
-    audio_transcription: TranscriptionUsage = metric("Audio transcription")
-    genai: GenAIUsage = metric("Generative AI providers")
-    classification_models: ClassificationUsage = metric("Custom classification models")
-    birdseye: BirdseyeUsage = metric("Birdseye")
-    mqtt: bool = metric("Whether MQTT is on")
-    notifications: bool = metric("Whether web push notifications are on")
-    auth: bool = metric("Whether authentication is on")
-    proxy_auth: bool = metric("Whether a proxy supplies the user header")
-    tls: bool = metric("Whether TLS is on")
-    users: dict[UserRole, int] = metric("Users by role")
-    camera_groups: int = count("Camera groups")
-    profiles: int = count("Profiles")
-    plus_api_key: bool = metric("Whether a Frigate+ API key is set", public=False)
-
-
-class NoticeCounts(AnalyticsModel):
-    occurrences: int = count("Occurrences since the last accepted report")
-    dismissals: int = count("Dismissals since the last accepted report")
-
-
-class HealthSection(AnalyticsModel):
-    uptime_hours: int = count("Hours since Frigate started")
-    cpu_percent: int = metric("System CPU use at send time", ge=0, le=100)
-    enrichment_ms: dict[EnrichmentTiming, float] = metric(
-        "Mean enrichment inference times in milliseconds"
-    )
-    retention_unmet: bool = metric(
-        "Whether storage can't keep the configured retention"
-    )
-    notices: dict[NoticeKindKey, NoticeCounts] = metric(
-        "Notice counts by kind since the last accepted report", public=False
-    )
-
-
-class AnalyticsReport(AnalyticsModel):
-    schema_version: int = metric("Report format version", ge=1)
-    install_id: str = metric(
-        "Random install identifier", public=False, pattern=r"^[0-9a-f]{32}$"
-    )
-    report_id: str = metric(
-        "Random identifier of this report",
-        public=False,
-        pattern=r"^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
-    )
-    sent_at: int = count("Unix time the report was built")
-    install: InstallSection | None = metric("Install, null if its collector failed")
-    hardware: HardwareSection | None = metric("Hardware, null if its collector failed")
-    detection: DetectionSection | None = metric(
-        "Object detection, null if its collector failed"
-    )
-    cameras: CamerasSection | None = metric("Cameras, null if its collector failed")
-    features: FeaturesSection | None = metric("Features, null if its collector failed")
-    health: HealthSection | None = metric("Health, null if its collector failed")

frigate/analytics/state.py

@@ -1,85 +0,0 @@
-"""The install's analytics identity and last attempt time, kept under /config."""
-
-import json
-import logging
-import os
-import re
-from dataclasses import dataclass
-from uuid import uuid4
-
-from frigate.const import CONFIG_DIR
-
-logger = logging.getLogger(__name__)
-
-STATE_PATH = os.path.join(CONFIG_DIR, ".analytics.json")
-INSTALL_ID_PATTERN = re.compile(r"[0-9a-f]{32}")
-
-
-@dataclass(frozen=True)
-class AnalyticsState:
-    install_id: str
-    last_attempt_at: float
-
-
-def new_state() -> AnalyticsState:
-    return AnalyticsState(install_id=uuid4().hex, last_attempt_at=0.0)
-
-
-def load_state(path: str = STATE_PATH) -> AnalyticsState | None:
-    """The saved state, or None when the file is missing or unusable."""
-    try:
-        with open(path) as f:
-            data = json.load(f)
-    except FileNotFoundError:
-        return None
-    except (OSError, ValueError):
-        logger.warning("Ignoring unreadable analytics state at %s", path)
-        return None
-
-    if not isinstance(data, dict):
-        return None
-
-    install_id = data.get("install_id")
-    last_attempt_at = data.get("last_attempt_at")
-
-    if (
-        not isinstance(install_id, str)
-        or not INSTALL_ID_PATTERN.fullmatch(install_id)
-        or isinstance(last_attempt_at, bool)
-        or not isinstance(last_attempt_at, int | float)
-    ):
-        logger.warning("Ignoring invalid analytics state at %s", path)
-        return None
-
-    return AnalyticsState(install_id=install_id, last_attempt_at=float(last_attempt_at))
-
-
-def save_state(state: AnalyticsState, path: str = STATE_PATH) -> bool:
-    """Write the state atomically, returning False when it can't be written."""
-    temp_path = f"{path}.tmp"
-
-    try:
-        with open(temp_path, "w") as f:
-            json.dump(
-                {
-                    "install_id": state.install_id,
-                    "last_attempt_at": state.last_attempt_at,
-                },
-                f,
-            )
-
-        os.replace(temp_path, path)
-    except OSError:
-        return False
-
-    return True
-
-
-def delete_state(path: str = STATE_PATH) -> None:
-    """Forget the install ID, so a later opt-in starts a fresh identity."""
-    try:
-        os.remove(path)
-    except FileNotFoundError:
-        pass
-    except OSError:
-        logger.warning("Unable to delete analytics state at %s", path)

frigate/analytics/transport.py

@@ -1,54 +0,0 @@
-"""POST a report to the ingest endpoint."""
-
-import logging
-from enum import Enum
-
-import requests
-
-from frigate.version import VERSION
-
-logger = logging.getLogger(__name__)
-
-TIMEOUT_S = 30
-
-
-class SendOutcome(Enum):
-    accepted = "accepted"
-    rejected = "rejected"
-    rate_limited = "rate_limited"
-    failed = "failed"
-
-
-def send_report(url: str, body: str) -> SendOutcome:
-    """Send one report. Never raises; the outcome says what happened."""
-    try:
-        # a redirect would turn the POST into a GET, so it counts as a failure
-        response = requests.post(
-            url,
-            data=body.encode(),
-            headers={
-                "Content-Type": "application/json",
-                "User-Agent": f"Frigate/{VERSION}",
-            },
-            timeout=TIMEOUT_S,
-            allow_redirects=False,
-        )
-    except requests.RequestException as err:
-        logger.warning("Unable to send the analytics report: %s", err)
-        return SendOutcome.failed
-
-    status = response.status_code
-
-    if 200 <= status < 300:
-        return SendOutcome.accepted
-
-    if status == 400:
-        logger.warning("The analytics report was rejected: %s", response.text[:200])
-        return SendOutcome.rejected
-
-    if status == 429:
-        logger.debug("The analytics endpoint is rate limiting this install")
-        return SendOutcome.rate_limited
-
-    logger.warning("The analytics endpoint returned %s", status)
-    return SendOutcome.failed

frigate/api/analytics.py

@@ -1,25 +0,0 @@
-"""Analytics APIs."""
-
-import logging
-
-from fastapi import APIRouter, Depends, Request
-from fastapi.responses import JSONResponse
-
-from frigate.analytics.report import preview_report
-from frigate.api.auth import require_role
-from frigate.api.defs.tags import Tags
-
-logger = logging.getLogger(__name__)
-
-router = APIRouter(tags=[Tags.analytics])
-
-
-@router.get("/analytics/preview", dependencies=[Depends(require_role(["admin"]))])
-def get_analytics_preview(request: Request) -> JSONResponse:
-    """Get the analytics report Frigate would send next, without sending it."""
-    report = preview_report(
-        request.app.frigate_config,
-        request.app.stats_emitter,
-        request.app.notice_registry,
-    )
-    return JSONResponse(content=report.model_dump(mode="json"))

frigate/api/app.py

@@ -2,6 +2,7 @@
 
 import asyncio
 import copy
+import json
 import logging
 import os
 import platform
@@ -10,6 +11,7 @@ import urllib
 from datetime import datetime, timedelta
 from functools import reduce
 from io import StringIO
+from pathlib import Path as FilePath
 from typing import Any
 
 import aiofiles
@@ -54,7 +56,6 @@ from frigate.jobs.media_sync import (
     start_media_sync_job,
 )
 from frigate.models import Event, Timeline
-from frigate.plus import load_plus_model_info
 from frigate.stats.prometheus import get_metrics, update_metrics
 from frigate.types import JobStatusTypesEnum
 from frigate.util.builtin import (
@@ -189,20 +190,6 @@ def genai_models(request: Request):
     return JSONResponse(content=request.app.genai_manager.list_models())
 
 
-@router.get(
-    "/genai/roles",
-    dependencies=[Depends(allow_any_authenticated())],
-    summary="Get the model assigned to each GenAI role",
-    description=(
-        "Returns the selected model and its context size for each configured "
-        "GenAI role. Reads only what the client saved when it initialized, so "
-        "the provider is not queried for its model list."
-    ),
-)
-def genai_roles(request: Request):
-    return JSONResponse(content=request.app.genai_manager.role_info())
-
-
 @router.post(
     "/genai/probe",
     dependencies=[Depends(require_role(["admin"]))],
@@ -400,7 +387,13 @@ def config(request: Request):
         model_dict["plus"] = None
 
         if model.path:
-            model_dict["plus"] = load_plus_model_info(os.path.basename(model.path))
+            model_json_path = FilePath(model.path).with_suffix(".json")
+
+            try:
+                with open(model_json_path) as f:
+                    model_dict["plus"] = json.load(f)
+            except (FileNotFoundError, json.JSONDecodeError):
+                pass
 
     return JSONResponse(content=config)
 

frigate/api/auth.py

@@ -8,7 +8,6 @@ import logging
 import os
 import re
 import secrets
-import threading
 import time
 from datetime import datetime
 from pathlib import Path
@@ -35,7 +34,6 @@ from frigate.api.media_auth import (
 from frigate.config import AuthConfig, ProxyConfig
 from frigate.const import CONFIG_DIR, JWT_SECRET_ENV_VAR, PASSWORD_HASH_ALGORITHM
 from frigate.models import User
-from frigate.notices import raise_notice
 
 logger = logging.getLogger(__name__)
 
@@ -255,58 +253,6 @@ class RateLimiter:
 
 rateLimiter = RateLimiter()
 
-# a failed login this long after the user's previous one opens a new burst
-FAILED_LOGIN_BURST_GAP_S = 300
-
-# the username comes from the request, so it is cut before it reaches a notice
-MAX_NOTICE_USERNAME = 64
-
-# unknown usernames are unbounded, so past this many open bursts a new one only
-# reaches the log
-MAX_OPEN_BURSTS = 100
-
-
-class FailedLoginTracker:
-    """Groups each user's failed logins into bursts, one notice per burst."""
-
-    def __init__(self) -> None:
-        self._lock = threading.Lock()
-
-        # user -> (burst start, last attempt), stalest attempt first
-        self._bursts: dict[str, tuple[int, float]] = {}
-
-    def record(self, user: str, now: float, *, known: bool = False) -> None:
-        """Count a failed login toward the user's open burst, or open a new one.
-
-        Once MAX_OPEN_BURSTS are open, only a known user opens another.
-        """
-        user = user[:MAX_NOTICE_USERNAME]
-
-        with self._lock:
-            # bursts that went quiet are over
-            while self._bursts:
-                stalest = next(iter(self._bursts))
-
-                if now - self._bursts[stalest][1] < FAILED_LOGIN_BURST_GAP_S:
-                    break
-
-                del self._bursts[stalest]
-
-            if (
-                not known
-                and user not in self._bursts
-                and len(self._bursts) >= MAX_OPEN_BURSTS
-            ):
-                return
-
-            start, _ = self._bursts.pop(user, (int(now), now))
-            self._bursts[user] = (start, now)
-
-        raise_notice("failed_login", scope=f"{user}:{start}", params={"user": user})
-
-
-failed_logins = FailedLoginTracker()
-
 
 def get_remote_addr(request: Request):
     # fall back to the direct TCP peer when no proxy chain is present
@@ -551,7 +497,6 @@ def resolve_role(
                      Admin matches short-circuit to admin.
                  - If no role_map is configured, treat the header as role names directly.
       2. If no valid role is found, return proxy_config.default_role if it's valid in config_roles, else 'viewer'.
-         The literal value 'none' is a valid default and means access should be denied.
 
     Args:
         headers (dict): Incoming request headers (case-insensitive).
@@ -564,17 +509,10 @@ def resolve_role(
     default_role = proxy_config.default_role
     role_header = proxy_config.header_map.role
 
-    # Validate default_role against config; fallback to 'viewer' if invalid.
-    # "none" is a sentinel meaning "deny access when no mapping matches"; it is
-    # reserved in AuthConfig.validate_roles so it is never a configured role.
-    validated_default = (
-        default_role
-        if default_role in config_roles or default_role == "none"
-        else "viewer"
-    )
+    # Validate default_role against config; fallback to 'viewer' if invalid
+    validated_default = default_role if default_role in config_roles else "viewer"
     if not config_roles:
-        # Edge case: no roles defined
-        validated_default = "none" if default_role == "none" else "viewer"
+        validated_default = "viewer"  # Edge case: no roles defined
 
     if not role_header:
         logger.debug(
@@ -679,9 +617,6 @@ def resolve_role(
             },
         },
         401: {"description": "Authentication Failed"},
-        403: {
-            "description": "Access Denied (proxy user resolved to a default role of 'none')"
-        },
     },
 )
 def auth(request: Request):
@@ -731,10 +666,6 @@ def auth(request: Request):
         config_roles_set = set(auth_config.roles.keys())
         role = resolve_role(request.headers, proxy_config, config_roles_set)
 
-        if role == "none":
-            logger.debug("Resolved role is 'none', denying access")
-            return Response("", status_code=403)
-
         success_response.headers["remote-role"] = role
 
         deny_status = deny_response_for_media_uri(original_url, role, frigate_config)
@@ -786,13 +717,6 @@ def auth(request: Request):
 
         user = token.claims.get("sub")
         role = token.claims.get("role")
-
-        # the token keeps the role it was issued with, so a role removed from
-        # the config since then must send the user back through login
-        if role not in auth_config.roles:
-            logger.debug("jwt role %s is not in the config", role)
-            return fail_response
-
         current_time = int(time.time())
 
         # if the jwt is expired
@@ -941,7 +865,6 @@ def login(request: Request, body: AppPostLoginBody):
         db_user: User = User.get_by_id(user)
     except DoesNotExist:
         logger.warning(f"Login failed for unknown user '{user}' from {remote_addr}")
-        failed_logins.record(user, time.time())
         return JSONResponse(content={"message": "Login failed"}, status_code=401)
 
     password_hash = db_user.password_hash
@@ -973,7 +896,6 @@ def login(request: Request, body: AppPostLoginBody):
     logger.warning(
         f"Login failed for user '{user}' (invalid password) from {remote_addr}"
     )
-    failed_logins.record(user, time.time(), known=True)
     return JSONResponse(content={"message": "Login failed"}, status_code=401)
 
 

frigate/api/camera.py

@@ -302,9 +302,7 @@ def ffprobe(request: Request, paths: str = "", detailed: bool = False):
                     stderr_decoded = str(ffprobe.stderr)
 
             stderr_lines = [
-                clean_camera_user_pass(line.strip())
-                for line in stderr_decoded.split("\n")
-                if line.strip()
+                line.strip() for line in stderr_decoded.split("\n") if line.strip()
             ]
 
             result = {
@@ -1303,9 +1301,6 @@ async def delete_camera(
             if request.app.dispatcher is not None:
                 request.app.dispatcher.clear_runtime_state_for_camera(camera_name)
 
-            if request.app.notice_registry is not None:
-                request.app.notice_registry.resolve_camera(camera_name)
-
             # Publish removal to stop ffmpeg processes and clean up runtime state
             request.app.config_publisher.publish_update(
                 CameraConfigUpdateTopic(CameraConfigUpdateEnum.remove, camera_name),

frigate/api/chat.py

@@ -10,7 +10,6 @@ from functools import reduce
 from typing import Any, Literal
 
 import cv2
-import numpy as np
 from fastapi import APIRouter, Body, Depends, HTTPException, Request
 from fastapi.responses import JSONResponse, StreamingResponse
 from pydantic import BaseModel
@@ -24,7 +23,6 @@ from frigate.api.chat_util import (
     chunk_content,
     distance_to_score,
     format_events_with_local_time,
-    format_local_time,
     fuse_scores,
     hydrate_event,
     parse_iso_to_timestamp,
@@ -35,44 +33,29 @@ from frigate.api.defs.response.chat_response import (
     ChatCompletionResponse,
     ChatMessageResponse,
     ToolCall,
-    ToolCallInvocation,
 )
 from frigate.api.defs.tags import Tags
 from frigate.api.event import _build_attribute_filter_clause, events
-from frigate.api.export import _build_export_job, _validate_export_source
 from frigate.config import FrigateConfig
 from frigate.config.classification import SemanticSearchModelEnum
 from frigate.genai.prompts import (
     build_chat_system_prompt,
     get_attribute_classifications,
     get_tool_definitions,
-    get_write_tool_names,
-    strip_tool_access,
 )
-from frigate.genai.utils import (
-    build_assistant_message_for_conversation,
-    parse_tool_calls_from_message,
-)
-from frigate.jobs.export import ExportQueueFullError, start_export_job
+from frigate.genai.utils import build_assistant_message_for_conversation
 from frigate.jobs.vlm_watch import (
     get_vlm_watch_job,
     start_vlm_watch_job,
     stop_vlm_watch_job,
 )
-from frigate.models import Event, Export, ExportCase
-from frigate.record.export import PlaybackSourceEnum
-from frigate.util.file import get_event_thumbnail_bytes, load_event_snapshot_image
+from frigate.models import Event
 from frigate.util.object_names import get_categorized_object_names
 
 logger = logging.getLogger(__name__)
 
 router = APIRouter(tags=[Tags.chat])
 
-# Tool result recorded for a rejected write tool call. Providers require a
-# result for every requested call; the user's intent is conveyed in a
-# follow-up user message built by _rejection_message.
-TOOL_REJECTED_RESULT: dict[str, str] = {"error": "user_rejected"}
-
 
 class ToolExecuteRequest(BaseModel):
     """Request model for tool execution."""
@@ -683,39 +666,29 @@ async def _get_live_frame_image_url(
         frame = frame_processor.get_current_frame(camera, {})
         if frame is None:
             return None
-        return _encode_frame_data_url(frame)
+        height, width = frame.shape[:2]
+        target_height = 480
+        if height > target_height:
+            scale = target_height / height
+            frame = cv2.resize(
+                frame,
+                (int(width * scale), target_height),
+                interpolation=cv2.INTER_AREA,
+            )
+        _, img_encoded = cv2.imencode(".jpg", frame, [cv2.IMWRITE_JPEG_QUALITY, 85])
+        b64 = base64.b64encode(img_encoded.tobytes()).decode("utf-8")
+        return f"data:image/jpeg;base64,{b64}"
     except Exception as e:
         logger.debug("Failed to get live frame for %s: %s", camera, e)
         return None
 
 
-def _encode_frame_data_url(frame: np.ndarray, target_height: int = 480) -> str:
-    """Downscale a BGR frame and encode it as a JPEG data URL for the model."""
-    height, width = frame.shape[:2]
-    if height > target_height:
-        scale = target_height / height
-        frame = cv2.resize(
-            frame,
-            (int(width * scale), target_height),
-            interpolation=cv2.INTER_AREA,
-        )
-    _, img_encoded = cv2.imencode(".jpg", frame, [cv2.IMWRITE_JPEG_QUALITY, 85])
-    b64 = base64.b64encode(img_encoded.tobytes()).decode("utf-8")
-    return f"data:image/jpeg;base64,{b64}"
-
-
-def _request_roles(request: Request) -> list[str]:
-    """Roles from the auth proxy header, split on the configured separator."""
-    separator = request.app.frigate_config.proxy.separator
-    header = request.headers.get("remote-role", "")
-    return [r.strip() for r in header.split(separator) if r.strip()]
-
-
 async def _execute_set_camera_state(
     request: Request,
     arguments: dict[str, Any],
 ) -> dict[str, Any]:
-    if "admin" not in _request_roles(request):
+    role = request.headers.get("remote-role", "")
+    if "admin" not in [r.strip() for r in role.split(",")]:
         return {"error": "Admin privileges required to change camera settings."}
 
     camera = arguments.get("camera", "").strip()
@@ -765,189 +738,6 @@ def _execute_get_categorized_object_names(
     return {"names": names}
 
 
-def _execute_get_export_cases(allowed_cameras: list[str]) -> dict[str, Any]:
-    """List export cases with how many accessible exports each one holds."""
-    from peewee import fn
-
-    count_rows = (
-        Export.select(Export.export_case, fn.COUNT(Export.id))
-        .where(Export.camera << allowed_cameras, Export.export_case.is_null(False))
-        .group_by(Export.export_case)
-        .tuples()
-    )
-    counts = {case_id: count for case_id, count in count_rows}
-
-    cases: list[dict[str, Any]] = []
-    for case in ExportCase.select().order_by(ExportCase.created_at.desc()):
-        created_at = case.created_at
-        cases.append(
-            {
-                "id": case.id,
-                "name": case.name,
-                "description": case.description,
-                "created_at_local": format_local_time(created_at.timestamp())
-                if isinstance(created_at, datetime)
-                else str(created_at),
-                "export_count": counts.get(case.id, 0),
-            }
-        )
-
-    if not cases:
-        return {"cases": [], "message": "No export cases exist yet."}
-
-    return {"cases": cases}
-
-
-async def _execute_create_export(
-    request: Request,
-    arguments: dict[str, Any],
-    allowed_cameras: list[str],
-) -> dict[str, Any]:
-    """Queue a recording export, optionally attached to an existing case."""
-    config = request.app.frigate_config
-    camera = (arguments.get("camera") or "").strip()
-    start_time = parse_iso_to_timestamp(arguments.get("start_time"))
-    end_time = parse_iso_to_timestamp(arguments.get("end_time"))
-    name = (arguments.get("name") or "").strip() or None
-
-    if not camera or start_time is None or end_time is None:
-        return {"error": "camera, start_time, and end_time are all required."}
-
-    if camera not in config.cameras:
-        return {"error": f"Camera '{camera}' not found."}
-
-    if camera not in allowed_cameras:
-        return {"error": f"Camera '{camera}' not found or access denied"}
-
-    if end_time <= start_time:
-        return {"error": "end_time must be after start_time."}
-
-    try:
-        playback_source = PlaybackSourceEnum(arguments.get("source") or "recordings")
-    except ValueError:
-        return {"error": "source must be 'recordings' or 'preview'."}
-
-    # Mirror the export API: attaching to an existing case is admin-only
-    # until case-level ACLs exist.
-    export_case_id = (arguments.get("export_case_id") or "").strip() or None
-    if export_case_id is not None:
-        if "admin" not in _request_roles(request):
-            return {"error": "Only admins can attach exports to an existing case."}
-        try:
-            ExportCase.get(ExportCase.id == export_case_id)
-        except ExportCase.DoesNotExist:
-            return {"error": f"Export case '{export_case_id}' not found."}
-
-    source_error = _validate_export_source(
-        camera, start_time, end_time, playback_source
-    )
-    if source_error is not None:
-        return {"error": source_error}
-
-    export_job = _build_export_job(
-        camera,
-        start_time,
-        end_time,
-        name,
-        None,
-        playback_source,
-        export_case_id,
-        chapters=config.cameras[camera].record.export.chapters,
-    )
-    try:
-        start_export_job(config, export_job)
-    except ExportQueueFullError:
-        return {"error": "Export queue is full. Try again once current exports finish."}
-
-    return {
-        "success": True,
-        "export_id": export_job.id,
-        "status": "queued",
-        "camera": camera,
-        "name": name,
-        "source": playback_source.value,
-        "start_time_local": format_local_time(start_time),
-        "end_time_local": format_local_time(end_time),
-        "export_case_id": export_case_id,
-        "message": "Export queued. It will appear on the Export page when finished.",
-    }
-
-
-async def _execute_get_event_image(
-    request: Request,
-    arguments: dict[str, Any],
-    allowed_cameras: list[str],
-) -> dict[str, Any]:
-    """Attach an event's thumbnail or snapshot for a vision model to view."""
-    event_id = (arguments.get("event_id") or "").strip()
-    if not event_id:
-        return {"error": "event_id is required."}
-
-    image_type = arguments.get("image") or "thumbnail"
-    if image_type not in ("thumbnail", "snapshot"):
-        return {"error": "image must be 'thumbnail' or 'snapshot'."}
-
-    try:
-        event = Event.get(Event.id == event_id)
-    except Event.DoesNotExist:
-        return {"error": f"Could not find event {event_id}."}
-
-    if event.camera not in allowed_cameras:
-        return {"error": f"Event {event_id} not found or access denied"}
-
-    chat_client = request.app.genai_manager.chat_client
-    if chat_client is None or not chat_client.supports_vision:
-        return {
-            "error": (
-                "The configured chat model does not support vision, so images "
-                "cannot be viewed."
-            )
-        }
-
-    note = None
-    frame = None
-    if image_type == "snapshot":
-        if event.has_snapshot:
-            frame, _ = load_event_snapshot_image(event)
-        if frame is None:
-            note = "Snapshot not available; returning the thumbnail instead."
-            image_type = "thumbnail"
-
-    if frame is None:
-        thumbnail = get_event_thumbnail_bytes(event)
-        if thumbnail:
-            frame = cv2.imdecode(
-                np.frombuffer(thumbnail, dtype=np.uint8), cv2.IMREAD_COLOR
-            )
-
-    if frame is None:
-        return {"error": f"No image is available for event {event_id}."}
-
-    result: dict[str, Any] = {
-        "id": event.id,
-        "camera": event.camera,
-        "label": event.label,
-        "sub_label": event.sub_label,
-        "zones": event.zones,
-        "start_time_local": format_local_time(event.start_time),
-        "image": image_type,
-    }
-    if event.end_time is not None:
-        result["end_time_local"] = format_local_time(event.end_time)
-    description = (event.data or {}).get("description")
-    if description:
-        result["description"] = description
-    if note:
-        result["note"] = note
-
-    result["_image_url"] = _encode_frame_data_url(frame)
-    result["_image_text"] = (
-        f"Here is the {image_type} for event {event.id} "
-        f"({event.sub_label or event.label} on {event.camera})."
-    )
-    return result
-
-
 async def _execute_tool_internal(
     tool_name: str,
     arguments: dict[str, Any],
@@ -1003,18 +793,11 @@ async def _execute_tool_internal(
         return _execute_get_profile_status(request)
     elif tool_name == "get_recap":
         return _execute_get_recap(arguments, allowed_cameras)
-    elif tool_name == "get_export_cases":
-        return _execute_get_export_cases(allowed_cameras)
-    elif tool_name == "create_export":
-        return await _execute_create_export(request, arguments, allowed_cameras)
-    elif tool_name == "get_event_image":
-        return await _execute_get_event_image(request, arguments, allowed_cameras)
     else:
         logger.error(
             "Tool call failed: unknown tool %r. Expected one of: search_objects, find_similar_objects, "
             "get_categorized_object_names, get_live_context, start_camera_watch, stop_camera_watch, "
-            "get_profile_status, get_recap, get_export_cases, create_export, get_event_image. "
-            "Arguments received: %s",
+            "get_profile_status, get_recap. Arguments received: %s",
             tool_name,
             json.dumps(arguments),
         )
@@ -1243,74 +1026,14 @@ def _execute_get_recap(
         return {"error": "Failed to fetch recap data."}
 
 
-def _pending_tool_calls_from_tail(
-    conversation: list[dict[str, Any]],
-) -> list[dict[str, Any]] | None:
-    """Return the tool calls of a trailing assistant message, if any.
-
-    A conversation that ends with an assistant message requesting tools is a
-    resume after an approval pause: the client sends the chain back with its
-    decisions and the loop runs those calls before asking the model again.
-    """
-    if not conversation:
-        return None
-    tail = conversation[-1]
-    if tail.get("role") != "assistant" or not tail.get("tool_calls"):
-        return None
-    return parse_tool_calls_from_message(tail)
-
-
-def _tool_calls_awaiting_approval(
-    pending_tool_calls: list[dict[str, Any]],
-    body: ChatCompletionRequest,
-    write_tools: set[str],
-) -> list[dict[str, Any]]:
-    """Return the write tool calls the user still has to decide on."""
-    return [
-        {
-            "id": tc["id"],
-            "name": tc["name"],
-            "arguments": tc.get("arguments") or {},
-        }
-        for tc in pending_tool_calls
-        if tc["name"] in write_tools and tc["id"] not in body.tool_decisions
-    ]
-
-
-def _rejection_message(tool_names: list[str]) -> dict[str, Any]:
-    """User message telling the model a rejected call should not proceed.
-
-    Uses list-form content so the UI, which only renders string user
-    content, does not show it as something the user typed.
-    """
-    names = ", ".join(name.replace("_", " ") for name in tool_names)
-    return {
-        "role": "user",
-        "content": [
-            {
-                "type": "text",
-                "text": (
-                    f"I do not want to proceed with the {names} call. Ask me for "
-                    "clarification or suggest adjustments instead of running it."
-                ),
-            }
-        ],
-    }
-
-
 async def _execute_pending_tools(
     pending_tool_calls: list[dict[str, Any]],
     request: Request,
     allowed_cameras: list[str],
-    decisions: dict[str, str] | None = None,
 ) -> tuple[list[ToolCall], list[dict[str, Any]], list[dict[str, Any]]]:
     """
     Execute a list of tool calls.
 
-    Calls the user rejected (per `decisions`) are not executed; they get a
-    placeholder result and a user message saying not to proceed is appended
-    after the tool results.
-
     Returns:
         (ToolCall list for API response,
          tool result dicts for conversation,
@@ -1319,28 +1042,10 @@ async def _execute_pending_tools(
     tool_calls_out: list[ToolCall] = []
     tool_results: list[dict[str, Any]] = []
     extra_messages: list[dict[str, Any]] = []
-    rejected_tools: list[str] = []
     for tool_call in pending_tool_calls:
         tool_name = tool_call["name"]
         tool_args = tool_call.get("arguments") or {}
         tool_call_id = tool_call["id"]
-        if decisions and decisions.get(tool_call_id) == "reject":
-            logger.debug(
-                "Tool %s (id: %s) was rejected by the user", tool_name, tool_call_id
-            )
-            rejected_tools.append(tool_name)
-            rejected_content = json.dumps(TOOL_REJECTED_RESULT)
-            tool_calls_out.append(
-                ToolCall(name=tool_name, arguments=tool_args, response=rejected_content)
-            )
-            tool_results.append(
-                {
-                    "role": "tool",
-                    "tool_call_id": tool_call_id,
-                    "content": rejected_content,
-                }
-            )
-            continue
         logger.debug(
             f"Executing tool: {tool_name} (id: {tool_call_id}) with arguments: {json.dumps(tool_args, indent=2)}"
         )
@@ -1374,21 +1079,17 @@ async def _execute_pending_tools(
                     if isinstance(evt, dict)
                 ]
 
-            # Extract _image_url from tool results — images can only be sent
-            # in user messages, not tool results
+            # Extract _image_url from get_live_context results — images can
+            # only be sent in user messages, not tool results
             if isinstance(tool_result, dict) and "_image_url" in tool_result:
                 image_url = tool_result.pop("_image_url")
-                image_text = tool_result.pop("_image_text", None) or (
-                    "Here is the current live image from camera "
-                    f"'{tool_result.get('camera', 'unknown')}'."
-                )
                 extra_messages.append(
                     {
                         "role": "user",
                         "content": [
                             {
                                 "type": "text",
-                                "text": image_text,
+                                "text": f"Here is the current live image from camera '{tool_result.get('camera', 'unknown')}'.",
                             },
                             {
                                 "type": "image_url",
@@ -1432,8 +1133,6 @@ async def _execute_pending_tools(
                     "content": error_content,
                 }
             )
-    if rejected_tools:
-        extra_messages.append(_rejection_message(rejected_tools))
     return (tool_calls_out, tool_results, extra_messages)
 
 
@@ -1480,8 +1179,6 @@ async def chat_completion(
         attribute_classifications=attribute_classifications,
         embeddings_language=_embeddings_language(config),
     )
-    write_tools = get_write_tool_names(tools)
-    llm_tools = strip_tool_access(tools)
     conversation = []
 
     # Build the system message only when the client hasn't already pinned one.
@@ -1520,10 +1217,6 @@ async def chat_completion(
     tool_calls: list[ToolCall] = []
     max_iterations = body.max_tool_iterations
 
-    # Resume after an approval pause: run the tail's tool calls (honoring the
-    # client's decisions) before asking the model for anything new.
-    resume_pending = _pending_tool_calls_from_tail(conversation)
-
     logger.debug(
         f"Starting chat completion with {len(conversation)} message(s), "
         f"{len(tools)} tool(s) available, max_iterations={max_iterations}"
@@ -1535,64 +1228,93 @@ async def chat_completion(
 
         async def stream_body_llm():
             nonlocal conversation, stream_iterations
-            pending: list[dict[str, Any]] | None = resume_pending
 
-            def _emit(payload: dict[str, Any]) -> bytes:
-                return json.dumps(payload).encode("utf-8") + b"\n"
-
-            def _emit_chain(extra: list[dict[str, Any]] | None = None) -> bytes:
+            def _emit_chain(extra: list[dict[str, Any]] | None = None):
                 # Return the full conversation (including the system message) so
                 # the client persists and replays it verbatim next turn.
-                return _emit(
-                    {"type": "messages", "messages": conversation + (extra or [])}
+                chain = conversation + (extra or [])
+                return (
+                    json.dumps({"type": "messages", "messages": chain}).encode("utf-8")
+                    + b"\n"
                 )
 
             while stream_iterations < max_iterations:
                 if await request.is_disconnected():
                     logger.debug("Client disconnected, stopping chat stream")
                     return
-
-                if pending is None:
-                    logger.debug(
-                        f"Streaming LLM (iteration {stream_iterations + 1}/{max_iterations}) "
-                        f"with {len(conversation)} message(s)"
-                    )
-                    async for event in genai_client.chat_with_tools_stream(
-                        messages=conversation,
-                        tools=llm_tools if llm_tools else None,
-                        tool_choice="auto",
-                        enable_thinking=body.enable_thinking,
-                    ):
-                        if await request.is_disconnected():
-                            logger.debug("Client disconnected, stopping chat stream")
-                            return
-                        kind, value = event
-                        if kind == "content_delta":
-                            yield _emit({"type": "content", "delta": value})
-                        elif kind == "reasoning_delta":
-                            yield _emit({"type": "reasoning", "delta": value})
-                        elif kind == "stats":
-                            yield _emit({"type": "stats", **value})
-                        elif kind == "message":
-                            msg = value
-                            if msg.get("finish_reason") == "error":
-                                yield _emit(
+                logger.debug(
+                    f"Streaming LLM (iteration {stream_iterations + 1}/{max_iterations}) "
+                    f"with {len(conversation)} message(s)"
+                )
+                async for event in genai_client.chat_with_tools_stream(
+                    messages=conversation,
+                    tools=tools if tools else None,
+                    tool_choice="auto",
+                    enable_thinking=body.enable_thinking,
+                ):
+                    if await request.is_disconnected():
+                        logger.debug("Client disconnected, stopping chat stream")
+                        return
+                    kind, value = event
+                    if kind == "content_delta":
+                        yield (
+                            json.dumps({"type": "content", "delta": value}).encode(
+                                "utf-8"
+                            )
+                            + b"\n"
+                        )
+                    elif kind == "reasoning_delta":
+                        yield (
+                            json.dumps({"type": "reasoning", "delta": value}).encode(
+                                "utf-8"
+                            )
+                            + b"\n"
+                        )
+                    elif kind == "stats":
+                        yield (
+                            json.dumps({"type": "stats", **value}).encode("utf-8")
+                            + b"\n"
+                        )
+                    elif kind == "message":
+                        msg = value
+                        if msg.get("finish_reason") == "error":
+                            yield (
+                                json.dumps(
                                     {
                                         "type": "error",
                                         "error": "An error occurred while processing your request.",
                                     }
+                                ).encode("utf-8")
+                                + b"\n"
+                            )
+                            return
+                        pending = msg.get("tool_calls")
+                        if pending:
+                            stream_iterations += 1
+                            conversation.append(
+                                build_assistant_message_for_conversation(
+                                    msg.get("content"), pending
+                                )
+                            )
+                            if await request.is_disconnected():
+                                logger.debug(
+                                    "Client disconnected before tool execution"
                                 )
                                 return
-                            requested = msg.get("tool_calls")
-                            if requested:
-                                stream_iterations += 1
-                                conversation.append(
-                                    build_assistant_message_for_conversation(
-                                        msg.get("content"), requested
-                                    )
-                                )
-                                pending = requested
-                                break
+                            (
+                                _executed_calls,
+                                tool_results,
+                                extra_msgs,
+                            ) = await _execute_pending_tools(
+                                pending, request, allowed_cameras
+                            )
+                            conversation.extend(tool_results)
+                            conversation.extend(extra_msgs)
+                            # Emit the running chain so the client can render tool
+                            # calls live and replay them verbatim next turn.
+                            yield _emit_chain()
+                            break
+                        else:
                             # Streaming never appends the final assistant message
                             # to the conversation, so add it to the chain.
                             yield _emit_chain(
@@ -1603,41 +1325,11 @@ async def chat_completion(
                                     }
                                 ]
                             )
-                            yield _emit({"type": "done"})
+                            yield (json.dumps({"type": "done"}).encode("utf-8") + b"\n")
                             return
-                    if pending is None:
-                        # The stream ended without a final message; nothing
-                        # more to run.
-                        break
-
-                awaiting = _tool_calls_awaiting_approval(pending, body, write_tools)
-                if awaiting:
-                    # Pause before running write tools. The client shows the
-                    # calls, collects decisions, and resends the chain.
-                    yield _emit_chain()
-                    yield _emit({"type": "approval_required", "tool_calls": awaiting})
-                    yield _emit({"type": "done"})
-                    return
-
-                if await request.is_disconnected():
-                    logger.debug("Client disconnected before tool execution")
-                    return
-                (
-                    _executed_calls,
-                    tool_results,
-                    extra_msgs,
-                ) = await _execute_pending_tools(
-                    pending, request, allowed_cameras, decisions=body.tool_decisions
-                )
-                conversation.extend(tool_results)
-                conversation.extend(extra_msgs)
-                pending = None
-                # Emit the running chain so the client can render tool
-                # calls live and replay them verbatim next turn.
+            else:
                 yield _emit_chain()
-
-            yield _emit_chain()
-            yield _emit({"type": "done"})
+                yield json.dumps({"type": "done"}).encode("utf-8") + b"\n"
 
         return StreamingResponse(
             stream_body_llm(),
@@ -1646,129 +1338,102 @@ async def chat_completion(
         )
 
     try:
-        pending_tool_calls = resume_pending
         while tool_iterations < max_iterations:
-            if pending_tool_calls is None:
+            logger.debug(
+                f"Calling LLM (iteration {tool_iterations + 1}/{max_iterations}) "
+                f"with {len(conversation)} message(s) in conversation"
+            )
+            response = genai_client.chat_with_tools(
+                messages=conversation,
+                tools=tools if tools else None,
+                tool_choice="auto",
+                enable_thinking=body.enable_thinking,
+            )
+
+            if response.get("finish_reason") == "error":
+                logger.error("GenAI client returned an error")
+                return JSONResponse(
+                    content={
+                        "error": "An error occurred while processing your request.",
+                    },
+                    status_code=500,
+                )
+
+            conversation.append(
+                build_assistant_message_for_conversation(
+                    response.get("content"), response.get("tool_calls")
+                )
+            )
+
+            pending_tool_calls = response.get("tool_calls")
+            if not pending_tool_calls:
                 logger.debug(
-                    f"Calling LLM (iteration {tool_iterations + 1}/{max_iterations}) "
-                    f"with {len(conversation)} message(s) in conversation"
-                )
-                response = genai_client.chat_with_tools(
-                    messages=conversation,
-                    tools=llm_tools if llm_tools else None,
-                    tool_choice="auto",
-                    enable_thinking=body.enable_thinking,
+                    f"Chat completion finished with final answer (iterations: {tool_iterations})"
                 )
+                final_content = response.get("content") or ""
 
-                if response.get("finish_reason") == "error":
-                    logger.error("GenAI client returned an error")
-                    return JSONResponse(
-                        content={
-                            "error": "An error occurred while processing your request.",
-                        },
-                        status_code=500,
-                    )
+                if body.stream:
+                    final_reasoning = response.get("reasoning")
 
-                conversation.append(
-                    build_assistant_message_for_conversation(
-                        response.get("content"), response.get("tool_calls")
-                    )
-                )
+                    chain = list(conversation)
 
-                pending_tool_calls = response.get("tool_calls")
-                if not pending_tool_calls:
-                    logger.debug(
-                        f"Chat completion finished with final answer (iterations: {tool_iterations})"
-                    )
-                    final_content = response.get("content") or ""
-
-                    if body.stream:
-                        final_reasoning = response.get("reasoning")
-
-                        chain = list(conversation)
-
-                        async def stream_body() -> Any:
+                    async def stream_body() -> Any:
+                        yield (
+                            json.dumps({"type": "messages", "messages": chain}).encode(
+                                "utf-8"
+                            )
+                            + b"\n"
+                        )
+                        # Emit the full reasoning trace up front when the
+                        # underlying client did not stream it
+                        if final_reasoning:
                             yield (
                                 json.dumps(
-                                    {"type": "messages", "messages": chain}
+                                    {"type": "reasoning", "delta": final_reasoning}
                                 ).encode("utf-8")
                                 + b"\n"
                             )
-                            # Emit the full reasoning trace up front when the
-                            # underlying client did not stream it
-                            if final_reasoning:
-                                yield (
-                                    json.dumps(
-                                        {"type": "reasoning", "delta": final_reasoning}
-                                    ).encode("utf-8")
-                                    + b"\n"
+                        # Stream content in word-sized chunks for smooth UX
+                        for part in chunk_content(final_content):
+                            yield (
+                                json.dumps({"type": "content", "delta": part}).encode(
+                                    "utf-8"
                                 )
-                            # Stream content in word-sized chunks for smooth UX
-                            for part in chunk_content(final_content):
-                                yield (
-                                    json.dumps(
-                                        {"type": "content", "delta": part}
-                                    ).encode("utf-8")
-                                    + b"\n"
-                                )
-                            yield json.dumps({"type": "done"}).encode("utf-8") + b"\n"
+                                + b"\n"
+                            )
+                        yield json.dumps({"type": "done"}).encode("utf-8") + b"\n"
 
-                        return StreamingResponse(
-                            stream_body(),
-                            media_type="application/x-ndjson",
-                        )
-
-                    return JSONResponse(
-                        content=ChatCompletionResponse(
-                            message=ChatMessageResponse(
-                                role="assistant",
-                                content=final_content,
-                                reasoning=response.get("reasoning"),
-                                tool_calls=None,
-                            ),
-                            finish_reason=response.get("finish_reason", "stop"),
-                            tool_iterations=tool_iterations,
-                            tool_calls=tool_calls,
-                            messages=list(conversation),
-                        ).model_dump(),
+                    return StreamingResponse(
+                        stream_body(),
+                        media_type="application/x-ndjson",
                     )
 
-                tool_iterations += 1
-                logger.debug(
-                    f"Tool calls detected (iteration {tool_iterations}/{max_iterations}): "
-                    f"{len(pending_tool_calls)} tool(s) to execute"
-                )
-
-            awaiting = _tool_calls_awaiting_approval(
-                pending_tool_calls, body, write_tools
-            )
-            if awaiting:
-                # Pause before running write tools; the client resends the
-                # returned chain with its decisions to continue.
                 return JSONResponse(
                     content=ChatCompletionResponse(
                         message=ChatMessageResponse(
                             role="assistant",
-                            content=None,
-                            tool_calls=[ToolCallInvocation(**tc) for tc in awaiting],
+                            content=final_content,
+                            reasoning=response.get("reasoning"),
+                            tool_calls=None,
                         ),
-                        finish_reason="approval_required",
+                        finish_reason=response.get("finish_reason", "stop"),
                         tool_iterations=tool_iterations,
                         tool_calls=tool_calls,
                         messages=list(conversation),
                     ).model_dump(),
                 )
 
+            tool_iterations += 1
+            logger.debug(
+                f"Tool calls detected (iteration {tool_iterations}/{max_iterations}): "
+                f"{len(pending_tool_calls)} tool(s) to execute"
+            )
             executed_calls, tool_results, extra_msgs = await _execute_pending_tools(
-                pending_tool_calls,
-                request,
-                allowed_cameras,
-                decisions=body.tool_decisions,
+                pending_tool_calls, request, allowed_cameras
             )
             tool_calls.extend(executed_calls)
             conversation.extend(tool_results)
             conversation.extend(extra_msgs)
-            pending_tool_calls = None
             logger.debug(
                 f"Added {len(tool_results)} tool result(s) to conversation. "
                 f"Continuing with next LLM call..."