-
Notifications
You must be signed in to change notification settings - Fork 82
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
Failed to Setup - Missing 2 Factor Auth or Captcha Codes #795
Comments
It's not just you @bigbean2006, I've got the exact same error. |
same here! I am getting the 2 factor authentication code in my email but I am not asked for it from the HA to enter it (as it used to prior the recent update) |
I'm not getting an authentication code sent to me. For me, it just stopped working a few days ago. I saw there was an update to the add-on so I installed that hoping it would fix it, but it didn't. I don't know what error was being logged with the previous version, only that I get this error now. |
same here! Logger: homeassistant.config_entries Error setting up entry 127.0.0.1 for eufy_security |
Same here :( |
same here :( |
same here, i installed the eufy-security-ws app (via docker) and it triggered a 2FA from Eufy. I then installed the integration and it is sitting and spinning on the "Setup" screen after i enter in the IP of the eufy-security-ws instance |
Just installed 1.5.0 and still get the same error in the logs: This error originated from a custom integration. Logger: homeassistant.config_entries Error setting up entry Eufy Security for eufy_security |
Same issue as everyone else 2FA is not working. |
Same for me on 1.5.1. New install. |
I do have the same issue but already on initial installation, I see the following in the log of the eufy-security-ws: 2023-05-16 06:39:39.458 INFO [HTTPApi.sendVerifyCode] Requested verification code for 2FA I get an email with the code, however I do not know where to enter this code, I guess usually there should be one on the eufy integration, but actually this is only initialising and at some point it fails - HA logs show the following: Logger: homeassistant.config_entries Error setting up entry 127.0.0.1 for eufy_security cheers Mike |
Captcha and 2fa verification are not working as of now. I am trying to find a solution |
@fuatakgun 1.3.5 is still working. |
1.3.5 of add-on version, right :-) |
@fuatakgun I offcourse would love it if you can solve this problem! In maintime I would be very happy if I could somehow bypass the captcha manually. I find the base64 img in the addon logs, so is there a way to manually talk to the addon api to send the captcha code? I see a service call to send a message to the add-on, but I still can't manage to talk to the API with this particular call. May this be easy for you to explain maybe? I would also help a lot of people :) |
Problem is, integration is not receiving the event (captcha) so it is not known to home assistant about the image. You can put base 64 into a website and generate the image and use send message. |
Fully understood. Can you then just share the message format for the call? Can't figure it out. |
Any chance we have an ETA? |
I am getting this: 2023-05-19 07:14:55.135 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 127.0.0.1 for eufy_security |
Receiving the same error. Tried removing everything and then reinstalling with no change. Error setting up entry 127.0.0.1 for eufy_security |
I found a workaround. I use the last HA version 2023.5.4 installed in docker, which means I do not have Addons in my HA. So what I did:
|
I can also confirm that if the eufy-security-ws add-on gets downgraded to 1.3.5 both captcha and 2FA are still working.
|
@chrisf4lc0n The addons folder if you access HA through the Terminal Plugin? I tried but it didn't show up in the add-on section to then install? |
@tilleyjoe |
For Docker installation please follow widapro's guide. |
Thank you @chrisf4lc0n |
I'm getting exactly the same when using 1.3.5. |
This issue is not about schema incompatible, no need to overload here |
I got the schema_incompatible error as well after downgrading eufy-security-ws to 1.3.5 as recommended. To fix it I had to downgrade the eufy_security integration as well, I'm using 6.2.0 currently and used the MFA code emailed to me as the captcha key (see #707 (comment)) |
Is there any progress? I´m also stuck in the process of initialisation. |
Sadly not, i am also waiting for a solution from add-on |
I seem to be getting this issue even without 2FA on. Is it something to do with captcha? |
This solution was helpful to me. |
Sorry to be a pain but any chance you could point me in the right direction of how to wget the 1.3.5 version? Having trouble finding good instructions on google |
same here... |
As far as I know, I had to restore the backup to downgrade eufy-security-ws to version 1.3.5. In my case, I'm running HA on ubuntu 22.04, so I checked where my addons are running. |
Thanks! I’ll give this a go |
any news ? |
There is a newer version of add-on (1.6.0), please download it and test captcha/2fa specific issues. |
I can confirm with the latest versions of everything :D I was able to add my eufy devices to home assistant :) |
@bewA , did you go through captcha or 2fa? |
@fuatakgun yes, this was my first time trying to use it and I could never get past the 2fa as there was nowhere to enter the code, now there was and so i was able to fully authenticate and the devices were added :) |
Thanks for sharing, time to resolve this :-) |
For anyone else reading i'm using the latest version of this HACS integration and also the docker containers by bropat and yourself, not sure if one is unnecessary but it's all running and working as expected :) |
I'm still having a problem where I don't have any place to input the MFA code. I start the eufy-security-ws container (latest as of this post), I get the email with the code, I add the Eufy Security add-on through HACS, restart HA, add the integration, input the IP and port of the eufy-security-ws container, it connects but then says "Initialization Failed". I go into the integration and click "Configure" but there is no field for the MFA code. Where am I supposed to enter the code? |
@fuatakgun I've been following this thread for a while now, because of failing logins due to captcha. So I was happy to try the new updates. The add-on from bropat seems to be working fine now, logging in at Eufy and all, as far as I can tell from logging. The Eufy Security integration though fails with a 'Config-flow could not be loaded: {"message":"Invalid handler specified"}' in the HASS GUI. This happens both when I manually git clone the integration to custom_components as through a HACS setup. In the latter case, home-assistant.log tells below about it.
Please advise. |
You are using an old version of home assistant, you don't have an IMAGE entity in your home assistant version, which should be introduced a couple of months ago. |
This comment will probably only be useful for a small percentage of the folks with this issue. But I came here because I was prompted for captcha over and over. Then I figured out that my password had been too long for Eufy and my password manager didn't catch the fact that the password had been truncated during sign up. So, here is a heads up to double check your password if you have this issue. |
What's the password length? I though it was 20 char which is what I set mine to but still having the problem. I'm running https://github.com/bropat/eufy-security-ws in Docker Container on HA Core. This is the message I'm getting for Eufy-Security via Portainer: SECURITY WARNING: Reverting CVE-2023-46809: Marvin attack on PKCS#1 padding 2024-10-09 12:47:06.062 INFO eufy-security-ws Eufy Security server listening on host 0.0.0.0, port 3000 2024-10-09 12:47:07.437 INFO eufy-security-ws:eufy-security-client [http] [HTTPApi.login] Please send requested captcha to proceed with authentication 2024-10-09 12:49:22.764 INFO eufy-security-ws Client disconnected with ip: xxx.xxx.x.x port: 55111 code: 1000 reason: Normal Closure Has anyone managed to resolve this? |
I also have the problem. I do not know where to enter the verification code. |
I found it you go to the Eufy Security integration (it should be showing an error) there is a prompt that comes up - in my case it presented the CAPTCHA and let me enter a response. Perhaps in your case it will let you enter the 2FAOn 19 Oct 2024, at 23:51, JENDRIK ***@***.***> wrote:
I also have the problem.
2024-10-19 02:39:41.735 INFO eufy-security-ws Server closed
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
SECURITY WARNING: Reverting CVE-2023-46809: Marvin attack on PKCS#1 padding
2024-10-19 04:26:27.166 INFO eufy-security-ws Eufy Security server listening on host 0.0.0.0, port 3000
2024-10-19 04:26:27.406 INFO eufy-security-ws:eufy-security-client [http] [HTTPApi.sendVerifyCode] Requested verification code for 2FA
2024-10-19 04:26:27.407 INFO eufy-security-ws:eufy-security-client [http] [HTTPApi.login] Please send required verification code to proceed with authentication
I do not know where to enter the verification code.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Keep getting failed to setup error not sure where I went wrong but I have installed per documentation. But keeps outputting name error.
This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/eufy_security/eufy_security_api/product.py:40
Integration: Eufy Security (documentation, issues)
First occurred: 1:02:49 AM (1 occurrences)
Last logged: 1:02:49 AM
Error setting up entry 127.0.0.1 for eufy_security
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/eufy_security/init.py", line 50, in async_setup_entry
await coordinator.initialize()
File "/config/custom_components/eufy_security/coordinator.py", line 39, in initialize
await self._api.connect()
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 73, in connect
await self._set_products()
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 104, in _set_products
self._devices = await self._get_products(ProductType.device, result[MessageField.STATE.value]["devices"])
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 124, in _get_products
product = Device(self, serial_no, properties, metadata, commands)
File "/config/custom_components/eufy_security/eufy_security_api/product.py", line 130, in init
super().init(api, ProductType.device, serial_no, properties, metadata, commands)
File "/config/custom_components/eufy_security/eufy_security_api/product.py", line 33, in init
self._set_properties(properties)
File "/config/custom_components/eufy_security/eufy_security_api/product.py", line 40, in _set_properties
self.name = properties[MessageField.NAME.value]
KeyError: 'name'
The text was updated successfully, but these errors were encountered: