I have added “server: http://127.0.0.1:11984” to the custom webrtc card. 11984 is the internal API port from the go2rtc in the home assistant core. The streams I use are working again 
type: custom:webrtc-camera
url: rtsp://xxx:[email protected]:554/h264Preview_01_main
mode: webrtc
media: video
server: http://127.0.0.1:11984
Hello @karel123,
i found this documentation, but i’m unable to start go2rtc: go2rtc - Home Assistant
I deinstalled the addon, alos i deinstalled the webrtc addon.
do i habe to aktivare the go2rtc core version?
how did you do?
thanks
philipp
If you are using the default_config in your configuration.yaml, then the HA go2rtc integration should be running and it should have started the go2rtc server.
Do you have any log errors?
do i have to make a config ebtry in the configuaration.yaml? i deinstalled the old go2rtc addon, also the webrtc.
do you have an entry
default_config:
in your configuration.yaml? If yes, then you do not need to add another entry in configuration.yaml.
yes i habe this entry, where can i configure the go2rtc plugin? is the go2rtc.yaml needed?
HA’s go2rtc integration autoconfigures and runs the go2rtc server dynamically, so there is nothing for the user to do.
Do you have any cameras configured in HA?
Do we actually need custom:webrtc-camera anymore?
If you use 2-way audio I think you do.
IMHO the WebRTC integration seems to work better than the in-built one, although I’d love to remove the integration to reduce complexity.
I don’t know if ot helps someone. My Foscam was not working anymore after Update to Core 2024.11. Got a bunch of errors.
So I added a “Generic Camera” It worked, but the delays and quality of the image was disturbed. Finaly tried something stupid, for the Foscam: my password contains a “?”, replaced by “_” and voilá? Solved
How can a correct passw cause an issue ?
Anyway, i’ll give it a try…
Everything of mine still works OK, I’m just stuck in an endless loop that’s becoming tiresome! I Disable and Delete RTSPtoWebRTC and immediately get a notification that it’s been discovered and would I like to add it. I don’t have an option to say no, only ADD, and I can’t get rid of it.
So if I click Add, I get a notification that it’s been deprecated and I can delete it. So I delete it, and the loop resets and i’m back into the same vicious circle.
Ironically, I don’t even use it anywhere. I have the Reolink integration configured and Onvif setup and even after deleting RTSPtoWebRTC, all my stuff continues working.
I just don’t like having a permanent notification that won’t go away, because completing the action to remove the first notification in the loop causes the second to appear. and doing what it wants to remove that causes the first to appear. Argh, it’s diving me scatty 
By the way, before anyone asks or suggests it, I have tried restarting each time between these steps - no bueno…
Adding it and then just disabling it did the trick here to stop getting nagged.