docs/docs/troubleshooting/faqs.md
This error message is due to a shm-size that is too small. Try updating your shm-size according to this guide.
By default, Frigate removes audio from recordings to reduce the likelihood of failing for invalid data. If you would like to include audio, you need to set a FFmpeg preset that supports audio:
ffmpeg:
output_args:
record: preset-record-generic-audio-aac
Audio is only supported for live view when go2rtc is configured, see the live docs for more information.
Ensure your cameras send h264 encoded video, or transcode them.
You can open chrome://media-internals/ in another tab and then try to playback, the media internals page will give information about why playback is failing.
Frigate generally recommends cameras with configurable sub streams. However, if your camera does not have a sub stream that a suitable resolution, the main stream can be resized.
To do this efficiently the following setup is required:
detect -> width and detect -> height.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.
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.
These messages in the logs are expected in certain situations. Frigate checks the integrity of the recordings before storing. Occasionally these cached files will be invalid and cleaned up automatically.
If you see repeated "On connect called" messages in your logs, check for another instance of Frigate. This happens when multiple Frigate containers are trying to connect to MQTT with the same client_id.
SQLite does not work well on a network share, if the /media folder is mapped to a network share then this guide should be used to move the database to a location on the internal drive.
If MQTT isn't working in docker try using the IP of the device hosting the MQTT server instead of localhost, 127.0.0.1, or mosquitto.ix-mosquitto.svc.cluster.local.
This is because Frigate does not run in host mode so localhost points to the Frigate container and not the host device's network.
A camera being offline can be detected via MQTT or /api/stats, the camera_fps for any offline camera will be 0.
Also, Home Assistant will mark any offline camera as being unavailable when the camera is offline.
Frigate manages logs internally as well as outputs directly to Docker via standard output. To view these logs using the CLI, follow these steps:
docker logs -f frigate
Ctrl+C. If you'd like to learn more about using Docker logs, including additional options and features, you can explore Docker's official documentation.Alternatively, when you create the Frigate Docker container, you can bind a directory on the host to the mountpoint /dev/shm/logs to not only be able to persist the logs to disk, but also to be able to query them directly from the host using your favorite log parsing/query utility.
docker run -d \
--name frigate \
--restart=unless-stopped \
--mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 \
--device /dev/bus/usb:/dev/bus/usb \
--device /dev/dri/renderD128 \
--shm-size=64m \
-v /path/to/your/storage:/media/frigate \
-v /path/to/your/config:/config \
-v /etc/localtime:/etc/localtime:ro \
-v /path/to/local/log/dir:/dev/shm/logs \
-e FRIGATE_RTSP_PASSWORD='password' \
-p 5000:5000 \
-p 8554:8554 \
-p 8555:8555/tcp \
-p 8555:8555/udp \
ghcr.io/blakeblackshear/frigate:stable
No. Frigate uses the TCP protocol to connect to your camera's RTSP URL. VLC automatically switches between UDP and TCP depending on network conditions and stream availability. So a stream that works in VLC but not in Frigate is likely due to VLC selecting UDP as the transfer protocol.
TCP ensures that all data packets arrive in the correct order. This is crucial for video recording, decoding, and stream processing, which is why Frigate enforces a TCP connection. UDP is faster but less reliable, as it does not guarantee packet delivery or order, and VLC does not have the same requirements as Frigate.
You can still configure Frigate to use UDP by using ffmpeg input args or the preset preset-rtsp-udp. See the ffmpeg presets documentation.
Stationary tracking is designed to prevent this — a parked car should stay one tracked object and not generate new events. If you're getting repeated events for the same car, it's likely that Frigate is losing the tracked object and re-detecting it as a new one.
Open one of the events in Explore → Tracking Details. If the detection scores are low (< 70% or so), the model isn't confident the parked car is a car. This is common with the free COCO-trained object detection models on steep/top-down angles, partially occluded cars, foliage, or low-light footage. When detections fall below min_score for too many frames the tracker loses the object, and the next confident frame creates a brand new one.
What helps:
mobiledet to yolov9, or stepping up to a larger variant like yolov9-s over yolov9-t, can help (at the cost of inference time, and still on the COCO dataset). The biggest gains usually come from fine-tuning a model on images from your own cameras so it learns your specific scene. Frigate+ is a paid option that does this - models are trained on security-camera footage and can be fine-tuned on images you submit from your own setup.detect -> stationary -> max_frames for car — it artificially ends tracking and forces re-detection as a new object. See Stationary Objects.required_zones — see Zones. Make sure those zones use the default loitering_time: 0 unless you specifically want the review item to stay open until the car leaves.See Object Filters for more on tuning min_score and threshold — note that raising them too high will make this exact problem worse.