-
Notifications
You must be signed in to change notification settings - Fork 52
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
No match found (Code 2) and no ringing #58
Comments
Hi, the line you mentioned is to block duplicate or multiple ring events in a row e.g. if somebody holds the finger on a sensor for a long time (or a water drop is on the sensor). The ring event then will only be raised again after a scanResult ="no Finger" case was detected first. How is your bell triggered? By wire through one of the GPIOs or by mqtt messages? Maybe the problem for your missing ring events is located there? I had a similar problem in past caused by a defective optocoupler wired on the GPIO. |
Hello, thanks for your reply. This may be part of the issue. I have now logged the mqtt events while pressing several times with known and unknown fingers:
The Bell did never ring. The distance between ESP and Relay is 8m... Do you think, this may be part of the reason? Greetings, |
Hello,
for some reason, I sometimes get No match found (Code 2) and the bell does not ring.
I think, this must be due to this line:
FingerprintDoorbell/src/main.cpp
Line 564 in 53833b0
But I do not understand the reason for this line - and also not, why my bell is not ringing... The family is getting a bit annoyed :-(
What I also do not undertand: Even if I ensure that lastMatch is different, as it was my known finger rather than an unknown one, I get this message.
I.e.:
unknown finger -- No match found (Code 2)
known finger -- door opens
unknown finger -- No match found (Code 2)
It was working well for some weeks though...
Greetings,
Hendrik
The text was updated successfully, but these errors were encountered: