[Bug]: Unable to login

Client version

2.2.2

Node version

v16.18.0

Operating System type

Docker

Operating system version

Raspberry OS

Describe the bug

It seems the login isn’t working anymore. When using https://mysecurity.eufylife.com/apieu/v2/passport/login I do see a proper response with a data field. When logging into the eufy app with the configured user, everything works OK in the app, just not this client apparently? The app does not appear to have any changed login endpoints, although I did spot new paths: passport/update_agreement_records, passport/query_agreement_msg and passport/query_agreement_records. I am getting this stack trace and then that’s it:

2022-11-09 17:32:34.406  DEBUG [EufySecurity._initializeInternals] No stored data from last exit found 
2022-11-09 17:32:34.413  DEBUG [EufySecurity._initializeInternals] Handling of driver update 
{
  currentVersion: 2.22,
  previousVersion: 0
}
2022-11-09 17:32:34.992  DEBUG [undefined.constructor] Loaded API_BASE: https://security-app-eu.eufylife.com 
2022-11-09 17:32:34.999  DEBUG [EufySecurity._initializeInternals] Load previous login_hash: <redacted> 
2022-11-09 17:32:35.003  DEBUG [EufySecurity._initializeInternals] Generated new openudid: 962f147b4eb1406d 
2022-11-09 17:32:35.005  DEBUG [EufySecurity._initializeInternals] Generated new serial_number: 634a5dba74dd 
2022-11-09 17:32:35.080  DEBUG [src/lib/server.ts:489  EufySecurityServer.start] Starting server on host 0.0.0.0, port 3000 
2022-11-09 17:32:35.087  INFO  [src/lib/server.ts:495  EufySecurityServer.start] Eufy Security server listening on host 0.0.0.0, port 3000 
2022-11-09 17:32:35.091  DEBUG [HTTPApi.login] Login and get an access token 
{
  token: null,
  tokenExpiration: null
}
2022-11-09 17:32:35.098  DEBUG [HTTPApi.request] Request: 
{
  method: 'post',
  endpoint: 'v2/passport/login_sec',
  token: null,
  data: {
    ab: '<redacted>',
    client_secret_info: {
      public_key: '04bc749631da017d514f498652a849a7df4f7ade1731282479ba92b5d0856c6861c1e95c29df98eeef8a593e298edc0686e52747d948d31b29d5bae0a49719f391'
    },
    enc: 0,
    email: '<redacted>',
    password: '[***]',
    time_zone: 0,
    transaction: '1668015155096'
  }
}
2022-11-09 17:32:35.195  DEBUG [HTTPApi.request] Response: 
{
  response: {
    code: 0,
    msg: 'Succeed.'
  }
}
2022-11-09 17:32:35.204  ERROR [HTTPApi.login] Generic Error: 
 TypeError  Cannot read properties of undefined (reading 'user_id')
error stack:
• api.ts:289 login
    node_modules/eufy-security-client/src/http/api.ts:289:66

• task_queues:96 processTicksAndRejections
    node:internal/process/task_queues:96:5

• eufysecurity.ts:662 connect
    node_modules/eufy-security-client/src/eufysecurity.ts:662:9

• server.ts:496 start
    src/lib/server.ts:496:9

• server.ts:66 <anonymous>
    src/bin/server.ts:66:9

Same issue as: https://github.com/bropat/eufy-security-ws/issues/146

To reproduce

Start the client.

Screenshots & Logfiles

No response

Additional context

No response

[fuatakgun]

i am working on this

[bropat]

In the next version, if you do not set the parameter trustedDeviceName, a random model of an existing Android phone will simply be set and kept at the first login. This way, not so many people should use “eufyclient” (default value). If someone subsequently sets the above-mentioned parameter anyway, then this will of course take precedence.

Attention: If someone uses the 2FA and changes this parameter after a successful authentication, they will be asked to check again (new trust).