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

Failed to Setup - Missing 2 Factor Auth or Captcha Codes #795

Closed
bigbean2006 opened this issue May 8, 2023 · 55 comments
Closed

Failed to Setup - Missing 2 Factor Auth or Captcha Codes #795

bigbean2006 opened this issue May 8, 2023 · 55 comments

Comments

@bigbean2006
Copy link

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'

@lakofka
Copy link

lakofka commented May 9, 2023

It's not just you @bigbean2006, I've got the exact same error.

@mohammad-shadmehr
Copy link

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)

@lakofka
Copy link

lakofka commented May 10, 2023

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.

@raphael2711
Copy link

raphael2711 commented May 10, 2023

same here!
i installed the new S100 Wall Light camera , can this be the reason.

Logger: homeassistant.config_entries
Source: custom_components/eufy_security/eufy_security_api/product.py:40
Integration: Eufy Security (documentation, issues)
First occurred: 11:42:39 (3 occurrences)
Last logged: 14:58:34

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'

@pldmgg
Copy link

pldmgg commented May 10, 2023

Same here :(

@ajaymdesai
Copy link

same here :(

@treyd
Copy link

treyd commented May 11, 2023

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

@lakofka
Copy link

lakofka commented May 12, 2023

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
Source: custom_components/eufy_security/eufy_security_api/product.py:40
Integration: Eufy Security (documentation, issues)
First occurred: 20:09:55 (2 occurrences)
Last logged: 20:10:19

Error setting up entry Eufy Security 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'

@sircoynie
Copy link

Same issue as everyone else 2FA is not working.

@ravarelab
Copy link

Same for me on 1.5.1. New install.

@michaelmramor
Copy link

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
2023-05-16 06:40:37.333 DEBUG [ClientsController.addSocket] New client with ip: 127.0.0.1 port: 44004

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
Source: custom_components/eufy_security/eufy_security_api/api_client.py:345
Integration: Eufy Security (documentation, issues)
First occurred: 08:58:28 (1 occurrences)
Last logged: 08:58:28

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 383, 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 100, in _set_products
result = await self._start_listening()
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 145, in _start_listening
return await self._send_message_get_response(OutgoingMessage(OutgoingMessageType.start_listening))
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 345, in _send_message_get_response
return await future
asyncio.exceptions.CancelledError

cheers Mike

@fuatakgun
Copy link
Owner

Captcha and 2fa verification are not working as of now.

I am trying to find a solution

@raphael2711
Copy link

@fuatakgun 1.3.5 is still working.

@fuatakgun
Copy link
Owner

1.3.5 of add-on version, right :-)

@0R2YPsALXTVed6y
Copy link

@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 :)

@fuatakgun
Copy link
Owner

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.

@0R2YPsALXTVed6y
Copy link

Fully understood. Can you then just share the message format for the call? Can't figure it out.

@T-Fyre
Copy link

T-Fyre commented May 18, 2023

Any chance we have an ETA?

@tilleyjoe
Copy link

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
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'

@shindawg
Copy link

Receiving the same error. Tried removing everything and then reinstalling with no change.

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'

@widapro
Copy link

widapro commented May 24, 2023

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:

  1. I installed eufy-security-ws version 1.3.5 using docker-compose

version: '3'
services:
eufy-security-ws:
container_name: eufy-security-ws
image: bropat/eufy-security-ws:1.3.5
volumes:
- /data/eufy-security-ws:/data
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
network_mode: host
environment:
- USERNAME=myEufyEmail@demo.com
- PASSWORD=SecRetPasSwoRd
- TRUSTED_DEVICE_NAME=iPhone 13 mini
- PORT=3000
- DEBUG=true

  1. I installed fuatakgun/eufy_security version master in HA using HACS
  2. I added eufy Security integration in HA.
  3. I pressed reconfigure button for eufy Security and I was able to see the captcha and MFA requests in HA.
  4. After that I checked that all my cameras were created in HA and I was able to see RTSP stream from cameras in HA.
  5. Then I re-created eufy-security-ws docker container with the latest version 1.5.2

docker compose -f /home/pi/eufy-security-ws.yaml up -d --force-recreate

  1. Then I reload eufy_security integration in HA and everything continues work without any issues (no captcha, no MFA requests)

@chrisf4lc0n
Copy link

1.3.5 of add-on version, right :-)

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.
@widapro workaround will work for the docker installation, for the bare metal or VirtualBox installation there is also a workaround:

  1. Install SSH Terminal in the Add-on section.
  2. Use SSH Terminal to wget the 1.3.5 zip version from GitHub to the addon folder.
  3. Unzip it with unzip command and delete the zipped file.
  4. Uninstall 1.5.2 version.
  5. Reload add-on section and go to the top to see local add-ons and install the eufy-security-ws 1.3.5 version instead.
  6. Configure as normal.

@tilleyjoe
Copy link

@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?

@chrisf4lc0n
Copy link

chrisf4lc0n commented May 30, 2023

@tilleyjoe
Screenshot from 2023-05-30 08-24-40
Just to confirm you are using the Home Assistant OS or it is running in the virtual machine?
Also HACS has been installed and you have unzipped the downloaded addon to addon/eufy-security-ws folder and restarted the HA?

@tilleyjoe
Copy link

I am using HA OS, running on a VM on a QNAP NAS. Terminal is showing this, unzipped and in addons:
image

HACS is installed and restarted but it's not showing up:

image

@JimboJamez
Copy link

JimboJamez commented May 30, 2023

I'm having the same issue. I'm running HA in docker on Synology and the eufy-security-ws-1.3.5 folder is available in the addons directory:

image

HACS is installed, but I can't see the option to install it through Add-Ons:

image

@chrisf4lc0n
Copy link

For Docker installation please follow widapro's guide.

@JimboJamez
Copy link

2. eufy_security

Thank you @chrisf4lc0n

@chrisf4lc0n
Copy link

I am using HA OS, running on a VM on a QNAP NAS. Terminal is showing this, unzipped and in addons:
image

HACS is installed and restarted but it's not showing up:

image

Have you tried to clear the browser's cache?

@Gitdad
Copy link

Gitdad commented Jun 20, 2023

I'm also getting schema_incompatible when using 1.3.5 version.

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
2023-06-20 09:43:48.169 INFO Authentication properties changed, invalidate saved cloud token.
2023-06-20 09:43:48.555 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2023-06-20 09:43:49.589 ERROR Message error
Error
details:
{
schemaId: 17,
errorCode: 'schema_incompatible'
}
error stack:
• server.ts:91 receiveMessage
usr/src/app/node_modules/eufy-security-ws/src/lib/server.ts:91:27
• server.ts:68
usr/src/app/node_modules/eufy-security-ws/src/lib/server.ts:68:53
• node:events:513 emit
node:events:513:28
• websocket.js:1184 receiverOnMessage
usr/src/app/node_modules/ws/lib/websocket.js:1184:20
• node:events:513 emit
node:events:513:28
• receiver.js:541 dataMessage
usr/src/app/node_modules/ws/lib/receiver.js:541:14
• receiver.js:459 getData
usr/src/app/node_modules/ws/lib/receiver.js:459:17
• receiver.js:158 startLoop
usr/src/app/node_modules/ws/lib/receiver.js:158:22
• receiver.js:84 _write
usr/src/app/node_modules/ws/lib/receiver.js:84:10
• writable:392 writeOrBuffer
node:internal/streams/writable:392:12

@fuatakgun fuatakgun pinned this issue Jun 21, 2023
@asifhu03
Copy link

I'm also getting schema_incompatible when using 1.3.5 version.

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 2023-06-20 09:43:48.169 INFO Authentication properties changed, invalidate saved cloud token. 2023-06-20 09:43:48.555 INFO Eufy Security server listening on host 0.0.0.0, port 3000 2023-06-20 09:43:49.589 ERROR Message error Error details: { schemaId: 17, errorCode: 'schema_incompatible' } error stack: • server.ts:91 receiveMessage usr/src/app/node_modules/eufy-security-ws/src/lib/server.ts:91:27 • server.ts:68 usr/src/app/node_modules/eufy-security-ws/src/lib/server.ts:68:53 • node:events:513 emit node:events:513:28 • websocket.js:1184 receiverOnMessage usr/src/app/node_modules/ws/lib/websocket.js:1184:20 • node:events:513 emit node:events:513:28 • receiver.js:541 dataMessage usr/src/app/node_modules/ws/lib/receiver.js:541:14 • receiver.js:459 getData usr/src/app/node_modules/ws/lib/receiver.js:459:17 • receiver.js:158 startLoop usr/src/app/node_modules/ws/lib/receiver.js:158:22 • receiver.js:84 _write usr/src/app/node_modules/ws/lib/receiver.js:84:10 • writable:392 writeOrBuffer node:internal/streams/writable:392:12

I'm getting exactly the same when using 1.3.5.

@fuatakgun
Copy link
Owner

This issue is not about schema incompatible, no need to overload here

@oldsj
Copy link

oldsj commented Jul 9, 2023

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

@crohot
Copy link

crohot commented Jul 14, 2023

Is there any progress? I´m also stuck in the process of initialisation.

@fuatakgun
Copy link
Owner

Sadly not, i am also waiting for a solution from add-on

@yesterdayshero
Copy link

I seem to be getting this issue even without 2FA on. Is it something to do with captcha?

@guneezx
Copy link

guneezx commented Jul 28, 2023

  • Install SSH Terminal in the Add-on section.
  • Use SSH Terminal to wget the 1.3.5 zip version from GitHub to the addon folder.
  • Unzip it with unzip command and delete the zipped file.
  • Uninstall 1.5.2 version.
  • Reload add-on section and go to the top to see local add-ons and install the eufy-security-ws 1.3.5 version instead.
  • Configure as normal.

This solution was helpful to me.
I downgraded eufy-security-ws to 1.3.5 version and eufy security integration to 6.1.0.(6.3.1 not worked in my case)
Then I configured the integration and it worked well.
Finally, I upgraded eufy-security-ws to 1.5.2-1 and eufy security integration to 6.3.1 and those are still working.

This was referenced Jul 28, 2023
@iamthetrees
Copy link

  • Install SSH Terminal in the Add-on section.
  • Use SSH Terminal to wget the 1.3.5 zip version from GitHub to the addon folder.
  • Unzip it with unzip command and delete the zipped file.
  • Uninstall 1.5.2 version.
  • Reload add-on section and go to the top to see local add-ons and install the eufy-security-ws 1.3.5 version instead.
  • Configure as normal.

This solution was helpful to me. I downgraded eufy-security-ws to 1.3.5 version and eufy security integration to 6.1.0.(6.3.1 not worked in my case) Then I configured the integration and it worked well. Finally, I upgraded eufy-security-ws to 1.5.2-1 and eufy security integration to 6.3.1 and those are still working.

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

@daddyd0108
Copy link

same here...

@guneezx
Copy link

guneezx commented Jul 30, 2023

  • Install SSH Terminal in the Add-on section.
  • Use SSH Terminal to wget the 1.3.5 zip version from GitHub to the addon folder.
  • Unzip it with unzip command and delete the zipped file.
  • Uninstall 1.5.2 version.
  • Reload add-on section and go to the top to see local add-ons and install the eufy-security-ws 1.3.5 version instead.
  • Configure as normal.

This solution was helpful to me. I downgraded eufy-security-ws to 1.3.5 version and eufy security integration to 6.1.0.(6.3.1 not worked in my case) Then I configured the integration and it worked well. Finally, I upgraded eufy-security-ws to 1.5.2-1 and eufy security integration to 6.3.1 and those are still working.

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

As far as I know, I had to restore the backup to downgrade eufy-security-ws to version 1.3.5.
Unfortunately, I didn't have any backup of eufy-security-ws version 1.3.5.

