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

[Bug]: Eufy Indoor Cam 2k alarm state issue #38

Closed
njuart opened this issue May 24, 2022 · 22 comments
Closed

[Bug]: Eufy Indoor Cam 2k alarm state issue #38

njuart opened this issue May 24, 2022 · 22 comments
Labels
bug Something isn't working depends on eufy-security-client the solution to this issue relies on a change in bropats eufy-security-client library fixed in beta / next release this is a resolved issue which is fixed in current beta and will be fixed in next release

Comments

@njuart
Copy link

njuart commented May 24, 2022

What happened?

Hi, I have both Homebase 2 and Eufy Indoor Cam 2k. When I change alarm state for example from Away to Home in HomeKit, I see that alarm state of Indoor Cam doesn't change, it changes only after I manually open Eufy App and check state there. After this state of Indoor Cam in HomeKit changes immediately. With Homebase 2 I don't have this problem, it's alarm state changes at once. Any ideas? Thx

Device Type

Indoor Camera (Supported)

Plugin Version

beta (Best Effort)

HomeBridge Version

v1.4.x (Supported)

NodeJS Version

v16 (Supported)

Operating System

Raspbian 10+ (Supported)

Relevant log output

No response

@njuart njuart added the bug Something isn't working label May 24, 2022
@github-actions
Copy link

Did you check this Common Issues pages ?

@thieren
Copy link
Contributor

thieren commented May 28, 2022

As discussed in #39

Yes it occurs every time, but on earlier betas it was ok. When I arm it doesn't show it's armed at all, after I open Eufy app and refresh, it becomes armed. And when I disarm it hangs in arming state. Honestly I'm not sure if it hangs indefinitely, maybe a couple of times it was disarmed by itself, maybe after few minutes or so.

@njuart Can you specify on which version of the plugin it was working?
Also can you supply log output with debug enabled? Your config without the personal information would also be helpful. Thanks!

@njuart
Copy link
Author

njuart commented May 29, 2022

As discussed in #39

Yes it occurs every time, but on earlier betas it was ok. When I arm it doesn't show it's armed at all, after I open Eufy app and refresh, it becomes armed. And when I disarm it hangs in arming state. Honestly I'm not sure if it hangs indefinitely, maybe a couple of times it was disarmed by itself, maybe after few minutes or so.

@njuart Can you specify on which version of the plugin it was working? Also can you supply log output with debug enabled? Your config without the personal information would also be helpful. Thanks!

Sorry, but not sure I can recall on which beta exactly it was working. Here's what log shows:

image

  1. I've armed Camera to Away from Home app
  2. Saw infinite arming state
  3. (Red arrow pointer) It's when I've opened Eufy app and refreshed Security tab
  4. After I got back to Home app state was set to Away

@lenoxys
Copy link
Contributor

lenoxys commented May 29, 2022

Hello, I've the same issue on my setup. When arming we send a request to arm to the camera then we wait to receive the arming notification which can happend minutes after the ask. I don't see anything we can implement in order to force it. This issue is only related to camera operating their own alarm system. I don't have this issue with the homebase.

@njuart
Copy link
Author

njuart commented May 29, 2022

Hello, I've the same issue on my setup. When arming we send a request to arm to the camera then we wait to receive the arming notification which can happend minutes after the ask. I don't see anything we can implement in order to force it. This issue is only related to camera operating their own alarm system. I don't have this issue with the homebase.

Yes, with Homebase it's fine. But I'm pretty sure it was working fine some time ago.

@thieren
Copy link
Contributor

thieren commented May 29, 2022

Yes, with Homebase it's fine. But I'm pretty sure it was working fine some time ago.

Well since I don't own a solo camera I have difficulties to help here.
From looking through the code there is not much going on. We're doing exactly one thing and that is to give the command to the eufy-security-client package and then wait. I don't believe that this was changed much in the earlier versions but didn't have a closer look.
Honestly there are a myriad of things that could've changed that could cause your issue (software updates from eufy, maybe an update in the eufy-security-client dependency, ...) but as mentioned I don't believe that the cause is in this plugin.

You can revert to earlier version of the plugin and test if it has another behavior. Maybe then I can find a difference in the code bases.

