I thought it was just. I am having slow loading of the video along with stuttering. I will play a little, pause, play a little, etc..
This is a standalone Frigate setup running an Intel I5-6600K cpu and coral PCIe based detector.
CPU is around 35% and GPU is showing less than 4% usage. Running docker 27.1.1 on Debian 12.6
Edit: Seems to be more noticeable on higher resolution cameras. On my reolink RLC-823A @ 3840*2160 it is really noticeable. Now that I look at it again, every second that ticks by on the time from the camera, the video does a "burst" then stops, then the next second comes up and I get a video "burst", repeat. This is on multiple browsers and a Windows box and MAC laptop. No noticeable increase in GPU or CPU usage on the Frigate server.
I have had to set my frigate to use sub stream to record with. I can't play recordings on my mobile if the resolution is too high 😴
How are you accessing Frigate? We've seen a couple of reports from other users for recordings loading slowly when using the HA ingress proxy. When accessed directly, there are no slowdowns.
I access frigate through the addon for Home Assistant. I don't have frigate running next to Home Assistant 🤔
Is this when trying to play recordings or clips through the Home Assistant media browser? If so, this has always been an issue for me. Same when trying to watch recordings/clips through the lovelace card.
For me there are no issues when using the standard frigate API in Home Assistant, but for whatever reason the media browser and lovelace card use something else for playing back the media, and they take forever to load.
For example, this standard API call to play a clip works just fine:
I'm not having any issues. I run Frigate on it's own device in docker and stream everything from the Frigate Proxy and haven't had any problems.
Different setup than yours.. but the hardware I run it on is less than what you have. It's just a little Belink NUC with 8 gb of ram and 6 cameras on it with a coral tpu.
So it's probably because I run it in Home Assistant that it teases 🙂↕️
I thought it was just. I am having slow loading of the video along with stuttering. I will play a little, pause, play a little, etc..
This is a standalone Frigate setup running an Intel I5-6600K cpu and coral PCIe based detector.
CPU is around 35% and GPU is showing less than 4% usage. Running docker 27.1.1 on Debian 12.6
Edit: Seems to be more noticeable on higher resolution cameras. On my reolink RLC-823A @ 3840*2160 it is really noticeable. Now that I look at it again, every second that ticks by on the time from the camera, the video does a "burst" then stops, then the next second comes up and I get a video "burst", repeat. This is on multiple browsers and a Windows box and MAC laptop. No noticeable increase in GPU or CPU usage on the Frigate server.
I have had to set my frigate to use sub stream to record with. I can't play recordings on my mobile if the resolution is too high 😴
More replies
More replies
How are you accessing Frigate? We've seen a couple of reports from other users for recordings loading slowly when using the HA ingress proxy. When accessed directly, there are no slowdowns.
I access frigate through the addon for Home Assistant. I don't have frigate running next to Home Assistant 🤔
More replies More replies
Is this when trying to play recordings or clips through the Home Assistant media browser? If so, this has always been an issue for me. Same when trying to watch recordings/clips through the lovelace card.
For me there are no issues when using the standard frigate API in Home Assistant, but for whatever reason the media browser and lovelace card use something else for playing back the media, and they take forever to load.
For example, this standard API call to play a clip works just fine:
https://my.public.domain/api/frigate/notifications/1709310861.924537-t7gmq4/clip.mp4
To play the same clip in Home Assistant media browser it's using the following URL that is uniquely generated each time and takes forever to load:
https://my.public.domain/7a64ddac-67ce-4cf2-8fde-0ba87759cf90
I use Nabu Casa with Frigate running on a different server than Home Assistant.
Yep, this is what we've seen as well. Something with HA's ingress proxy.
More replies
I'm not having any issues. I run Frigate on it's own device in docker and stream everything from the Frigate Proxy and haven't had any problems.
Different setup than yours.. but the hardware I run it on is less than what you have. It's just a little Belink NUC with 8 gb of ram and 6 cameras on it with a coral tpu.
So it's probably because I run it in Home Assistant that it teases 🙂↕️
More replies More replies
I have the same problem. Running in an lxc container inside proxmox. Takes quite a while to load the recording while CPU and RAM are not stressed.
More replies
I have seen this on my iPad & iPhone, but desktop browser seems to be fine.