Sorry, i was just joking while checking if GitHub account is hacked or something and relieved after finding out all is fine.
1 Like
I also get no picture and RTSP (or p2p) stream from the doorbell. Both my cameras work fine
Potentially dumb questionā¦
@bropat just updated the eufy-security-ws code (GitHub - bropat/eufy-security-ws: Small server wrapper around eufy-security-client library to access it via a WebSocket.) that fixes an error Iām getting with my contact sensors. However, Iām not able to figure out how to update my deployment in HomeAssistant. Iām running HAOS on bare metal x86. Iāve restarted the add-on and the integration, still not reporting an update available. Iāve forced Home Assistant to look for updates (which, I assume is actually just for HA, not add-ons and integrations).
Help, what am I missing? How can I get the new 1.3.1 version deployed?
Itās not the same version as the add-on you use, this is the docker version which is the basis for the add-on. You need to wait for @anon63427907 to test this and incorporate these changes in his addon.
Yes, please wait for couple of days
2 Likes
Got it, thanks for the info! Iāll be patient.
Hi @anon63427907 - firstly many thanks for the work on this, easy to follow and I am mostly up and running. I have the cards for my 3 cameras and the doorbell working, clicking them does the streaming (rtsp for the cameras and p2p for doorbell using webrtc-camera) and it works fine.
Doorbell automation using the ringing function also works fine, but I am at a loss when it comes to getting the cards to update the pictures from motion activation (the workaround for the local image encryption).
I have it set as per your examples, just cut down to just triggering on motion (no alarm or snoozing stuff), but it seems that the binary_sensor isnāt working?
Any advice?
alias: Eufy Front
description: Eufy Front
trigger:
- platform: state
entity_id:
- binary_sensor.front_motion_detected
id: sensor
to: "on"
condition: []
action:
- choose:
- conditions:
- condition: trigger
id: sensor
sequence:
- service: eufy_security.start_p2p_livestream
data: {}
target:
entity_id: camera.front
- service: eufy_security.generate_image
data: {}
target:
entity_id: camera.front
- service: eufy_security.stop_p2p_livestream
data: {}
target:
entity_id: camera.front
mode: single
My EufyCams are showing up as inactive, someone know how I can see a livestream? Furthermore before I had thumbnails, after a detectionā¦ even this is not visible anymoreā¦
I want to receive a trigger in HA when someone presses the Eufy (2k) doorbell. Is that possible?
Thus I donāt need the videostream.
I try to login but it failed.
I created a second user used this login name and password.
Country is correct NL
I tried port 3000 and 3001.
I couldnāt find the Trusted_Device_Name, I used Eufy
The log:
2023-02-24 00:32:08.393 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2023-02-24 00:32:08.905 ERROR Response data is missing
{
code: 0,
msg: 'Succeed.',
data: undefined
}
What is wrong?
Please check here: [Bug]: Disconnection and log Ā· Issue #196 Ā· bropat/eufy-security-ws Ā· GitHub
@bropat had created a new repository to manage the add on part with latest version. I myself had an issue on updating in my system but apparently it worked for him
Json serialization error, i had to update configuration (add a space and save it) and then worked fine.
Ik got segmentation fault during startup of the addon. Anyone know how to troubleshoot this?
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/run.sh: line 118: 182 Segmentation fault /usr/bin/node /usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js --host 0.0.0.0 --config $CONFIG_PATH $DEBUG_OPTION $PORT_OPTION
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/run.sh: line 95: 192 Segmentation fault /usr/bin/node /usr/src/app/node_modules/eufy-security-ws/dist/bin/server.js --host 0.0.0.0 --config $CONFIG_PATH $DEBUG_OPTION $PORT_OPTION
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Same here on a Pi4
After the inserting the suggested format for āstationsā (as stated in the documentation) the configuration was exepted ands started. after acception, the addon shut itself down after the above faultā¦ any suggestions?
Edit: used this https://github.com/bropat/hassio-eufy-security-ws/issues/2 and got the add-on to start.
Problem is solved in the latest release (.1.3.4)
I can confirm that the bropat (1.3.4) euf-sec-ws add-on works stable 
Now yust need to find a way to get the doorbell-camera working again in my HA-dashboard 
How do you get the 1.3.4? For me there is no update?