id: installation
Frigate is a Docker container that can be run on any Docker host including as a HassOS Addon. Note that a Home Assistant Addon is not the same thing as the integration. The integration is required to integrate Frigate into Home Assistant.
MQTT broker - Frigate requires an MQTT broker. If using Home Assistant, Frigate and Home Assistant must be connected to the same MQTT broker.
Frigate runs best with docker installed on bare metal debian-based distributions. For ideal performance, Frigate needs access to underlying hardware for the Coral and GPU devices. Running Frigate in a VM on top of Proxmox, ESXi, Virtualbox, etc. is not recommended. The virtualization layer often introduces a sizable amount of overhead for communication with Coral devices, but not in all circumstances.
Windows is not officially supported, but some users have had success getting it to run under WSL or Virtualbox. Getting the GPU and/or Coral devices properly passed to Frigate may be difficult or impossible. Search previous discussions or issues for help.
Frigate utilizes shared memory to store frames during processing. The default shm-size
provided by Docker is 64m.
The default shm-size of 64m is fine for setups with 2 or less 1080p cameras. If frigate is exiting with "Bus error" messages, it is likely because you have too many high resolution cameras and you need to specify a higher shm size.
You can calculate the necessary shm-size for each camera with the following formula:
(width * height * 1.5 * 9 + 270480)/1048576 = <shm size in mb>
The shm size cannot be set per container for Home Assistant Addons. You must set default-shm-size
in /etc/docker/daemon.json
to increase the default shm size. This will increase the shm size for all of your docker containers. This may or may not cause issues with your setup. https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file
By default, the Raspberry Pi limits the amount of memory available to the GPU. In order to use ffmpeg hardware acceleration, you must increase the available memory by setting gpu_mem
to the maximum recommended value in config.txt
as described in the official docs.
Additionally, the USB Coral draws a considerable amount of power. If using any other USB devices such as an SSD, you will experience instability due to the Pi not providing enough power to USB devices. You will need to purchase an external USB hub with it's own power supply. Some have reported success with this (affiliate link).
Running in Docker directly is the recommended install method.
Make sure you choose the right image for your architecture:
Arch | Image Name |
---|---|
amd64 | blakeblackshear/frigate:stable-amd64 |
amd64nvidia | blakeblackshear/frigate:stable-amd64nvidia |
armv7 | blakeblackshear/frigate:stable-armv7 |
aarch64 | blakeblackshear/frigate:stable-aarch64 |
It is recommended to run with docker-compose:
version: "3.9"
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: blakeblackshear/frigate:<specify_version_tag>
shm_size: "64mb" # update for your cameras based on calculation above
devices:
- /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions
- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- /path/to/your/config.yml:/config/config.yml:ro
- /path/to/your/storage:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000"
- "1935:1935" # RTMP feeds
environment:
FRIGATE_RTSP_PASSWORD: "password"
If you can't use docker compose, you can run the container with something similar to this:
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.yml:/config/config.yml:ro \
-v /etc/localtime:/etc/localtime:ro \
-e FRIGATE_RTSP_PASSWORD='password' \
-p 5000:5000 \
-p 1935:1935 \
blakeblackshear/frigate:<specify_version_tag>
:::caution
Due to limitations in Home Assistant Operating System, Frigate cannot utilize external storage for recordings or snapshots.
:::
:::tip
If possible, it is recommended to run Frigate standalone in Docker and use Frigate's Proxy Addon.
:::
HassOS users can install via the addon repository.
Configuration
tabfrigate.yml
in your config
directory with your detailed Frigate configuration:::tip
If possible, it is recommended to run Frigate standalone in Docker and use Frigate's Proxy Addon.
:::
When running Home Assistant with the Supervised install method, you can get the benefit of running the Addon along with the ability to customize the storage used by Frigate.
In order to customize the storage location for Frigate, simply use fstab
to mount the drive you want at /usr/share/hassio/media
. Here is an example fstab entry:
UUID=1a65fec6-c25f-404a-b3d2-1f2fcf6095c8 /media/data ext4 defaults 0 0
/media/data/homeassistant/media /usr/share/hassio/media none bind 0 0
Then follow the instructions listed for Home Assistant Operating System.
Use the helm chart.
Many people have powerful enough NAS devices or home servers to also run docker. There is a Unraid Community App. To install make sure you have the community app plugin here. Then search for "Frigate" in the apps section within Unraid - you can see the online store here
It is recommended to run Frigate in LXC for maximum performance. See this discussion for more information.
For details on running Frigate under ESX, see details here.