Eufy Security Integration

what kind of cameras? i have the 2K Video Doorbell and a Solocam E20. On the doorbell person detection does work but video doesnt work at all and i don’t see how to access the snapshots. so not really much use.

Pretty much the same situation with the Solocam except that its in a permenantly unknown state in HA and can’t be set to Home/Away.

options seem to be:

  1. Remove Eufy integration from HA and just use the Eufy app seperate from HA
  2. Give up on Eufy as a bad job and look to find other equipment that works with HA. I’m thinking of replacing both cameras with any other battery powered camera, the doorbell with any battery powered switch and using Frigate for person detection, which already works very well with my wired cameras.

i’m not someone that expects HA to run without issue, i don’t mind a regular tinker. but i’d say its now been 6 months of not working and no indication that will change

Integration works well with these:

eufy security eufyCam 2 Pro, Kabellose Überwachungskamera, Sicherheitssystem 365 Tage Akkuleistung, HomeKit Kompatibilität, 2K Auflösung, IP67 Wasserschutzklasse, Nachtsicht, 2-Cam-Set : Amazon.de: Baumarkt

Someone knows, if it is possible that when the doorbell is pressed, a stream will start on the Google Nest Hub?

Someone knows more?

Hi, just start using this integration. Works well.
I don’t get the person_name attributes being populated though even though I can see in the Eufy Doorbell app that a person was detected and recognized. Anyone had success getting this in HA?
Thanks

Hi - is there a way to arm into schedule mode on Eufy if we have a keypad? Eg. I have CUS on the keypad set to schedule. Not hurrying to rebuild the schedule as it is finicky and I usually end up setting things wrong. Can I use that button maybe somehow to arm in schedule mode?

Hey,

I’m really struggling with the setup (still a newbie here with HA). I have followed all steps on this page - GitHub - fuatakgun/eufy_security: Home Assistant integration to manage Eufy Security devices as cameras, home base stations, doorbells, motion and contact sensors. but I’m still coming up blank.

I have a Eufy solo cam 2 which is connected to my network.

When I use the conditional card for Lovelace, I get the following message show

If I press start stream on the device itself it will change the logbook to show the queue size but when I view the camera its still slowing cannot find URL.

Any ideas?
Thanks

Using conditional cards as documented

Card 1

type: conditional
conditions:

  • entity: camera.backyard
    state: idle
    card:
    show_state: true
    show_name: true
    type: picture-entity
    entity: camera.backyard
    camera_image: camera.backyard
    tap_action:
    action: call-service
    service: camera.turn_on
    data: {}
    target:
    entity_id: camera.backyard

Card 2
type: conditional
conditions:

  • entity: camera.backyard
    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.backyard
      entity: camera.backyard
      name: Stop
    • type: custom:webrtc-camera
      entity: camera.backyard

RSTP is running. Managed to get it to stream for a few minutes then it turned off and I get the URL message

Same question, I cant get video working. Any suggestions?

Hallo all,

I’ve installed the addon now twice following all steps. It looks like it is working but I have a strange problem with all of my entry sensors. It seems they are not updating when a door is opened or closed.

I figured that the open/close event is to short before a new “fetch” but also when I open a door for longer then, let’s say, 30 minutes it’s not updating. I looked in the logs and found it full of errors. Any suggestion on what to do?

      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":0}}\x00'
}
2023-05-17 17:14:44.887  ERROR Station T8010P2322381E5F - CMD_NOTIFY_PAYLOAD Error: 
{
  error: SyntaxError: Unexpected token  in JSON at position 35
      at JSON.parse (<anonymous>)
      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":1}}\x00'
}
2023-05-17 17:15:04.631  ERROR Station T8010P2322381E5F - CMD_NOTIFY_PAYLOAD Error: 
{
  error: SyntaxError: Unexpected token  in JSON at position 35
      at JSON.parse (<anonymous>)
      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":0}}\x00'
}
2023-05-17 17:16:21.928  ERROR Station T8010P2322381E5F - CMD_NOTIFY_PAYLOAD Error: 
{
  error: SyntaxError: Unexpected token  in JSON at position 35
      at JSON.parse (<anonymous>)
      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":1}}\x00'
}
2023-05-17 17:16:25.998  ERROR Station T8010P2322381E5F - CMD_NOTIFY_PAYLOAD Error: 
{
  error: SyntaxError: Unexpected token  in JSON at position 35
      at JSON.parse (<anonymous>)
      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":0}}\x00'
}
2023-05-17 17:21:29.544  ERROR Station T8010P2322381E5F - CMD_NOTIFY_PAYLOAD Error: 
{
  error: SyntaxError: Unexpected token  in JSON at position 35
      at JSON.parse (<anonymous>)
      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":1}}\x00'
}
2023-05-17 17:21:35.362  ERROR Station T8010P2322381E5F - CMD_NOTIFY_PAYLOAD Error: 
{
  error: SyntaxError: Unexpected token  in JSON at position 35
      at JSON.parse (<anonymous>)
      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":0}}\x00'
}
2023-05-17 17:32:07.292  ERROR Station T8010P2322381E5F - CMD_NOTIFY_PAYLOAD Error: 
{
  error: SyntaxError: Unexpected token  in JSON at position 35
      at JSON.parse (<anonymous>)
      at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
      at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
      at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
      at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
      at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
      at Socket.emit (node:events:513:28)
      at UDP.onMessage [as onmessage] (node:dgram:930:8),
  payload: '{"cmd":1550,"payload":{"status":0}}\x00'
}

