search

homebridge-eufy-security / plugin

Homebridge plugin to control certain Eufy Security devices
Apache License 2.0
166 stars 24 forks source link

[Bug]: Login failed #250

Closed yanavery closed 11 months ago

yanavery commented 1 year ago

What happened?

As a follow-up to #201 which was closed, I'm still observing generalized and systematic login issues (always fails) between the homebridge-eufy-security plugin and Eufy.

With release 2.1.3 (for which I believe included the necessary fix(es) for #201), I still can't login ... Homebridge logs say:

[12/18/2022, 6:47:15 PM] [EufySecurity-2.1.3] ERROR: Not connected can't continue!

Different login attempts with either my main Eufy account or another one I created for Homebridge purposes are both failing while those 2 accounts are working fine when used from the Eufy mobile app. I'm also seeing this in the Homebridge logs after I attempt a login:

[18/12/2022, 19:23:54] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /login
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Terminating child process...
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Child process ended

From the plugin's UI, when I'm trying to use my main account which has 2FA configured, I do receive the Eufy email and I do get challenged by the plugin to enter my 2FA code in the Homebridge Eufy Plug-in UI, but it fails after ... For my other Eufy account that doesn't have 2FA enabled, I obviously don't get challenged for a 2FA code and it fails immediately with a message that says "Login was not successful!" ... I do get some Captha challenges along the way, so it looks like some communication between the Homebridge plugin and Eufy is happening, but it just doesn't seem to be able to finalize.

BTW, Eufy country for me is set to Canada (both in Eufy account and in the Homebridge plugin), maybe it could be related to that?

If any additional details are needed to troubleshoot, please let me know.

Thanks,

Device Type

Station (Supported)

Plugin Version

v2.0.x (Supported)

HomeBridge Version

v1.4.x (Supported)

NodeJS Version

v16 (Supported)

Operating System

Raspbian 10+ (Supported)

Relevant log output

[12/18/2022, 6:47:15 PM] [EufySecurity-2.1.3] ERROR: Not connected can't continue!

[18/12/2022, 19:23:54] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /login
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Terminating child process...
[18/12/2022, 19:27:13] [Homebridge UI] [homebridge-eufy-security] Child process ended

config

{
    "platform": "EufySecurity",
    "username": "****redacted****",
    "password": "****redacted****",
    "pollingIntervalMinutes": 30,
    "hkHome": 1,
    "hkAway": 0,
    "hkNight": 3,
    "hkOff": 63,
    "enableDetailedLogging": true,
    "ignoreStations": [
        "****redacted****",
        "****redacted****",
        "****redacted****"
    ],
    "ignoreDevices": [
        "****redacted****",
        "****redacted****",
        "****redacted****",
        "****redacted****"
    ],
    "country": "CA",
    "CameraMaxLivestreamDuration": 30,
    "cleanCache": true,
    "_bridge": {
        "username": "****redacted****",
        "port": 53985
    },
    "cameras": [
        {
            "serialNumber": "****redacted****",
            "rtsp": false,
            "talkback": false
        },
        {
            "serialNumber": "****redacted****",
            "rtsp": false,
            "talkback": false
        },
        {
            "serialNumber": "****redacted****",
            "rtsp": false,
            "talkback": false
        }
    ]
}
Z1mDMan commented 1 year ago

so this is interesting, when I tried beta 16, I got the following error:

[12/22/2022, 11:28:20 PM] ==================== [12/22/2022, 11:28:20 PM] ERROR LOADING PLUGIN homebridge-eufy-security: [12/22/2022, 11:28:20 PM] Error: Cannot find module 'got' Require stack:

but when I manually went to beta 15, everything works...?

Z1mDMan commented 1 year ago

removed and re-added beta 15 because I wasn't able to add my doorbell for some reason. I now get the same error about cannot find module "got"

jp-lno commented 1 year ago

Is anyone else getting the same errors again? Seeing this after every restart of HomeBridge again.

[12/22/2022, 1:28:34 PM] [EufySecurity-2.2.0-beta.15] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/22/2022, 1:28:34 PM] [EufySecurity-2.2.0-beta.15] ERROR: Not connected can't continue!

Yes even after installing beta 16. No issues while installing last beta. But on restart. Always get ERROR. Sounds bad 😰

Z1mDMan commented 1 year ago

yes, I'm also seeing this now. I've tried a couple different accounts as well.

Z1mDMan commented 1 year ago

I think I'm having the same issue. I'm on node 18.12.1> Wow, thank you for the fast work! Can anyone give tips on how to run npm

install? I'm a newb on a mac and I'm SSH'd into my HomeBridge box but am not sure where to run the install from. The plugin installation failed as expected, (didn't work subsequent tries) but I'm not sure about where to go from there. TIA! On Thu, Dec 22, 2022 at 4:08 AM thieren @.***> wrote:

Hi folks, so I've just published 2.2.0-beta.15 which in theory has a fix for the login. Unfortunately this version installs not correctly on my server due to some errors. I don't know if I'll get around to debugging this because of the holidays (kudos to eufy who had the balls to make such changes to their login the week before christmas). So to any fellow programmers who like to help out - maybe one of you has experience with this:

  • I've added a submodule of the eufy-security-client to the beta branch to include the necessary changes directly
  • the build command was changed so that this submodule is compiled correctly
  • all together is then published to npm

Here is what I found:

first there was some obscure error, that a 'dev' setting could not set

by npm - I got around this by updating npm to the latest 9.2.0 - don't know what that was about now when installing npm complains that the package.json of the submodule is not found - even though it is there if you open the directory afterwards This prevents the package from installing correctly. You can use it nevertheless if you run npm install in the plugin install path - but for now I don't know why it won't work at first install. At least after that the login seems to work again. Unfortunately the beta.15 is therefore broken for now. Maybe someone has a hint. I'll try to get back to it as soon as I can. — Reply to this email directly, view it on GitHub #250 (comment), or unsubscribe https://github.com/notifications/unsubscribe-auth/A44TEKMSWHQQDJVF3KQRHGDWORAEZANCNFSM6AAAAAATDM4WEI . You are receiving this because you commented.

npm install --save homebridge-eufy-security@2.2.0-beta.16

timmy8784 commented 1 year ago

Still getting the error below when trying to install beta 16. Anyone have any idea what it is?

pi@homebridge:/var/lib/homebridge $ pm install --save homebridge-eufy-securi ty@2.2.0-beta.16 pm ERR! code ENOTEMPTY npm ERR! syscall rename nom ERR! path /var/lib/homebridge/node modules /homebridge-eufy-security pm ERR! dest /var/lib/homebridge/node modules/.homebridge-eufy-security-bkoC ZZOI nom ERR! errno -39 pm ERR! ENOTEMPTY: directory not empty, rename '/var/lib/homebridge/node mod ules/homebridge-eufy-security 'Ivar/lib/homebride/node modules /. homebrid ge-eufy-security-bkoCzz0I pm ERR! A complete log of this run can be found in: npm ERR! / home/pi/.npm/_1ogs/2022-12-23707_31_59_9587-debug-0.1og

timmy8784 commented 1 year ago

I'm even getting the same error when I try to uninstall 2.1.3

TheBassfly commented 1 year ago

Hey together

I'm running Homebridge with the Sinology spk on my disk station. The Install of the Beta16 worked after installing it two times. After this update I was able to log in to my guest account again and to see the devices.

But the Plugin still dropped the following error: [12/23/2022, 8:38:35 AM] [EufySecurity-2.2.0-beta.16] ERROR: Not connected can't continue!

So for me the issue still is not solved.

MartinJRS commented 1 year ago

Hi all,

same here, I agree to TheBassfly. Not working.

DolmensDude commented 1 year ago

Installed beta 15 last night. Did not error on install but I did the install again. Using install alternate version option straight out of the gui.

seemed to be logged in but logged in again.

all seemed to work. And is still working > 12hours later.

ran thru device options - some of these don’t make sense if thumbnails functionality is essentially gone.

pushing a lot of messages to the console, and certainly using more bandwidth than I think eufy probably wants. Not sure why but of course there’s no thumbnails, so cameras that show previews are refreshing quite often. Somehow better but I have 6 cams/doorbells going thru this plug-in… we’ll see.

