Eufy Camera Integration

Ok so your issues are:

  1. getting syntax errors for your blog examples; in particular the one for guard mode.

Try @MaxW’s updated sensor guide for guard mode and see if that fixes your issue. It goes in your configuration.yaml file (unless you break yours out into separate files)

  1. I am however able to get the last picture event image, but it doesn’t change.

Not sure how to help on this one as it changes just fine for me.

  1. Also, I wonder if these environment settings of the iobroker container may have some impact. I’m in the US and CST timezone.

No, they should have absolutely no impact. The only one I set was language to English, as I have in my blog post, and everything works fine.

I seem to be in an infinite install state. Tried a reboot too. 2020.12.7 version of Hassio and HaOS 5.9.

@fuzzymistborn,

Are you displaying the last picture event on your HA? If so, which card are you using and are there special setting to trigger refresh?

Yes. It’s nothing special:

type: picture-entity
entity: camera.eufy_doorbell
show_state: false
name: Front Door Eufy
  - platform: generic
    name: Eufy Doorbell
    still_image_url: http://iobrokerserverip:8082/eufy-security.0/SERIAL_NUMBEr.jpg

@fuzzymistborn,

Would this line in your docker compose cause issue if volume does not get created? I don’t see it.

volumes:
- /home/fuzzy/docker/iobroker:/opt/iobroker

Probably. You need to adjust the first part of the path to whatever you want the path to be. I should make that clearer in the post.

But why to use iobroker for this? Here this is working with your/the HA adapter as well. Hm.

Can you provide some logs?

Supervisor > System Tab

Something that sounds like docker, e.g. mine:

20-12-30 09:53:43 INFO (SyncWorker_2) [supervisor.docker.interface] Stopping addon_f1c878cb_iobroker application
20-12-30 09:53:44 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_f1c878cb_iobroker application
20-12-30 09:53:44 INFO (SyncWorker_2) [supervisor.docker.interface] Removing image f1c878cb/aarch64-addon-iobroker with latest and 0.3.0
20-12-30 09:53:44 INFO (SyncWorker_4) [supervisor.docker.addon] Starting build for f1c878cb/aarch64-addon-iobroker:0.3.0
20-12-30 09:54:47 INFO (SyncWorker_4) [supervisor.docker.addon] Build f1c878cb/aarch64-addon-iobroker:0.3.0 done
20-12-30 09:54:47 INFO (MainThread) [supervisor.addons] Add-on 'f1c878cb_iobroker' successfully rebuilt
20-12-30 09:54:49 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on f1c878cb/aarch64-addon-iobroker with version 0.3.0

Whow !!!
Nice @MaxW… I take my time tonight to play with it !!!

Sorry to crash this thread, but I’m looking to replace my Alro doorbell (It. Is. Awful. Seriously…how did it even make it through testing - the button doesn’t even feel like a button, so people stab at it unsure if it actually pressed or not?!)

How are you all finding your Eufy doorbell? My primary concern is Eufy never release RTSP or an API despite their support reps saying “soon”. With Alro I can track pushed state, put it on silent mode etc. without needing additional complicated brokers installed, as the REST api has been reverse engineered.

Thanks!

One less custom component to run for now.

@timdonovanuk I love the doorbell especially now that there’s a (slightly hackey) way to control some aspects of it. Regarding RTSP and an API, I dont believe they ever promised an open api, it’s just been heavily requested. The RTSP is definitely something that they’ve promised and haven’t delivered. I give them a pass for now because COVID but the previous example of IFTTT being promised and never delivered is concerning.

Best advice for anything smart home is buy what features exist, not what is promised. As what is promised may never come to being.

1 Like

Thanks @fuzzymistborn! “buy what features exist, not what is promised” some sage advice for sure. To be honest, my Arlo doorbell doesn’t even deliver the features that are supposed to exist, so I think this will be a step up. It’s also on sale on Amazon UK so worth a go!

It looks like everyone is quite dedicated to getting this going on HA too - the iobroker looks promising as I see lots of state attributes are exposed. RTSP is less important to me anyway, it’s not like a babycam where I need a live feed in HA.

Nice gonna try too
Especially for me the doorbellpresses.
IS that one working for you?

Guys guys guys !
I think i will make your day today !
Some dutch guy made a new script.

Take a look, i think this is what we want in a simple way !
No iobroker needed, i think this is a better way?

5 Likes

That would cover the doorbell presses/motion activities very well. Wouldn’t handle changing the guard mode. So for your usecase give a go. But again, not a HassOS addon atm so you’d need to find a way to run the container.

Another options I keep forgetting to mention is try using the HA Companion App to get notifications (I think that’s available in iOS too, apologies if it’s not). Could intercept the notification and trigger off that (which would pick up doorbell presses and motion events).

About the notification in the companion app,
that would be ok on smartphones but not on google hubs…
Think i still need that script…

MAybe he’s gonna add the guard thing too

Have no doorbellthing, sorry.

the idea using mqtt autodiscovery is good.

This should be easily wrapped as addon :thinking:

1 Like

Easily wrapped?
Maybe you can help him to do so? Contribute?
My knowledge to do so is so limited

You guys want the changing the guard mode.
Can you explain why?
For me i dont see the point there… only the doorbell press stuff :stuck_out_tongue: But maybe i’m just unknowing

his current thing is using some interactive workflow that does not really fit into (afaik) the addon workflow.

The Need to chane guard mode is pretty easy in my case. I have some cameras with motion detection and alarm running 24/7. But sometimes I want to enter that area without starting some alarm and scaring everybody. Having the possibly inside HA creates easy steps to change the guard mode. E.g. some tag to scan instead of manually opening the app and pressing all those buttons…

Morning guys and gals. I started down this path last night, and with help from Fuzzy I am the proud owner of a still image of my last camera state! I have 4 eufycam 2’s and a door bell, soon to also have the wifi door lock. Has anyone tried storing locally to the cam and pulling data from the mSD card? I have a 32gb card lying around somewhere I could play with and a camera not installed yet. Looking through ioBroker I don’t see an entry for local path to an mSD card but I wonder if that’s due to my not having installed one yet. Thoughts and feelings?

I also logged into my online portal and noticed this:

" It’s unavailable to play the clips stored in HomeBase local storage by web portal because they have been advanced encrypted. It’s recommended you to play them in the app or subscribe to the cloud recording service."