absolutely more important 
Thanks for all your hard work
Please forgive me if I’ve missed reading a part of this thread.
I’m currently running iobroker on a separate docker server from home assistant. I used https://github.com/bropat/ioBroker.eufy-security according to the guide (https://blog.fuzzymistborn.com/controlling-eufy-security-devices-with-iobroker/)
I’m assuming this version 0.1.5 updated 28 days ago includes all of the code to pull down video events? Currently I have only figured out how to get still pics following the mentioned guide and I do have all of my cams listed in the objects. What is the recommended method for accessing video events? My goal is to have events from specific cameras autoplay on cast devices around the house.
No, I don’t think video events are yet in the library.
I see they are mentioned in this repository (https://github.com/bropat/eufy-security-client) but I don’t know much about it.
I guess this post Eufy Camera Integration
means we’re just waiting for the next public release of the ioBroker Adapter.
Precisely. It’s in the library but it’s not incorporated yet into a working integration/client/whatever you want to call iobroker/the ha-mqtt addon
1 Like
@fuzzymistborn @MaxW
Regarding the problem with the MQTT ioBroker adapter and a possible infinite loop, I just wanted to point out that a user had exactly this behavior and the cause was found (see here).
The cause was the parameter Subscribe patterns under the configuration item MQTT SETTINGS which has the default value #, this leads to the MQTT adapter making a subscription for all MQTT topics. If you delete the character # or specify only the topics you are interested in (do not specify the eufy security topic!!), the problem should be solved and you could get the changes in Home Assistant in realtime again.
PS: In the case of the user, he has specified a non-existent topic.
2 Likes
I recently upgraded the ioBroker Addon to use remote prebuild images. This should speedup installation/updates and cleanup old images now 
Everyone might want to check with e.g. portainer if there is any unsued image laying around. This sadly is some side effect of locally build images…
1 Like
nice job !!!
I’m still looking to find a way to get a picture once somebody rings my doorbell
It currently works, but the image is always 1 ring behind if u know what i mean.
Strangely im the only one who wants this?
Is there some kind of way i do get this thing working which is fast enough?
Lol im getting an error with it when starting
Failed to start addon
404 Client Error for http+docker://localhost/v1.40/containers/create?name=addon_1e14b3fb_iobroker: Not Found (“No such image: maxwinterstein/homeassistant-addon-iobroker-aarch64:0.6.0”)
Same error here, is this aarch64 related?
404 Client Error for http+docker://localhost/v1.40/containers/create?name=addon_f1c878cb_iobroker: Not Found (“No such image: maxwinterstein/homeassistant-addon-iobroker-aarch64:0.6.0”)
yeah reinstalled too , fixes it
anyhow my adapters are gone now lol
Have to reinstall them too, but im not sure if i will
i need to find a way to get the image when doorbell is pressed
Actually right now, i have the doorbell and cam since christmas, and im kinda regretting i didnt go the google nest doorbell way, since that is possible in ha too
Yep - same, took it as practise 
Still its experimental and I can see only good things ahead in the long run
Thanks! That worked
Question: all of the ioBroker docs in HA state to point to port 8087. I would rather use your version of the docker but realize there is t a port 8087 open in the configuration. Thoughts?
Yes, came across that in my tests too. This should be a one-time-issue, as HA seems to have some issue when switching from locally build images to prebuild ones.
Sorry for everyone who needs to re-click their iobroker configuration
1 Like
Can you point me to some documentation?
adding port 8087 should be no issue at all, but I guess you wouldn’t need it.
You can map port 8087 from outside the container to the inside port 8086 for example.
Well, in that case I agree. Havin different ports here and there confuses a little bit…
Released new version with more ports
1 Like