-
Notifications
You must be signed in to change notification settings - Fork 54
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
Receiving a second incorrect Mqtt message #61
Comments
Hi, thats the designed behaviour and also mentioned in the documentation:
You have to evaluate the payload of the mqtt topic, not only do stuff when the topic was sent. |
As mqtt is usally more event based and it's easier to work with if you just have all values available I've personally added a new topic
This way I can do easily things like |
Hi,
first of all, thanks a lot for this amazing project. I have the following problem:
When the finger is placed on the sensor and removed I always receive a the correct mqtt messages, with
lastLogMessages, ring, matchId, matchName, matchConfidence
always filled with the correct values.
3 seconds later I always receive another set of messages always not recognized and always without lastLogMessages so only:
ring, matchId, matchName, matchConfidence
In the grey div of http://fingerprintdoorbell/ I only see the correct message not the unrecognized one 3 seconds later. The problem seems to be only in mqtt.
I've already tried to factory reset but no luck. Maybe I'm overlooking something and someone can help me out.
Thanks for your help.
The text was updated successfully, but these errors were encountered: