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?
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”)
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”)
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
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
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.
Hi everyone, can anyone just get the camera status (without using ioBroker) ?
I only wish to use it has trigger to turn on lights when it detect someone.
Tks.
I have released the new version (0.2.0) with livestream support via P2P (but not only). Please test and let me know
The functionality to download videos over P2P is deliberately not released yet, because I still need to implement a better solution here.
I already tested a download of the video when receiving a push notification, but this only transfers about 2 seconds of the video (the adapter is too fast ). I thought here to start the download after a delay that depends on the configured power mode of the device (depending on the power mode the video is longer or shorter).
Thanks for this new release, I installed it but get a load of error messages - hopefully some tips on how to resolve these; could it be certain parts of the library are not loaded properly?
First the good - the rest api still functions, arming and disarming works. Also I still get to see the last_picture of the doorbell.
Challenges however arise when attempting to activate the video / livestream:
Start/stop works for the regular cameras (T8113) - URL however does not work, log shows difficulties writing the files
Start/stop for the doorbell (T8210) does not work. (see log)
I have included a number of errors and warnings from my log. Let me know if you want some more output.
2021-02-14 19:59:30.930 - warn: eufy-security.0 (5702) writeFile will not write this file (T8113Nxxxxxx.jpg) in future versions: eufy-security.0 is not an object of type "meta"
2021-02-14 20:00:12.470 - error: eufy-security.0 (5702) EufySecurity.stationP2PCommandResult(): Station: T8010Nxxxxxx command CMD_DOORBELL_SET_PAYLOAD failed with error: ERROR_INVALID_COMMAND (-103)
2021-02-14 20:01:26.873 - warn: eufy-security.0 (5702) P2PClientProtocol.handleDataControl(): Not implemented - CONTROL message with commandId: CMD_SUB1G_REP_UNPLUG_POWER_LINE (2111) channel: 2 - data: 0300000000000000
2021-02-14 20:03:12.629 - error: eufy-security.0 (5702) Camera.stopStream(): Response code not ok (code: 20023 msg: Failed to request.)
2021-02-14 20:03:31.662 - error: eufy-security.0 (5702) EufySecurity.stationP2PCommandResult(): Station: T8010Nxxxxxx command CMD_DOORBELL_SET_PAYLOAD failed with error: ERROR_INVALID_COMMAND (-103)
2021-02-14 20:04:30.100 - info: eufy-security.0 (5702) Refresh data from cloud and schedule next refresh.
2021-02-14 20:04:30.590 - warn: eufy-security.0 (5702) writeFile will not write this file (T8113Nxxxxxx.jpg) in future versions: eufy-security.0 is not an object of type "meta"
2021-02-14 20:04:30.594 - warn: writeFile will not write this file (T8113Nxxxxxx.jpg) in future versions: eufy-security.0 is not an object of type "meta"
2021-02-14 20:04:30.620 - warn: eufy-security.0 (5702) writeFile will not write this file (T8113Nxxxxxx.jpg) in future versions: eufy-security.0 is not an object of type "meta"
2021-02-14 20:04:30.624 - warn: writeFile will not write this file (T8113Nxxxxxx.jpg) in future versions: eufy-security.0 is not an object of type "meta"
2021-02-14 20:04:30.656 - warn: eufy-security.0 (5702) writeFile will not write this file (T8210Pxxxxxx.jpg) in future versions: eufy-security.0 is not an object of type "meta"
2021-02-14 20:04:30.660 - warn: writeFile will not write this file (T8210Pxxxxxx.jpg) in future versions: eufy-security.0 is not an object of type "meta"
2021-02-14 20:06:31.793 - error: eufy-security.0 (5702) Camera.stopStream(): Response code not ok (code: 20023 msg: Failed to request.)
2021-02-14 20:40:39.165 - error: eufy-security.0 (5702) EufySecurity.onStartLivestream(): station: T8010Nxxxxxx device: T8113Nxxxxxx - Error: Error: ENOENT: no such file or directory, open '/data/iobroker/iobroker-data/files/eufy-security.0/T8010Nxxxxxx/last_live/T8113xxxxxx.jpeg'
2021-02-14 20:42:23.125 - error: eufy-security.0 (5702) EufySecurity.stationP2PCommandResult(): Station: T8010xxxxxx command CMD_DOORBELL_SET_PAYLOAD failed with error: ERROR_INVALID_COMMAND (-103)
2021-02-14 20:43:14.060 - error: eufy-security.0 (5702) Camera.stopStream(): Response code not ok (code: 20023 msg: Failed to request.)
Hi @RT1080,
please activate the debug mode of the adapter and reproduce the error. Then please send me the logfile (note: the logfile contains sensitive data; mainly the token, so redact it).
I have only the Eufycam 2, the rest I can’t test unfortunately and I implement it only by reverse engineering.
The warnings are not a problem (but I’ll fix them in the next release anyway).