I probably will wait to install beta 16 as I don’t see anyone saying it’s working for them.

I run this in Container Station on a QNAP. Docker image thus.

bmpalmeida commented 1 year ago

I'm having a slightly different error upgrading from beta.14 on Homebridge UI.

USER: pi DIR: /usr/local CMD: sudo -E -n npm install -g homebridge-eufy-security@2.2.0-beta.16

npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /usr/local/lib/node_modules/homebridge-eufy-security/eufy-security-client/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/usr/local/lib/node_modules/homebridge-eufy-security/eufy-security-client/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-12-23T10_04_34_812Z-debug-0.log

Operation failed. Please review log for details.

PeterAlexander75 commented 1 year ago

If I create a new sub- account without 2FA, I get the CAPTCHA, but then login fails. If I create a new account with 2FA, I get as far as "Loading Accessories", but that hangs. If I cancel out and try again with the same account, I just get a hard stop at "login failed".

Gemuir commented 1 year ago

Great work! Installation failed first time but worked second time around.

What error did you receive the first time? I am getting the error above and can't figure out what is happening. Do you know what node version or npm you are running?

I'm on npm 8.19.2 node.js 18.12.1

I'm on npm: '8.19.2', node: '18.12.0',

PeterAlexander75 commented 1 year ago

I managed to get everything working again on beta 15. I removed the plugin completely. Removed cached accessories (Homebridge UI settings > Manage Cached Accessories). Installed beta 16 from the Homebridge GUI. Rebooted. Then installed beta 15 from the command line.

npm install -g homebridge-eufy-security@2.2.0-beta.15

I was then able to log in to my master account (I know... not the right thing to do) getting through CAPTCHA and emailed login code and everything is working.

I'll try beta 17 maybe later when I'm feeling brave.

thieren commented 1 year ago

Hi again.

2.2.0-beta.17 is out and should at least install correctly now.

As for the ones not being able to login again: Is this always accompanied with a log warning, that a captcha was requested? Then it could also be that your account was flagged by eufy for too much logins. Maybe try with a new guest account that you share your devices with?

MartinJRS commented 1 year ago

Affirmative, all seems to work as usually. Thank you very much for taking the effort in this time of the year ... seriously appreciated and not taken for granted.

Merry Christmas and a good time with the family.

Z1mDMan commented 1 year ago

2.2.0-beta.17 resolved the issue for me. I have my doorbell camera back. Thank you @thieren!

frogking1012 commented 1 year ago

[12/24/2022, 12:09:16 AM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

not working for me ={

tysxno commented 1 year ago

So, I'm a first time HomeBridge user and I was finally able to login using the beta, and can see my devices, but now I'm getting this error:

[12/23/2022, 10:07:41 PM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

TheBassfly commented 1 year ago

Beta17 also seems to work for me :)

The Only Error I get is "No Snapshot in Memory". But this seems okay for me.

thieren commented 1 year ago

I think the cause of the recurring login issues might be that the homebridge instance cannot be added as 'trusted device' yet (this function is still on v1 api). I'll see if I can do something about this.

TOTO-DK commented 1 year ago

Beta 17 does´t work for me at all.

No matter how many Captchas, I but in, the reboot still demands a new one = endless loop ;-(

[12/23/2022, 5:32:14 PM] Homebridge v1.5.1 (HAP v0.10.4) (Homebridge C2FC) is running on port 51005. [12/23/2022, 5:32:14 PM] [EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/23/2022, 5:32:14 PM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

TOTO-DK commented 1 year ago

Beta 17 does´t work for me at all.

No matter how many Captchas, I but in, the reboot still demands a new one = endless loop ;-(

[12/23/2022, 5:32:14 PM] Homebridge v1.5.1 (HAP v0.10.4) (Homebridge C2FC) is running on port 51005. [12/23/2022, 5:32:14 PM] [EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/23/2022, 5:32:14 PM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

Just switched to another Eufy account, and then it worked fine again ;-)

timmy8784 commented 1 year ago

Can anyone help me with this? It won't even let me uninstall 2.1.3 and giving this error. No clue what this means or how to fix

pm ERR! code ENOTEMPTY npm ERR! syscall rename nom ERR! path /var/lib/homebridge/node modules /homebridge-eufy-security pm ERR! dest /var/lib/homebridge/node modules/.homebridge-eufy-security-bkoC ZZOI nom ERR! errno -39 pm ERR! ENOTEMPTY: directory not empty, rename '/var/lib/homebridge/node mod ules/homebridge-eufy-security 'Ivar/lib/homebride/node modules /. homebrid ge-eufy-security-bkoCzz0I pm ERR! A complete log of this run can be found in: npm ERR! / home/pi/.npm/_1ogs/2022-12-23707_31_59_9587-debug-0.1og

thieren commented 1 year ago

@timmy8784

I think this is not related to the original issue. I'll try to give you some hints, but if these don't help I would suggest opening a new issue, or write me on the discord channel, ok?

  1. please update npm on your homebridge system (npm install -g npm@latest) - 9.x after that
  2. also restart the system once - might be that there is a lock on some directory, or something
  3. try the tip in the error message - it says something that a directory is not empty. Maybe delete this directory, or the contents of it
  4. try to run npm as root. so something like sudo npm ... might help (this might differ depending on your system distro/setup)
timmy8784 commented 1 year ago

@timmy8784

I think this is not related to the original issue. I'll try to give you some hints, but if these don't help I would suggest opening a new issue, or write me on the discord channel, ok?

  1. please update npm on your homebridge system (npm install -g npm@latest) - 9.x after that

  2. also restart the system once - might be that there is a lock on some directory, or something

  3. try the tip in the error message - it says something that a directory is not empty. Maybe delete this directory, or the contents of it

  4. try to run npm as root. so something like sudo npm ... might help (this might differ depending on your system distro/setup)

@thieren

Thank you for the help. I upgraded to 9.2 and rebooted everything and still have the same issue.

I am running a raspberry pi for homebridge and I'm not very well versed in the other steps you mentioned about checking directories and things like that or running Npm as root.

I will open a new issue to see if I can get some further help. Thanks!

noppie commented 1 year ago

After restarting the child bridge I get this message: EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in followed by: EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

outrageouskiwi commented 1 year ago

Really grateful for the updates. It’s working better than before. Is there a tip jar? That’s a lot of bug-fixing on a holiday! On Dec 23, 2022 at 10:49 AM -0800, noppie @.***>, wrote:

After restarting the child bridge I get this message: EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in followed by: EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

noppie commented 1 year ago

Absolutely grateful for all the work:

But even tried switching to another eufy Account, stil getting this messages:

[12/23/2022, 8:10:09 PM] [EufySecurity-2.2.0-beta.17] WARN: warning: planned changes, see https://github.com/homebridge-eufy-security/plugin/issues/1 [12/23/2022, 8:10:09 PM] [EufySecurity-2.2.0-beta.17] INFO: Country set: NL [12/23/2022, 8:10:09 PM] [EufySecurity-2.2.0-beta.17] INFO: Finished initializing! [23/12/2022, 20:10:10] Homebridge v1.6.0 (HAP v0.11.0) (homebridge-eufy-security) is running on port 50245. [12/23/2022, 8:10:15 PM] [EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/23/2022, 8:10:15 PM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

noppie commented 1 year ago

Absolutely grateful for all the work:

But even tried switching to another eufy Account, stil getting this messages:

[12/23/2022, 8:10:09 PM] [EufySecurity-2.2.0-beta.17] WARN: warning: planned changes, see #1 [12/23/2022, 8:10:09 PM] [EufySecurity-2.2.0-beta.17] INFO: Country set: NL [12/23/2022, 8:10:09 PM] [EufySecurity-2.2.0-beta.17] INFO: Finished initializing! [23/12/2022, 20:10:10] Homebridge v1.6.0 (HAP v0.11.0) (homebridge-eufy-security) is running on port 50245. [12/23/2022, 8:10:15 PM] [EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/23/2022, 8:10:15 PM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

noppie commented 1 year ago

I thought it was a security issue on the directory but it isn't:

[12/23/2022, 8:35:40 PM] [EufySecurity-2.2.0-beta.17] DEBUG: plugin data store: /var/lib/homebridge/eufysecurity [12/23/2022, 8:35:40 PM] [EufySecurity-2.2.0-beta.17] DEBUG: Using bropats eufy-security-client library in version 2.3.0 [12/23/2022, 8:35:40 PM] [EufySecurity-2.2.0-beta.17] INFO: Country set: NL [12/23/2022, 8:35:40 PM] [EufySecurity-2.2.0-beta.17] INFO: Finished initializing! [23/12/2022, 20:35:41] Homebridge v1.6.0 (HAP v0.11.0) (homebridge-eufy-security) is running on port 50245. [12/23/2022, 8:35:48 PM] [EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/23/2022, 8:35:48 PM] [EufySecurity-2.2.0-beta.17] DEBUG: EufyClient connected false [12/23/2022, 8:35:48 PM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

thieren commented 1 year ago

After a bit more testing it seems as if eufy has increased its captcha frequency quite a bit. Maybe it's just this why some of you experience the login failure with captchas right now.

I have already an idea what can be done about that, but I'm afraid that I will not be able to implement that over the holidays. If someone finds a pattern in the captcha requests, please do share your findings

Is there a tip jar? That’s a lot of bug-fixing on a holiday!

@outrageouskiwi Thx for the offer. If you really want there is a 'Support' section on the main page of the repo, or a 'Donation'-Link on the Plugins-Page in Homebridge-UI. But please do know that you don't have to. If you want to give something nevertheless, it will be highly appreciated. Thx!

tysxno commented 1 year ago

All seems to work after I logged in to a shared account, I'd suggest anyone to do this on Beta 17.

noppie commented 1 year ago

All seems to work after I logged in to a shared account, I'd suggest anyone to do this on Beta 17.

I tried with a shared account but still doesn't work

andypburke commented 1 year ago

I have just experienced this issue today after not having any problems for some time. Tried the beta and suggestions above but no joy. I don't get the captcha error, but I do get the can't connect error. Appreciate everyone's efforts in trying to resolve.

thieren commented 1 year ago

Can anyone who experiences the can't connect but without the captcha warning please provide the eufy-log.log file? Send it via discord if possible.

cldparisi commented 1 year ago

I had the exact same behavior. I resolted it when I installed Beta17 and I re-config all

tjfontaine commented 1 year ago

Sorry not on discord, but here’s the final stack trace


2022-12-24 16:49:43.115  DEBUG [HTTPApi.request] Response:
{
  response: {
    code: 0,    msg: 'Succeed.',    data: '<REDACT>'
  }
}

2022-12-24 16:49:43.146  ERROR [HTTPApi.getPassportProfile] Generic Error:
 Error  error:1C800064:Provider routines::bad decrypt
details:
{
  library: 'Provider routines',
  reason: 'bad decrypt',
  code: 'ERR_OSSL_BAD_DECRYPT'
} 
error stack:
• cipher:193 final
    node:internal/crypto/cipher:193:29
• utils.ts:176 decryptAPIData
    node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/http/utils.ts:176:16
• api.ts:1018 decryptAPIData
    node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/http/api.ts:1018:41
• api.ts:1191 getPassportProfile
    node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/http/api.ts:1191:46
• task_queues:95 processTicksAndRejections
    node:internal/process/task_queues:95:5
• api.ts:352 login
    node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/http/api.ts:352:33
• eufysecurity.ts:685 connect
    node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/eufysecurity.ts:685:9
• platform.ts:229 pluginSetup
    node_modules/homebridge-eufy-security/src/plugin/platform.ts:229:7
• platform.ts:193 <anonymous>
    node_modules/homebridge-eufy-security/src/plugin/platform.ts:193:7
thieren commented 1 year ago

@tjfontaine at least this shows that it's likely an issue that the client cannot decrypt the api response correctly. But to further investigate I'd need a full log.

sunnymody commented 1 year ago

Facing the same problem even after upgrading to beta 17. Following is the error log. Looking for some issue resolution if anyone has figured this out. Thanks!

[12/24/2022, 4:04:52 PM] [EufySecurity-2.2.0-beta.17] WARN: There was a Captcha request while login in. This cannot be fulfilled by the plugin itself. Please login using the configuration wizard (settings) in the Homebridge UI plugins tab. [12/24/2022, 4:04:52 PM] [EufySecurity-2.2.0-beta.17] DEBUG: EufyClient connected false [12/24/2022, 4:04:52 PM] [EufySecurity-2.2.0-beta.17] ERROR: Not connected can't continue!

thieren commented 1 year ago

@sunnymody it is not yet clear why some users are getting captcha requests now every time they try to connect the plugin. Most likely it's something that eufy has changed in their login process.

I'm working on a workaround but for now there is nothing much you can do except trying different (maybe new created) accounts.

la7eralus commented 1 year ago

I'm on beta 17, and I get the captcha error with two newly created users. Disabling 2FA for the User solves the issue, even though it's a bad practice, and should only be set temporarily. Just in case, someone needs this urgently for the holidays.

adekka commented 1 year ago

Just sharing my experience: i've waited for more then 12 hours and now I didn't get the captcha error.

PeterAlexander75 commented 1 year ago

I’ve stayed on beta 15. I have 2FA off and captcha worked fine when setting up the plug-in anew. I have had no login errors in the log and the plug-in is working fine.

mpjalexander commented 1 year ago

I had the same issue with `Not connected can’t continue!” shown in the Homebridge log when it was restarted. I tried logging in with the guest account in the app, which worked but I’d still get the error in Homebridge. I tried changing the password for the guest account using the app, but still got the Homebridge error. I then tried creating a new guest account and finally the plugin started working again. (Note that I’m currently using v2.2.0 beta 17 of the plugin.)

One thing I noticed is that my old guest account had two homes set up: a default one that must have been created when the account was set up (but had no devices in it) and the home I shared from my main account. The new guest account did not have this default home; only the one I shared from my main account. Could this have anything do to with the underlying issue?

noppie commented 1 year ago

I had the same issues.  Waited for about 12 hours and now it works.  No captcha issues.  Nothing.  Verstuurd vanaf mijn Op 26 dec. 2022 om 12:23 heeft Mike Alexander @.***> het volgende geschreven: I had the same issue with `Not connected can’t continue!” shown in the Homebridge of when it was restarted. I tried logging in with the guest account in the app, which worked but I’d still get the error in Homebridge. I tried changing the password for the guest account using the app, but still got the Homebridge error. I then tried creating a new guest account and finally the plugin started working again. One thing I noticed is that my old guest account had two homes set up: a default one that must have been created when the account was set up (but had no devices in it) and the home I shared from my main account. The new guest account did not have this default home; only the one I shared from my main account. Could this have anything do to with the underlying issue?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

smitty078 commented 1 year ago

This seems to be completely solve in beta17/ security-lib2.4.0 (released 12/24)

mariomaz87 commented 1 year ago

hi, I'm using the latest beta (17) on a fresh new install (I removed the plugin and installed it again) and on a fresh new Eufy account without 2FA. The email of the account has been validated and I can login using the app on iPhone. I insert the credentials in the Login pop-up of the plugin and when I press Login, it just spins and spins. In HB log I don't see anything relevant, only:

[29/12/2022, 10:36:33] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /login [29/12/2022, 10:36:42] [Homebridge UI] [homebridge-eufy-security] Child process ended

I have the same behavior also on 2.1.4. Can I try something else? Thanks!

thieren commented 1 year ago

hi, I'm using the latest beta (17) on a fresh new install (I removed the plugin and installed it again) and on a fresh new Eufy account without 2FA. The email of the account has been validated and I can login using the app on iPhone.

I insert the credentials in the Login pop-up of the plugin and when I press Login, it just spins and spins. In HB log I don't see anything relevant, only:

[29/12/2022, 10:36:33] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /login

[29/12/2022, 10:36:42] [Homebridge UI] [homebridge-eufy-security] Child process ended

I have the same behavior also on 2.1.4. Can I try something else? Thanks!

Have you shared all your devices already with the new account and also accepted this invitation in the eufy app?

The log for this login is not mixed with the homebridge log but the debug messages are stored in configui-server.log files instead.

frogking1012 commented 1 year ago

somehow it works now, without me changing anything....so weird...