@thieren
Copy link
Contributor

thieren commented May 30, 2022

I've added a log message that should be triggered if the mode change isn't done.

It's part of 2.0.1-beta.2. Until it's published you could download it directly from the repo.

Then there will be exactly one retry. But as stated before in #39 and from the information given I don't believe that the retry will do any good.

Please report if this helps.

@njuart
Copy link
Author

njuart commented May 30, 2022

I've added a log message that should be triggered if the mode change isn't done.

It's part of 2.0.1-beta.2. Until it's published you could download it directly from the repo.

Then there will be exactly one retry. But as stated before in #39 and from the information given I don't believe that the retry will do any good.

Please report if this helps.

Didn't help unfortunately. There is a timeout =( Even after retry.

@thieren
Copy link
Contributor

thieren commented May 30, 2022

Didn't help unfortunately. There is a timeout =( Even after retry.

Yeah, I expected that really.

I suppose there is a power management setting in the eufy app. Could you test whether different settings have different results in the homebridge behavior?

@njuart
Copy link
Author

njuart commented May 30, 2022

Hmm, didn't find any in Eufy app. Maybe because my Indoor 2k is wired.

@thieren
Copy link
Contributor

thieren commented May 31, 2022

Ok, another try.

I've hacked a eufy-test-client application which shall help me debug some issues in the future. For now there are only two options to change guard mode.

You can find it here: https://github.com/thieren/eufy-test-client
It's just quick and dirty, so don't expect too much.

Can you try something with this please?

  1. If you use the standard 'change guard mode' option, you should get the same result as with the plugin.
  2. The alternative option is a clutch at a straw to get this working for you.

Please report back, if this does anything for you.

@njuart
Copy link
Author

njuart commented May 31, 2022

Ok, another try.

I've hacked a eufy-test-client application which shall help me debug some issues in the future. For now there are only two options to change guard mode.

You can find it here: https://github.com/thieren/eufy-test-client

It's just quick and dirty, so don't expect too much.

Can you try something with this please?

  1. If you use the standard 'change guard mode' option, you should get the same result as with the plugin.

  2. The alternative option is a clutch at a straw to get this working for you.

Please report back, if this does anything for you.

Wow, thx. Not sure if I'll be near computer today, so probably tmrw. Maybe @lenoxys can assist you also, as he reported the same issue for him a bit a above in this thread.

@njuart
Copy link
Author

njuart commented May 31, 2022

@thieren Hey, again. Luckily managed to do it today and got the log. So:

  1. I've changed Camera guard mode to 0 (AWAY) via your client (standard option)
  2. After few minutes opened Home app, nothing changed there (as expected unfortunately)
  3. Opened Eufy app, Camera guard mode there was already AWAY, which I suppose means that it was successfully changed via your client
  4. After it opened Home app again and status there was also AWAY this time

Here's the log
eufylog_1654003655751.txt

@thieren

This comment was marked as off-topic.

@njuart

This comment was marked as off-topic.

@thieren

This comment was marked as off-topic.

@thieren

This comment was marked as off-topic.

@njuart

This comment was marked as off-topic.

@njuart

This comment was marked as off-topic.

@thieren

This comment was marked as off-topic.

@thieren thieren added the wontfix This will not be worked on label Jun 1, 2022
@thieren
Copy link
Contributor

thieren commented Jun 1, 2022

Confirmed with @njuart that this is not a plugin issue, but rather with eufy-security-client
Maybe @bropat can do something about this.

Closed.

@thieren
Copy link
Contributor

thieren commented Jul 18, 2022

Should be fixed with latest beta.

@thieren thieren added fixed in beta / next release this is a resolved issue which is fixed in current beta and will be fixed in next release depends on eufy-security-client the solution to this issue relies on a change in bropats eufy-security-client library and removed wontfix This will not be worked on labels Jul 18, 2022
@thieren thieren mentioned this issue Sep 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working depends on eufy-security-client the solution to this issue relies on a change in bropats eufy-security-client library fixed in beta / next release this is a resolved issue which is fixed in current beta and will be fixed in next release
Development

No branches or pull requests

3 participants