Ah yes indeed! It just updated to the mail guy that delivered the mail. So that works. I think i found out that my doorbell ( Eufy Video Doorbell Dual 2 Pro) does not support RTSP. So i have changed the cards tap action to call a different service then ‘start’ i switched it to: ‘eufy_security.start_p2p_livestream’ & ‘eufy_security.stop_p2p_livestream’. And this looked promising but when the stream ‘starts’ it gives me that the url cannot be found and then some tcp & io read errors.
What i find strange is the following screenshot. It had an address for a couple of minutes while i was following the guide and then not anymore.
Is there something known for causing this or do i have to start over and see which step or when this happened?
// Edit: Can this be because currently its on battery power and not hardwired? Thats something i will fix this weekend.
Just to chime in on the battery vs. hard-wired question - it doesn’t matter. Eufy doesn’t allow rtsp to be enabled on the doorbells at all, regardless of power source.
I previously followed some steps online to modify and recompile a special Eufy Android app to expose the rtsp option for the doorbell. It sort-of works, in that when the feed is “active” (e.g. senses movement) it will stream to the rtsp feed. However, it still follows the same pattern as the other battery-powered devices (like the 2c pro) in that it won’t stream 24/7.
If the primary goal is to just get the “event” streams into another NVR, it could be a viable solution, but for trying to actively watch the feed on-demand, you still need to call the start/stop services exposed by this integration (which IMO makes the rtsp feature worthless as-is).
Hey @jouster can you share some details about how you got this working? Which Home base have you got? I have the home base 2 and I couldn’t see any events that I could set as a trigger and turn the alarm on. Cheers in advance . (some screenshots of your automations would be killer)
Hi, I’m trying to get this add-on to work on my HA system (running on x86 PC with Debian supervised) and my home-base & 2khd doorbell.
I tried following the installation steps, but this fails right after starting up the add-on with following messages in the log:
2022-12-04 10:22:57.816 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-12-04 10:23:10.264 INFO Push notification connection successfully established
2022-12-04 10:23:23.034 ERROR Station 12345 - All address lookup tentatives failed.
2022-12-04 10:23:23.035 INFO Timeout connecting to station 12345
This last log message keeps on repeating.
I’ve been searching this repo’s issue list , on bropat’s repo and also the limited documention I could find. But sadly I cannot find the actual solution although I found a couple of more reports on this log-message.
My guess is that it has something to do with the add-on running in a docker container not being able to reach the home-base via local network or something.
Anyone a clue on how to fix this, or how to debug this ?
Thanks in advance for the help.
@jouster I’d be keen too. I have a Eufy Alarm with motion and contact sensors - and I also have some other Zigbee contact sensors. I want to keep using the physical Eufy keypad to be the main user interface to arm/disarm. I’ve gone down the automation route of “If Eufy is armed, arm Alarmo”. And “If Eufy is triggered, trigger Alarmo”. Triggering Alarmo then sets off a siren and sends a message to the Google speakers.
Would be keen to know how others have integrated Eufy into their Home Assistant alarm system - or the other way round.
Thanks to latest updates from eufy sides, add-on will probably fail to login and so the integration. I will be following up closely and when there is a solution, i will publish the newer version of add-on to mitigate the problem. Until then, we all need to hold on.
Since you said Eufy made some updates I tried reloading my integration again today and everything is now working:
To refresh the thread on the issues I was having:
On the integrations page I had the following error:
And on the eufy security addon page the log was reporting the following:
2022-12-02 00:49:41.507 INFO Eufy Security server listening on host 0.0.0.0, port 3000
/usr/src/app/node_modules/eufy-security-client/build/http/station.js:107
this.rawStation.params.forEach(param => {
^
TypeError: Cannot read properties of null (reading ‘forEach’)
at Station.update (/usr/src/app/node_modules/eufy-security-client/build/http/station.js:107:36)
at new Station (/usr/src/app/node_modules/eufy-security-client/build/http/station.js:62:14)
at Function.initialize (/usr/src/app/node_modules/eufy-security-client/build/http/station.js:73:25)
at EufySecurity.handleHubs (/usr/src/app/node_modules/eufy-security-client/build/eufysecurity.js:360:51)
at HTTPApi. (/usr/src/app/node_modules/eufy-security-client/build/eufysecurity.js:126:44)
at HTTPApi.emit (node:events:513:28)
at HTTPApi.refreshStationData (/usr/src/app/node_modules/eufy-security-client/build/http/api.js:518:22)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async HTTPApi.refreshAllData (/usr/src/app/node_modules/eufy-security-client/build/http/api.js:543:9)
at async EufySecurity.refreshCloudData (/usr/src/app/node_modules/eufy-security-client/build/eufysecurity.js:565:9)
I currently hve a reolink camera and hate it because the motion detection takes 20 seconds or never to trigger that there was motion. I want to use my camera to turn on my light when I go to the backyard.
I am currently using a motion sensor from Aqara because the reolink is so bad at it.
Does thie integration have fast motion detecition? is there also person detection if I go for the 2k outdoor cam (T8441C21) ?
Actually, I was wrong on assuming that there were breaking changes from eufy side and it would cause issues on overall add-on. I had received couple of issues and prematurely assumed that it is result of recent firmware and software updates. With the latest trusted device name attribute, login is still working for many of us.
Would be great to understand How to set that up. Do you need to put that name somewhere in Eufy settings too? Or just time the name of your HA instance?
Solved… Just included the name of my HA instance in Trusted devices and integration works again!
If you enable basic notifications (without picture) it is 1-2 seconds. If you enable notifications with picture, it could take 4-5 seconds. Mine is battery operated device, so it could be faster for mains powered ones.
Trying to set this up (Eufy Doorbell here), started with RTSP but found out it probably doesn’t support it. P2P does the exact same thing:
NotSupportedError: Failed to execute 'addSourceBuffer' on 'MediaSource': The type provided ('video/mp4;codecs="hvc1.016000") is unsupported.
ffmpeg is in the configuration.yaml. I have set all the streaming options to low, and played with the 1-5 seconds setting for it to identify the stream. Any tips?
EDIT: it started working when I disabled the tickbox “Use RTSP Add On”.
. (some screenshots of your automations would be killer)
although I found a couple of more reports on this log-message.
