In the future, it will likely be renamed from clips to snapshots. /media/frigate/clips: Used for snapshot storage.You will also see a few files alongside the database file while Frigate is running. /config: Used to store the Frigate config file and sqlite database.Docker volume mappings can be used to map these to any location on your host machine. Storage įrigate uses the following locations for read/write operations in the container. Search previous discussions or issues for help. Getting the GPU and/or Coral devices properly passed to Frigate may be difficult or impossible. Windows is not officially supported, but some users have had success getting it to run under WSL or Virtualbox. The virtualization layer often introduces a sizable amount of overhead for communication with Coral devices, but not in all circumstances. Running Frigate in a VM on top of Proxmox, ESXi, Virtualbox, etc. For ideal performance, Frigate needs access to underlying hardware for the Coral and GPU devices. Preparing your hardware Operating System įrigate runs best with docker installed on bare metal debian-based distributions. If using Home Assistant, Frigate and Home Assistant must be connected to the same MQTT broker. MQTT broker (optional) - An MQTT broker is optional with Frigate, but is required for the Home Assistant integration. The integration is required to integrate Frigate into Home Assistant. Note that a Home Assistant Addon is not the same thing as the integration. Frigate is a Docker container that can be run on any Docker host including as a HassOS Addon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |