I just installed 2 of these and used the WebRTC card to place the camera views on a couple of dashboards with the ID of the 'Fluent' entity (no idea how they came up with that name) as the card's URL. All worked as expected and both camera views showed on the dashboard - until the following day - today.
One of the doorbell cams is still showing on the dashboard, but the other one shows an icon with a line through it which I guess means not accessible, even though it keeps retrying, but never succeeds.
Since the install I did update Home Assistant from 2026.6 to 2026.6.1 but that seems an unlikely cause as both cameras would be affected, but it is specifically only this one and adding another card for the same camera shows the same problem.
Here's the odd thing though, if I access the camera directly through the Reolink Integration, the device and then that Fluent entity, the camera popup perfectly displays the stream from the camera. So it appears there is no actual problem with the camera, but for some reason the WebRTC card which was originally able to display this camera feed is now not able to do so, while I CAN view it through its Device/entity.
Both are PoE devices so this is not a WiFi problem and anyway as I said, it is only in the dashboard card this problem has arisen and nothing has been changed in the card's YAML. There's only 2 lines, one of which is the entity ID which is exactly correct, did work when first configured but now refuses to do so, yet its identical twin (exact same config apart from name) continues to work as it should.
I hate having to ask, but anyone any ideas why one doorbell camera of the 2 will no longer work in the WebRTC card on a dashboard?
Logger: frontend.js.modern.202605274
Source: components/system_log/__init__.py:329
First occurred: 18:20:56 (92 occurrences)
Last logged: 19:01:45
Uncaught error from Safari 26.5 on macOS 10.15.7 InvalidStateError: The object is in an invalid state. /webrtc/video-rtc.js:452:39
That involves WebRTC and the time is probably correct as the page was open and multiple redraws and failures, but…
While I am using Safari version 26.5, I am currently running the latest MacOS Tahoe which is v26.5.1, so where did MacOS 10.15.7 come from? That's Catalina and I don't think I have any Mac running that, let alone accessing Home Assistant with it. So not sure what to make of that.
I tried a Picture Glance card and then a Picture Entity card. Both worked perfectly with the troublesome camera feed, but the former was more complicated than the latter which also opens the entity view of the camera feed when clicked which is handy.
So I have working dashboard displays of all the camera feeds, but the question still remains, why did a formerly working WebRTC card stop working with a perfectly functioning camera entity while another WebRTC card continues to have no problem at all with a virtually identical camera device?
Interesting to note that other users have experienced the same bizarre behaviour from the WebRTC card, so I guess I'll stop using that and instead use working alternatives as mentioned above.
I use the webrtc-camera card because I can dynamically change its behavior, when working with go2rtc. But it does have its quirks. Sometimes (fortunately, very rarely) it won't display the stream. A simple page refresh doesn't help: I need to restart the companion app on my phone.
As I mentioned, I like the dynamic nature of this card. For example, I have a view for intercom calls. The calls are placed via SIP, but I can switch the camera audio independently of SIP.
if ya have the picture glance card....tiny in overview >
what i did is as follow..did make a qucik link to navigate to a path.....
then made a new view (subview)
and picture entity (big) wiht all config options in it...
also made in there a quicklink to go back to overview.....
that way ya got a bigger cam view (if on tablet etc)
