Thanks. After upgrade my hikvision cameras are working with picture-entity card but it’s too simple compared with go2rtc-related custom:webrtc-camera card used before.
Most missing features are 1-click fullscreen mode and integrated microphone on/off control.
Is there some alternative dashboard card usable for webrtc-mode cameras with integrated speaker?
it appears webrtc doesn’t natively support h265 encoding, resulting in 1fps stream. i switch my camera to h264 and this issue goes away… any support coming in the future, or do any of those go2rtc addons resolves this?
1 Like
I use the built-in generic camera integration.
I converted all my pages to the new sections mode and its been really nice and stable views of all I need on them and its also nice to have things actually centered when I only need 1 column when viewing on a side monitor.
1 Like
See Check WebRTC H265 support for Chrome and Safari · Issue #1439 · AlexxIT/go2rtc · GitHub
So there is a little hope for h265/webrtc in the near future.
1 Like
After reading many comments here about the new core WebRTC in 2024.11, I’m confused and hesitant to upgrade! I’m using generic cameras with @AlexxIT’s WebRTC which works great for me with real-time live broadcasting (Reolink cams). So, the new core WebRTC version is not based on that, but it’s a totally different version? If I upgrade to 2024.11 would I have to use the core version (which seems to have some issues) or can I disable/remove it and continue using the HACS version? Also just to verify, if I upgrade, the WebRTC Camera Card is no longer available?
Thanks, using reolink integration RTSP, and set to live the camera view in the picture card. Works like a charm.
Yes I know that. It is also clear that I could remove the default_config from the configuration.yaml and then add all integrations manually, but there must also be a way to exclude an integration - in this case go2rtc - from the default_config via configuration.yaml?
If I deactivate the WebRTC cloud connection, it doesn’t help. go2rtc is still loaded and even with Core 2024.11.1 it still causes errors.
Probably they are still there, but hidden!
Did you read the part about the imported cards section?
When the dashboard is converted to the new sections layout, you have to go to edit mode, en drag the cards out of the imported cards section .
Yes! Thanks for the tip! I have custom config, not default, so in this case it’s mandtory to add this line into config:
go2rtc:
After restart there’s no more delay. Perhaps this shoudl be pointed out more clearly…
1 Like
WebRTC custom card uses go2rtc app as streaming core.
Starting from 2024.11 - HA core uses same go2rtc app for build-in lovelace cards.
They both uses different binaries of same app. Same technology. Both can works simultaneously.
2 Likes
I found even better “system”: an old thread: user arturpragacz wrote an addon which does exactly what we need: exclude only what we don’t want to be loaded in default_config, rather to exclude all, then include wanted (and forget some…). i installed it and it seems that it works just fine.
1 Like
After updating to 2024.11 i deleted RTSP to WEBRTC because it is build in in this version.
However my camera streams are much slower than before ??
Someone else having this issue ?
Yeah I just tested exactly this. After removing the integration the videos had poor latency. I’m using reolink camera with reolink integration. It was bad with both RTSP and flv setting. Doing a restore now. I feel the inclusion of webrtc in 2024.11 needs more explanation than I can currently find.
2 Likes
I have the same setup, RTSP to WEBRTC with reolink integration.
Before the update it worked like a charm.
I restored already and it looks fine now.
I’ll wait for some news about this issue.
As you said it needs more explanation !!
1 Like
Removing default config and adding everything in except go2rtc is the way you exclude go2rtc. There is no other way.
OK, thanks for the info and it’s a shame that it doesn’t work. I was hoping that I could exclude certain things from the default_config: using configuration.yaml.
Something like:
default_config:
exclude:
go2rtc
You can. Read my post above!
Sorry, I should have been more precise. 
I mean that you can do it directly under/with HA without having to install any additional custom integrations. I assumed that this is possible with the default_config: using exclude: just like with recorder:, logbook: etc.
@petro using pipUp from here: GitHub - rogro82/PiPup: Enhanced notifications for Android TV
Sent an rest command with an go2rtc link like this:
- data:
title: Ding Dong!
message: Es steht jemand vor der Tür!
width: 960
height: 720
duration: 60
url: http://192.168.0.8:1984/stream.html?src=doorbell_main&mode=webrtc
enabled: true
action: rest_command.pipup_url_on_tv_wz
How can i archive this with the new integrated go2rtc version? (get the link)
Do i have to enable debug_ui?
PS.: i know that HA go2rtc port is 11984, but when changing this, it doesnt work.
Thank you
1 Like