Computing/Frigate: Difference between revisions
From Cricalix.Net
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Coral support | Coral support | ||
When running in Incus, two different USB IDs need to be passed through - the Coral device initially shows up as one vendor/product, and then switches to another. If only the first is passed through, Frigate's libraries will initialize the device and then it vanishes from the container.<syntaxhighlight lang="yaml"> | When running in Incus, two different USB IDs need to be passed through - the Coral device initially shows up as one vendor/product, and [https://github.com/blakeblackshear/frigate/discussions/2599 then switches to another]. If only the first is passed through, Frigate's libraries will initialize the device and then it vanishes from the container.<syntaxhighlight lang="yaml"> | ||
devices: | devices: | ||
coral-google: | coral-google: | ||
Latest revision as of 06:21, 30 April 2026
Coral support
When running in Incus, two different USB IDs need to be passed through - the Coral device initially shows up as one vendor/product, and then switches to another. If only the first is passed through, Frigate's libraries will initialize the device and then it vanishes from the container.
devices:
coral-google:
productid: '9302'
type: usb
vendorid: 18d1
coral-raw:
productid: 089a
type: usb
vendorid: 1a6e
There's also a need to set a larger shared memory space.
devices:
shm:
path: /dev/shm
size: 256MiB
source: 'tmpfs:'
type: disk
Note that the /dev/shm has to be done with the yaml config or CLI; the LXC/D web UI that can be attached to Incus is not aware of the extra values when adding a disk.
