#frigate setup on HA when frigate is on a seperate VM via unraid?

7 messages · Page 1 of 1 (latest)

uncut comet
#

hey all, I've been using frigate for about 6 months, deployed directly through HACs - it worked totally fine, however, it would complain about the coral speeds, being ~110ms to detection, the UI tells me this is slow. Sometimes it would skip detections in a busy enviornment. (this HA instance is setup in a VM) deployed in unraid

I had some free time, and set up another frigate instances outside of HACs directly in a docker container via unraid, and the detection speed (with the same config file) is at 20 ms. it's definitely much better!

My questions -

  • has anyone seen anything similar? It makes sense to me, but I've pulled frigate up a "layer" (deployed in unraid->frigate, vrs unraid->ha->frigate). It kinda makes sense to me, but is this a valid thought process?
  • if it IS valid thought process, has anyone set up frigate in this way, and how would I get this seperate instance of frigate to be viewable from within HA? based on googling, frigate doesn't have any authentication and instead relies on whatever parent service is hosting
dense pike
#

All you need to do is point the Frigate integration to the IP address of your unraid server. You could use the internal docker IP as well (172.#.#.#), but that IP could change.

rigid pollen
uncut comet
#

oh, perfect. thanks guys!

uncut comet
#

derp, I re-read it a few times. the integration tab

dense pike
#

lol poke around long enough and you’ll find it 😉