Eufy Camera Integration

jbrukardt · January 27, 2021, 4:49pm

@skank seems like you and I had a lot of the same issues. You finally have yours all the way up and running with MaxW’s addon and fuzzys guide?

henry8866 · January 27, 2021, 5:06pm

Tried call the start stream rest_command from dev->services, the log shows “Status code 500. Payload: None”

WARNING (MainThread) [homeassistant.components.rest_command] Error. Url: http://xxxx:8087/toggle/eufy-security.0.xxx.cameras.xxx.start_stream. Status code 500. Payload: None

The rest sensor itself always showing “No Stream”.

the rest_command url in browser gave:

{
    error: "object has no state"
}

skank · January 28, 2021, 7:45am

I’m constantly moving through 3 addons…

the iobroker setup following fuzzys guide -> which is pushing the image too slow
mqtt addon which is fast but doesnht have always an image
the eufy security integration which only has the pics, and nothing else

So no, 30 posts further, i’m still stuck
Theres not 1 way to have things working which is fast using mqtt and has always an image… when i press my doorbell

I’m in desperate need of someone who succesfully mangaged to get a google home push the image of the doorbell camera once the doorbell is pressed.
I’m able to get that, but its always showing the wrong or no pic at all

timdonovanuk · January 28, 2021, 12:31pm

I really don’t think iobroker is the best long-term solution to all this. We’re effectively running an automation system WITHIN another automation system, just because iobroker integration got there first. Not that I have a solution or time to port it to HA/python but still just my two cents. I’m sad iobroker is even a thing, it’s a complete duplication of efforts against HA, and has 1/100 of the contributors. I’m all for open source and personal choice but reinventing the wheel is crazy, and iobroker isn’t even a wheel, “it’s more of a concept” (in it’s own words).

MaxW · January 28, 2021, 1:12pm

oh, seems like there is a new player on the field:

@Rihan is this yours?

fuzzymistborn · January 28, 2021, 2:22pm

It absolutely is not a great long term solution, I agree. But until a dev comes along who has time to port over/recreate a library that will work with HASS (it’s not me, it’s moved well beyond my skill to the point I’m going to put a disclaimer on the github library that it’s unmaintained) we’re stuck with it.

sgobat · January 29, 2021, 12:33am

I’m using the Eufy Home Assistant MQTT Bridge and it seems to be working well! I’m wondering if there’s a way around having to use notifications? I’d like HA to be the one giving me notifications. Perhaps I could just disable the notifications on all our phones? I use a third Eufy account for the bridge but it doesn’t seem like notifications are controlled individually by each user (which is silly, come on Eufy).

Laqoore · January 29, 2021, 10:56am

That’s exactly what I did. Thanks to the incredible work in https://greghesp.github.io/assistant-relay/docs/integration/hass + https://github.com/MaxWinterstein/homeassistant-addons/tree/main/eufy-ha-mqtt-bridge + automation now there is a video on my TV when someone presses the bell.

brendanheyu · January 30, 2021, 10:10am

Hi Folks,

I went the Eufy Home Assistant MQTT Bridge route for my Eufy 2k battery doorbell.

Things seem to have gone well. I can see a thumbnail of an event from the camera - and I have a simple MP3 playing when the button is pressed.

What I’m looking to have as an exposed property is the battery level. I can see a message in the mqtt bridge log:
{"message":"Publishing battery percentage 68% for T8210P002041013F","level":"debug","timestamp":"2021-01-28T01:09:05.322Z"}

Is there already an MQTT topic I should be subscribing to? I can’t seem to find a list of items that are exposed. I subscribed to the parent topic with a # hoping I would be inundated with a tonne of info and I could pat myself on the back. Not quite the way it happened
Thanks folks.

MaxW · January 30, 2021, 10:34am

If you take the walk over Configuration >> Integrations >> MQTT and then click on N devices you should see your cameras.
Should look like this:

Clicking on one should lead you towards this:

Is there a battery level available for you?

skank · January 30, 2021, 4:13pm

Hi,

Another one? Whats the difference with this one?

skank · January 30, 2021, 4:17pm

Theres no way arount notifications if you use the mqtt bridge

The bridge works well, but is slow giving pics…
I wonder if thats cause its just slow or if my doorbell is too far away from the base…

Still
I found it strange im the only one who wants a pic when doorbell is pressed and havent seen a solution for this

MizterB · January 30, 2021, 11:14pm

I had the same issue…the REST commands for starting/stopping the stream fail when using the ‘toggle’ method. I was able to get ‘set’ working instead. If I adapt the example in the @fuzzymistborn guide:

rest_command:
  eufy_start_stream:
    url: "http://IOBROKER:8087/set/eufy-security.0.CAMERA_ID.cameras.CAMERA_ID.start_stream?value=true"

  eufy_stop_stream:
    url: "http://IOBROKER:8087/set/eufy-security.0.CAMERA_ID.cameras.CAMERA_ID.stop_stream?value=true"

brendanheyu · January 31, 2021, 5:44am

Thanks Max,

My install of HA is a little bit of a basket case - my MQTT setup might not be what it should!

I had manually added the three properties I do have shown - I used the examples shown here https://github.com/matijse/eufy-ha-mqtt-bridge .

I don’t think that MQTT discovery is happening for me as it might be expected. Is there a way to manually add the battery value?

Thanks!

MaxW · January 31, 2021, 10:18am

This is somehow weird, I personally would consider to fix that installation

Using some MQTT Tool (I use MQTT.fx) you can see the topic that contains the battery state.
Is should be something like homeassistant/sensor/eufy/YOURDEVICEANDSERIALNUMBER_battery/state
Using this information you can create a sensor like this:

configuration.yaml

sensors:
- platform: mqtt
  name: cameras_YOURDEVICEANDSERIALNUMBER_battery
  state_topic: "homeassistant/sensor/eufy/YOURDEVICEANDSERIALNUMBER_battery/state"
  device_class: battery
  unit_of_measurement: "%"

untested, but should be a good starting point.

brendanheyu · February 2, 2021, 12:02am

Hi Max,

Worked a treat! Thanks for your work so far! So just for others that might be having the same issue with MQTT discovery or other issues with this - my manual MQTT integration looks like this:

# Doorbell
binary_sensor:
  - platform: mqtt
    name: Camera motion detected
    device_class: motion
    state_topic: homeassistant/binary_sensor/eufy/YOURDEVICEANDSERIALNUMBER_motion/state
    json_attributes_topic: homeassistant/binary_sensor/eufy/YOURDEVICEANDSERIALNUMBER_motion/attributes
    payload_on: motion
    payload_off: clear
    off_delay: 5
  - platform: mqtt
    name: Doorbell button pressed
    device_class: motion
    state_topic: homeassistant/binary_sensor/eufy/YOURDEVICEANDSERIALNUMBER_doorbell/state
    json_attributes_topic: homeassistant/binary_sensor/eufy/YOURDEVICEANDSERIALNUMBER_doorbell/attributes
    payload_on: motion
    payload_off: clear
    off_delay: 5

sensors:
  - platform: mqtt
    name: cameras_YOURDEVICEANDSERIALNUMBER_battery
    state_topic: "homeassistant/sensor/eufy/YOURDEVICEANDSERIALNUMBER_battery/state"
    device_class: battery
    unit_of_measurement: "%"

camera:
  - platform: mqtt
    name: Camera - Last event
    topic: homeassistant/camera/eufy/YOURDEVICEANDSERIALNUMBER_thumbnail

That get’s me most events I need to action - and a thumbnail of the last event - as well as the current states.

I also have the Google Assistant relay add-on https://github.com/Apipa169/Assistant-Relay-for-Hassio - this enables me to announce to my 9 Google home/mini/Nests that there someone has rung the doorbell. The advantage to using Relay rather than playing a sound is that the Assistants will return to what that where doing before the event - you won’t interrupt someone’s streaming/video activity. Here is a great video on how to setup the Google Assistant relay: https://youtu.be/CUc6NEEbbeo

My automation looks like this

- id: 1611799375904a
  alias: Doorbell notification
  description: ''
  trigger:
  - platform: mqtt
    topic: homeassistant/binary_sensor/eufy/YOURDEVICEANDSERIALNUMBER_doorbell/state
    payload: motion
  condition: []
  action:
  - service: media_player.volume_set
    entity_id: media_player.whole_house
    data:
      volume_level: 0.9
  - service: rest_command.assistant_broadcast
    data:
      message: Excuse me. Ding Dong! There is someone at the door.
  - service: light.turn_on
    data:
      brightness: 255
    entity_id: light.foyer
  mode: single

Thanks again!

B

skank · February 2, 2021, 8:30am

Hi,

Do you get a screenshot too on google? or even audio/video?

brendanheyu · February 2, 2021, 11:07am

I have the Eufy integration that works with Google (“Hey Google, show me the doorbell” etc)… But I have no Eufy video feed being managed by HA or casting of video as yet to the Nest Hubs.

I’ll look into that next I suppose - or my weird MQTT setup eh, @MaxW ?

jbrukardt · February 2, 2021, 6:10pm

huh, ive gotta have an error in my config somplace. That spits the same error for me

Error. Url: http://192.168.1.xxx:8086/set/eufy-security.0.T8400P2020190xxx.cameras.T8400P2020190xxx.start_stream?value=true. Status code 404. Payload: None

skank · February 2, 2021, 6:47pm

I have it working but its always showing the wrong pic event