Open Tierney11290 opened 1 month ago
Minor update: I was somehow able to view the stream for a split second using the custom webrtc card. No idea how or why it worked but I will say I just converted my Home Assistant environment over to a dedicated bare metal install (had Windows 10 for my Plex Server before) over from a Raspberry Pi 5. Not sure if that made a difference.
And even though I was able to view it for a split second in Home Assistant, I have not been able to since. I was able to get it to come up in VLC from my local PC for a split second as well. Going to continue troubleshooting.
Another update: I have disabled the Frigate addon that has go2RTC built-in and installed the standalone go2RTC instead. The stream still does not show up through using this addon.
However, I was able to install the eufyp2pstream addon and I am now able to stream the feed of the doorbell. If both are running at the same time, only the eufyp2pstream is viewable. I do see this addon trying to "inject" the doobell stream according to the go2RTC addon UI though. Not sure what I have configured wrong with this addon but this narrows it down a bit more.
Probably the final update: still unable to get this addon to work even with the stand alone go2rtc addon as opposed to the one through Frigate. The stream still works with the eufyp2pstream addon using go2rtc addon though (but not through Frigate). I believe the problem with using the Frigate go2rtc is the fact that for some reason my frigate has version 1.9.2 rather than the 1.9.4 version that go2rtc has, which is odd because frigate's documentation claims it comes with 1.9.4. The instructions on how to use a custom go2rtc version in Frigate is some of the most vague instructions I've ever read, but I digress.
I am definitely still doing something wrong with this addon for it not to work consistently but the documentation is confusing and contradictory so that's not helping things. Hopefully the issue and potential updates I've posted here will help someone later down the road!
Not sure if this is a bug so I opened an issue separate that of a bug. Please delete my other issue #1214 that was not yet meant to be submitted if you don't mind!
Describe the bug
Camera stream is blank when using the template webrtc custom card (or any method for that matter). It seems to get the URL after clicking the Play button to start the stream and shows that it is using MSE but has a blank image/stream once started.
To reproduce
Steps to reproduce the behavior:
**1. Configure integration and associated custom WebRTC card as laid out in Eufy Security Integration guide
Expected behavior
After pressing the Play button, the stream should appear after several moments
Additional information
Installation type: Home Assistant OS Home Assistant Core Version: core-2024.9.3 Eufy Security Add-on Version: 1.9.0 Eufy Security Integration Version: 8.0.4 Hardware Information: Raspberry Pi5 8GB
Camera Model: Eufy S330 (T8530K)
Live Streaming Protocol (RTSP/P2P): P2P
Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):
Would you share your device with me in case further debugging required? (Yes/No):
Yes
Additional context
Some of the readme steps are confusing particularly around Step 3, Substep 5 or contradicting such as the inclusion of RTSP Simple Server Addon but then also mentioning go2rtc even though RTSP Simple Server Addon is apparently no longer needed?
I've also been using Frigate (go2rtc built in) for my others cameras around the house with no issue but was getting nowhere with the Eufy Doorbell with it enabled so for the purpose of troubleshooting this, I have disabled Frigate and reinstalled WebRTC (Camera?) Addon. Also had issues even getting the custom WebRTC card to show when adding it to the dashboard but for some reason that started working. While I am a bit further on troubleshooting with all of that done, I still can't get anything more than a blank WebRTC card.
Thank you in advance for any and all assistance!
What I've done to try to fix the issue: