Odd. When connected to my wifi the app has no problem accessing through the local IP. The second I put it on data and access through the domain it’s dead in the water. I can access the cameras through my domain when connecting from my LAN, but it seems trying to do the same through my mobile carrier’s network is the problem.
As an aside, found that my “needing a refresh” web browser is fixed simply by changing my bookmark from mydomain.com to mydomain.com/lovelace. I wonder if the reauthentication is part of that hiccup.
After the update, I no longer saw any histories for entities. the corresponding section loaded endlessly. After the return to 10.4 they are there again. You should simply never update to x.0
@Swallowtail try the PAT site now… it just started working. It’s a … somewhat questionable site (you’ll see what I mean if it loads for you).
I was also a bit disappointed in the entities it created, but just sifting through all of it now. The HACS integration has more detail, I think. But need more time to compare them.
It seems the Frigate-hass-card does not support the WebRTC changes. The live stream is just a static image now and the only error message is in the JS console.
Has anyone had luck with Unifi Protect and the new WebRTC stuff? I enabled a medium RTSP in Protect, reloaded the integration, I see the entity it created (camera.playroom_medium). I put a picture glance card on my dashboard but I’m only getting an update about every 10 seconds.
I’ve tried it with and without the new enhanced encoding or whatever it’s called (h.265).
With 2024.11.0 that page now loads the previews much faster. The static images refresh every 10 seconds. Clicking on the picture loads the video feed, but that still takes about 8 to 10 seconds to load and play. It is better now in terms of continuity of playback. Note I am running through cloudflared.
Could someone please clarify what the recommended setup is now for WebRTC?
I set up WebRTC ages ago to work with my UniFi Camera feeds and can’t quite recall the rationale for all of it. Before this update, I had the following:
an rtsp_to_webrtc INTEGRATION
an rtsp_to_webrtc ADD-ON
an rtsp_to_web ADD-ON
each camera entity setup as a “WebRTC” version via individual RTSP feeds from UniFi via the Generic Camera INTEGRATION
recently, I added the custom:frigate-card to view them
Does this WebRTC update mean I can remove the rtsp_webrtc INTEGRATION and both ADD-ONs, and get WebRTC natively from HA?
Do I still need separate Generic Cameras configured from the RTSP feed from UniFi or should the native UniFi Protect cameras work with WebRTC now?
Also, does the Frigate-Card really matter or should the standard Picture Entity Card in Live view work just as well as the Frigate Card?
Appreciate guidance and info here, as I haven’t yet upgraded and I’m trying to gauge how much time I need to carve out for the update. Thanks.
I think I need time to write a post about whether you still need the custom WebRTC component or the go2rtc addon. In short - there are cases where you need them. There are cases when you don’t need them anymore. It all depends on your goals.
Something about recorder taking > 10s to set up… while i was booting my offline backup server, it eventually seems to have finished starting, even though it didn’t look like it would.
You can also cut or copy paste cards using the 3 dots
We have some technical limitations from auto scroll but I will take a look if we can improve that.
I was going to post that I use the custom WebRTC, go2rtc and LG ThinQ components all of which seem to have moved to Core with this release. It’s great to see them included in core but instructions on what people who have been using custom components for months/years without any issues need to do would be much appreciated, ideally documented in the release notes.
