That’s a shame, anyway I don’t have to look further for a solution. Thanks for the reply.
Integration doesn’t intervene existing rtsp or p2p functions, just reusing them. So, it is safe
They both coexist dont worry just go rtsp
Is there a fix for the tumbnail? I read something that the pictures are not stored in the cloud anymore. I wonder how this works when you dont have a security base. I only have the Eufy wired doorbell. Maybe it stores the pictuers on the SD card inside now.
Thanks! I turned RTSP on in the Eufy app. Does it automatically discover the RTSP addon that I’ve got running in HA? How can I tell that it’s working?
The Eufy app gives me a URL and credentials. Do I enter those into the addon somewhere?
If camera supports RTSP, you don’t need rtsp add-on, it is used for p2p based streaming
OK. Yes - I’ve got a floodlight that supports RTSP. Once I turn RTSP on in the Eufy app, I keep ending up at the “confirm” step with a title of “RTSP security”. It shows auth type, username and password. Do I set those somewhere in the addon? I don’t see where to do that.
If I view the settings of “sensor.driveway_streaming_source_address”, It’s “unknown”. I’ve tried restarting the Eufy addon.
@anon63427907 I just noticed the binary_sensor.doorbell_(global_)motion_sensor also isn’t working. Is that a known bug or is it just me? I wanted to create an automation based on motion to turn on the front door light…
I have been using this for years. As of right now, I am unable to figure out why my 2 Eufy Floodlight Camera will no longer send snapshots or streams. I have enabled and stopped and re-installed and still no action. All other sensors show up and work but just can not get the stream any longer.
Log only says:
2022-12-20 01:49:32.222 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-12-20 01:49:42.458 INFO Connected to station T8420H011935190F on host and port 15548
2022-12-20 01:49:42.559 INFO Connected to station T8420H01193504FA on host and port 15548
2022-12-20 01:49:47.144 INFO Push notification connection successfully established
2022-12-20 01:50:04.841 INFO Stopping the station stream for the device T8420H011935190F, because we haven’t received any data for 5000 seconds
Euffy changed where snapshots where stored and added encryption due to having lied to us about the security of its security cameras.
Snapshots are broken although streaming should still work depending on the camera.
Doing this may help
Go into the Eufy Security Add-ons
Go to configuration
Edit it in YAML
Add the following line
TRUSTED_DEVICE_NAME: DEVICENAME
There presently working on a fix here …[Question]: Cover_Path returns local file · Issue #273 · bropat/eufy-security-client · GitHub
Hum… that is a shame. So happy I got these cams on such a discount. lol They have caused me nothing greef and this add on was their only saving grace. haha
So I did see someone say something about that TRUSTED_DEVICE_NAME: DEVICENAME
but It was already in my setup. Still no joy on the stream. But very appreciative of your explanation. Now I can stop going crazy about it…
Yea this didnt work for me neither, only worked with the cams attached to the homebase but didnt with my indoor cams 401 Unauthorized
In theory, it is stored locally, if you have its url, you can extract it somehow, since the HA integration also looks at it locally.
The problem is getting it and this is now much harder to to the encryption. The apk may show how to but for now it’s broken tell they figure it out.
I have updated the first post with latest issues and announcements
Still seeing issues today. I tried switching TRUSTED_DEVICE_NAME
to Eufy
, eufyclient
, and 23jdsh14jdfsdf
(a random string). I also tried setting up 2FA on the shared Eufy account and used the trusted device label listed in the app, in my case, the name (model) of my phone SM-G981U1
. None of that has worked so far. Every time I start the container I see a 403 in the logs:
EufyError - Code: undefined Message: undefined (HTTP Code: 403) - requestUrl: https://security-app.eufylife.com/v1/passport/profile
I have updated initial post about this (doing it now) please check
I‘m also seeing the 403 error in my logs. I read the initial post and following the linked issue it looks like there are still issues even when setting a trusted device name.
I read some issues on GitHub and it sounds like quite a lot was changed by eufy after the security incident. Looks like there is now a v2 api and v1 resources are sometimes delivering 403?
But still I want to thank the maintainers of this addon for keeping up with the changes and fixing things. I’m sure things will be more stable soon, so thanks again.
I am also getting errors, all I have in my eufy system is the security sensors/keypad, no video camera or doorbell.
Tried adding EVENT_DURATION_SECONDS=10 and TRUSTED_DEVICE_NAME=XXX to the docker compose file and still no joy. XXX being my phone which has 2FA enabled (just done it), name of my HA instance, Eufy and eufyclient. Only difference being setting it to my phone has the error “Failed to set up” instead of “Start Listening was not completed in timely manner” so i assume the phone name is correct here?
2022-12-21 15:00:44.394 ERROR Generic Error:
EufyError Code: undefined Message: undefined (HTTP Code: 403)
details:
{
code: 'ERR_NON_2XX_3XX_RESPONSE',```