When I go to look at the Ring live view, it briefly flashes the live view then immediately returns the error "Failed to connect WebRTC stream: Answer tried to set recv when an offer did not set send." It is happening on both cameras. Any idea how to fix? TIA
Turned out to be a problem with FireFox. Works fine in Chrome and Edge.
Has anyone figured this out, beyond âuse a different browserâ?
Unfortunately, itâs a bug/feature in FireFox. Hopefully, Mozilla will fix it.
It seems that rather than a bug on Mozillaâ side, it is an integration issue. Mozilla is following the proper protocol, while other browsers are not. I donât have enough technical knowledge to confirm this for myself, but I wouldnât be surprised if that is the case. Sure using another browser works, but this isnât Mozillas fault and the integration should be fixed. This was also an issue with NEST cameras, so hopefully it is a similar fix.
Iâd very much like to see this fixed.
Yes but we sort of like open source and non proprietary software here.
Surely home assistant is not going to force me to change to Chrome or Edge?
This is now happening to me with the companion app on Android and Chrome on Android. Same error, same symptoms. Quick flash of live view then this error. Ring doorbell using the official Ring integration in HA.
Core 2025.12.1
Supervisor 2025.12.2
Operating System 16.3
Frontend 20251203.1
Failed to connect WebRTC stream: Failed to execute âsetRemoteDescriptionâ on âRTCPeerConnectionâ: Failed to set remote answer sdp: Incompatible send direction
Same probleme, whit Brave browser and FireFox and LibreWolf but work on android app! Same error on tplink tapo camera
I have the issue with Chrome for the last several days. I have reset browser cache, upgraded HA Core, etc. On Windows and Android Chrome.
This issue persists on Chrome. I feel like the Ring API is having issues. Occasionally the ring integration fails to load.
Hi,
I have added a write-up regarding this issue here: Ring camera live view "Failed to connect WebRTC stream" ¡ Issue #138821 ¡ home-assistant/core ¡ GitHub
Contrary to the title of this discussion: This is not âsolvedâ and it is not a âproblem with Firefoxâ
The Summary: This affects Firefox and all Chromium-based browsers from v143 onwards. Chromium v143 was released only 5 days ago; as the rollout continues, user reports are going to spike.
The Technical Cause: Ringâs cloud services are returning malformed SDP answers that violate the spec. Newer browser versions (Firefox/Chromium) have stricter validation and are now rejecting these responses. Unless Ring fixes this server-side, we have to patch the response within the library.
Current Status & Help Needed
- The Fix: There was an existing PR for the
python-ring-doorbelllibrary to fix this for Firefox, but it has been ignored by maintainers since October. Iâve opened a new draft PR that expands the fix to cover Chromium. - Testing: I do not have a Home Assistant dev environment set up, so would appreciate if anyone could test that fix.
- Escalation: Given the library maintainer has been unresponsive for months, it is unlikely to be approved, so this needs to be escalated. Iâm new to the HA dev side so Iâm not certain on the process for overrides or forking;
Yep, seeing this too, Chrome version 143.0.7499.40
Same issue here on Chrome browser
this was working great⌠![]()
BTW everyone this works fine on Android.
Same issue with Wallpanel. It was working good until one week ago.
Nothing yet?
There are open pull requests, so a fix on the home assistant side is in the works.
Some folk are applying a patched version of the integration in the mean-time (Details here: WebRTC Answer Fix for Firefox and Device Addition by JackieGCodes ¡ Pull Request #491 ¡ python-ring-doorbell/python-ring-doorbell ¡ GitHub)
This has nothing to do with âAndroidâ; The issue manifests on any browser which utilises strict webrtc validation which includes Chromium based browsers and Firefox.
It will work on android if your browser or âandroid web viewâ version uses Chromium 142 or lower. And if thatâs the case, it probably wonât work for long as updates to Chromium are rolling out.
Interestingly, this problem is manifesting itself in Fully Kiosk and the HA app on my Android tablet (also with Chrome, but FK & HA app surprised me).
In conjunction with previous posts I confirm it also fails when running chrome on my MacBook Air running MacOS.
My ring cameras are still streaming well in the following scenarios:
â Fully Kiosk, Silk Browser, and HA app on older Fire 8 tablet
â Safari and the HA app with iOS on my iPhone
â Safari and the HA app with iPadOS on my iPad
â Safari and the HA app with MacOS on MacBook Air
HA Specs:
- Installation method: Home Assistant OS
- Core2025.12.3
- Supervisor2025.12.3
- Operating System16.3
- Frontend20251203.2