bropat / eufy-security-ws

Small server wrapper around eufy-security-client library to access it via a WebSocket.
MIT License
177 stars 26 forks source link

[Bug]: Disconnect from Station #174

Closed WillWNL closed 1 year ago

WillWNL commented 1 year ago

Version

1.3.0

Node version

1.3.0

Operating System type

Other

Operating system version

Rpi4

Describe the bug

I have a HB2 with a Doorbell T8210.

For well over a week now my homeassistant integration (fuatakgun Eufy add-on) stopped working. I stopped having Thumbnail for the Doorbell. I saw a lot of errorlogging (below) regarding the connection to the station.

I tried a few suggestions in some of the threads regarding similar issues. removed add-on, reinstalled it, configured it with ‘Eufy’ as Trusted_Device_Name and pre-used accountsettings, and still no thumbnail wenn Doorbell is pressed and keep getting the same disconnect to station logging.

It used to work yust fine before Eufy changed their security policy...

2022-12-28 14:36:39.762 INFO Eufy Security server listening on host 0.0.0.0, port 3000 2022-12-28 14:36:44.418 INFO Push notification connection closed 2022-12-28 14:36:50.080 INFO Push notification connection successfully established 2022-12-28 14:36:50.116 INFO Push notification connection successfully established 2022-12-28 14:36:50.169 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 17267 2022-12-28 14:37:53.637 INFO Disconnected from station T8010P2320361053 2022-12-28 14:37:58.712 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 14954 2022-12-28 14:39:02.184 INFO Disconnected from station T8010P2320361053 2022-12-28 14:39:07.261 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 17351 2022-12-28 14:40:10.718 INFO Disconnected from station T8010P2320361053 2022-12-28 14:40:15.789 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 23958 2022-12-28 14:41:09.491 INFO Client disconnected with ip: 172.30.32.1 port: 35612 code: 1000 reason: Normal Closure 2022-12-28 14:41:19.261 INFO Disconnected from station T8010P2320361053 2022-12-28 14:41:24.320 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 23811 2022-12-28 14:42:27.785 INFO Disconnected from station T8010P2320361053 2022-12-28 14:42:32.886 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 14958 2022-12-28 14:43:36.347 INFO Disconnected from station T8010P2320361053 2022-12-28 14:43:41.407 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 13385 2022-12-28 14:44:44.870 INFO Disconnected from station T8010P2320361053 2022-12-28 14:44:49.931 INFO Connected to station T8010P2320361053 on host 192.168.1.13 and port 17975

Eufy Security add-on 1.3.0 Eufy security V5.1.4

To reproduce

removed add-on, reinstalled it, configured it with ‘Eufy’ as Trusted_Device_Name and pre-used accountsettings, and still no thumbnail wenn Doorbell is pressed and keep getting the same disconnect to station logging.

Screenshots & Logfiles

No response

Additional context

No response

GentleGiantSoftware commented 1 year ago

Same issue here, bug #168 might be closed, things are still not working and see the same issue in the log file. Did delete the persistent.json and added 'Homebase' which is the name in my Eufy app as the TRUSTED_DEVICE_NAME as the description " (viewable with 2fa activated in Eufy App; default: eufyclient)" is not very clear on where to look and what to use....!?

After updating the Eufy Security client in HACS I see the Eufy devices again in HA. The information lines of connected/disconnect all the time remains which are logged about once per minute, assuming this is just informational?

googanhiem commented 1 year ago

I also have this problem (RPi3b+ on latest HA, HB2). To debug I've tried both eufy homebase working modes, also tried reducing the polling rate and changing trusted device name with no change. Did a bit of packet sniffing and looking through network logs, don't think this is directly caused/triggered by network/firewall/dns/UPnP issues.

Multiple disconnections show up every 48hrs or so. Requires a restart of the add-on and reload of the eufy integration in HA. Not sure if a reload can be triggered after x number of disconnections in a row as a temporary solution?

This library is an amazing piece of work @bropat, thanks for your continued support on this.

Daylights commented 1 year ago

I have the same problem, same Eufy hardware. I did a clean install of version 1.3.0 in docker on an Ubuntu server. First it didn't seem to work without the TRUSTED_DEVICE_NAME variable (even though I don't have MFA enabled for the dedicated account). Now the notifications work fine, video stream isn't very stable, and every minute the connection drops for 5 seconds.

googanhiem commented 1 year ago

Just an update, I switched from rpi3 to a x86 setup, with a fresh install. Hasn't fixed the bug.

ersan commented 1 year ago

This is currently happening to me, disconnects every minute or so. Tried resetting persistent.json, changing trusted device names, rebooting HomeBase and nothing helps.

Everything works while it's connected - but it just drops over and over again.

This did not happen before, and I didn't change anything. HB2 with 2C cameras, using this standalone and not part of Home Assistant or anything.

Edit: After enabling verbose mode, this repeats:

2023-02-16 04:00:02.944  DEBUG [P2PClientProtocol.handleMsg] Station <SERIAL> - END - received from host <IP>:<PORT> 
2023-02-16 04:00:02.945  INFO  [Station.onDisconnect] Disconnected from station <SERIAL> 
2023-02-16 04:00:02.946  DEBUG [Station.scheduleReconnect] Schedule reconnect to station <SERIAL>... 
{
  delay: 5000
}
2023-02-16 04:00:07.951  DEBUG [Station.connect] Connecting to station <SERIAL>...
googanhiem commented 1 year ago

Yeah this issue is still ongoing for me. Much of my setup still works, slightly unreliably, with missed alerts a couple times a day.

I'd imagine a lot of people have this issue and haven't seen it in their logs.

bropat commented 1 year ago

Fixed in release 1.3.1 .

doug144 commented 1 year ago

Fixed in release 1.3.1 .

I just upgraded from 1.3.0 (from fuatakgun's repo) to 1.3.4 and the issue still persists. Are there any remnants from the old version that need to be removed or something?

rohanb1965 commented 1 year ago

Hi I have installed the addons Bropats version 1.5.2 and fuatakgun version 6.2.0 I have setup a secondary account which I have confirmed works Doorbell is a T8222-Z Chime is a T8020 on latest firmware

and I am getting

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 2023-05-24 16:43:59.586 INFO Eufy Security server listening on host 0.0.0.0, port 3000 2023-05-24 16:44:04.282 INFO Connected to station T8020P1123021XXX on host 192.168.41.XXX and port 18450 2023-05-24 16:44:11.034 INFO Push notification connection successfully established 2023-05-24 16:44:12.672 INFO Disconnected from station T8020P1123021XXX 2023-05-24 16:44:17.853 INFO Connected to station T8020P1123021AA2 on host 192.168.41.XXX and port 24504 2023-05-24 16:44:25.750 INFO Disconnected from station T8020P1123021XXX

from the log viewer in HA File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 352, in send_message await self._client.send_message(json.dumps(message)) File "/config/custom_components/eufy_security/eufy_security_api/web_socket_client.py", line 86, in send_message raise WebSocketConnectionError() custom_components.eufy_security.eufy_security_api.exceptions.WebSocketConnectionError

This is causing many missed events per day Is there something I have missed ??