I second this. My 2C cams and doorbell all stopped working after I updated. I downgraded to v2.2.4 to fix the issue. For some reason the new update isnt sitting well with my setup
1 Like
I have finally working all the parts, including installing the integration via HACS, but regardless which version I choice in HACS, it wonât show up in the add integrations part⌠Restarted couple of times. eufy-security-ws docker is running succesfully and listening. HACS is downloading it into the custom-components folders, but still no success. Could this have anything to do with HA 2022.6.1 version?
Pff after two nights of bad sleep, and multiple problems after a failed update of HACS itself, this was just a case of remove cache before trying to add integrationâŚ
I just installed a new doorbell and I am seeing the same error as well. Has anyone found a solution?
What version are you running of the integration?
how do you downgrade?
EDIT
my problems are with v2.2.4 i updated to 2.2.6
with the version 2.2.6 i have another problem, the entity is now not longer unavaiaible, its idle, but the camera stream doesnt work.
Error Cant get URL for camer.XXX
You can downgrade by going into HACS, going to integrations, clicking on the 3 dots next to eufy integration and clicking âRedownloadâ. Then select the version you want from the drop down.
I have 2.2.4v and have no issues. I have 4 2Câs and 1 doorbell. All attached to one Base2.
Could you please describe in a bit more detail what entity you are talking about? or what does your card in dashboard (lovelace) look like?
here is the card config I am using, feel free to use it in your setup, replace my camera name with yours.
type: grid
square: false
cards:
- type: conditional
conditions:
- entity: binary_sensor.doorbell_streaming_sensor
state: 'False'
card:
type: picture-entity
entity: camera.doorbell
tap_action:
action: call-service
service: eufy_security.start_p2p_livestream
target:
entity_id: camera.doorbell
show_state: false
- type: conditional
conditions:
- entity: binary_sensor.doorbell_streaming_sensor
state: 'True'
card:
type: vertical-stack
cards:
- type: custom:webrtc-camera
entity: camera.doorbell
- type: button
name: Stop Streaming
show_state: false
show_icon: false
tap_action:
action: call-service
service: eufy_security.stop_p2p_livestream
target: {}
service_data: {}
columns: 1
The way this card works is you tap on it once, wait a couple seconds and your video stream should popup in theory. You also need to lower the quality of your stream, especially doorbell.
Ă´f course, with version 2.2.4 i had here no thumbs , now with version 2.26 i had a thumb but only one of 4 cameras.
when i click on the card it opens a poup with my error
this error is on all cameras.
and under the settings of the camera there stands ânot avaiableâ but now there stands âidleâ
but the stream is still dead. always the ERROR: Cant get URL for camera.wohnzimmer
Are you using P2P or RTSP to stream? Do you have the RTSP Simple Server Add-on installed? I would try P2P and use the settings described in 136794616-fa238dd8-9bd6-41d8-ac14-2c0fb4f0eb23.png (397Ă509) (user-images.githubusercontent.com) if you dont already have it.
What kind of cameras are you using?
The last thing I would suggest is to remove all eufy integrations from your system (again if you tried other ones before) and start over using standard settings. I know its a lot of work, I myself did it 4 times before I got it working. I assume I made a mistake somewhere during my previous attempts.
I followed install directions from:
The versioning is as follows:
Eufy Security Add-on Current version: 0.9.1
RTSP Simple Server Add-on Current version: v0.17.6
Eufy Security Integration (via HACS) v2.2.6
Is there any known problem with the install directions from the website listed?
I quickly read through it. But I would follow whats on @anon63427907 github page. On the website it skips a few steps I think. I set this up 6 months ago so I am a bit rusty. If it comes down to it, redo the integration following the github steps.
Lets try one thing before you try to redo the entire integration. Restart the add-on and look in logs. Do you see any errors?
Next, goto integration and uncheck âauto start stream on clickâ. Use the card config I gave above, and see if that solves your problem.
thanks for your response.
I uninstalled the Eufy Security WS Addon, the RTSP Simple Server Addon, and the Eufy Security HACS integration (after removing my devices).
I installed the Eufy Security WS Addon using the steps on the @anon63427907 github page. I then started the Eufy Security WS Addon after the configuration, checked the log, and there is the error, the same as before, so I have stopped here, on the error.
2022-06-05 22:23:45.866 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-06-05 22:23:47.468 INFO Connected to station T8200T6021330931 on host 44.196.45.200 and port 11038
2022-06-05 22:23:48.075 ERROR Response code not ok
{
code: 35000,
msg: 'Failed to request.'
}
2022-06-05 22:23:48.082 INFO Push notification connection closed
i use the p2p with the localhost method, i use the settings on your picture.
i have the eufy indoor 2K cameras.
it all working until to start a stream. 
in the addon log i get a error
2022-06-06 07:34:02.863 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-06-06 07:34:07.228 INFO Connected to station T8410P3121302681 on host 178.200.147.102 and port 11788
2022-06-06 07:34:07.284 INFO Connected to station T8410P3121431696 on host 178.200.147.102 and port 20040
2022-06-06 07:34:07.294 INFO Connected to station T8410P2021132A69 on host 178.200.147.102 and port 15441
2022-06-06 07:34:18.334 INFO Push notification connection closed
2022-06-06 07:34:18.537 INFO Push notification connection successfully established
2022-06-06 07:34:22.197 ERROR P2PClientProtocol.lookup(): station: T8410P3121280D8B - All address lookup tentatives failed.
2022-06-06 07:34:22.202 INFO Timeout connecting to station T8410P3121280D8B
2022-06-06 07:34:23.923 INFO Push notification connection successfully established
2022-06-06 07:34:42.215 ERROR P2PClientProtocol.lookup(): station: T8410P3121280D8B - All address lookup tentatives failed.
2022-06-06 07:34:42.218 INFO Timeout connecting to station T8410P3121280D8B
2022-06-06 07:35:07.230 ERROR P2PClientProtocol.lookup(): station: T8410P3121280D8B - All address lookup tentatives failed.
2022-06-06 07:35:07.231 INFO Timeout connecting to station T8410P3121280D8B
i am not alone with the problem
Canât get URL for camera ¡ Issue #348 ¡ fuatakgun/eufy_security (github.com)
I myself have a T8210 so maybe there is some difference in T8200 which it seems you have. My last advice would to be to play around with the settings to see if you can get it to pop up. Unfortunately, this is getting out of my wheelhouse. Also if you havnt lowered the quality of your stream from your Eufy app settings for your doorbell, please do that as well and try.
It seems from your logs you are having some success. You might be on the right track here. Personally, RTSP never worked for my cameras and the T8210 2k battery doorbell I have does not have RTSP. I have turned OFF RTSP on all my cameras. I have solar panels, so I donât really worry about battery life. Turning off RTSP worked for me. Try turning off RTSP. Restart add on and integration and then try again.
If that doesnât work, one last thing to try would be playing around with the video analyzer setting. Mine is set a 3 I believe. but feel free to change it to different values to see. Usually, video analyzer is helpful once you have a stream started at least (thats what my understanding is)
Thank you Hasan. I donât know what happened, b/c since my last post yesterday, I did nothing. But I see in my new log, it has connected successfully! I suspect something at eufy hosting changes over time - now Iâm working.
2022-06-06 11:54:13.067 INFO Disconnected from station T8200T6021330931
2022-06-06 11:54:33.211 WARN Station T8200T6021330931 - Tried all hosts, no connection could be established
2022-06-06 11:54:33.211 INFO Timeout connecting to station T8200T6021330931
2022-06-06 11:54:43.423 INFO Connected to station T8200T6021330931 on host 44.196.45.200 and port 14672
Glad to hear that. It could be that a restart of Eufy hosting, or your systems might have helped make that connection.
I spoke too soon. Yes, the error went away, but I noticed in looking at the github instructions, that the IP address shown should be a local IP and it is not, also, no indication was shown of a setup of push notifications.
So, I restarted the add-on, and again I see the error:
2022-06-06 12:49:23.147 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-06-06 12:49:25.049 INFO Connected to station T8200T6021330931 on host 44.196.45.200 and port 14370
2022-06-06 12:49:25.508 ERROR Response code not ok
{
code: 35000,
msg: 'Failed to request.'
}
2022-06-06 12:49:25.513 INFO Push notification connection closed
2022-06-06 12:49:25.564 INFO Push notification connection closed
2022-06-06 12:49:30.892 ERROR Response code not ok
{
code: 35000,
msg: 'Failed to request.'
}
2022-06-06 12:49:30.894 INFO Push notification connection closed
As far as configuration, I do have the video quality set to low quality and non-HDR, non-2K. There really isnât anything else other than
EVENT_DURATION_SECONDS *
EVENT_DURATION_SECONDS
10
Not sure what to set that to to try something else.
Hi,
Firstly, big thanks to @anon63427907 for this integration (and @bropat), I have it (mostly) working and its great.
I wonder if someone can confirm something for me. I am not receiving motion sensor updates on a Eufy Security E 2k Floodlight (model on device says: T8422S). I think I have the setup correct (Iâm running hass in its own docker container so it might be the issue), but I see these logs when I enable debugging:
I can see the 2 events at the exact time the camera recorded events here in eufy_security_ws:
grep -i 'Normalized push message received' eufy_logs_with_pushes.txt
eufy_security_ws | 2022-06-06 15:44:22.918 DEBUG [PushNotificationService.onMessage] Normalized push message received
eufy_security_ws | 2022-06-06 15:54:49.816 DEBUG [PushNotificationService.onMessage] Normalized push message received
but in hass/eufy_security integration, there is nothing at the same time (logs covering first event only):
2022-06-06 15:41:11 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - set_event_for_entity - device / T8422XXXXXXX / pictureUrl / https://cdn-us.eufylife.com/thumb/2022/06/06/station/XXXXXXX
2022-06-06 15:41:12 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data
<removed hundreds of the same lines of Manually updated eufy_security_data>
2022-06-06 15:51:15 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data
2022-06-06 15:51:15 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - set_event_for_entity - device / T8422XXXXXXX / pictureUrl / https://cdn-us.eufylife.com/thumb/2022/06/06/station/XXXXXXX
You can see that every 10 minutes I do get the pictureURL and that works. I can also control the light, and use p2p streaming (albeit its slow, but my camera doesnât support RTSP - I think, can anyone confirm that for me?).
From the logs, I am receiving push notifications in bropatâs eufy_security_ws, but for some reason, I donât see any debugs/mentions of it in the hass side. Could someone at least confirm that this is expected or a broken setup, or a bug? I expected that the push would trigger some flow to update the binary_sensor.* motion sensors? Also, given I can control lights, and stream, I think the setup is working. I do wonder if the model being an T8422S is somehow slightly different to an T8422?
no that dont work, where can i find the settings for the analyzer?
always the same error in the addon
2022-06-07 12:35:51.752 ERROR P2PClientProtocol.lookup(): station: T8410P3121280D8B - All address lookup tentatives failed.
sometimes this error
2022-06-07 12:38:27.130 ERROR Stations - Generic Error:
EufyError Code: undefined Message: undefined (HTTP Code: 423)
details:
{
code: 'ERR_NON_2XX_3XX_RESPONSE',
timings: {
start: 1654605507001,
socket: 1654605507002,
lookup: 1654605507012,
connect: 1654605507029,
secureConnect: 1654605507082,
upload: 1654605507083,
response: 1654605507116,
end: 1654605507116,
error: undefined,
abort: undefined,
phases: {
wait: 1,
dns: 10,
tcp: 17,
tls: 53,
request: 1,
firstByte: 33,
download: 0,
total: 115
}
}
}
error stack:
⢠index.js:117 <anonymous>
node_modules/got/dist/source/as-promise/index.js:117:42
⢠task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
i dont think thats my fault, it works until a few days without problems.
i think its a integration or addon error.
its wasting time, hours and hours for a problem that is open on github.
@anon63427907
can you perhaps say somthing about this?
Since a while my window/door sensors seemed to have stopped working. Initially it would sometimes report a window or two being open for days (2 sensors not reporting correctly). But since a week or 2 all sensors have stopped reporting in. Saying that everything is always âclosedâ. Iâm a bit at a loss how to solve it.
Looking at the logs there seem to be a lot of errors, but I cannot make heads of tails of it.
2022-06-07 07:38:42.620 INFO Push notification connection closed
2022-06-07 07:38:44.659 ERROR onSocketError:
Error connect ECONNREFUSED 10.0.0.1:5228
details:
{
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '10.0.0.1',
port: 5228
}
error stack:
⢠node:net:1187 afterConnect
node:net:1187:16
2022-06-07 07:38:57.636 ERROR onSocketError:
Error getaddrinfo EAI_AGAIN mtalk.google.com
details:
{
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'mtalk.google.com'
}
error stack:
⢠node:dns:71 onlookup
node:dns:71:26
2022-06-07 07:38:57.643 INFO Push notification connection closed
2022-06-07 07:39:17.474 ERROR onSocketError:
Error getaddrinfo EAI_AGAIN mtalk.google.com
details:
{
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'mtalk.google.com'
}
and it goes on like that.