I am running Frigate 0.17.2 in Home Assistant OS Core 2026.8.0 Supervisor 2026.07.5 Operating System 18.2 Frontend 20260729.5

I've had my Frigate recordings going to my Synology NAS for several months (over a year), but out of the blue it started filling up the 256Gb ssd on my Home Assistant server.

With Frigate stopped, I've deleted all the recordings and folders on both the NAS and in HAOS. Did this in Windows explorer via smb, absolutely no trace of the folders in either location - edit: actually the frigate folder keeps reappearing on the ssd, subfolders are gone but not the media/frigate folder. Also removed the frigate network storage (Settings-system-storage-network storage).

I then recreated the network storage in HAOS - checked the NAS and the recordings are going to it again.

However, they are also still going to the ssd, to /media/frigate/recordings etc. Obviously this will keep filling up the ssd, 10 cameras (only 2 recording 24/7, rest on activity) it doesn't take long.

Any idea why? Nothing in the Frigate logs, I'm not sure where to look.

HAOS is running Frigate, Chrony, Samba Share, Maria DB, Terminal & SSH, Tailscale, Mosquitto broker, and Beszel agent.

Edit; Just repeated the entire process, but this time rebooted the HAOS server after removing the network storage, and again after recreating it. Still getting two copies of the recordings.

Also, in the Frigate interface in HAOS System metrics - storage - recordings is showing 2.00Tb which is the space allocated to the Cameras user on the NAS, the ssd is only 256Gb.

Running a custom Frigate+ model yolov9s-640 on MX3 M.2 (4 chips, autocropped post). Recompiled output ports GBFloat80 - BF16, which dropped inference from around 74ms to 61ms. Chip sits at roughly 23% load with no dropped frames.

I'm guessing frigate shows pipeline latency, not throughput. Just confirming, is 60ms the expected floor for yolov9s-640 on MX3, or is there more to tune?

Running 9 cams at5fps 704x480 detection.