Closed fuatakgun closed 1 year ago
As soon as eufy-security-ws
receives a captcha request, it is cached so that every client that connects and executes start listening
also receives the event as long as no client has sent the captcha. Look here and here.
What has not been implemented is whether a captcha has expired in the meantime (this information is not available and could only be implemented with a simple timer), but if the captcha request is answered incorrectly, you get another one right away ;)
we can create a new command to initiate login flow.
There is already a command to initiate a connection. See here.
I remember it was the case but yesterday i tried with 1.4.1 and i didn't receive captcha event. Even after trying driver.connect didn't receive respective events, let me double check and share the logs
This gets more problematic when user had enabled 2fa because they will get multiple emails (one delivered at docker startup and one after driver connect)
my findings;
stations loaded
(https://github.com/bropat/eufy-security-client/blob/76772a2f49aae2b05f4c17eab5294831b2886c65/src/eufysecurity.ts#L291)when I am running client against server, this is the response;
ts-node src/bin/client.ts
{
type: 'version',
driverVersion: '2.5.1',
serverVersion: '1.4.1',
minSchemaVersion: 0,
maxSchemaVersion: 17
}
{
type: 'result',
success: true,
messageId: 'api-schema-id',
result: {}
}
Is there any update to this? I think I have the same issue. When I start the integration, it says no entities found:
When I went to the Eufy add on, it says "schema incomplete":
It used to be working but have stopped working for few weeks now and can't seem to figure out why.
@fuatakgun checkout latest version (1.6.0
).
Describe the solution you'd like
Cont. from https://github.com/bropat/eufy-security-ws/issues/150
I am having issues to receive
captcha/verification (2fa)
events from WS on container, assuming that before I can even reach tostart listening
state, WS on container had already tried logging in and received respective events.So timeline perspective;
start listening
captcha
orverify (2fa)
so it cannot react accordingly.Suggestions;