Eufy Security Integration

The new version does work at first but fails on the live stream end as noticed.

On the upside i never had the live stream working on my eufy security doorbell before.

It’s also quite the resource hog nearly doubling the cpu usage.

2022-12-24 16:26:30.530 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-12-24 16:26:40.811 INFO Push notification connection successfully established
2022-12-24 16:26:40.856 INFO Connected to station T8200T60213309E2 on host 192.168.1.166 and port 24946
2022-12-24 16:27:25.163 ERROR Message error
LivestreamNotRunningError Livestream for device T8200T60213309E2 could not be stopped, because it is not running
error stack:
• message_handler.ts:240 handle
src/lib/device/message_handler.ts:240:31
• task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
• server.ts:125 receiveMessage
src/lib/server.ts:125:21

Cpu usage before eufy 1.30 was around 20 percent.
This is with 9 blueiris cam’s connected

Cpu usage once new eufy security update bounces between 35 to 40%.

Once the update fails or is stopped cpu usage drops back to 20%.

This is with one security doorbell so with multiple cam’s this would be unusable due to cpu overhead.

Great step ahead but needs more work and refinement.

Uninstalled old version and installed 1.3, after setting the configuration and starting it, logs just say killed and Addon stops. Any idea? running on Raspberry Pi 3 (32-bit)

1 Like

This is a possible workaround for those waiting for the thumbnails to be fixed.

This automation switches on the doorbell camera, waits 3 seconds (might not be required), takes a snapshot and places it in a folder, then switches off the doorbell camera again. The snapshot can be used for the thumbnail of your camera card. Now I’m just waiting for the motion sensor to get fixed :slight_smile:

alias: Doorbell snapshot
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.doorbell_ringing_sensor
    to: "on"
condition: []
action:
  - service: camera.turn_on
    target:
      entity_id: camera.doorbell
    data: {}
  - delay:
      hours: 0
      minutes: 0
      seconds: 3
      milliseconds: 0
  - service: camera.snapshot
    target:
      entity_id: camera.doorbell
    data:
      filename: /config/www/doorbell_snapshot.jpg
  - service: camera.turn_off
    target:
      entity_id: camera.doorbell
    data: {}
mode: single
1 Like

Thank you!

Happy Holidays! :evergreen_tree: :champagne:

1 Like

Everyone, please uninstall previous version of addon, install the new version 1.3.0. It is very important to uninstall it because we need to get rid of previous login data which is not compatible anymore.

2 Likes

This would bypass the need to deal with the new security and avoid having to deal with encryption changes .

Interesting idea :thinking:

Agree but thumbnail would be 5 to 10 seconds delayed probably, compared to notification ones, but a good idea.

Actually, i see that @bropat is doing like this in his iobroker integration

1 Like

I also notice something strange regarding CPU usage which I never noticed before. In idle my CPU usage is about 5% (2vcores), when I start streaming my frontdoor camera (T8210) it goes up to about 25%, which is fine. After I close the stream the CPU usage goes down to 15% and stays there. While it should be going back to being about 5% I’d say. I’m on 1.3.0 btw. The idle usage stabilises back to being 5% after about 15 minutes btw, not a big deal but not sure if it’s something new or not.

I installed the Eufy security add-on 1.3.0 the first time. Created a new account in Eufy. A couple of minutes after I started the add-on, I got the following message in log. I tried uninstall, reinstall, restart homeassistant, but nothing fixed the issue. If anyone has any solution, please help.

2022-12-25 15:25:47.834 INFO Authentication properties changed, invalidate saved cloud token.
Killed

Can you remove the add-on and install it again and try later?

Still not working for me. Also completely removed everything and reinstalled it again.The Doorbell is still not working and still get below errors in the add-on log. Also not sure what exactly to put into the trusted device name as this is not described anywhere. So I used my home assistant IP address.
2022-12-25 16:38:47.036 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-12-25 16:38:57.349 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 21265
2022-12-25 16:39:00.498 INFO Push notification connection successfully established
2022-12-25 16:40:00.834 INFO Disconnected from station T8010P232028289A
2022-12-25 16:40:05.868 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 10140
2022-12-25 16:41:09.379 INFO Disconnected from station T8010P232028289A
2022-12-25 16:41:14.410 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 19779
2022-12-25 16:42:17.893 INFO Disconnected from station T8010P232028289A
2022-12-25 16:42:22.927 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 20433
2022-12-25 16:43:26.430 INFO Disconnected from station T8010P232028289A
2022-12-25 16:43:31.458 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 21551
2022-12-25 16:44:34.950 INFO Disconnected from station T8010P232028289A
2022-12-25 16:44:39.983 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 12469
2022-12-25 16:45:43.478 INFO Disconnected from station T8010P232028289A
2022-12-25 16:45:48.508 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 11674
2022-12-25 16:46:16.128 INFO Client disconnected with ip: 172.30.32.1 port: 60302 code: 1006 reason: Abnormal Closure
2022-12-25 16:46:16.130 INFO Client disconnected with ip: 172.30.32.1 port: 60304 code: 1006 reason: Abnormal Closure

In the past few days, I uninstalled the Eufy security add-on, reinstalled, restarted HA, but still got the same message in log: killed. I tried the same account I used in eufy app as well as a different account, but no difference. Should I go ahead and install the RTSP add-on and then integration even though the Eufy Security add-on is not working? I figured if Eufy security add-on does not work, the rest won’t work either. Any help is greatly appreciated.

I have standalone indoor Eufy 2k cameras and somehow I am still getting 401 Unauthorized.

Cameras connected to my HomeBase seem to work fine however. I have set the trusted device config.

I’ve tried resetting the RSTP settings from app, un-installing/re-installing the addon, no luck.
Anyone else having similar issues or is it just me?

OK I had to disable rstp security from the app and now it works, but how would i configure the rstp security parameters if I want to use them? :frowning:

1 Like

Could you use simple username and password for rtsp parameters? Maybe unescaped characters are breaking it?

When I restart the Eufy Security Addon it works for short period then it throws these errors and all my cameras become unavailable

I was hoping I could get some help as well. After a HUGE nightmare, I managed to get video to work on my E8201 working. May I suggest a new tutorial that includes updated screenshots/information? Unless things are just different somehow with mine.
Anyway, on to my problem. None of the sensors update. Primarily binary_sensor.doorbell_ringing_sensor. No matter what I do, its “off” I ring the doorbell, off. Wait a while, off. Ring it again. off. It only changes to “unavailable” when I was doing configuration updates to get the camera working. Same is true for all the other sensors.
I have googled around a bit, and for a different cameras it has been suggested to enable push notifications… However I don’t seem to have that option (at least that I can find.) I do however get notifications on my phone when the doorbell rings.
Finally, if it matters, this in in fact a battery doorbell, however I have it wired.
Thanks in advance, and thank you for creating this. Once I get it to work with doorbell presses, it will be very useful to me.

Please set RTSP security to disabled and try again, it fixed mine Indoor Pan Tilt Camera.
It was on digest and I was using admin/admin :slight_smile: and eufy had introduced additional requirements for those.

2 Likes

1.30 out and here some thoughts.

The previous issues seem to be gone and it working correctly now to show the stream.

No picture yet for obvious reason just the stream.
Beginning to wonder if grabbing a picture from the stream is a better idea as notifications tend to take 5-10 sec anyway . Then again i have a doorbell and not a camera.

Cpu usage is not being reported correctly in the addon with the actually being around 12% spike now and then to 20%

Of course this is the get it working stage the refinement comes after .

So far i not seeing any errors in the log. :+1:

Update: It fails eventually but takes longer to do so now.

2022-12-27 03:11:43.938 WARN Station T8200T60213309E2 - AES key could not be decrypted! The entire stream is discarded. - Error:
Error Error during decryption (probably incorrect key). Original error: Error: error:0407109F:rsa routines:RSA_padding_check_PKCS1_type_2:pkcs decoding error
error stack:
• NodeRSA.js:301 module.exports.NodeRSA.$$decryptKey
node_modules/node-rsa/src/NodeRSA.js:301:19
• NodeRSA.js:249 module.exports.NodeRSA.decrypt
node_modules/node-rsa/src/NodeRSA.js:249:21
• session.ts:1304 handleDataBinaryAndVideo
node_modules/eufy-security-client/src/p2p/session.ts:1304:63
• session.ts:1239 handleData
node_modules/eufy-security-client/src/p2p/session.ts:1239:18
• session.ts:1132 parseDataMessage
node_modules/eufy-security-client/src/p2p/session.ts:1132:26
• session.ts:965 handleMsg
node_modules/eufy-security-client/src/p2p/session.ts:965:26
• session.ts:127
node_modules/eufy-security-client/src/p2p/session.ts:127:56
• node:events:513 emit
node:events:513:28
• node:dgram:930 onMessage
node:dgram:930:8
2022-12-27 03:25:11.503 ERROR Message error
LivestreamNotRunningError Livestream for device T8200T60213309E2 could not be stopped, because it is not running
error stack:
• message_handler.ts:240 handle
src/lib/device/message_handler.ts:240:31
• task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
• server.ts:125 receiveMessage
src/lib/server.ts:125:21