Closed tetele closed 3 weeks ago
Same thing is happening to me with plain generic_camera with plain rtsp url stream and no add on related to video streams.
The integration does not support the async offering approach added in 2024.11 and therefore the frontend fallsback to the sync one (The only one supported until 2024.11). You can see this from getCandidatesUpfront: true
. This means the frontend will resolve any candidate first and include them in the offer. On Chromium-based browser this can take up to the 40s
The integration does not support the async offering approach added in 2024.11
You mean the Frigate integration?
On Chromium-based browser this can take up to the 40s
But it seems to do nothing after resolving them in less than one second. It's not like it says it resolves anything else afterwards. Maybe I'm just not getting how this works...
But it seems to do nothing after resolving them in less than one second. It's not like it says it resolves anything else afterwards.
This was the reason why I implemented the async approach as Chromium based browsers will wait 40s to get all candidates. As some could be received later... Will check if we can fix this bug
Checklist
Describe the issue you are experiencing
I'm running HAOS on a Proxmox VM, Frigate in Docker on a Proxmox LXC on the same host, with the Frigate Proxy addon and Frigate integration.
I have WebRTC cameras provided by Frigate. Ever since I have updated to 2024.11 beta, whenever I open up the more info popup on any of them (to start streaming), I get a static image for 40 seconds, then after 40s the stream starts, but there is no time cursor at the bottom as there was until now.
Describe the behavior you expected
When I open up the more info dialog to allow the camera to start streaming, I get a loader "doughnut" (i.e. a circle rotating until the buffering is complete) and then the camera would start streaming, albeit with a couple of seconds of lag.
Steps to reproduce the issue
camera
entity, either from a dashboard or from the device pageWebRTC: 39960.857177734375 ms Ice gathering state changed complete
in the browser consoleWhat version of Home Assistant Core has the issue?
2024.11.0b2
What was the last working version of Home Assistant Core?
2024.10.3
In which browser are you experiencing the issue with?
Chrome 130.0.6723.70
Which operating system are you using to run this browser?
Windows 11
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
Additional information
No response