recallfx / node-red-contrib-eufy-security

Eufy security node for Node RED
MIT License
6 stars 6 forks source link

Connection Problem #18

Closed bmshine closed 1 year ago

bmshine commented 2 years ago

The node always shows connecting. If i start the node i get the following: 25.11.2022, 23:15:35 msg : string[14] "Generic Error:" 25.11.2022, 23:15:36 msg : string[11] "Token error" Is there a way to fix it? BR Markus

markcudok commented 1 year ago

Hi Markus, I got the same error, looks like this problem started when I upgraded Node-RED to 13.5.3.

jageerdarjaggy commented 1 year ago

I still have this problem. strangely enough, it suddenly started to work and continued to develop my flow. and then suddenly it stopped , no change to node-red or anything, but just stopped and started getting "token error" what can i do?

jageerdarjaggy commented 1 year ago

something to do with tokens when logging in.... not sure why it suddenly started to work and then stopped again after couple of hours... any help ?

bmshine commented 1 year ago

Maybe it will work if the libraries (eufy-security-client) are updated to the newest version (2.3.0) Right now an very old version is used. I have tried to replace it, but it doesn't looks compatible. :(

jageerdarjaggy commented 1 year ago

I have also installed the latest version of eufy-client libraries,but no change

On Wed, 7 Dec 2022, 09:51 bmshine, @.***> wrote:

Maybe it will work if the libraries (eufy-security-client) are updated to the newest version (2.3.0) Right now an very old version is used. I have tried to replace it, but it doesn't looks compatible. :(

— Reply to this email directly, view it on GitHub https://github.com/recallfx/node-red-contrib-eufy-security/issues/18#issuecomment-1340117442, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4TBPPI4IYETEB4G6U57QOLWL67OJANCNFSM6AAAAAASLUZJMA . You are receiving this because you commented.Message ID: @.***>

itb3 commented 1 year ago

same issue here. stopped working with "generic error: token error", started working again at some point after restarting flows etc (do not know when exactly, tried a lot), but stopped working again after a few hours. now several days of consistent "token error". restarting flows, node-red or machine does not help.

jageerdarjaggy commented 1 year ago

I think the original developer is no longer maintaining it. This was a good solution but as with most opensource contrib solutions, things get abandoned

On Sat, 17 Dec 2022, 10:53 Iwan Bron, @.***> wrote:

same issue here. stopped working with "generic error: token error", started working again at some point after restarting flows etc (do not know when exactly, tried a lot), but stopped working again after a few hours. now several days of consistent "token error". restarting flows, node-red or machine does not help.

— Reply to this email directly, view it on GitHub https://github.com/recallfx/node-red-contrib-eufy-security/issues/18#issuecomment-1355844107, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4TBPPLTQPCC2DXNDNAPRKLWNT6GHANCNFSM6AAAAAASLUZJMA . You are receiving this because you commented.Message ID: @.***>

Sprocket02 commented 1 year ago

That's too bad. Does anyone have this running for them now? Looking for a solution for OpenHAB.

jageerdarjaggy commented 1 year ago

Nope, no integration for now

On Mon, 26 Dec 2022, 17:22 Sprocket, @.***> wrote:

That's too bad. Does anyone have this running for them now? Looking for a solution for OpenHAB.

— Reply to this email directly, view it on GitHub https://github.com/recallfx/node-red-contrib-eufy-security/issues/18#issuecomment-1364928950, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4TBPPO5QQMIX6YYTFNESETWPE2R7ANCNFSM6AAAAAASLUZJMA . You are receiving this because you commented.Message ID: @.***>

robertusw commented 1 year ago

Same problem here. No solution???

I use my Eyeful Security alarm system to trigger behavior of my entire Home Automation (Tado, Sonos, Hue, ....). The status of the alarm (Off, Home, Away, Long Away) switches my smart devices through NodeRed. Because the Eufy Security integration no longer works my smart home system is also broken (sort of). Looked to switch over to Homey Pro but read there same problems with (official) apps made by Atom that are updated (for example Tado) and lost important functionality.

Let's hope that somebody makes a new integration?!

jageerdarjaggy commented 1 year ago

Utterly disappointing...

On Sun, 15 Jan 2023, 19:39 robertusw, @.***> wrote:

Same problem here. No solution???

I use my Eyeful Security alarm system to trigger behavior of my entire Home Automation (Tado, Sonos, Hue, ....). The status of the alarm (Off, Home, Away, Long Away) switches my smart devices through NodeRed. Because the Eufy Security integration no longer works my smart home system is also broken (sort of). Looked to switch over to Homey Pro but read there same problems with (official) apps made by Atom that are updated (for example Tado) and lost important functionality.

Let's hope that somebody makes a new integration?!

— Reply to this email directly, view it on GitHub https://github.com/recallfx/node-red-contrib-eufy-security/issues/18#issuecomment-1383090116, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4TBPPJGD3GPUQLF4OQBKK3WSOZSRANCNFSM6AAAAAASLUZJMA . You are receiving this because you commented.Message ID: @.***>

Leethal1977 commented 1 year ago

Hi - has anyone managed to get this working. Not overly experienced with node-red - managed to get it running in a Docker container, installed the eufy-security-client (not sure what else I need to do after installing?) but just get the "error", "generic error" or "token error" responses in the node-reg logs. Have been trying to get this working for a couple of days now and discovered this thread - any pointers would be very much appreciated!

recallfx commented 1 year ago

I have updated code with #21. In my case, the issue was with captcha request event, that was not handled, thus no messages. Now it will show directly on the node, if captcha/TFA or generic connection error happened.