Plugin not working?

[skazzyskills]

Describe The Bug:

push token timeout. Here are the logs: Starting to advertise 'Homebridge 55E8 F863' using bonjour-hap backend! [14/04/2021, 17:37:29] Homebridge v1.3.4 (Homebridge 55E8) is running on port 51572. [14/04/2021, 17:37:49] [EufySecurityHomebridgePlugin] registering a push token timed out (node:31750) UnhandledPromiseRejectionWarning: Error: Request failed: https://security-app.eufylife.com/v1/passport/login -> 100028 - Failed to request. at /usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:24:15 at Generator.next () at fulfilled (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:5:58) at processTicksAndRejections (internal/process/task_queues.js:93:5) (Use `node --trace-warnings ...` to show where the warning was created) (node:31750) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:31750) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [14/04/2021, 17:38:13] [EufySecurityHomebridgePlugin] failed to register push token Error: Request failed: https://security-app.eufylife.com/v1/passport/login -> 100028 - Failed to request. at /usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:24:15 at Generator.next () at fulfilled (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:5:58) at processTicksAndRejections (internal/process/task_queues.js:93:5) [14/04/2021, 17:38:19] [EufySecurityHomebridgePlugin] failed to confirm push token **To Reproduce:** Just installed the plugin. That's it. **Expected behavior:** For it to work and see my accessory **Logs:** ``` Starting to advertise 'Homebridge 55E8 F863' using bonjour-hap backend! [14/04/2021, 17:37:29] Homebridge v1.3.4 (Homebridge 55E8) is running on port 51572. [14/04/2021, 17:37:49] [EufySecurityHomebridgePlugin] registering a push token timed out (node:31750) UnhandledPromiseRejectionWarning: Error: Request failed: https://security-app.eufylife.com/v1/passport/login -> 100028 - Failed to request. at /usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:24:15 at Generator.next () at fulfilled (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:5:58) at processTicksAndRejections (internal/process/task_queues.js:93:5) (Use `node --trace-warnings ...` to show where the warning was created) (node:31750) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:31750) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [14/04/2021, 17:38:13] [EufySecurityHomebridgePlugin] failed to register push token Error: Request failed: https://security-app.eufylife.com/v1/passport/login -> 100028 - Failed to request. at /usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:24:15 at Generator.next () at fulfilled (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/http/http.utils.js:5:58) at processTicksAndRejections (internal/process/task_queues.js:93:5) [14/04/2021, 17:38:19] [EufySecurityHomebridgePlugin] failed to confirm push token ``` **Plugin Config:** ```json Show your Homebridge config.json here, remove any sensitive information. ``` { "bridge": { "name": "Homebridge 55E8", "username": "xxxx", "port": 51572, "pin": "xxxxx" }, "accessories": [], "platforms": [ { "name": "Config", "port": 8588, "platform": "config" }, { "username": "xxx", "password": "xxxxx", "enablePush": true, "platform": "EufySecurityHomebridgePlugin" } ] } **Screenshots:**

Environment:

• Plugin Version:homebridge-plugin-eufy-security v0.1.8
• Homebridge Version: v1.3.4
• Node.js Version: v14.16.1
• NPM Version: v6.14.12
• Operating System: Raspbian

[deanlyoung]

This may be due to the fact that this plugin relies on the now deprecated https://github.com/JanLoebel/eufy-node-client instead of the more up-to-date https://github.com/bropat/eufy-security-client

[skazzyskills]

Hmmm…this one isn’t appearing when I do a plugin search in Homebridge with the web client.

Shawn Skalinski @.***

On Apr 18, 2021, at 12:31 PM, Dean L. Young @.***> wrote:

This may be due to the fact that this plugin relies on the now deprecated https://github.com/JanLoebel/eufy-node-client https://github.com/JanLoebel/eufy-node-client instead of the more up-to-date https://github.com/bropat/eufy-security-client https://github.com/bropat/eufy-security-client — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/birkir/homebridge-plugin-eufy-security/issues/45#issuecomment-822047310, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2ONOBP4LMYUIF4MDEI2ZTTJMXQNANCNFSM426NIO4Q.

[Mike92115]

I believe that the https://github.com/bropat/eufy-security-client plugin is for use with the https://iobroker.net/ and not Homebridge that would be why you are not finding it when you search. I could be wrong but when I looked at the plugin and followed it back that is what I found.

[skazzyskills]

So does that mean there’s no way to see my doorbell in HomeKit?

Shawn Skalinski @.***

On Apr 19, 2021, at 10:25 AM, Mike92115 @.***> wrote:

I believe that the https://github.com/bropat/eufy-security-client https://github.com/bropat/eufy-security-client plugin is for use with the https://iobroker.net/ https://iobroker.net/ and not Homebridge that would be why you are not finding it when you search. I could be wrong but when I looked at the plugin and followed it back that is what I found.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/birkir/homebridge-plugin-eufy-security/issues/45#issuecomment-822642295, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2ONOEC3HREMXFXN2RDSC3TJRRQBANCNFSM426NIO4Q.

[Mike92115]

I am just a user of Homebridge not a developer, but based upon what I have found until someone fixes this plugin or creates a new one that works there is no way currently to have your Eufy Doorbell in HomeKit. I have looked and looked and not found anything else for the doorbell, I could have missed something but I don't think so.

Mike

So does that mean there’s no way to see my doorbell in HomeKit? Shawn Skalinski @.*** …

[mmz06]

Hi There, I'm also just a user of this plugin, which happens to work particularly well, at least for me. But I faced 2 issues at first which were actually easily solved:

1. if your account uses dual factor authentication (2FA), you need to disable it, or to create a separate invite account without dual factor, which you will use for this purpose.
2. You need to disable "Push Client" option, as I'm not sure about what it should bring, but at least it created an issue for me. Disabling it has solved this problem, since 1 or 2 weeks now.

[ivangotti]

Hi! Can you have notifications on AppleTV? Where do I disable the "Push Client" thing?

Regards, Ivan Gotti www.linkedin.com/in/ivangotti

On Fri, 23 Apr 2021 at 14:19, mmz06 @.***> wrote:

Hi There, I'm also just a user of this plugin, which happens to work particularly well, at least for me. But I faced 2 issues at first which were actually easily solved:

1. if your account uses dual factor authentication (2FA), you need to disable it, or to create a separate invite account without dual factor, which you will use for this purpose.
2. You need to disable "Push Client" option, as I'm not sure about what it should bring, but at least it created an issue for me. Disabling it has solved this problem, since 1 or 2 weeks now.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/birkir/homebridge-plugin-eufy-security/issues/45#issuecomment-825618884, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALRAIDGIEUH7GYRRXS7GFJLTKFQUJANCNFSM426NIO4Q .

[mmz06]

I don't own an AppleTV, but I have i can see the stream in my iPhone and in my Mac, in Home app. The push client option is in EufySecurity Plugin configuration in Homebridge as per the attached picture

[ivangotti]

Thank you!!

On Fri, 23 Apr 2021 at 14:45, mmz06 @.***> wrote:

I don't own an AppleTV, but I have i can see the stream in my iPhone and in my Mac, in Home app. The push client option is in EufySecurity Plugin configuration in Homebridge as per the attached picture [image: PushClient] https://user-images.githubusercontent.com/22093843/115872752-743ec680-a442-11eb-9c27-2c42709f5077.jpg

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/birkir/homebridge-plugin-eufy-security/issues/45#issuecomment-825633257, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALRAIDFCK4KPELI4DDLLZT3TKFTX5ANCNFSM426NIO4Q .

-- Ivan Gotti www.linkedin.com/in/ivangotti

[andypburke]

I think this plugin is great and it was working fine until today after a restart of Homebridge. Now I am getting error messages saying unable to register push token. Is this related to the issue above?

[Mike92115]

@andypburke I would assume it is, this worked for me for a very short time then an update occurred and it stopped working and rolling back did not correct the issue. I would think that you updated at some point and did not restart Homebridge so what you had kept working but after the restart you would have picked up the new version and are now at the same point most of us are with this.

I think this plugin is great and it was working fine until today after a restart of Homebridge. Now I am getting error messages saying unable to register push token. Is this related to the issue above?

[karesake]

Forget it. The plugin is dead. The last release was in February and only with a non-working version.

[skazzyskills]

That sucks.

Shawn Skalinski @.***

On May 15, 2021, at 1:14 AM, karesake @.***> wrote:

 Forget it. The plugin is dead. The last release was in February and only with a non-working version.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[andypburke]

Actually I have managed to get this to work, but not sure it is related to the node.js dependency. It appears my account was failing to login to the my eufy security portal so the API call in the plug-in was failing, even though my account was working in the app. Changing the password didn’t change anything. However, setting up a new guest account did work when I rolled back to the previous version of the plug-in. Been working fine for a few days now. Not sure it will help all you guys, but thought I would share anyway.

[CameronSmith93]

However, setting up a new guest account did work when I rolled back to the previous version of the plug-in. Been working fine for a few days now. Not sure it will help all you guys, but thought I would share anyway.

Which version did you roll back to?

[andypburke]

However, setting up a new guest account did work when I rolled back to the previous version of the plug-in. Been working fine for a few days now. Not sure it will help all you guys, but thought I would share anyway.

Which version did you roll back to?

0.16

[richie510]

Just rolled back to 0.16 and it is at least partially working for me. Push client timed out, but I can see a live feed. Pushing the doorbell button also seems to have no effect, I suspect due to push client not working.

[CameronSmith93]

Had video working fine as described by @richie510 on version 0.16.

Now, my plugin is working on version 0.18 after I manually updated eufy-node-client to version 0.5.0 - I have push client enabled and get the notification on my Apple TV, along with the chime on my HomePods - however the live video feed is no longer working.

Edit: After a reboot of my Homebridge server, the live video feed is working as well. Happy days.

[Mike92115]

@CameronSmith93,

Please let us know how to manually update the eufy-node-client? So we can get this working as well.

Thank you, Mike

Had video working fine as described by @richie510 on version 0.16.

Now, my plugin is working on version 0.18 after I manually updated eufy-node-client to version 0.5.0 - I have push client enabled and get the notification on my Apple TV, along with the chime on my HomePods - however the live video feed is no longer working.

Edit: After a reboot of my Homebridge server, the live video feed is working as well. Happy days.

[skazzyskills]

Except that it’s not working. The live feed doesn’t work so really this plug-in is dead.

Shawn Skalinski @.***

On May 17, 2021, at 9:44 AM, Mike92115 @.***> wrote:

 @CameronSmith93,

Please let us know how to manually update the eufy-node-client? So we can get this working as well.

Thank you, Mike

Had video working fine as described by @richie510 on version 0.16.

Now, my plugin is working on version 0.18 after I manually updated eufy-node-client to version 0.5.0 - I have push client enabled and get the notification on my Apple TV, along with the chime on my HomePods - however the live video feed is no longer working.

Edit: After a reboot of my Homebridge server, the live video feed is working as well. Happy days.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[andypburke]

@CameronSmith93,

Please let us know how to manually update the eufy-node-client? So we can get this working as well.

Thank you, Mike

Had video working fine as described by @richie510 on version 0.16. Now, my plugin is working on version 0.18 after I manually updated eufy-node-client to version 0.5.0 - I have push client enabled and get the notification on my Apple TV, along with the chime on my HomePods - however the live video feed is no longer working. Edit: After a reboot of my Homebridge server, the live video feed is working as well. Happy days.

I checked and I already had version 0.50 so I reinstalled 0.18 and the live feed works. If installing manually I would expect you would need to run the command npm i eufy-node-client.

[CameronSmith93]

@CameronSmith93,

Please let us know how to manually update the eufy-node-client? So we can get this working as well.

Thank you, Mike

Had video working fine as described by @richie510 on version 0.16. Now, my plugin is working on version 0.18 after I manually updated eufy-node-client to version 0.5.0 - I have push client enabled and get the notification on my Apple TV, along with the chime on my HomePods - however the live video feed is no longer working. Edit: After a reboot of my Homebridge server, the live video feed is working as well. Happy days.

Hi all,

I navigated to /usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/ and ran the following command:

npm install eufy-node-client@0.5.0

Confirming the live video feed is working, as well as chime on HomePods and Apple TV notifications on version 0.18.

Not sure what issue @skazzyskills is having.

[mmz06]

I navigated to /usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/ and ran the following command:

npm install eufy-node-client@0.5.0

Hi All,

Let me confirm this is working for me as well using Homebridge v1.3.4, but from a different folder as the provided one didn't exist for me, but /homebridge/node_modules/homebridge-plugin-eufy-security/node_modules/

Now to find the right directory, I used find / -name homebridge-plugin-eufy-security, then cd <my_path> then npm install eufy-node-client@0.5.0

Hope this will help to keep this nice plugin alive !!!

[PeterAlexander75]

If I enable push, I get error messages. Does anyone have this working with push enabled?

TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined
    at new NodeError (node:internal/errors:363:5)
    at Hash.update (node:internal/crypto/hash:105:11)
    at Object.generate (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/uuid.ts:11:11)
    at PushClient.callback (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/src/platform.ts:134:46)
    at PushClient.handleParsedMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:206:26)
    at PushClientParser.<anonymous> (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:103:63)
    at PushClientParser.emit (node:events:365:28)
    at PushClientParser.onGotMessageBytes (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:150:14)
    at PushClientParser.handleFullMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:79:22)
    at PushClientParser.waitForData (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:64:18)

[CameronSmith93]

If I enable push, I get error messages. Does anyone have this working with push enabled?

TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined
    at new NodeError (node:internal/errors:363:5)
    at Hash.update (node:internal/crypto/hash:105:11)
    at Object.generate (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/uuid.ts:11:11)
    at PushClient.callback (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/src/platform.ts:134:46)
    at PushClient.handleParsedMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:206:26)
    at PushClientParser.<anonymous> (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:103:63)
    at PushClientParser.emit (node:events:365:28)
    at PushClientParser.onGotMessageBytes (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:150:14)
    at PushClientParser.handleFullMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:79:22)
    at PushClientParser.waitForData (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:64:18)

Yes I have this working with push enabled. What version of eufy-node-client have you got installed?

[PeterAlexander75]

If I enable push, I get error messages. Does anyone have this working with push enabled?

TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined
    at new NodeError (node:internal/errors:363:5)
    at Hash.update (node:internal/crypto/hash:105:11)
    at Object.generate (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/uuid.ts:11:11)
    at PushClient.callback (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/src/platform.ts:134:46)
    at PushClient.handleParsedMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:206:26)
    at PushClientParser.<anonymous> (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:103:63)
    at PushClientParser.emit (node:events:365:28)
    at PushClientParser.onGotMessageBytes (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:150:14)
    at PushClientParser.handleFullMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:79:22)
    at PushClientParser.waitForData (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:64:18)

Yes I have this working with push enabled. What version of eufy-node-client have you got installed?

0.5.0

[CameronSmith93]

If I enable push, I get error messages. Does anyone have this working with push enabled?

TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined
    at new NodeError (node:internal/errors:363:5)
    at Hash.update (node:internal/crypto/hash:105:11)
    at Object.generate (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/uuid.ts:11:11)
    at PushClient.callback (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/src/platform.ts:134:46)
    at PushClient.handleParsedMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:206:26)
    at PushClientParser.<anonymous> (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client.service.js:103:63)
    at PushClientParser.emit (node:events:365:28)
    at PushClientParser.onGotMessageBytes (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:150:14)
    at PushClientParser.handleFullMessage (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:79:22)
    at PushClientParser.waitForData (/usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules/eufy-node-client/build/push/push-client-parser.service.js:64:18)

Yes I have this working with push enabled. What version of eufy-node-client have you got installed?

0.5.0

Not being a NodeJS developer myself, I'm not really sure what the problem could be there. Is your eufy account perhaps locked out temporarily? And can you view the live video stream via the Home app?

[PeterAlexander75]

Not being a NodeJS developer myself, I'm not really sure what the problem could be there. Is your eufy account perhaps locked out temporarily? And can you view the live video stream via the Home app?

I can. Yeah, all very odd. Looks like we're slowly getting there, though.

[andypburke]

Not being a NodeJS developer myself, I'm not really sure what the problem could be there. Is your eufy account perhaps locked out temporarily? And can you view the live video stream via the Home app?

I can. Yeah, all very odd. Looks like we're slowly getting there, though.

Can you log into the site https://mysecurity.eufylife.com/ with the credentials you have setup with the plugin? I found most of my issues came from this site rejecting my credentials, so I created another account to login to this site (and therefore the API for the plug-in) and everything works on version 0.18.

[PeterAlexander75]

Not being a NodeJS developer myself, I'm not really sure what the problem could be there. Is your eufy account perhaps locked out temporarily? And can you view the live video stream via the Home app?

I can. Yeah, all very odd. Looks like we're slowly getting there, though.

Can you log into the site https://mysecurity.eufylife.com/ with the credentials you have setup with the plugin? I found most of my issues came from this site rejecting my credentials, so I created another account to login to this site (and therefore the API for the plug-in) and everything works on version 0.18.

Yes - I have two “sub”‘accounts just for this purpose. Both are working fine. I can login on the website and see the stream in HomeKit, but enabling push throws that error.

Argh! So close!

[andypburke]

I have ran into a new problem which I think is related to how Eufy Security manage their API. Both of my accounts are now locked out from the portal (which impacts the API) and so the plug-in is failing. I think this might be related to the push token request for the push client feature. I suspect this might breach the number of API requests and Eufy blocks that account for a while. It seems to come back in a day or so, but it is frustrating. I plan to disable push client when it comes back to see if that is the cause. Not sure what can be done about this.

@CameronSmith93 have you experienced this issue?

[CameronSmith93]

I have ran into a new problem which I think is related to how Eufy Security manage their API. Both of my accounts are now locked out from the portal (which impacts the API) and so the plug-in is failing. I think this might be related to the push token request for the push client feature. I suspect this might breach the number of API requests and Eufy blocks that account for a while. It seems to come back in a day or so, but it is frustrating. I plan to disable push client when it comes back to see if that is the cause. Not sure what can be done about this.

@CameronSmith93 have you experienced this issue?

I experienced that issue before updating eufy-node-client to version 0.5.0, but have not experienced it since updating fortunately. I believe the lockout period is 24 hours.

[andypburke]

I have ran into a new problem which I think is related to how Eufy Security manage their API. Both of my accounts are now locked out from the portal (which impacts the API) and so the plug-in is failing. I think this might be related to the push token request for the push client feature. I suspect this might breach the number of API requests and Eufy blocks that account for a while. It seems to come back in a day or so, but it is frustrating. I plan to disable push client when it comes back to see if that is the cause. Not sure what can be done about this. @CameronSmith93 have you experienced this issue?

I experienced that issue before updating eufy-node-client to version 0.5.0, but have not experienced it since updating fortunately. I believe the lockout period is 24 hours.

Thanks. When I check the version of eufy-node-client it already states it is on 0.5.0, so I didn't manually update. I just wonder if I should update manually anyway.

[CameronSmith93]

Interesting that you already have 0.5.0 when the package.json file list version 0.3.1 as the current dependency.

Not sure, but might be worth mentioning that I made sure I had the live video feed working on version 0.16 before upgrading back to 0.18 and updating eufy-node-client to 0.5.0.

[PeterAlexander75]

OK folks, I have resolved this after a bit of poking around. I knew my homebridge install was a little messed up, as plugins/permissions have been problematic. I did a bit of careful re-installing and took the following steps.

1. Make sure all plugins are up to date
2. Eufy plugin up to date at 0.1.8.
3. Found the "homebridge-plugin-eufy-security" plugin install location. By default this is /usr/local/lib/node_modules/homebridge-plugin-eufy-security
4. Found the node_modules directory within the above directly and navigated to there in Terminal, which by default is

cd /usr/local/lib/node_modules/homebridge-plugin-eufy-security/node_modules

5. Ran the command

npm install eufy-node-client@latest

Went into homebridge config, turned on the push client for eufy

"enablePush": true,

and rebooted homebridge server. The error I posted above appeared again, caused homebridge to terminate and reboot. However, on second reboot, the error did not appear. With the push client off, my account worked just fine and thus far, the account is not being locked and push is working - including chimes on HomePods and also, rather excitingly, Apple TV.

Let us hope the account doesn't lock, as this is now a working plugin.

[PeterAlexander75]

UPDATE: Account got locked, so back to square one on that.

[skazzyskills]

This is why it’s broken.

Shawn Skalinski @.***

On May 18, 2021, at 7:58 AM, PeterAlexander75 @.***> wrote:

 UPDATE: Account got locked, so back to square one on that.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[karesake]

Thats exactly the problem we have since 0.1.1 version ;)

[karesake]

i say it one more : forget it! The Plugin development is dead! And also Eufy will block any Account for 24 hours if you tried to log in with HomeBridge

[skazzyskills]

Time to buy Logitech I guess.

Shawn Skalinski @.***

On May 18, 2021, at 8:03 AM, karesake @.***> wrote:

 i say it one more : forget it! The Plugin development is dead! And also Eufy will block any Account for 24 hours if you tried to log in with HomeBridge

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[PeterAlexander75]

What's weird though is that I can still log in at https://mysecurity.eufylife.com, even when the account is supposedly locked.

[karesake]

@skazzyskills Hmm. I am not a fan of Logi. Logitech drops product support as they want (Logitech Harmony)

We have all product from Eufy and to be honest, I don't miss HomeKit Support. The Only thing that would be nice is the HomePod ringing - on every HomePod. Otherwise we don't actually pay any attention to the doorbell.

I think I build it by myself. I Put a Indoor Camera in the Doorbell Housing and using a HomeKit Button that starts a automation for example a Ringing Sound File on HomePod.

[andypburke]

Interesting that you already have 0.5.0 when the package.json file list version 0.3.1 as the current dependency.

Not sure, but might be worth mentioning that I made sure I had the live video feed working on version 0.16 before upgrading back to 0.18 and updating eufy-node-client to 0.5.0.

Yes I did the same, except I didn't actually do the upgrade. Is your install still working and no lock out?

[xraywinedrinker]

Has anyone tried to use this plugin for other eufy cameras? I want to be able to set the guard modes via HomeKit. I’d like to use the HomeKit automation to trigger the mode change with another virtual device via the homebridge smartthings plugin.

[Mike92115]

Thank you everyone, I was able to get it working at least for now. I needed to uninstall the plugin then did a find to see if there was any other eufy directory and it turned out I had one. So I removed that, re-installed, updated the Eufy Client, then created a new account since I locked my other 2nd account out. Then I added it to HomeKit and it showed, I then went back and turned on Push Client and my HomeKit notifications are working and so is the Chime on my HomePod's. Not sure how long it will last, but at least I got this far.

Once again, thank you all for the help. Mike

[CameronSmith93]

push is working - including chimes on HomePods and also, rather excitingly, Apple TV.

Let us hope the account doesn't lock, as this is now a working plugin.

Out of interest, is the picture that shows up on your Apple TV the current picture of the person who pushed the button? I usually get the snapshot of whatever motion had previously been detected or the previous button push (i.e. whatever is showing up in the Home app prior to pressing the doorbell). But something I can happily live with given that I now get the HomePod chimes.

[mannyr7]

Just curious if there’s any chance Eufy would open source the driver for this? Obviously Apple won’t open source their end, but have the endpoints been discovered? Perhaps through examining other HomeKit compatible cam manufacturer’s software/hardware? Excuse my ignorance if these are dumb questions.

On Tue, May 18, 2021 at 6:08 PM CameronSmith93 @.***> wrote:

push is working - including chimes on HomePods and also, rather excitingly, Apple TV.

Let us hope the account doesn't lock, as this is now a working plugin.

Out of interest, is the picture that shows up on your Apple TV the current picture of the person who pushed the button? I usually get the snapshot of whatever motion had previously been detected or the previous button push (i.e. whatever is showing up in the Home app prior to pressing the doorbell). But something I can happily live with given that I now get the HomePod chimes.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/birkir/homebridge-plugin-eufy-security/issues/45#issuecomment-843669985, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFIUHXRQLSVUU2HRKLUQJQ3TOMFQ3ANCNFSM426NIO4Q .

[PeterAlexander75]

push is working - including chimes on HomePods and also, rather excitingly, Apple TV. Let us hope the account doesn't lock, as this is now a working plugin.

Out of interest, is the picture that shows up on your Apple TV the current picture of the person who pushed the button? I usually get the snapshot of whatever motion had previously been detected or the previous button push (i.e. whatever is showing up in the Home app prior to pressing the doorbell). But something I can happily live with given that I now get the HomePod chimes.

I get a live picture.

Your account doesn’t lock when you have push enabled?

[PeterAlexander75]

Just curious if there’s any chance Eufy would open source the driver for this? Obviously Apple won’t open source their end, but have the endpoints been discovered? Perhaps through examining other HomeKit compatible cam manufacturer’s software/hardware? Excuse my ignorance if these are dumb questions. …

I doubt that but I did wonder whether the Alexa skill could be used as a basis for fixing the account authentication issues. Although, the Alexa skill itself is garbage - motion and rings are often really delayed.

[CameronSmith93]

push is working - including chimes on HomePods and also, rather excitingly, Apple TV. Let us hope the account doesn't lock, as this is now a working plugin.

Out of interest, is the picture that shows up on your Apple TV the current picture of the person who pushed the button? I usually get the snapshot of whatever motion had previously been detected or the previous button push (i.e. whatever is showing up in the Home app prior to pressing the doorbell). But something I can happily live with given that I now get the HomePod chimes.

I get a live picture.

Your account doesn’t lock when you have push enabled?

Confirming that I have push enabled and my account is not locked.

Interesting that you get the live picture, mine is always the picture of the previous press. And there I have about a 3-5 second delay in the HomePod chime/Apple TV/HomeKit notification. My HomeBase 2 is on Wi-Fi, not Ethernet, so perhaps that has something to do with it.