-
Notifications
You must be signed in to change notification settings - Fork 83
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
Doorbell not always triggering #286
Comments
@denniedegroot - this issue is being automatically closed because it does not follow either the feature request or bug report issue template. The issue templates have been designed to help in the troubleshooting (or feature request) process. Please use them and populate it as completely as possible to streamline troubleshooting or feature request discussions. |
Appreciate it. It’s a recent change that occurred in the last two revisions for Protect. This is already fixed in my tree and will be in a future update. Thanks! |
This issue is locked to prevent necroposting on closed issues. Please create a new issue for related support requests, bug reports, or feature suggestions. |
Describe The Problem:
The G4 doorbell is not always triggering. This is due to the following line:
homebridge-unifi-protect/src/protect-nvr-events.ts
Line 212 in 3552015
A payload can contain both a lastMotion and lastRing object. So the "return" needs to be deleted.
To Reproduce:
Dance before the G4 Doorbell and press the button.
Logs:
Both JSON messages when a doorbell is pressed with and without motion detected:
The text was updated successfully, but these errors were encountered: