Eufy Security Integration

Hi @anon63427907 - firstly many thanks for the work on this, easy to follow and I am mostly up and running. I have the cards for my 3 cameras and the doorbell working, clicking them does the streaming (rtsp for the cameras and p2p for doorbell using webrtc-camera) and it works fine.

Doorbell automation using the ringing function also works fine, but I am at a loss when it comes to getting the cards to update the pictures from motion activation (the workaround for the local image encryption).

I have it set as per your examples, just cut down to just triggering on motion (no alarm or snoozing stuff), but it seems that the binary_sensor isn’t working?

Any advice?

alias: Eufy Front
description: Eufy Front
trigger:
  - platform: state
    entity_id:
      - binary_sensor.front_motion_detected
    id: sensor
    to: "on"
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id: sensor
        sequence:
          - service: eufy_security.start_p2p_livestream
            data: {}
            target:
              entity_id: camera.front
          - service: eufy_security.generate_image
            data: {}
            target:
              entity_id: camera.front
          - service: eufy_security.stop_p2p_livestream
            data: {}
            target:
              entity_id: camera.front
mode: single


My EufyCams are showing up as inactive, someone know how I can see a livestream? Furthermore before I had thumbnails, after a detection… even this is not visible anymore…

I want to receive a trigger in HA when someone presses the Eufy (2k) doorbell. Is that possible?
Thus I don’t need the videostream.

Hi @anon63427907

Can you tell me when the add-on will be updated?

Thanks,
Rien

I try to login but it failed.
I created a second user used this login name and password.
Country is correct NL
I tried port 3000 and 3001.
I couldn’t find the Trusted_Device_Name, I used Eufy

The log:

2023-02-24 00:32:08.393  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
2023-02-24 00:32:08.905  ERROR Response data is missing 
{
  code: 0,
  msg: 'Succeed.',
  data: undefined
}

What is wrong?

Please check here: [Bug]: Disconnection and log · Issue #196 · bropat/eufy-security-ws · GitHub

@bropat had created a new repository to manage the add on part with latest version. I myself had an issue on updating in my system but apparently it worked for him

Hi @anon63427907 ,

What kind of issue did you have?

Json serialization error, i had to update configuration (add a space and save it) and then worked fine.

Ik got segmentation fault during startup of the addon. Anyone know how to troubleshoot this?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/run.sh: line 118: 182 Segmentation fault /usr/bin/node /usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js --host 0.0.0.0 --config $CONFIG_PATH $DEBUG_OPTION $PORT_OPTION
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/run.sh: line 95: 192 Segmentation fault /usr/bin/node /usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js --host 0.0.0.0 --config $CONFIG_PATH $DEBUG_OPTION $PORT_OPTION
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Same here on a Pi4

After the inserting the suggested format for “stations” (as stated in the documentation) the configuration was exepted ands started. after acception, the addon shut itself down after the above fault… any suggestions?

Edit: used this https://github.com/bropat/hassio-eufy-security-ws/issues/2 and got the add-on to start.

Problem is solved in the latest release (.1.3.4)

I can confirm that the bropat (1.3.4) euf-sec-ws add-on works stable :partying_face:

Now yust need to find a way to get the doorbell-camera working again in my HA-dashboard :thinking:

How do you get the 1.3.4? For me there is no update?

Check here: Eufy Security Integration - #1487 by fuatakgun

1 Like

I removed the old Eufy-Sec-ws add-on and then added the Bropat Repo for the latest version.

1 Like

Ok, I got the new add-on running and I’m on 1.3.4. In the logs, I now see well-formed events coming from my T8900 door sensors. However, the Eufy Security integration still isn’t recognizing open/close events on the device, so no automations firing.

1 Like

Must be something stupid, but I tried installing the new addon 1.3.4.
I uninstalled and removed the old addon and repo, added the new one, finished the config as before but I am getting the following error. If anyone knows what I am doing wrong please?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
curl: (7) Couldn't connect to server
[17:57:30] ERROR: Something went wrong contacting the API
Error: failed loading config file /data/eufy-security-ws-config.json
Error: Cannot find module '/data/eufy-security-ws-config.json'
Require stack:
- /usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Module._load (node:internal/modules/cjs/loader:920:27)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at /usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js:26:22
    at Object.<anonymous> (/usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js:78:3)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js' ]
}
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

same here, open and close events don’t come in. i just get one close event when i start up the eufy security ws container. hoping these sensors work soon, would be cool to trigger the lights with them :sunglasses:

Reverted back to 1.3.0 with the old repo and all works fine. Not sure what I did wrong with 1.3.4 and the new repo :frowning:

Hi @anon63427907

I have eufy 2k doorbell and recently integrated it with HA using your add on. All seem to work fine except streaming and last event picture.

I want to stream from the doorbell if there is doorbell press or when I click a button it starts to stream. I’m sure this is possible but I cant get it work.

Can you tell me where I have gone wrong. Below is what I’m using for the card.

Thanks!

square: false
columns: 1
type: grid
cards:

  • type: conditional
    conditions:
    • entity: camera.doorbell
      state: idle
      card:
      show_state: true
      show_name: true
      type: picture-entity
      entity: camera.doorbell
      camera_image: camera.doorbell
      tap_action:
      action: call-service
      service: camera.turn_on
      data: {}
      target:
      entity_id: camera.doorbell
  • type: conditional
    conditions:
    • entity: camera.doorbell
      state: streaming
      card:
      type: vertical-stack
      cards:
      • show_name: true
        show_icon: false
        type: button
        tap_action:
        action: call-service
        service: camera.turn_off
        data: {}
        target:
        entity_id: camera.doorbell
        entity: camera.doorbell
        name: Stop
      • type: custom:webrtc-camera
        entity: camera.doorbell