It seems something broke indeed. On GitHub I think a patch has already been submitted. But waiting to be pushed. So should be fixed soon I hope…
1 Like
If your impatient you could edit the two files for now yourself: fix: don't use auto() for str enum by piitaya · Pull Request #1261 · fuatakgun/eufy_security · GitHub
I don’t think this is a permanent fix. But will hold you over until either this is rolled out or another fix is rolled out.
Anyone? Thanks.
Streaming seems to be a real pain with the eufy cameras. Sometimes it will play fine, other times it shows message below and if I click error it sorts itself out, other times I have to click stop / start multiple times
I have the same exact thing, same behavior and all. Been troubleshooting this forever…
Just did some tests with
seems to work better, so it’s the version of Go2rtc which is buggy
Hello
i remove old webrtc add-ons to keep only the native one.
But now my Eufy cameras don’t show up anymore in go2rtc server (no streams).
What to change in the config overall?
Thanks
im using webrtc addon still, not native, and all is working here
I managed to create a button to start the stream
If it starts, then a dynamic webrtc comes up with buttons to stop the stream.
When stopped, u dont see anything
1 Like
Thanks, could you share the code of the button?
Button:
type: custom:bubble-card
card_type: button
button_type: name
name: Camera Garage
icon: mdi:cctv
tap_action:
action: call-service
target:
entity_id: camera.garage
service: camera.turn_on
button_action:
tap_action:
action: call-service
target:
entity_id: camera.garage
service: camera.turn_onThen the dynamic tile
type: conditional
conditions:
- condition: state
entity: camera.garage
state: streaming
card:
type: custom:webrtc-camera
entity: camera.garage
ui: true
shortcuts:
- name: Play
icon: mdi:play
service: camera.turn_on
service_data:
entity_id: camera.garage
- name: Stop
icon: mdi:stop
service: camera.turn_off
service_data:
entity_id: camera.garage
1 Like
Yeah, I saw some whole thread on GitHub for go2rtc. I tried the unstable version and it only sometimes works for me. It sounds like the latest version broke it. Do you know how we can use an older version of go2rtc?
Also, for any individual camera that’s not a doorbell, I have hundreds of these responses:
14:55:14.841 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 > error=EOF url=http://192.168.1.X:8123/api/camera_proxy_stream/camera.garage_2?token=string_token_here
I was struggling with my doorbell setup. Installing go2RTC, various camera components, and even the Frigate Lovelace card, until I came across EufyP2PStream.
By following the add-on instructions for both go2RTC and the custom WebRTC-camera card, I’m now almost tempted to bring the doorbell finally into full production at home 
.
It’s because I’m deeply invested in the ecosystem; otherwise, I would never have purchased all these components, knowing how many parts are required for a seamless end-to-end experience with Home Assistant or any other integration (Google and Amazon solutions just don’t cut it).
The locked-down aspect of not being able to add a third-party door opener in the official app for example, really boggles my mind, especially since Eufy locks aren’t even available, at least not in the Netherlands.
Unfortunately, it looks like that solution you found only works with one camera and not multiple. Also, I couldn’t get it to work with any of my solar Eufy cameras.
I only use p2p for my doorbell and that works ok-ish. Do have the “issue” it switches to live mode at times causing for interesting issues on my in-house screens showing a dashboard including that cam, like looping the audio causing feedback 
Did anyone get this working successfully with an s330 solar camera? If so, how long are the load times? Any scheme loading issues? What setup do you have if all works smoothly for you?
Not sure if someone can help me with the doorbell T8210 in Home Assistant, it seems working better now, however when I start the P2P streaming, it mostly go to a older timeframe, mostly of the moment when I started a stream earlier.
So I created a flow when someone is ringing → start p2p and stream it to the nest hub, but then I get a older stream…
Hello, I had a few cameras (T8161) and a homebase 3 before getting into Home Assistant. For the past few months I have been building a dashboard, and now the time has come to integrate the cameras. I have installed all the stuff needed (Eufy Security and the eufy security ws addon) and with the latest update of HA it seems we can now use the picture entity card to show the webrtc-video stream.
It just doesn’t work very well.
The default view of the picture entity card is this:
Of course I want to show a snapshot of the latest stream. Maybe that is something I have failed to set up properly.
The biggest issue I have is streaming. In the eufy app, streaming start within 2 seconds, and is crystal clear. When I tap the picture card, I have an action that set camera_on, and then maybe after 10 seconds a choppy picture appears, or maybe I get an error that says the stream can’t be found, or some other error, or just some green crap. I tested the custom:webrtc-viewer and it was not much better.
What is going on here? Has it always been this bad or is it just lately? As a fellow software developer I am of course curious as to why it is not working better? Maybe it is the eufy software that has bad support for 3rd party integrations?
Needless to say, I do pray that this matter will be resorted, because we spent a lot of money on the eufy system and it is working great for us with the native software. On some places we can use grid powered cameras, but for most places it is not an option, so we need battery cameras.