Once I reboot the addon and reboot home assistant everything seems to work fine. The log shows me the following but after a while it goes back to what happened above…

2023-05-17 18:05:59.105  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
2023-05-17 18:06:09.324  INFO  Connected to station T8010P2322381E5F on host 192.168.1.180 and port 25192 
2023-05-17 18:06:12.764  INFO  Push notification connection successfully established 
2023-05-17 18:07:13.363  INFO  Disconnected from station T8010P2322381E5F 
2023-05-17 18:07:18.444  INFO  Connected to station T8010P2322381E5F on host 192.168.1.180 and port 26767 
2023-05-17 18:08:22.297  INFO  Disconnected from station T8010P2322381E5F 
2023-05-17 18:08:27.358  INFO  Connected to station T8010P2322381E5F on host 192.168.1.180 and port 18258 
2023-05-17 18:09:31.248  INFO  Disconnected from station T8010P2322381E5F 
2023-05-17 18:09:36.310  INFO  Connected to station T8010P2322381E5F on host 192.168.1.180 and port 28795 
2023-05-17 18:10:40.205  INFO  Disconnected from station T8010P2322381E5F 
2023-05-17 18:10:45.282  INFO  Connected to station T8010P2322381E5F on host 192.168.1.180 and port 17378 
2023-05-17 18:11:49.131  INFO  Disconnected from station T8010P2322381E5F 
2023-05-17 18:11:54.189  INFO  Connected to station T8010P2322381E5F on host 192.168.1.180 and port 16541 
2023-05-17 18:12:49.943  INFO  Alarm mode for station T8010P2322381E5F changed to: DISARMED 
2023-05-17 18:12:50.504  INFO  Received push notification for changing guard mode 
{
  guard_mode: 63,
  current_mode: 63,
  stationSN: 'T8010P2322381E5F'
}
2023-05-17 18:12:56.293  INFO  Alarm mode for station T8010P2322381E5F changed to: HOME 
2023-05-17 18:12:56.654  INFO  Received push notification for changing guard mode 
{
  guard_mode: 1,
  current_mode: 1,
  stationSN: 'T8010P2322381E5F'
}

Please raise an issue to bropat’s repository, he could help

I have a eufy doorbell working via this integration, is there any way I can get the doorbell to chime if another button is pressed

Hello all,

I have a question. After a few days of trail and error I managed to get the entry sensors working in HA. For some reason the open/close state was not updating in the app while I was able to change the alarm state for homebase to away or home etc…

It turned out that the entry sensors (open / close state) only update if you allow push-notifications in the Eufy Security app. Else Eufy won’t send out the change of state.

Now its quite annoying to get notifications on my mobile all of the time when someone opens or closes a door or window so my question is, is it possible to have the open/close state in HA updated WITHOUT having 9000 push notifications on my phone. I thought about blocking the notifications on my phone from the app but that way I don’t get a notification when the alarm is triggered and that’s nor really helpful…

I would say no but maybe others have a different opinion

Does anyone know what the below error means?

offer: source 0 error: wrong response on DESCRIBE

I have set up the rtsp camera (2C Pro) in a dashboard card the same as another one that is showing correctly but the 2C Pro is returning the above error.

EDITED: just to say, the stream does show for a few seconds after creating the card but then disappears with the error.

Yes, that’s possible. Provided you are on a relatively new Android version. If you long press the notification in android you will end up in a menu allowing you to switch off or silence notifications. It should even allow you to keep some on (eg. Doorbell press) and others off.

Thanks for the reply. However I only have one category to choose from. I’m on the latest version of Android.

I’ve seen what you mean before but can’t seem to find it anymore.

My apologies, i am pretty new to this. I have the add on/integration working and can see my 2 cameras and doorbell entities. But I cannot see the video either as a snapshot or live

What am I doing wrong?



What is the difference between the two add-ons available that enable this integration?

The first was in the original documentation when I set up, the second is in the current documentation.

I migrated to the newer and higher version add-on but my door lock can not be locked or unlocked - although the state is updated if I lock it the old fashioned way. Moving back to the older add-on and all is working as intended again.

Thinks its because the rTSP stream only gets started after a motion detection.

enable motion detection, let it detect something and then the stream should work, might need a refresh of dashboard tho

struggling with the same

1 Like