Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Eufy Security Add-on Disconnected from station #573

Closed
jeroenschwankhuizen opened this issue Dec 12, 2022 · 34 comments
Closed

Eufy Security Add-on Disconnected from station #573

jeroenschwankhuizen opened this issue Dec 12, 2022 · 34 comments

Comments

@jeroenschwankhuizen
Copy link

Yesterday Eufy updated my HomeBase and since then my security add-on shows the following issue. I'm on the latest Home Assistant release. Please help in fixing this.

2022-12-12 15:08:24.065 INFO Disconnected from station T8010P232028289A 2022-12-12 15:08:29.091 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 18996 2022-12-12 15:09:32.689 INFO Disconnected from station T8010P232028289A 2022-12-12 15:09:37.718 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 22512 2022-12-12 15:10:41.290 INFO Disconnected from station T8010P232028289A 2022-12-12 15:10:46.315 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 27629 2022-12-12 15:11:49.886 INFO Disconnected from station T8010P232028289A

@Alacard
Copy link

Alacard commented Dec 13, 2022 •
edited
Loading

ive noticed this too. ive found someone else with a similar problem (bropat/eufy-security-ws#130). but ive tryed every thing there but no go, ive even tryed moving the eufy-security-ws docker out of HA OS (HA OS is running in a linux based VM ) put it in a stand alone docker but its still doing it.

P.S.
Server OS: Unraid
Station: Homebase 3
VM: QEMU

2022-12-13 23:04:33.334  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
2022-12-13 23:04:43.665  INFO  Push notification connection successfully established 
2022-12-13 23:04:43.738  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 11285 
2022-12-13 23:05:44.207  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:05:49.504  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 19335 
2022-12-13 23:06:49.931  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:06:55.231  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 26153 
2022-12-13 23:07:55.660  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:08:00.958  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 19955 
2022-12-13 23:09:01.391  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:09:06.688  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 20839 
2022-12-13 23:10:07.112  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:10:12.411  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 12042 
2022-12-13 23:11:12.825  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:11:18.124  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 27202 
2022-12-13 23:12:18.549  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:12:23.851  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 19251 
2022-12-13 23:13:24.274  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:13:29.568  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 21273 
2022-12-13 23:14:29.996  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:14:35.293  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 16388 
2022-12-13 23:15:35.727  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:15:41.022  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 18640 
2022-12-13 23:17:28.845  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:17:34.152  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 23414 
2022-12-13 23:18:34.569  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:18:39.870  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 28391 
2022-12-13 23:19:40.281  INFO  Disconnected from station T8030P1322****** 
2022-12-13 23:19:45.581  INFO  Connected to station T8030P1322****** on host 192.168.*.* and port 14234

@kauthmbt
Copy link

kauthmbt commented Dec 14, 2022 •
edited
Loading

I am in the same boat.
Additionally it seems like that the (preview) image of the last record doesn't work anymore while it is still visible in the app. Applies both for doorbell (T8210) + camera (T8142-Z)..

Nevertheless it is still possible to see live streams & entity changes or switching modes. So the rest of the communication between base station and HA still seems to work somehow

@jmc1983
Copy link

jmc1983 commented Dec 14, 2022

I am having the same issue with "Disconnected from station" errors, and no preview images showing. Also do not seem to be able to view any live streams. It does look like some of the sensors are working - for example, my "Doorbell Ringing" sensor has been registering accurately. It is just the images that do not display.

@guthibber
Copy link

Same here. No preview of doorbell camera. I think that also the "doorbell ringing sensor" is nog working anymore.
It was working like a charm for a long time. Then I had to give a "trusted_device_name" and now an update broke things again. Hopefully there will come a solution.

@marcoelgordo
Copy link

Hi,

Great add-on thanks for the good work
I have the same error message since upgrading to Home Assistant 2022.12

@kauthmbt
Copy link

@marcoelgordo call it a timely coincidence as I also have this error with 2022.11.5
But what I figured out safely is that using the thumbnails notification doesn't change the behaviour.
Additionally checked the system version on the Basestation and it reads the date 2022-12-11 (3.2.5.1h). It would perfectly match the time when the behaviour appeared for the first time.
And if it is really an issue caused by the firmware, I assume a potential solution might only come from bropat...

@vaderag
Copy link

vaderag commented Dec 15, 2022

Unsure if this is related I’ve found something has gone wrong in the past few days
I have an automation using NodeRed which activated Night mode, but it’s stopped working…

The api calls successfully
image

But no change in the Eufy app or in HA status
image

I recall this roughly tallies with when I ran an update to my HACS integrations and I think there was an update to Eufy - has something significant changed?

@fuatakgun
Copy link
Owner

Did you all set trusted device name field in add-on configuration?

@marcoelgordo
Copy link

Hi,

I did add it for the doorbell, not the station.
Cheers,

M

@vaderag
Copy link

vaderag commented Dec 15, 2022

Did you all set trusted device name field in add-on configuration?

Is this something new? I don't have it set but everything was working until a few days ago
Can it be anything?

@guthibber
Copy link

Did you all set trusted device name field in add-on configuration?

Yes, I put DEVICENAME as TRUSTED_DEVICE_NAME, it was the solution to get things working last time.
I think the Eufy update on the HomeBase 2 broke things this time.
I am running 3.2.5.1h since December 11.

@jeroenschwankhuizen
Copy link
Author

Did you all set trusted device name field in the add-on configuration?

Yes, I did and it was working until the next day on 11 December I saw that Eufy Home HomeBase was updated with the following fixes: 1. Fixed the issue of selecting "switch modes from keypad" 2. Improved the system security and stability by fixing some bugs

@vaderag
Copy link

vaderag commented Dec 15, 2022

Yes, looks like it was the trusted device name for me...
What is this actually used for? Can I suggest it gets autopopulated to TRUSTED_DEVICE_NAME so that when people update they don't need to worry about this unless they want to?

@fuatakgun
Copy link
Owner

Earlier this change, it was a fix value (eufy security) but apparently eufy somehow didn't like it. So we want every user to set this something intentionally.

You see these values in eufy app (two favtor authentication-devices) when you enable two factor authentication, which we don't support as of now :-)

@Alacard
Copy link

Alacard commented Dec 15, 2022

Did you all set trusted device name field in add-on configuration?

Yes sir, that is set

@jeroenschwankhuizen
Copy link
Author

It tried switching the TRUSTED_DEVICE_NAME from 192.168.86.111 (home assistant IP address) to 192.168.86.23 (host mentioned in the addon log error messages) but that is also not working

@Alacard
Copy link

Alacard commented Dec 15, 2022

It tried switching the TRUSTED_DEVICE_NAME from 192.168.86.111 (home assistant IP address) to 192.168.86.23 (host mentioned in the addon log error messages) but that is also not working

"TRUSTED_DEVICE_NAME" is suppose to be a "name" not a ip. example HomeAssistent or AutomationStation or MasterController. its really just a way to assign a name to that connection so it can easily be referred to on eufy's end

@PMizz13
Copy link

PMizz13 commented Dec 15, 2022

Not sure where I am going wrong but my configure menu doesn't show a trusted device name field anywhere. Any ideas?

@Alacard
Copy link

Alacard commented Dec 15, 2022

Not sure where I am going wrong but my configure menu doesn't show a trusted device name field anywhere. Any ideas?

This is starting to get off topic but ill help you real quick, make sure your running the lastest Add-on (V2.90) (not talking about the integration plugin but the add-on, from step 6.1 if you following the installation guide)

@marcoelgordo
Copy link

marcoelgordo commented Dec 15, 2022 via email

@jmc1983
Copy link

jmc1983 commented Dec 15, 2022

Wanting to bring this back to the original issue - I have TRUSTED_DEVICE_NAME set, and have for some time - with the integration working properly. The issue in this thread is a new issue that seems to have started the week of December 4 2022. I wonder if this is a break due to an update that Eufy made in response to the recent articles about their cameras storing thumbnails on AWS servers?

@PMizz13
Copy link

PMizz13 commented Dec 15, 2022

Apologies I didn't realise I was going off as mine only broke today. Thanks for your help though! Managed to get it working again.

@Timeteo
Copy link

Timeteo commented Dec 20, 2022

@fuatakgun
Also having issues. I did populate the Trusted Device name when this add-on had issues a few weeks ago and worked but I am having new issues now. I have set the port to 3001 in the add-on config, not sure why it shows 3000 in the add-on log along with the log dump below.
After seeing the 403 error I validated that the account I am using for the add-on is functioning using the Eufy app and it also has access to the device.

2022-12-20 15:01:12.227  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
2022-12-20 15:01:12.585  ERROR EufyError - Code: undefined Message: undefined (HTTP Code: 403) - requestUrl: https://security-app.eufylife.com/v1/passport/profile 
2022-12-20 15:01:12.803  ERROR Generic Error: 
 EufyError  Code: undefined Message: undefined (HTTP Code: 403)
details:
{
  code: 'ERR_NON_2XX_3XX_RESPONSE',
  timings: {
    start: 1671548472268,
    socket: 1671548472270,
    lookup: 1671548472290,
    connect: 1671548472358,
    secureConnect: 1671548472503,
    upload: 1671548472504,
    response: 1671548472573,
    end: 1671548472575,
    error: undefined,
    abort: undefined,
    phases: {
      wait: 2,
      dns: 20,
      tcp: 68,
      tls: 145,
      request: 1,
      firstByte: 69,
      download: 2,
      total: 307
    }
  }
}
error stack:
• index.js:118 <anonymous>
    node_modules/got/dist/source/as-promise/index.js:118:42
• task_queues:96 processTicksAndRejections
    node:internal/process/task_queues:96:5

@Timeteo
Copy link

Timeteo commented Dec 20, 2022

Perhaps this is the culprit?
https://community.security.eufy.com/t/to-our-eufy-security-customers-and-partners/3568215

"Today, users can still log in to our eufy.com Web portal to view live streams of their cameras. However, users can no longer view live streams (or share active links to these live streams with others) outside of eufy’s secure Web portal. Anyone wishing to view these links must first log in to the eufy.com Web portal."

@celson
Copy link

celson commented Dec 20, 2022

There is the same problem that @Timeteo mentioned. HTTP Code: 403

@crispywisp
Copy link

My integration broke. And I can't get it working again. I'm getting a similar error as @Timeteo.

2022-12-21 04:27:09.454  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
2022-12-21 04:27:09.696  ERROR EufyError - Code: undefined Message: undefined (HTTP Code: 403) - requestUrl: https://security-app.eufylife.com/v1/passport/profile 
2022-12-21 04:27:09.708  ERROR Generic Error: 
 EufyError  Code: undefined Message: undefined (HTTP Code: 403)
details:
{
  code: 'ERR_NON_2XX_3XX_RESPONSE',
  timings: {
    start: 1671596829480,
    socket: 1671596829483,
    lookup: 1671596829491,
    connect: 1671596829542,
    secureConnect: 1671596829641,
    upload: 1671596829641,
    response: 1671596829684,
    end: 1671596829686,
    error: undefined,
    abort: undefined,
    phases: {
      wait: 3,
      dns: 8,
      tcp: 51,
      tls: 99,
      request: 0,
      firstByte: 43,
      download: 2,
      total: 206
    }
  }
}
error stack:
• index.js:118 <anonymous>
    node_modules/got/dist/source/as-promise/index.js:118:42
• task_queues:96 processTicksAndRejections
    node:internal/process/task_queues:96:5

@ez12a
Copy link

ez12a commented Dec 21, 2022

This might be related to the addon integration. They're getting the 403 error, looks like the version of the API it's using was deprecated recently: bropat/eufy-security-client#282

@jeroenschwankhuizen
Copy link
Author

I'm now also getting the below errors
2022-12-21 08:07:47.740 INFO Disconnected from station T8010P232028289A 2022-12-21 08:07:52.792 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 11171 2022-12-21 08:08:42.674 ERROR EufyError - Code: undefined Message: undefined (HTTP Code: 403) - requestUrl: https://security-app-eu.eufylife.com/v1/house/station_list 2022-12-21 08:08:42.679 ERROR Stations - Generic Error: EufyError Code: undefined Message: undefined (HTTP Code: 403) details: { code: 'ERR_NON_2XX_3XX_RESPONSE', timings: { start: 1671610122601, socket: 1671610122602, lookup: 1671610122602, connect: 1671610122617, secureConnect: 1671610122656, upload: 1671610122657, response: 1671610122671, end: 1671610122672, error: undefined, abort: undefined, phases: { wait: 1, dns: 0, tcp: 15, tls: 39, request: 1, firstByte: 14, download: 1, total: 71 } } } error stack: • index.js:118 <anonymous> node_modules/got/dist/source/as-promise/index.js:118:42 • task_queues:96 processTicksAndRejections node:internal/process/task_queues:96:5 2022-12-21 08:08:42.681 INFO No stations found.

@calvinbui
Copy link

I'm still getting the constant connected/disconnected log messages on version 1.3.0 of the add-on

@marcoelgordo
Copy link

Same issue here

@jeroenschwankhuizen
Copy link
Author

I still get the same errors after updating to the newer version of the add-on for Eufy

@Timeteo
Copy link

Timeteo commented Dec 25, 2022

Works now with latest (yesterday) update. I needed to uninstall (do no upgrade) the Eufy add-on and then re-installed and set-up the configuration properties again.

I see this issue being tracked in multiple place. There are a bunch of duplicate issues here in Github, as well as the thread on community.home-assistant.io. That thread appears to be where the ongoing discussion and updates are posted.

@jeroenschwankhuizen
Copy link
Author

tried removing, restarting and reinstalling from scratch. Still not working:
2022-12-25 16:38:47.036 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-12-25 16:38:57.349 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 21265
2022-12-25 16:39:00.498 INFO Push notification connection successfully established
2022-12-25 16:40:00.834 INFO Disconnected from station T8010P232028289A
2022-12-25 16:40:05.868 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 10140
2022-12-25 16:41:09.379 INFO Disconnected from station T8010P232028289A
2022-12-25 16:41:14.410 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 19779
2022-12-25 16:42:17.893 INFO Disconnected from station T8010P232028289A
2022-12-25 16:42:22.927 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 20433
2022-12-25 16:43:26.430 INFO Disconnected from station T8010P232028289A
2022-12-25 16:43:31.458 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 21551
2022-12-25 16:44:34.950 INFO Disconnected from station T8010P232028289A
2022-12-25 16:44:39.983 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 12469
2022-12-25 16:45:43.478 INFO Disconnected from station T8010P232028289A
2022-12-25 16:45:48.508 INFO Connected to station T8010P232028289A on host 192.168.86.23 and port 11674
2022-12-25 16:46:16.128 INFO Client disconnected with ip: 172.30.32.1 port: 60302 code: 1006 reason: Abnormal Closure
2022-12-25 16:46:16.130 INFO Client disconnected with ip: 172.30.32.1 port: 60304 code: 1006 reason: Abnormal Closure

@fuatakgun fuatakgun mentioned this issue Dec 27, 2022
Closed
@fuatakgun
Copy link
Owner

#597

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests