Go to frigate_nvr

Frigate much slower going through HA than direct

Thumbnail image: Calling all experts and enthusiasts! Time is money, and with Squarespace, you can make even *more* when you offer your services with its all-in-one Commerce tools. So turn your practice into profit and your expertise into income.

Using the nabu.casa address means your request is going from your phone, to the Nabu Casa servers, then proxying to home assistant, which proxies to Frigate, and then the response traffic follows the same path.

In short, it’s not optimal. Ideally if you’re on your local network you won’t use the nabu.casa address and go direct to home assistant.

Outside the house there’s not much you can do.

Makes sense. Just that since upgraded to v14, it seems quite a bit slower through naba.casa than before. Perhaps there are some code optimizations that are due? Also, I am now running it on a dedicated i3 machine, whereas before I was running it on an i7 but under proxmox.

More replies More replies

I found the Nabu proxy was causing me a bunch of performance issues when trying to view Frigate content. Like any request would stall out while a video was streaming.

I ended up setting up a Cloudflare reverse tunnel proxy using their docker image. I limit the requests to the path for events. This works for either the HA endpoint or the Fridge API. Performance is much better and Nabu no longer locks up

If you have the opportunity them setup a reverse proxy and access your HA directly that way when outside your home network. I do it and its just as fast as if I was using the home network.