eufy-security-client: [Bug]: Unable to login

i am working on this

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).

The main and only concern here is that eufy started to intervene with this client. This measure is easily circumvented, but what’s next? How long until the next countermeasure, and most importantly, when will one be of a kind we cannot circumvent?

I know what I’d do… sell all of my eufy products and get cameras with proper API’s!

That’s because I’ve been tinkering all evening trying to figure this sh*t out xD

Well no actually. I apparently tested locally with a different config.json. I found extra_hosts exists for Docker Compose so I tried that with the default config settings I used all the time. It failed.

I then changed the trustedDeviceName field to something other than the default, with default hosts and now I get a captcha request in Docker with the default eufy-security-ws image (1.0.2).

This is short term good news, long term bad news… It likely means that they’re now actively countering this client. 😦

Omitting data from the initial login response in specific scenarios is a deliberate action!

Thanks for all the clues… I have been using the bropat/eufy-security-ws for quite a while and it’s awesome. I wanted share what I had to do to fix the issue in case it helps someone else.

First, I don’t use docker. I start the service as follows from a systctl script using ts-node: e.g. ts-node /opt/eufy-security-ws/src/bin/server.ts --config config.json

Based on what I read above, I changed “trustedDeviceName?”: “eufyclient”, to “trustedDeviceName?”: “somerandomothername”, in the config.json file. This didn’t help… continued to get the user_id error.

To fix the issue,I had to edit line 65 in /opt/eufy-security-ws/node_modules/eufy-security-client/build/eufysecurity.js and recompile.

                        if (this.config.trustedDeviceName === undefined) {
                        this.config.trustedDeviceName = "somerandomothername";  //edited line

This seems to indicate that changing the variable trustedDeviceName in config.json doesn’t work for some reason.

Thanks again.

Brilliant, for others in the same situation, I just added an environment var in my docker-compose file

This isn’t possible with HASS addon is it?

Okay… something changed… I added the IP to the hosts file, ran it locally and it works!

EDIT: The above statement is incorrect. See below.

OK I found it, but it doesn’t contain a cloud token (it’s ""). It does contain a login hash.

@bropat yes. The webportal is working just fine. I have tried a custom Docker image calling this endpoint in the login function, but that also resulted in an absent data object.

EDIT: regarding user_id, the response above it does not contain the data object (see also the log above): https://github.com/bropat/eufy-security-client/blob/master/src/http/api.ts#L289

  response: {
    code: 0,
    msg: 'Succeed.'
  }

The response is marked as OK, but data is missing which is used on L289 in api.ts.

@Palmke

I have just carried out a test and it works perfectly. I think Eufy may have bungled some servers again.

{
   "code":0,
   "msg":"Succeed.",
   "data":{
      "user_id":"redacted",
      "email":"redacted",
      "nick_name":"pat***",
      "auth_token":"redacted",
      "token_expires_at":1670615045,
      "avatar":"",
      "invitation_code":"redacted",
      "inviter_code":"",
      "verify_code_url":"",
      "mac_addr":"",
      "domain":"security-app-eu.eufylife.com",
      "ab_code":"IT",
      "geo_key":"redacted",
      "privilege":0,
      "phone":"",
      "phone_code":"",
      "server_secret_info":{
         "public_key":"0470ca96234263082120ab0646918187a9df3f0b70f1429e349b5d8a7bcde7cc4f5dd00fadbe1fd225ed0576fce145c785c8ed6b667485619bbcf57b2e5faa8405"
      },
      "params":[
         {
            "param_type":10002,
            "param_value":"off"
         }
      ],
      "trust_list":[
         
      ]
   }
}