In my case, I'm running HA on ubuntu 22.04, so I checked where my addons are running.
I connected ubuntu SSH terminal, then I found that my addons are in /usr/share/hassio/addons folder.
I also could find "git" and "data" folder in that path.
In the "git" folder, you can find git download of eufy-security-ws, but the names of the of each addon folders are shown in only hexa value.
I had to find the map between hexa value and addon.
I could find the the map by simply searching "data" folder because in that folder each folder name had both hexa value and the name of the addons.
In my case, the name started with "402F".
I removed all the contents in git/402FXXXX/ folder and wget 1.3.5 version, untared, and made it look like original one by matching the name of the subfolder.
After, reboot HA, I could find the upgrade to v1.3.5 button in the supervisor for the eufy-security-ws addon.
By clinking the upgrade button, I could downgrade eufy-security-ws to version 1.3.5.

@iamthetrees
Copy link

  • Install SSH Terminal in the Add-on section.
  • Use SSH Terminal to wget the 1.3.5 zip version from GitHub to the addon folder.
  • Unzip it with unzip command and delete the zipped file.
  • Uninstall 1.5.2 version.
  • Reload add-on section and go to the top to see local add-ons and install the eufy-security-ws 1.3.5 version instead.
  • Configure as normal.

This solution was helpful to me. I downgraded eufy-security-ws to 1.3.5 version and eufy security integration to 6.1.0.(6.3.1 not worked in my case) Then I configured the integration and it worked well. Finally, I upgraded eufy-security-ws to 1.5.2-1 and eufy security integration to 6.3.1 and those are still working.

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

As far as I know, I had to restore the backup to downgrade eufy-security-ws to version 1.3.5. Unfortunately, I didn't have any backup of eufy-security-ws version 1.3.5.

In my case, I'm running HA on ubuntu 22.04, so I checked where my addons are running. I connected ubuntu SSH terminal, then I found that my addons are in /usr/share/hassio/addons folder. I also could find "git" and "data" folder in that path. In the "git" folder, you can find git download of eufy-security-ws, but the names of the of each addon folders are shown in only hexa value. I had to find the map between hexa value and addon. I could find the the map by simply searching "data" folder because in that folder each folder name had both hexa value and the name of the addons. In my case, the name started with "402F". I removed all the contents in git/402FXXXX/ folder and wget 1.3.5 version, untared, and made it look like original one by matching the name of the subfolder. After, reboot HA, I could find the upgrade to v1.3.5 button in the supervisor for the eufy-security-ws addon. By clinking the upgrade button, I could downgrade eufy-security-ws to version 1.3.5.

Thanks! I’ll give this a go

@einfall
Copy link

einfall commented Jul 31, 2023

any news ?

@fuatakgun
Copy link
Owner

There is a newer version of add-on (1.6.0), please download it and test captcha/2fa specific issues.

@bewA
Copy link

bewA commented Aug 3, 2023

I can confirm with the latest versions of everything :D I was able to add my eufy devices to home assistant :)

@fuatakgun
Copy link
Owner

@bewA , did you go through captcha or 2fa?

@bewA
Copy link

bewA commented Aug 3, 2023

@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 :)

@fuatakgun
Copy link
Owner

Thanks for sharing, time to resolve this :-)

@bewA
Copy link

bewA commented Aug 3, 2023

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

@fuatakgun fuatakgun unpinned this issue Aug 10, 2023
@treyd
Copy link

treyd commented Aug 11, 2023

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?

@remconiesten
Copy link

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

2023-08-17 13:13:05.204 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.eufy_security.config_flow Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/loader.py", line 779, in get_platform cache[full_name] = self._import_platform(platform_name) File "/usr/src/homeassistant/homeassistant/loader.py", line 796, in _import_platform return importlib.import_module(f"{self.pkg_path}.{platform_name}") File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 992, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/config/custom_components/eufy_security/__init__.py", line 10, in <module> from .const import COORDINATOR, DOMAIN, PLATFORMS File "/config/custom_components/eufy_security/const.py", line 36, in <module> Platform.IMAGE, File "/usr/local/lib/python3.10/enum.py", line 437, in __getattr__ raise AttributeError(name) from None AttributeError: IMAGE 2023-08-17 13:13:05.206 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration eufy_security: Exception importing custom_components.eufy_security.config_flow

Please advise.

@fuatakgun
Copy link
Owner

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.

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

No branches or pull requests