You can do this however ths stream stops after 3 min or so. you can the camera stop and camera start service to fire up the stream. you can see the screen in lovelace
the integration does not support this :(. You can use a RF radio to intercept the ping on 443mhz if you have the eufy doorbell that transmits, or you can use alexa to trigger an automation.
Much the same as above you cannot trigger an automation from the doorbell without intercepting the ping on 443mhz or working with alexa.
Forgot to mention, i dont have alexa, i only have google.
Getting the doorbell press is the key to all i want.
I thought this could be done with google , but i cant find it.
Truly pity
Not even with mqtt or the rest way?
So my only luck is the 443mhz IF its being used?
How do i get this to work?
Will my hamony hub capture this? How do i do it?
I’m not sure if my doorbell is the right version that will have the 433 signal… i bought it from coolblue
I tried to consume the last_event_pic but was not able to create something useful of it. the last_event_pic_html is way to long to be stored in a entity state as they are limited by 255 chars.
This is possible by using the ioBroker webview. So for me I have a camera entity like this:
- platform: generic
name: Eufy Camera Image
still_image_url: http://IP_ADDRESS:8082/eufy-security.0/T8200XXXXXXXXXX.jpg
Pulls the still into HASS.
Also thanks for the rest sensor tip, I just set up mine and it’s working very well. Though Iobroker doesn’t seem to be picking up motion/doorbell ringing events.
Couldn’t you use Portainer in HassOS to add another docker image to load? Just curious if anyone has gone down this route verses setting up another VM or RPi.
I’m in the same boat.
Running HASS OS here on pi 4, so i cant install iobroker…
Or i would have to turn on a second machine running 24/24 7/7
Also strange the doorbell presses isnt working … as @MaxW says its included…
Should the really be the way? iobroker as a “competitor” to HA to be installed in parallel to HA to be able to use this single integration instead of having the same features in the HA adapter as the ioBrober adapter has?
I decided to go with HA instead of ioBrober and now I have to install this in parallel because of eufy security? Would strongly suggest having a generic “io adapter wrapper” or to improve the HA adapter instead.
I don’t think anyone would like the idea of running ioBroker next to HA to integrate a simple doorbell.
Given the traffic in this forum and the questions elsewhere, I think we should especially stalk [email protected] with the request to do a decent job of an HA integration or at least provide a documented and open API.
In the meantime, thanks for all the work to look for a solution.
@nonsleepr Is your adapter still in progress/maintained or a dead end? Esp. if you crosscheck the features already in iobroker adapter. Apriciate the current state , but of course, if you look in this thread, it would be more than great to …
I tried the AddOn way, but got stuck at some point.
Had some huge graphic issues and the mounting gave me a headache.
The graphic stuff could be resolved by using a real nginx reverse proxy instead just pointing the ingress towards iobroker i guess, but the mounting was bad.
Afaik there is no option to either set the default iorbroker path away from /opt/iobroker/ nor change the mounting point at hassio side. Therefore configs would not be persistent through updates or anything else, which was a bummer and not really production like.
Starting ioBroker through portainer should work I guess.
Not really. I mostly created the repo because nobody else had and I wanted to try to learn reverse engineering an API. But it quickly grew beyond my meager skills (P2P stuff, mqtt, etc) so I left it up after some other folks (bachya and nosleepr) did some awesome work to improve it.