-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
Bump - Same here, looking but have not found an answer just yet |
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: {"command":"connect","verifyCode":"123456"} Hope that helps |
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:
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:
|
I am having the same issue, I tried several things but cannot get it to work. I'm new to nodered so maybe its a simple question. |
The easiest solution is to deactivate your node and wait a few days. (For me this was a week before I could continue) If you then reactivate your node it will work again without Captcha. |
In your response, do you receive payload property msg.payload.event equal to "captcha request"? If so, you should also have in the msg payload (along with the image that you are viewing) the captcha ID. These are the two variables you need to send back via the API's connect command (outlined in my previous post) |
Thanks for your fast response. Mm somehow its working again now, not sure if it was this inject block with the payload (changed into my id and the captcha code) you described earlier or that its is a new day. Anyway thanks |
As the other post mentioned, after a day or so the captcha request goes away--I'm not sure of Eufy's logic on this, I presume to stop automated systems from trying to penetrate the login. Anyway, you are correct, use an inject module with the following: I just edit the inject module with the new captcha id and answer (code). I will probably use the dashboard in node-red to create a form for displaying the captcha image and an input for the human response. I am still evaluating whether or not its worth integrating Eufy's security model into my project. |
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?
The text was updated successfully, but these errors were encountered: