Slow Camera Streams using HA Camera Entities

[kranked]

Android TV Hardware

Sony Android TV 75"

QuickBars Version

Latest

Home Assistant Core Version

Latest

What is happening?

It looks like quickbars uses HA's camera proxy for serving video streams which is essentially a series of static images. When I view the cameras on both the TV's I set up quickbars on the stream FPS is 3-5 FPS. I looked in to whether it's somehow using the substreams instead but it seems it isn't and quickbars is set to use HA's proxy. Any way to change this so the video stream is smooth?

Screenshots or Video

No response

Upload Configuration or Logs

No response

Relevant Logs

No response

Final Checks

• I have checked the entire troubleshooting section on the website, and tried all relevant steps.
• I have searched in the Q&A discussions if someone asked this question
• I have restarted both my Android TV and Home Assistant instance.

[Trooped]

Hey, I assume you're using the MJPEG camera entity. As you've said - it's literally a series of static images (MJPEG = Moving JPEG). This is the most basic option of camera streams inside QuickBars, and it's working as expected - this is how MJPEG streams work and function.
There's a detailed guide which is also referenced from Troubleshooting (which you checked that you went through entirely), which explains how to set up RTSP streams - which are higher quality + FPS, and in general allows more options within the app.
You need to follow all steps there, and provide an RTSP URL, which varies by your camera type and maker.

[kranked]

Thanks for your quick reply, I have read the guide, unfortunately I can't use RTSP to the camera as both streams are in use by Frigate (they have a limit of two (Tapo cameras). I think I may be stuck on static images.

[Trooped]

Thanks for clarifying, and you're definitely not stuck.
While I haven't tried it myself, some users reported using the restream/proxy stream function (I don't remember the exact name) of Frigate, which allows you to just create another RTSP stream URL based in Frigate.

[kranked]

Thank you @Trooped, I already use restream and will give this a go later.

[Gizmopower1]

I have same setup and had to use stream2 (lower res) in quickbars. I did use stream1 in frigate and quickbars, but for some reason it dosent work anymore, or only sometimes.
Let me know if U find a solution. i´ll post aswell if I get it to work with stream1 on both..

[Trooped]

I have same setup and had to use stream2 (lower res) in quickbars. I did use stream1 in frigate and quickbars, but for some reason it dosent work anymore, or only sometimes.
Let me know if U find a solution. i´ll post aswell if I get it to work with stream1 on both..

Some cameras don't support viewing RTSP streams from 2 sources at once. That sounds like the reason it sometimes works.

[Gizmopower1]

@Trooped Yes, this is not a Quickbars problem, but rather limited streams available.
2 rtsp streams can simultaneously run on most Tapo cameras. In my case c310
That in mind, there will probably be 1 stream in the tapo app on the phone, and one in frigate, then maybe somwhat other app in Home assistant..?
I had a stream running in ONVIF that I forgot about. :/
Also, if you close the Tapo app on phone, the stream will be available to use..
@kranked So, if you close the Tapo app on phone completly, and only have one rtsp strem in Frigate, the quickbar notifcation with same rtsp stream should work

[Gizmopower1]

@kranked
Gemini helped me to use the rtsp streams from frigate, and not directly from tapo cameras
It workes great for me...
Here is how:

When running Frigate in Docker (e.g., on TrueNAS) and trying to get live, zero-latency video via go2rtc into Home Assistant (using the WebRTC Camera integration), a port conflict often occurs, resulting in a "Wrong response" error or an endless loading spinner.

The issue is usually caused by the go2rtc web interface/API and the actual video stream trying to use the exact same port.
How we solved it (without stressing the cameras with dual streams):

In TrueNAS/Docker (Separate the ports):

Change the "Go2RTC Port" (which is the API/web interface) to port 1984.

Set the "RTSP Port" (which is the actual video stream) to use port 8554.

Set the "WebRTC Port" (for zero-latency video) to port 8555 (Ensure it supports both TCP and UDP).

In Home Assistant (Install the translator):

Install the WebRTC Camera integration (by AlexxIT) via HACS, and add it under Devices & Services. This "translates" the RTSP stream so it can actually be displayed it. (dont enter anything when asked, just hit the send button)

In Quickbars (Use the correct link):

In your Quickbars script use this exact link: rtsp://[YOUR_SERVER_IP]:8554/camera_name (replace with your server's IP and the specific stream name from your go2rtc config).

Once port 8554 is finally allowed to output a pure video stream instead of a webpage, the live view will appear immediately without any stuttering!

A little off topic maybe, but just wanted to let you know.
If any questions, dont hesitate to ask :)