search

homebridge-eufy-security / plugin

Homebridge plugin to control certain Eufy Security devices
Apache License 2.0
166 stars 24 forks source link

[Bug]: Login failed #250

Closed yanavery closed 11 months ago

yanavery commented 1 year ago

What happened?

As a follow-up to #201 which was closed, I'm still observing generalized and systematic login issues (always fails) between the homebridge-eufy-security plugin and Eufy.

With release 2.1.3 (for which I believe included the necessary fix(es) for #201), I still can't login ... Homebridge logs say:

[12/18/2022, 6:47:15 PM] [EufySecurity-2.1.3] ERROR: Not connected can't continue!

Different login attempts with either my main Eufy account or another one I created for Homebridge purposes are both failing while those 2 accounts are working fine when used from the Eufy mobile app. I'm also seeing this in the Homebridge logs after I attempt a login:

[18/12/2022, 19:23:54] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /login
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Terminating child process...
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Child process ended

From the plugin's UI, when I'm trying to use my main account which has 2FA configured, I do receive the Eufy email and I do get challenged by the plugin to enter my 2FA code in the Homebridge Eufy Plug-in UI, but it fails after ... For my other Eufy account that doesn't have 2FA enabled, I obviously don't get challenged for a 2FA code and it fails immediately with a message that says "Login was not successful!" ... I do get some Captha challenges along the way, so it looks like some communication between the Homebridge plugin and Eufy is happening, but it just doesn't seem to be able to finalize.

BTW, Eufy country for me is set to Canada (both in Eufy account and in the Homebridge plugin), maybe it could be related to that?

If any additional details are needed to troubleshoot, please let me know.

Thanks,

Device Type

Station (Supported)

Plugin Version

v2.0.x (Supported)

HomeBridge Version

v1.4.x (Supported)

NodeJS Version

v16 (Supported)

Operating System

Raspbian 10+ (Supported)

Relevant log output

[12/18/2022, 6:47:15 PM] [EufySecurity-2.1.3] ERROR: Not connected can't continue!

[18/12/2022, 19:23:54] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /login
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Terminating child process...
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Child process ended

config

{
    "platform": "EufySecurity",
    "username": "****redacted****",
    "password": "****redacted****",
    "pollingIntervalMinutes": 30,
    "hkHome": 1,
    "hkAway": 0,
    "hkNight": 3,
    "hkOff": 63,
    "enableDetailedLogging": true,
    "ignoreStations": [
        "****redacted****",
        "****redacted****",
        "****redacted****"
    ],
    "ignoreDevices": [
        "****redacted****",
        "****redacted****",
        "****redacted****",
        "****redacted****"
    ],
    "country": "CA",
    "CameraMaxLivestreamDuration": 30,
    "cleanCache": true,
    "_bridge": {
        "username": "****redacted****",
        "port": 53985
    },
    "cameras": [
        {
            "serialNumber": "****redacted****",
            "rtsp": false,
            "talkback": false
        },
        {
            "serialNumber": "****redacted****",
            "rtsp": false,
            "talkback": false
        },
        {
            "serialNumber": "****redacted****",
            "rtsp": false,
            "talkback": false
        }
    ]
}
github-actions[bot] commented 1 year ago

Did you check this Common Issues pages ?

thieren commented 1 year ago

Hi @yanavery

  1. Can you please try with the beta? There'll be at least additional log messages if the login fails due to 2fa or captcha requests.

From the plugin's UI, when I'm trying to use my main account which has 2FA configured, I do receive the Eufy email and I do get challenged by the plugin to enter my 2FA code in the Homebridge Eufy Plug-in UI, but it fails after

What does 'fail' mean here exactly? To be more precise: the login process for the plugin itself and for the ui config are separate from each other. So does the config ui show you your devices after login, but the plugin itself can't login, or does the config ui also has problems logging in?

If the latter: could you provide the config-ui.log from the plugin storage path?

yanavery commented 1 year ago

Upgrading to beta is giving an error but not much details unfortunately:

[19/12/2022, 21:43:25] [Homebridge UI] Running Command: npm install --save homebridge-eufy-security@2.2.0-beta.14
[19/12/2022, 21:53:58] [Homebridge UI] Operation failed. Please review log for details.

Not seeing anything additional and/or relevant in the logs.

In https://github.com/homebridge-eufy-security/plugin/issues/201#issuecomment-1357109747, I believe @jp-lno tried with the latest beta and said he was still observing the problem in the beta version as well.

jp-lno commented 1 year ago

I Have the exact same behavior. On both Beta and release. I’m Able to connect via captcha and fetch devices. But on restart still have login was not successful. In the mean time I receive 2FA email every time I restart HB platform as required after each plugin change. The Plugin Seems to retry login for every restart. I’ve uninstalled plugin and clean cache. And always won’t able to start plugin.

thieren commented 1 year ago

I Have the exact same behavior. On both Beta and release. I’m Able to connect via captcha and fetch devices. But on restart still have login was not successful. In the mean time I receive 2FA email every time I restart HB platform as required after each plugin change. The Plugin Seems to retry login for every restart. I’ve uninstalled plugin and clean cache. And always won’t able to start plugin.

Did you try to write something into the new "Device Name" Field at the login screen? Does this change anything?

yanavery commented 1 year ago

I tried entering a "Device Name" or leaving that field blank and still getting the issue. Obviously, as far as I'm concerned I was not able to try this on the beta version, but only on latest release, as I'm getting an error when trying to install latest beta. I hope this helps. Thanks,

thieren commented 1 year ago

I tried entering a "Device Name" or leaving that field blank and still getting the issue. Obviously, as far as I'm concerned I was not able to try this on the beta version, but only on latest release, as I'm getting an error when trying to install latest beta. I hope this helps. Thanks,

Well the thing is that I'm not entirely sure if this is the same issue for both of you.

@jp-lno clearly can 'log in' in the way that it's asking for the 2fa code every time. The plugin can only resolve this with the config ui. It's not clear for me why it's asking this, but for him it could maybe be resolved by changing to another account. I'd advise to try a new guest account with which the devices are then shared.

But as he stated

I’m Able to connect via captcha and fetch devices.

So the login issue is just on plugin restart, not in the config ui itself.

As I was understanding it you (@yanavery) cannot even log in with the config ui screen. That's why I believe these two issues are not really related. Again, if I could have a look at the config-ui.log file, this might help. There is much more information in that, than just in the homebridge log.

yanavery commented 1 year ago

@thieren, thanks for getting back so quickly. Here's a redacted extract for my configui-server.log file. I couldn't find a config-ui.log file, at least not in the /var/lib/homebridge/eufysecurity folder.

I'm seeing in there a couple of received unknown message entries, not sure if that could be related, but letting you look at this in greater details.

Let me know if you need anything else to help troubleshoot. Thanks,

{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Normalized Properties {\n  stationSN: '***redacted***B0C',\n  properties: {\n    name: 'HomeBase',\n    model: 'T8010',\n    serialNumber: '***redacted***B0C',\n    type: 0,\n    hardwareVersion: 'P0',\n    softwareVersion: '3.2.5.1h',\n    macAddress: '04:17:B6:1C:28:F4',\n    timeFormat: 1,\n    alarmVolume: 26,\n    alarm: false,\n    alarmType: 0,\n    alarmArmed: false,\n    alarmArmDelay: 0,\n    alarmDelay: 0,\n    alarmDelayType: 0,\n    promptVolume: NaN,\n    switchModeWithAccessCode: false,\n    guardMode: 1,\n    stationOffSecuritySettings: {\n      mode_id: 6,\n      devices: [Array],\n      account_id: 'a41a7dcb30bf8659e513def83527c57e6a5da616'\n    },\n    turnOffAlarmWithButton: false,\n    alarmTone: 1,\n    notificationStartAlarmDelay: true,\n    notificationSwitchModeSchedule: true,\n    notificationSwitchModeGeofence: true,\n    notificationSwitchModeApp: true,\n    notificationSwitchModeKeypad: true,\n    stationAwaySecuritySettings: {\n      devices: [Array],\n      count_down_alarm: [Object],\n      mode_id: 0,\n      count_down_arm: [Object],\n      account_id: 'a41a7dcb30bf8659e513def83527c57e6a5da616'\n    },\n    autoEndAlarm: false,\n    lanIpAddress: '***redacted***.111'\n  }\n}","time":"2022-12-19T00:38:06.613Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Normalized Properties {\n  stationSN: '***redacted***3A0',\n  properties: {\n    name: 'WiFi Bridge',\n    model: 'T8021',\n    serialNumber: '***redacted***3A0',\n    type: 0,\n    hardwareVersion: 'P0',\n    softwareVersion: '3.2.4.9h',\n    macAddress: '04:17:B6:27:CC:8C',\n    timeFormat: 1,\n    alarmVolume: 26,\n    alarm: false,\n    alarmType: 0,\n    alarmArmed: false,\n    alarmArmDelay: 0,\n    alarmDelay: 0,\n    alarmDelayType: 0,\n    autoEndAlarm: true,\n    notificationStartAlarmDelay: true,\n    alarmTone: 1,\n    promptVolume: NaN,\n    notificationSwitchModeSchedule: true,\n    notificationSwitchModeGeofence: true,\n    notificationSwitchModeApp: true,\n    notificationSwitchModeKeypad: true,\n    lanIpAddress: '***redacted***.156',\n    guardMode: 1\n  }\n}","time":"2022-12-19T00:38:06.627Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Normalized Properties {\n  stationSN: '***redacted***AE3',\n  properties: {\n    name: 'Kitchen',\n    model: 'T8410',\n    serialNumber: '***redacted***AE3',\n    type: 31,\n    hardwareVersion: 'P3',\n    softwareVersion: '2.1.5.1',\n    lanIpAddress: '***redacted***.108',\n    macAddress: '0417B607E80D',\n    timeFormat: 1,\n    alarm: false,\n    alarmType: 0,\n    guardMode: 1,\n    currentMode: 1\n  }\n}","time":"2022-12-19T00:38:06.647Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Normalized Properties {\n  stationSN: '***redacted***203',\n  properties: {\n    name: 'Garage',\n    model: 'T8410',\n    serialNumber: '***redacted***203',\n    type: 31,\n    hardwareVersion: 'P4',\n    softwareVersion: '2.1.5.1',\n    lanIpAddress: '***redacted***.101',\n    macAddress: '0417B62866EB',\n    timeFormat: 1,\n    alarm: false,\n    alarmType: 0,\n    guardMode: 1,\n    currentMode: 1\n  }\n}","time":"2022-12-19T00:38:06.656Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Normalized Properties {\n  stationSN: '***redacted***D7F',\n  properties: {\n    name: 'Living Room',\n    model: 'T8410',\n    serialNumber: '***redacted***D7F',\n    type: 31,\n    hardwareVersion: 'P4',\n    softwareVersion: '2.1.5.1',\n    lanIpAddress: '***redacted***.183',\n    macAddress: '0417B666648C',\n    timeFormat: 1,\n    alarm: false,\n    alarmType: 0,\n    guardMode: 1,\n    currentMode: 1\n  }\n}","time":"2022-12-19T00:38:06.675Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Login response: GCM -> logged in -> waiting for push messages...","time":"2022-12-19T00:38:15.231Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Request: {\n  method: 'post',\n  endpoint: 'v1/apppush/register_push_token',\n  token: '***redacted***7a5',\n  data: {\n    is_notification_enable: true,\n    token: '***redacted***Cm7k',\n    transaction: '1671410295252'\n  }\n}","time":"2022-12-19T00:38:15.260Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"IqStanza: Not implemented {\n  tag: 7,\n  object: { type: 'SET', id: '', extension: { id: 12, data: <Buffer > } }\n}","time":"2022-12-19T00:38:16.044Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Response: { response: { code: 0, msg: 'Succeed.' } }","time":"2022-12-19T00:38:17.096Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Push token registered successfully","time":"2022-12-19T00:38:17.100Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Request: {\n  method: 'post',\n  endpoint: 'v1/app/review/app_push_check',\n  token: '***redacted***7a5',\n  data: { app_type: 'eufySecurity', transaction: '1671410297109' }\n}","time":"2022-12-19T00:38:17.114Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Response: {\n  response: {\n    code: 0,\n    msg: 'Succeed.',\n    data: { app_type: 'eufySecurity', pushable: true, reviewable: false }\n  }\n}","time":"2022-12-19T00:38:17.836Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Push token OK","time":"2022-12-19T00:38:17.838Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":30,"msg":"Push notification connection successfully established","time":"2022-12-19T00:38:17.839Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - END - received from host ***redacted***.111:13704","time":"2022-12-19T00:38:58.328Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":30,"msg":"Disconnected from station ***redacted***B0C","time":"2022-12-19T00:38:58.343Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Schedule reconnect to station ***redacted***B0C... { delay: 5000 }","time":"2022-12-19T00:38:58.352Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Connecting to station ***redacted***B0C... { p2pConnectionType: 'QUICKEST' }","time":"2022-12-19T00:39:04.081Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Trying to local lookup address for station ***redacted***B0C with host ***redacted***.111","time":"2022-12-19T00:39:04.085Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.212Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.214Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_RESP - Got response {\n  remoteAddress: '***redacted***.122',\n  remotePort: 32100,\n  response: { responseCode: 0 }\n}","time":"2022-12-19T00:39:04.228Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_ADDR - Got response {\n  remoteAddress: '***redacted***.122',\n  remotePort: 32100,\n  response: { ip: '***redacted***.242', port: 26862 }\n}","time":"2022-12-19T00:39:04.232Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - QUICKEST - Try to connect to ***redacted***.242:26862...","time":"2022-12-19T00:39:04.234Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.242 on port 26862...","time":"2022-12-19T00:39:04.235Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_ADDR - Got response {\n  remoteAddress: '***redacted***.122',\n  remotePort: 32100,\n  response: { ip: '***redacted***.111', port: 28627 }\n}","time":"2022-12-19T00:39:04.249Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - QUICKEST - Try to connect to ***redacted***.111:28627...","time":"2022-12-19T00:39:04.250Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.252Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.263Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.264Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.284Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.285Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.297Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.298Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.309Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.310Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_ADDR2 - Got response {\n  remoteAddress: '***redacted***.122',\n  remotePort: 32100,\n  response: { ip: '***redacted***.66', port: 10000, data: '149720f4' }\n}","time":"2022-12-19T00:39:04.324Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM2 - Connecting to host ***redacted***.66 on port 10000...","time":"2022-12-19T00:39:04.326Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - received unknown message {\n  remoteAddress: '***redacted***.122',\n  remotePort: 32100,\n  response: {\n    message: 'f169008408000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000',\n    length: 136\n  }\n}","time":"2022-12-19T00:39:04.342Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_ADDR2 - Got response {\n  remoteAddress: '***redacted***.101',\n  remotePort: 32100,\n  response: { ip: '***redacted***.66', port: 10000, data: '148a8425' }\n}","time":"2022-12-19T00:39:04.346Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM2 - Connecting to host ***redacted***.66 on port 10000...","time":"2022-12-19T00:39:04.347Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_RESP - Got response {\n  remoteAddress: '***redacted***.101',\n  remotePort: 32100,\n  response: { responseCode: 0 }\n}","time":"2022-12-19T00:39:04.360Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_ADDR - Got response {\n  remoteAddress: '***redacted***.101',\n  remotePort: 32100,\n  response: { ip: '***redacted***.242', port: 26862 }\n}","time":"2022-12-19T00:39:04.365Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - QUICKEST - Try to connect to ***redacted***.242:26862...","time":"2022-12-19T00:39:04.366Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.242 on port 26862...","time":"2022-12-19T00:39:04.368Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - received unknown message {\n  remoteAddress: '***redacted***.101',\n  remotePort: 32100,\n  response: {\n    message: 'f169008408000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000',\n    length: 136\n  }\n}","time":"2022-12-19T00:39:04.381Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOOKUP_ADDR - Got response {\n  remoteAddress: '***redacted***.101',\n  remotePort: 32100,\n  response: { ip: '***redacted***.111', port: 28627 }\n}","time":"2022-12-19T00:39:04.385Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - QUICKEST - Try to connect to ***redacted***.111:28627...","time":"2022-12-19T00:39:04.386Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.387Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.399Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.400Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.411Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.412Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.424Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.425Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - LOCAL_LOOKUP_RESP - Got response { ip: '***redacted***.111', port: 28627 }","time":"2022-12-19T00:39:04.437Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CHECK_CAM - Connecting to host ***redacted***.111 on port 28627...","time":"2022-12-19T00:39:04.438Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - CAM_ID - Connected to station ***redacted***B0C on host ***redacted***.111 port 28627","time":"2022-12-19T00:39:04.450Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":30,"msg":"Connected to station ***redacted***B0C on host ***redacted***.111 and port 28627","time":"2022-12-19T00:39:04.454Z","v":0}
{"name":"[EufySecurity-2.1.3]","hostname":"homebridge","pid":7637,"level":20,"msg":"Station ***redacted***B0C - received unknown message {\n  remoteAddress: '***redacted***.22',\n  remotePort: 32100,\n  response: {\n    message: 'f169008408000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000000210273d3cb7360000000000000000',\n    length: 136\n  }\n}","time":"2022-12-19T00:39:04.464Z","v":0}
jp-lno commented 1 year ago

I tried entering a "Device Name" or leaving that field blank and still getting the issue. Obviously, as far as I'm concerned I was not able to try this on the beta version, but only on latest release, as I'm getting an error when trying to install latest beta. I hope this helps. Thanks,

Well the thing is that I'm not entirely sure if this is the same issue for both of you.

@jp-lno clearly can 'log in' in the way that it's asking for the 2fa code every time. The plugin can only resolve this with the config ui. It's not clear for me why it's asking this, but for him it could maybe be resolved by changing to another account. I'd advise to try a new guest account with which the devices are then shared.

But as he stated

I’m Able to connect via captcha and fetch devices.

So the login issue is just on plugin restart, not in the config ui itself.

As I was understanding it you (@yanavery) cannot even log in with the config ui screen. That's why I believe these two issues are not really related. Again, if I could have a look at the config-ui.log file, this might help. There is much more information in that, than just in the homebridge log.

Hello thanks for feedback.

I will try again with a new guest account. But for the moment plugin won't start, even in Beta 14 :/ Will do my best to cleanup and get a working fresh install. I let you know when it's done. Thanks [12/20/2022, 4:46:12 PM] ==================== [12/20/2022, 4:46:12 PM] ERROR LOADING PLUGIN homebridge-eufy-security: [12/20/2022, 4:46:12 PM] Error: Cannot find module 'ms'

EDIT: @thieren I confirm that creating a new account and share devices solve my login issue. It's work again now.

walloutlet commented 1 year ago

Looks like Eufy changed something with their login process. I have the same issue above, just started today for me. When I logged into the Eufy Security app on my iPhone to validate that my devices were online and I could login directly with a Eufy supplied app, I got a notification that they made changes to their login/password requirements requiring numbers and letters. I dismissed this as my passwords are all randomized with a password manager, could log in via the Eufy Security app on my iPhone but this plugin doesn't seem to to like logging in anymore.

Not sure if that is helpful, but something observed.

hanssep commented 1 year ago

Same here. Everything was fine until today where the plugin fails because it cannot login. Using beta version, tested with multiple accounts. Log below:

{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"init eufyClient","time":"2022-12-20T16:52:56.599Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"Loaded API_BASE: https://security-app.eufylife.com","time":"2022-12-20T16:52:57.072Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"Load previous login_hash: ##redacted##","time":"2022-12-20T16:52:57.077Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"Load previous token: {\n  token: '##redacted##',\n  tokenExpiration: 1673284308000\n}","time":"2022-12-20T16:52:57.083Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"login with credentials","time":"2022-12-20T16:52:57.107Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"Login and get an access token {\n  token: '##redacted##',\n  tokenExpiration: 2023-01-09T17:11:48.000Z\n}","time":"2022-12-20T16:52:57.109Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"Request: {\n  method: 'get',\n  endpoint: 'v1/passport/profile',\n  token: '##redacted##',\n  data: undefined\n}","time":"2022-12-20T16:52:57.110Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":50,"msg":"EufyError - Code: undefined Message: undefined (HTTP Code: 403) - requestUrl: https://security-app.eufylife.com/v1/passport/profile","time":"2022-12-20T16:52:57.469Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":50,"msg":"Generic Error: HTTPError [EufyError]: Code: undefined Message: undefined (HTTP Code: 403)\n    at Request.<anonymous> (/homebridge/node_modules/homebridge-eufy-security/node_modules/got/dist/source/as-promise/index.js:118:42)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {\n  code: 'ERR_NON_2XX_3XX_RESPONSE',\n  timings: {\n    start: 1671555177118,\n    socket: 1671555177119,\n    lookup: 1671555177120,\n    connect: 1671555177201,\n    secureConnect: 1671555177380,\n    upload: 1671555177381,\n    response: 1671555177463,\n    end: 1671555177464,\n    error: undefined,\n    abort: undefined,\n    phases: {\n      wait: 1,\n      dns: 1,\n      tcp: 81,\n      tls: 179,\n      request: 1,\n      firstByte: 82,\n      download: 1,\n      total: 346\n    }\n  }\n}","time":"2022-12-20T16:52:57.472Z","v":0}
{"name":"[EufySecurity-2.2.0-beta.14]","hostname":"vm-dietpi-hass","pid":429,"level":20,"msg":"connected?: false","time":"2022-12-20T16:52:57.473Z","v":0}
thieren commented 1 year ago

@yanavery

Here's a redacted extract for my configui-server.log file. I couldn't find a config-ui.log file

Hi. Yeah this file is correct. Sry, mixed up the filenames. But according to this snippet the config ui could login successfully. It even gets the devices. So It also might help if you try to create a new guest account like @jp-lno did.

@jp-lno

There seems to be some memory leak issues with homebridge or eufy plugin. My Pi doesn't respond for a while when I restart Homebridge. Memory/cpu consumption on HTOP is huge while homebridge is starting.

Have not seen this yet, but also did not look out for it before. Is this also an issue if you disable the plugin? Then it would be a homebridge issue.

@walloutlet The login process was changed a while ago, but the changes are already accounted for in the newer version of the plugin. At least I'm not aware of any other changes made recently. For me all seems working fine at least.

@hanssep Your log snippet states a HTTP 403 error. I cannot say why, but it seems that the server was not available at the time you tried to log in. Maybe try it again at a later time?

hanssep commented 1 year ago

Thanks for the prompt feedback. I double checked my setup, network, router, etc and nothing has changed. Logs show, camera’s worked just fine yesterday. Could it be Eufy is starting to block the plugin due to all the security news around Eufy? I’ve seen a slew of device updates and now also noticed a CAPTCHA when using the iOS app.

Is there any way I can clear a cache, change a device ID, etc to check this?

-- Hans On Dec 20, 2022 at 10:41 -0800, thieren @.***>, wrote:

@yanavery

Here's a redacted extract for my configui-server.log file. I couldn't find a config-ui.log file Hi. Yeah this file is correct. Sry, mixed up the filenames. But according to this snippet the config ui could login successfully. It even gets the devices. So It also might help if you try to create a new guest account like @jp-lno did. @jp-lno There seems to be some memory leak issues with homebridge or eufy plugin. My Pi doesn't respond for a while when I restart Homebridge. Memory/cpu consumption on HTOP is huge while homebridge is starting. Have not seen this yet, but also did not look out for it before. Is this also an issue if you disable the plugin? Then it would be a homebridge issue. @walloutlet The login process was changed a while ago, but the changes are already accounted for in the newer version of the plugin. At least I'm not aware of any other changes made recently. For me all seems working fine at least. @hanssep Your log snippet states a HTTP 403 error. I cannot say why, but it seems that the server was not available at the time you tried to log in. Maybe try it again at a later time? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Nazanne commented 1 year ago

We are also getting login errors. Our log looks exactly like the one @hanssep submitted with the 403 error.

thieren commented 1 year ago

We are also getting login errors. Our log looks exactly like the one @hanssep submitted with the 403 error.

Is this also only since today?

Has anyone the opportunity to install a fresh homebridge (maybe on a vm) and test with an absolutely new eufy account?

Nazanne commented 1 year ago

Followup: The user we were using to login with did not have 2FA turned on. Logging in with a different account that had 2FA turned on was successful. We'll try turning 2FA on in our Homebridge account.

Edit: Turning 2FA on in the Homebridge account was not successful. We'll try making a new account.

hanssep commented 1 year ago

I removed the plugin, re-installed, logged in with user with 2FA. Login is successful but getting devices takes a long time. After HB restart, no devices show and need to login again which then fails. Grrr, Eufy what are you doing?

-- Hans On Dec 20, 2022 at 12:07 -0800, Nazanne @.***>, wrote:

Followup: The user we were using to login with did not have 2FA turned on. Logging in with a different account that had 2FA turned on was successful. We'll try turning 2FA onto our Homebridge account. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

yanavery commented 1 year ago

@thieren, I was able to have everything working again (under 2.1.3) by, as suggested, creating a new guest account in the Eufy app and replacing my Homebridge setup to use that new account instead of the old one (which I also removed from the Eufy app).

[12/20/2022, 3:16:45 PM] [EufySecurity-2.1.3] DEBUG: EufyClient connected true
[12/20/2022, 3:16:45 PM] [EufySecurity-2.1.3] DEBUG: CameraMaxLivestreamDuration: 30
[12/20/2022, 3:17:01 PM] [EufySecurity-2.1.3] DEBUG: Push Connected!
[12/20/2022, 3:17:30 PM] [EufySecurity-2.1.3] INFO:  Looking for old cached accessories that seem to be outdated...
[12/20/2022, 3:17:30 PM] [EufySecurity-2.1.3] INFO:  No outdated cached accessories found.

I know others seem to be having issues, but as far as I'm concerned, this is resolved for me, maybe not in the most elegant way, but at this point, I'm a happy camper.

Thanks,

yanavery commented 1 year ago

Doh, I jinxed myself ... :-( I restarted Homebridge and it's now failing again ...

[12/20/2022, 3:31:48 PM] [EufySecurity-2.1.3] DEBUG: plugin data store: /var/lib/homebridge/eufysecurity
[12/20/2022, 3:31:48 PM] [EufySecurity-2.1.3] DEBUG: Using bropats eufy-security-client library in version 2.2.3
[12/20/2022, 3:31:48 PM] [EufySecurity-2.1.3] INFO:  Country set: CA
[12/20/2022, 3:31:48 PM] [EufySecurity-2.1.3] INFO:  Finished initializing!
[20/12/2022, 15:31:52] Homebridge v1.5.1 (HAP v0.10.4) (homebridge-eufy-security) is running on port 53985.
[12/20/2022, 3:32:11 PM] [EufySecurity-2.1.3] DEBUG: EufyClient connected false
[12/20/2022, 3:32:11 PM] [EufySecurity-2.1.3] ERROR: Not connected can't continue!
Z1mDMan commented 1 year ago

I am also having issues logging in again. I have tried my main account, and 3 other child accounts and it's not letting me log into any of them. I noticed it this afternoon when a package came and the doorbell rang. I opened up home app and there was no camera feed. I checked homebridge and had the same "ERROR: Not connected can't continue!" in the log after restarting the child bridge. I have tried accounts with and without 2FA enabled. I have tried 2.1.3 and the latest beta and nothing is working.

GunpowderLullaby commented 1 year ago

I am also having the same problem now.

Nazanne commented 1 year ago

We replicated @yanavery's experience when we created a new guest account. It seemed to work but our devices never showed up in Home and when we restarted Homebridge we were back to throwing 403 errors.

icesparta commented 1 year ago

I was able to get my login to work but it stops on loading accessories, and then just resets back to login page.

Z1mDMan commented 1 year ago

I noticed that as well. when it was able to log me in, it stuck on loading accessories.

On Tue, Dec 20, 2022 at 4:12 PM icesparta @.***> wrote:

I was able to get my login to work but it stops on loading accessories, and then just resets back to login page.

— Reply to this email directly, view it on GitHub https://github.com/homebridge-eufy-security/plugin/issues/250#issuecomment-1360387081, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5WH6L2XS2G2QRTVXSSIHLWOIVK7ANCNFSM6AAAAAATDM4WEI . You are receiving this because you commented.Message ID: @.***>

CGDaveMac commented 1 year ago

Anything to do with this? https://community.security.eufy.com/t/to-our-eufy-security-customers-and-partners/3568215 "Today, users can still log in to our 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 Web portal."

icesparta commented 1 year ago

That would be my guess. I wonder if there is going to be a work around for that. I loved having my doorbell exposed to HomeKit.

snapst3r commented 1 year ago

Add another same user experience here. Thanks to all who have pinned this down on the Eufy sharing change. Crossing fingers there's a solve.

jp-lno commented 1 year ago

Ok so to give more feedback about the issue. Creating a new account allow to connect using eufy plugin. But if homebridge is restarted

ERROR Not connected can’t continue. back at start

Devices can be detected. But there is no way to control them. And my use case is only alarm mode and siren trigger. I don’t use camera streaming through this plugin.

DolmensDude commented 1 year ago

Confirm same issue here.

4 floodlight pros, 2 doorbells, 6 internal motion sensors, all unable to be seen in homekit.

Before I bought the floodlight pros, surfy wrote me HomeKit support was coming. Well it came, but via this great plugin, NOT anything from eufy themselves.

understand the broader issue they’ve messed up and now this as a result but it destroys their platform in my house.

thieren commented 1 year ago

Hi @ all

Now the login is gone for me too. I think eufy updated their servers one after another and crashed the login for us.

There is already an issue in eufy-security-client and my hope is that bropat will find a fix soon: https://github.com/bropat/eufy-security-client/issues/283

nackerr commented 1 year ago

Same issue here. Was working fine, then I erased and re-setup in a VM and now I can't login. If the login succeeds, then it can't fetch devices and will just take me back to login.

DolmensDude commented 1 year ago

This seems to have hit all platforms that login via eufy security client, homebridge, homey, more.

Let’s hope they find a fix. Pretty brutal this…

MartinJRS commented 1 year ago

Oh, how I start to hate Eufy even more than I usually do already.

Experiencing a total disfunction as well: [12/21/2022, 12:38:07 PM] [EufySecurity-2.2.0-beta.14] ERROR: Not connected can't continue!

CGDaveMac commented 1 year ago

Ironic, because I believe the URLs we were using were generated randomly after login and then could be streamed to allow Homebridge access, which from a security point of view, I am fine with.

Z1mDMan commented 1 year ago

Hi @ all

Now the login is gone for me too. I think eufy updated their servers one after another and crashed the login for us.

There is already an issue in eufy-security-client and my hope is that bropat will find a fix soon: bropat/eufy-security-client#283

looking forward to it

outrageouskiwi commented 1 year ago

Looks like the issue was closed, but the problem is still persisting. (Same behavior here: Cannot log in; If I create a new guest account it will login, but fail at finding devices; after a HomeBridge restart it says it can't find any devices. Subsequent login attempts from the plugin fail with every Eufy account. Looking forward to a fix!

Z1mDMan commented 1 year ago

I think the eufy-security-client code needs to be updated first and then the plugin here can be updated with the fix.

DolmensDude commented 1 year ago

still open here.

seems like this will absolutely require a code fix, for logons, getting the list of devices, and ultimately the encrypted URLs, maybe even thumbnails although I doubt that last one as the web portal from Eufy themselves has no thumbnails for previews, they're just grey.

the Homey eufy security app for that platform has been getting hot fix updates this afternoon, so it can log in, get the list of devices, and integrate as far as the Homey platform goes, but as that hardware has nowhere near enough horsepower to do an ffmpeg, using as a HKSV cam is simply out of the question. Using that kit, I have no cams or doorbells integrated, but my motion sensors for automated lighting inside the house are up and running using that and an hour of automation setting...

these is some hope I guess!

Not a great day, and especially not for the folks who put together these plugins - it looks like a lot of work, as eufy is changing a lot on the fly...

cracyfloyd commented 1 year ago

Looks like the issue was closed, but the problem is still persisting. (Same behavior here: Cannot log in; If I create a new guest account it will login, but fail at finding devices; after a HomeBridge restart it says it can't find any devices. Subsequent login attempts from the plugin fail with every Eufy account. Looking forward to a fix!

For me the same. All works before.

thieren commented 1 year ago

Hi folks,

so I've just published 2.2.0-beta.15 which in theory has a fix for the login. Unfortunately this version installs not correctly on my server due to some errors. I don't know if I'll get around to debugging this because of the holidays (kudos to eufy who had the balls to make such changes to their login the week before christmas).

So to any fellow programmers who like to help out - maybe one of you has experience with this:

Here is what I found:

Unfortunately the beta.15 is therefore broken for now. Maybe someone has a hint. I'll try to get back to it as soon as I can.

icesparta commented 1 year ago

I was able to get beta 15 installed it failed the first time but I tried it again and it worked, I was able to see devices and got it all set up of course then I lost the internet and my doorbell cam isn’t working at all because the temp out side is -40 hopefully it will work when it warms back up

outrageouskiwi commented 1 year ago

Wow, thank you for the fast work! Can anyone give tips on how to run npm install? I'm a newb on a mac and I'm SSH'd into my HomeBridge box but am not sure where to run the install from. The plugin installation failed as expected, (didn't work subsequent tries) but I'm not sure about where to go from there. TIA!

On Thu, Dec 22, 2022 at 4:08 AM thieren @.***> wrote:

Hi folks,

so I've just published 2.2.0-beta.15 which in theory has a fix for the login. Unfortunately this version installs not correctly on my server due to some errors. I don't know if I'll get around to debugging this because of the holidays (kudos to eufy who had the balls to make such changes to their login the week before christmas).

So to any fellow programmers who like to help out - maybe one of you has experience with this:

  • I've added a submodule of the eufy-security-client to the beta branch to include the necessary changes directly
  • the build command was changed so that this submodule is compiled correctly
  • all together is then published to npm

Here is what I found:

-

first there was some obscure error, that a 'dev' setting could not set by npm - I got around this by updating npm to the latest 9.2.0 - don't know what that was about

now when installing npm complains that the package.json of the submodule is not found - even though it is there if you open the directory afterwards

This prevents the package from installing correctly. You can use it nevertheless if you run npm install in the plugin install path - but for now I don't know why it won't work at first install. At least after that the login seems to work again.

Unfortunately the beta.15 is therefore broken for now. Maybe someone has a hint. I'll try to get back to it as soon as I can.

— Reply to this email directly, view it on GitHub https://github.com/homebridge-eufy-security/plugin/issues/250#issuecomment-1362764407, or unsubscribe https://github.com/notifications/unsubscribe-auth/A44TEKMSWHQQDJVF3KQRHGDWORAEZANCNFSM6AAAAAATDM4WEI . You are receiving this because you commented.

outrageouskiwi commented 1 year ago

Never mind, I got it—second installation worked a charm. Thank you! On Dec 22, 2022 at 8:40 AM -0800, icesparta @.***>, wrote:

I was able to get beta 15 installed it failed the first time but I tried it again and it worked, I was able to see devices and got it all set up of course then I lost the internet and my doorbell cam isn’t working at all because the temp out side is -40 hopefully it will work when it warms back up — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

CGDaveMac commented 1 year ago

Works for me too. Had to install twice due to npm dev error, and then login/restart homebridge twice because the first time one camera didn't show up.

nackerr commented 1 year ago

Is anyone else getting the same errors again? Seeing this after every restart of HomeBridge again.

[12/22/2022, 1:28:34 PM] [EufySecurity-2.2.0-beta.15] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/22/2022, 1:28:34 PM] [EufySecurity-2.2.0-beta.15] ERROR: Not connected can't continue!

Electr1fying commented 1 year ago

Is anyone else getting the same errors again? Seeing this after every restart of HomeBridge again.

[12/22/2022, 1:28:34 PM] [EufySecurity-2.2.0-beta.15] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/22/2022, 1:28:34 PM] [EufySecurity-2.2.0-beta.15] ERROR: Not connected can't continue!

It worked a few hours for me as well (installing EufyCam 3's and Homebase 3 atm, so i'm actively monitoring Homebridge), and it stopped working for me with the same error as you since like 5 minutes.

timmy8784 commented 1 year ago

Is this the install error everyone is talking about? Getting this when trying to install beta .16

Is there a way around?

CMD: pm install --save homebridge-eufy-security@2.2.0-beta.16 apm ERR! code ENOTEMPTY pm ERR! syscall rename apm ERR! path /var/lib/homebridge/node m odules/homebridge-eufy-security npm ERR! dest /var/lib/homebridge/node_m odules/.homebridge-eufy-security-bkoCzz0 I apm ERR!| errno -39 nom ERR! ENOTEMPTY: directory not empty, rename /var/lib/homebridge/node_module s/homebridge-eufy-security' -> '/var/lib /homebridge/node modules/.homebridge-euf y-security-bkoCzz0I ppm ERR! A complete log of this run can be found in: mpm ERR! /home/pi/.npm/_logs/2022-12 -22T20_02_28_285Z-debug-0.log Operation failed. Please review log for details. CLOSE полтооттоуу

Gemuir commented 1 year ago

Great work! Installation failed first time but worked second time around.

timmy8784 commented 1 year ago

Great work! Installation failed first time but worked second time around.

What error did you receive the first time? I am getting the error above and can't figure out what is happening. Do you know what node version or npm you are running?

I'm on npm 8.19.2 node.js 18.12.1

timmy8784 commented 1 year ago

I think I'm having the same issue. I'm on node 18.12.1> Wow, thank you for the fast work! Can anyone give tips on how to run npm

install? I'm a newb on a mac and I'm SSH'd into my HomeBridge box but am not sure where to run the install from. The plugin installation failed as expected, (didn't work subsequent tries) but I'm not sure about where to go from there. TIA!

On Thu, Dec 22, 2022 at 4:08 AM thieren @.***> wrote:

Hi folks,

so I've just published 2.2.0-beta.15 which in theory has a fix for the login. Unfortunately this version installs not correctly on my server due to some errors. I don't know if I'll get around to debugging this because of the holidays (kudos to eufy who had the balls to make such changes to their login the week before christmas).

So to any fellow programmers who like to help out - maybe one of you has experience with this:

  • I've added a submodule of the eufy-security-client to the beta branch to include the necessary changes directly
  • the build command was changed so that this submodule is compiled correctly
  • all together is then published to npm

Here is what I found:

-

first there was some obscure error, that a 'dev' setting could not set by npm - I got around this by updating npm to the latest 9.2.0 - don't know what that was about

now when installing npm complains that the package.json of the submodule is not found - even though it is there if you open the directory afterwards

This prevents the package from installing correctly. You can use it nevertheless if you run npm install in the plugin install path - but for now I don't know why it won't work at first install. At least after that the login seems to work again.

Unfortunately the beta.15 is therefore broken for now. Maybe someone has a hint. I'll try to get back to it as soon as I can.

— Reply to this email directly, view it on GitHub https://github.com/homebridge-eufy-security/plugin/issues/250#issuecomment-1362764407, or unsubscribe https://github.com/notifications/unsubscribe-auth/A44TEKMSWHQQDJVF3KQRHGDWORAEZANCNFSM6AAAAAATDM4WEI . You are receiving this because you commented.