-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
Ignore out of range data seems not to be working #1052
Comments
I'm having the same exact issue |
It seems like you're experiencing an issue where the openScale app is not correctly differentiating between the weight data from you and your partner. This could be due to the "Ignore out of range data" setting not working as expected. Here are a few suggestions that might help:
Regarding the Xiaomi Mi Scale v.1, it seems that the scale itself does not support multiple users¹³. The differentiation of users is done at the app level, not at the scale level. Therefore, the issue you're experiencing is likely related to the openScale app rather than the scale itself. I hope this helps! Let me know if you have any other questions. (1) Multiple users for Xiaomi Mi Body Composition Scale 2 : r/Xiaomi - Reddit. https://www.reddit.com/r/Xiaomi/comments/vb6pfu/multiple_users_for_xiaomi_mi_body_composition/. |
Hi, my use case is the following:
Both I and my partner are using the same smart scale.
In openScale, I have setup a single user, for myself, with details including average weight.
I have enabled Bluetooth > Ignore out of range data.
When using openScale to pull data from smartscale, all the readings are added my user, including those of my partner.
Between me and my partner there's a ~15Kg weight difference. I was expecting that since there's an obviously difference between the reading, only those within (some) deviation from my configured weight will be considered valid and added to DB.
Using openScale v2.5.2(64) with a Xiaomi Mi Scale v.1
ngs -> About -> Save debug log to file) that is captured while reproducing the issue.
The text was updated successfully, but these errors were encountered: