-
-
Notifications
You must be signed in to change notification settings - Fork 24
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]: Disarming Dufy Security Fails and Crashes Homebridge Server #52
Comments
Did you check this Common Issues pages ? |
Yes, I did. After reporting this bug I completely reinstalled the plugin and validated the behavior is the same. Wish the reinstall did the trick, but sadly it did not. |
Sure @thieren, here you go. Thanks for the response. I haven’t done anything fancy. Just mapped the HomeKit off status to the Eufy Disarmed status. { |
Hi @cms365
Where did you do that? I don't see anything in your config that represents that. From your config and the plugin code I can't see where the issue lies. Can you at least confirm that the latest beta prevents homebridge from crashing for you? |
It is weird you don’t see these configurations in the json. Before v2.0 I set these all up in the HomeBridge UI. Screenshot attached. |
Beta installed! Crash does seem to be resolved here. However, the guard state change is still failing. Here’s the log output: |
+1 to the above [02/06/2022, 15:18:03] InvalidPropertyValueError: Value "NaN" isn't a valid value for property "guardMode" |
Hi @cms365 have added a few debug messages in 2.0.1-beta.4 that should help in understanding this problem. Please ensure that you'll get the entire homebridge log after the last restart or at least one line from the startup that reads something like this: |
So I think I found a workaround, that admittedly I should have thought of sooner. I switched the mapping for HomeKit Off to another Eufy guard status, saved and rebooted. Then, switched it back to my desired Disarmed guard status, saved and rebooted. That resolved the issue for me and now everything works as expected! |
Hey @cms365 yeah that was my thought also but wanted first to confirm it with the debug log. Can you tell me to what values you have mapped it now? |
Sure, @thieren! Current mappings attached. Probably didn’t need the restarts but years of engineering work has trained me to reboot for good measure haha. |
Can you provide your new json config? For me it is not really clear why the plugin crashed for you without this setting. |
Doing as @cms365 stated above (re-mapping disarm to something else, saving, rebooting, switching it back, saving and rebooting) worked for me as well. Config here: { (I blanked out username, password, country, and 'ignoreDevices') |
Finally could reproduce and fix in 2.0.1-beta11 Closing this. |
Thank you! |
Agree! Appreciate the eagerness to figure this out. Thank you! Keep up the awesome work! |
What happened?
When Eufy Security is switched from any status to disarmed/off from HomeKit, it fails and throws the below error. Also causes the HomeBridge server to crash and reboot. This issue did not exist prior to the 2.0 update.
Want to note that I love this plugin and am reporting this issue to help the community.
Device Type
Station (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v16 (Supported)
Operating System
Mac OS X 11+ (Supported)
Relevant log output
The text was updated successfully, but these errors were encountered: