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.

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

Client cannot connect: awaiting captcha #24

Open
DIY3D opened this issue Dec 4, 2023 · 4 comments
Open

Client cannot connect: awaiting captcha #24

DIY3D opened this issue Dec 4, 2023 · 4 comments

Comments

@DIY3D
Copy link

DIY3D commented Dec 4, 2023

Hi,

In my test flow the eufyclient tries to make a connection but asks to enter a code and after a few attempts I get the message: awaiting captcha.

Where can I enter a code or accept a captcha?
Do I need to install other software on Homebase?

@jova1971
Copy link

Bump - Same here, looking but have not found an answer just yet

@JapioVos
Copy link

Hello, I have the same problem. I was connected for a few days and everything works fine. However, now captcha verification is requested. Is there a way to verify the Captcha?

Question 2, Is it possible to connect using two factor authentication TWA. How do you return the TWA code?

Thanks in advance for a response

@Freeman015
Copy link

Hello, I have the same problem. I was connected for a few days and everything works fine. However, now captcha verification is requested. Is there a way to verify the Captcha?

Question 2, Is it possible to connect using two factor authentication TWA. How do you return the TWA code?

Thanks in advance for a response

To answer question 2 for you:
You can add the 2FA code to your connect:

{"command":"connect","verifyCode":"123456"}

Hope that helps

@stratacorps
Copy link

Although I am now working on my own fork to add additional functionality, here is what I have found. This goes for both the TFA two-factor-authorization request and the captcha. The answer above is partially correct, but it did not work for me. This is what I have found that works.

(Note: I have an image viewer and am using the node-red dashboard in node-red v4.0 to display the captcha image and captcha id. I am new to node-red so my plan is to build a page that has a text input for the human resolved answer to the image captcha and submit that back through with the necessary connect loginOptions payload that is needed to complete the process. For now I am just viewing the base64 image in the node-red workspace to view the image)

Anyway, the command "connect" is correct, but the verifyCode or the Captcha variables are objects, like below:

For TFA, send the command "connect" along with the verifyCode inside the loginOptions object as:

{ "command": "connect", "loginOptions": { "verifyCode": "123456" } }

For captcha, Bropat's eufy-security-client is looking for the captchID and the answer as part of the login options object, so your payload sent through this wrapper needs to look like this:

{ "command": "connect", "loginOptions": { "captcha": { "captchaId": "6d7b33ca-1661-4e82-9e94-14d52476b98e", "captchaCode": "naM7" } } }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants