Nice, so i end up with non working cameraās ?
Great job !
Why would you end up with non working cameras?
recorder:
purge_keep_days: 30
is what Iām using.
If you are using the default_config I would think you should not be getting this warning. If you are not using default_config and you have rtsp_to_webrtc explictly configured in your configuration.yaml file or you have manually added it via the UI, I think all you have to do is to remove it and restart HA core which I would think auto-configure the gotrtc integration as it now takes over the role rtsp_to_webrtc use to doā¦
Well, I used the RTSPtoWebrtc add-on for several years without any issue.
My camerastreams (all Reolink) worked flawless.
After upgrading to 2024.11 and 2024.12 the streams are very slow and laggy. Completely useless.
I did a lot of research and was advised to remove the go2rtc integration from the default_config and continue to use the RTSPtoWebrtc add-on wich i did.
But even after doing that the streams are useless.
Even the codeowner from go2rtc @AlexxIT admitted that go2rtc doesnāt work very well with the RTSP-stream from Reolink cameras.
So what can i do about it ?
I really hope there will be a solution. 
At the very least, you could post in the 2024.11 release thread. Thatās when the change for Webrtc was released.
Posting in this monthās release thread just because you skipped an update wonāt help anyone
I was using the default_config first but also got this warning.
Wich I didā¦
https://community.home-assistant.io/t/2024-11-slick-dashboards-and-speedy-cameras/791375/330
So why spam the new release thread if you already knew the issue was from a previous release?
2 Likes
Just an FYI, the RTSP to Web Integration was not deprecated until 2024.12 (PR here), so he would not have known about the deprecation in 2024.11 (but yeah, slow camera streams would be a 2024.11 problem)
Thanks, I added that to my config.
I got the same issue again, this time I reverted the OS to 13.2. Iāll probably wait a few releases until I try againā¦
1 Like
But I upgraded Home Assistant OS to 14.0 and Iām in 2024.12.1, which suposedly comes with python 3.13.
However, when I type in terminal python still says v3.12.3.
Where did you read that?
Oh yeah, it says it in the release notes!
But itās not true, in my home assistant container it is 3.12.3
Good to see Tapo H200 gateway added, however is thee a way to play the āalamā through HA? Only option appears to be to select the style of alarm tone, but not send a play command via service call?
Are you serious ? The problem stil exists.
It canāt be repeated enough !!
Iām not the only one here.
There are hundreds of people !!
And not a 2024.12 problem ?
Calm down.
The error/warning message you posted had two options. Which one did you choose?
āyou can either keep using the built-in modern WebRTC provider and remove the rtc_to_webrtc integration or remove the g2rtvintegration to use the legacy providerā
So it means, that actually upgrade wasnāt done.
Iāve homeassistant core running on Debain (I did the upgrade manually).
Do you, by any chance, run Frigate 15 beta? I am and in my system thatās the culprit