Bug with Beurer BF700 - Githubissues

maniackcrudelis commented 4 years ago

Describe the bug The app seems to work and show the weight, received from the scale. But nothing is stored. I have to try many times to finally have my data stored.

To Reproduce Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Reproduced with latest dev version: ??? I use the version 2.1.2(47), from FDroid.

Expected behavior I expect data to be stored when I connect the app to the scale.

Additional context Add any other context about the problem here.

Debug log

2020-02-23 23:12:01.222 Debug [2] AboutPreferences: Debug log enabled, openScale v2.1.2 (47), SDK 28, Sony I4113
2020-02-23 23:12:01.226 Debug [2] AboutPreferences: Selected user id(1) name(***) birthday(***) age(***) body height(***) scale unit(kg) gender(***) initial weight(***) goal weight(***) goal date(***) measure unt(cm) activity level(***)
2020-02-23 23:12:04.921 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: ***
2020-02-23 23:12:06.889 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: ***
2020-02-23 23:12:07.132 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: ***
2020-02-23 23:12:08.261 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: ***
2020-02-23 23:12:09.359 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: ***
2020-02-23 23:12:10.514 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: ***
2020-02-23 23:12:11.612 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: ***
2020-02-23 23:12:13.060 Info [2] BluetoothBeurerSanitas: Active measurement, stable weight: ***
2020-02-23 23:12:14.465 Info [2] BluetoothBeurerSanitas: Active measurement, stable weight: ***
2020-02-23 23:12:19.631 Debug [2] BluetoothCommunication: Invoke write bytes [E7 F1 59 03 01] on 0xffe1
2020-02-23 23:12:19.659 Debug [2] BluetoothPeripheral: writing <e7f1590301> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-02-23 23:12:19.767 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 F1 59 03 01> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-02-23 23:12:19.768 Debug [2] BluetoothCommunication: Step Nr 8
2020-02-23 23:12:19.768 Debug [2] BluetoothCommunication: Invoke delayed disconnect in 60s
2020-02-23 23:12:19.869 Debug [2] BluetoothCommunication: Invoke write bytes [E7 F1 59 03 02] on 0xffe1
2020-02-23 23:12:19.886 Debug [2] BluetoothPeripheral: writing <e7f1590302> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-02-23 23:12:20.008 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 F1 59 03 02> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-02-23 23:12:20.009 Debug [2] BluetoothCommunication: Step Nr 8
2020-02-23 23:12:20.009 Debug [2] BluetoothCommunication: Invoke delayed disconnect in 60s
2020-02-23 23:12:20.124 Error [2] BluetoothBeurerSanitas: java.lang.NullPointerException: Attempt to read from field 'int com.health.openscale.core.bluetooth.BluetoothBeurerSanitas$RemoteUser.localUserId' on a null object reference
    at com.health.openscale.core.bluetooth.BluetoothBeurerSanitas.processMeasurementData(BluetoothBeurerSanitas.java:350)
    at com.health.openscale.core.bluetooth.BluetoothBeurerSanitas.processMeasurement(BluetoothBeurerSanitas.java:401)
    at com.health.openscale.core.bluetooth.BluetoothBeurerSanitas.onBluetoothNotify(BluetoothBeurerSanitas.java:282)
    at com.health.openscale.core.bluetooth.BluetoothCommunication$1.onCharacteristicUpdate(BluetoothCommunication.java:343)
    at com.welie.blessed.BluetoothPeripheral$1$7.run(BluetoothPeripheral.java:534)
    at android.os.Handler.handleCallback(Handler.java:873)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:280)
    at android.app.ActivityThread.main(ActivityThread.java:6744)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

oliexdev commented 4 years ago

There is something wrong with the user. Could you do a full reset on the scale and in the app and initialize the scale again?

maniackcrudelis commented 4 years ago

Sorry for the late answer, I did some tests First I reset the scale only and it seems to work, but only once actually... After that the same behavior happened.

So I did reset both the scale and the app. But since then, that's even worse since the scale doesn't recognize me anymore and there's still no data saved into the app

2020-03-02 20:05:19.058 Debug [2] MainActivity: Bluetooth connection successful established
2020-03-02 20:05:19.240 Debug [2] BluetoothCommunication: SUCCESS: Notify set for 0000ffe1-0000-1000-8000-00805f9b34fb
2020-03-02 20:05:19.241 Debug [2] BluetoothCommunication: Resume machine state
2020-03-02 20:05:19.242 Debug [2] BluetoothCommunication: Step Nr 1
2020-03-02 20:05:19.243 Debug [2] BluetoothCommunication: Invoke write bytes [E6 01] on 0xffe1
2020-03-02 20:05:19.243 Debug [2] BluetoothCommunication: Stop machine state
2020-03-02 20:05:19.247 Debug [2] BluetoothPeripheral: writing <e601> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:19.329 Debug [2] BluetoothCommunication: SUCCESS: Writing <E6 01> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:19.420 Debug [2] BluetoothBeurerSanitas: Got init ack from scale; scale is ready
2020-03-02 20:05:19.422 Debug [2] BluetoothCommunication: Resume machine state
2020-03-02 20:05:19.422 Debug [2] BluetoothCommunication: Step Nr 2
2020-03-02 20:05:19.423 Debug [2] BluetoothCommunication: Invoke write bytes [E9 5E 5D 58 EF] on 0xffe1
2020-03-02 20:05:19.424 Debug [2] BluetoothCommunication: Step Nr 3
2020-03-02 20:05:19.425 Debug [2] BluetoothCommunication: Invoke write bytes [E7 4F 00 00 00 00 00 00 00 00] on 0xffe1
2020-03-02 20:05:19.426 Debug [2] BluetoothCommunication: Stop machine state
2020-03-02 20:05:19.429 Debug [2] BluetoothPeripheral: writing <e95e5d58ef> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:19.509 Debug [2] BluetoothCommunication: SUCCESS: Writing <E9 5E 5D 58 EF> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:19.513 Debug [2] BluetoothPeripheral: writing <e74f0000000000000000> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:19.599 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 4F 00 00 00 00 00 00 00 00> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.050 Debug [2] BluetoothBeurerSanitas: Battery level: 100; threshold: weight=2.00, body fat=2.00; unit: 1; requested user: exists=false, has reference weight=false, has measurement=false; scale version: 5
2020-03-02 20:05:20.052 Debug [2] BluetoothCommunication: Resume machine state
2020-03-02 20:05:20.054 Debug [2] BluetoothCommunication: Step Nr 4
2020-03-02 20:05:20.055 Debug [2] BluetoothCommunication: Invoke write bytes [E7 33] on 0xffe1
2020-03-02 20:05:20.056 Debug [2] BluetoothCommunication: Stop machine state
2020-03-02 20:05:20.059 Debug [2] BluetoothPeripheral: writing <e733> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.139 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 33> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.320 Debug [2] BluetoothBeurerSanitas: Have 1 users (max is 8)
2020-03-02 20:05:20.409 Debug [2] BluetoothBeurerSanitas: Received user 1/1: DOR (1984)
2020-03-02 20:05:20.410 Debug [2] BluetoothCommunication: Invoke write bytes [E7 F1 34 01 01] on 0xffe1
2020-03-02 20:05:20.417 Debug [2] BluetoothBeurerSanitas: Remote user DOR (0x65) is local user Dorian (1)
2020-03-02 20:05:20.420 Debug [2] BluetoothCommunication: Resume machine state
2020-03-02 20:05:20.421 Debug [2] BluetoothCommunication: Step Nr 5
2020-03-02 20:05:20.422 Debug [2] BluetoothBeurerSanitas: Request saved measurements for DOR
2020-03-02 20:05:20.424 Debug [2] BluetoothCommunication: Invoke write bytes [E7 41 00 00 00 00 00 00 00 65] on 0xffe1
2020-03-02 20:05:20.425 Debug [2] BluetoothCommunication: Stop machine state
2020-03-02 20:05:20.429 Debug [2] BluetoothPeripheral: writing <e7f1340101> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.499 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 F1 34 01 01> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.503 Debug [2] BluetoothPeripheral: writing <e7410000000000000065> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.590 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 41 00 00 00 00 00 00 00 65> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.679 Debug [2] BluetoothBeurerSanitas: No saved measurements found for user DOR
2020-03-02 20:05:20.680 Debug [2] BluetoothCommunication: Jump next to step nr 5
2020-03-02 20:05:20.681 Debug [2] BluetoothCommunication: Resume machine state
2020-03-02 20:05:20.682 Debug [2] BluetoothCommunication: Step Nr 5
2020-03-02 20:05:20.683 Debug [2] BluetoothCommunication: Step Nr 6
2020-03-02 20:05:20.684 Debug [2] BluetoothCommunication: Step Nr 7
2020-03-02 20:05:20.686 Debug [2] BluetoothCommunication: Invoke write bytes [E7 36 00 00 00 00 00 00 00 65] on 0xffe1
2020-03-02 20:05:20.687 Debug [2] BluetoothCommunication: Stop machine state
2020-03-02 20:05:20.690 Debug [2] BluetoothPeripheral: writing <e7360000000000000065> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.770 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 36 00 00 00 00 00 00 00 65> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:20.859 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 29.85
2020-03-02 20:05:21.765 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 73.35
2020-03-02 20:05:22.889 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 73.90
2020-03-02 20:05:24.007 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 74.30
2020-03-02 20:05:25.156 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 74.45
2020-03-02 20:05:26.247 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 74.45
2020-03-02 20:05:27.352 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 74.45
2020-03-02 20:05:28.604 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 74.45
2020-03-02 20:05:29.596 Debug [2] BluetoothBeurerSanitas: Active measurement, weight: 74.45
2020-03-02 20:05:31.055 Info [2] BluetoothBeurerSanitas: Active measurement, stable weight: 74.45
2020-03-02 20:05:32.455 Info [2] BluetoothBeurerSanitas: Active measurement, stable weight: 74.45
2020-03-02 20:05:37.256 Debug [2] BluetoothCommunication: Invoke write bytes [E7 F1 59 03 01] on 0xffe1
2020-03-02 20:05:37.263 Debug [2] BluetoothPeripheral: writing <e7f1590301> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:37.347 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 F1 59 03 01> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:37.448 Debug [2] BluetoothCommunication: Invoke write bytes [E7 F1 59 03 02] on 0xffe1
2020-03-02 20:05:37.455 Debug [2] BluetoothPeripheral: writing <e7f1590302> to characteristic <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:37.549 Debug [2] BluetoothCommunication: SUCCESS: Writing <E7 F1 59 03 02> to <0000ffe1-0000-1000-8000-00805f9b34fb>
2020-03-02 20:05:37.650 Error [2] BluetoothBeurerSanitas: java.lang.NullPointerException: Attempt to read from field 'int com.health.openscale.core.bluetooth.BluetoothBeurerSanitas$RemoteUser.localUserId' on a null object reference
    at com.health.openscale.core.bluetooth.BluetoothBeurerSanitas.processMeasurementData(BluetoothBeurerSanitas.java:350)
    at com.health.openscale.core.bluetooth.BluetoothBeurerSanitas.processMeasurement(BluetoothBeurerSanitas.java:401)
    at com.health.openscale.core.bluetooth.BluetoothBeurerSanitas.onBluetoothNotify(BluetoothBeurerSanitas.java:282)
    at com.health.openscale.core.bluetooth.BluetoothCommunication$1.onCharacteristicUpdate(BluetoothCommunication.java:343)
    at com.welie.blessed.BluetoothPeripheral$1$7.run(BluetoothPeripheral.java:534)
    at android.os.Handler.handleCallback(Handler.java:873)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:280)
    at android.app.ActivityThread.main(ActivityThread.java:6744)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

oliexdev commented 4 years ago

Looks fine until the last error with the localUserId.

Could you reset everything (app and scale) and register again while your logging in openScale? I want to check if the user creation works fine and please post the full log file.

maniackcrudelis commented 4 years ago

Ok, so I reset both scale and app, recreate an user, with default values and it worked... I reset again the app (not the scale) and recreate my common user, still working...

Finally I didn't reproduce for now. Last time I did it, it worked at first and failed later. We'll see... Anyway, here the log of my last reset: https://crudelis.fr/zerobin/?8c2c2b2bbe9db8e2#2PdDcouN9tfSTlmPe23M8npOWSMhZ4bvNUGIOeKANi4=

oliexdev commented 4 years ago

Did you use an empty user name in openScale or did you delete it in the log file? Also how many users did you have in openScale? More than one?

maniackcrudelis commented 4 years ago

Into my last log, I didn't use an empty user nor remove it from the log. But after the reset, I didn't create an user at first, to enable the log. Then, I went back to the user list to create the user.

I only had 1 user all long.

oliexdev commented 4 years ago

ok then your log file makes sense because in the log file your user name were empty and the user id mismatched with the scale user id.

I will close this issue until your problem occurs again.

maniackcrudelis commented 4 years ago

You won't have to wait long before the problem occurs again... Just used it and again, the scale does not recognize the user. And so the app does not store any data. Here the log: https://crudelis.fr/zerobin/?5908914afd717e5c#MEIqtc7BG0JOIcZN+HbKFv23akslf2NVyKmZGW4Kb+A=

Note that this time I didn't reset anything, just used the app, connected to the scale and used it.

oliexdev commented 4 years ago

It seems openScale wants to create again the user on the scale!? I am not sure but did you connect to the scale in the initialization process without an openScale user?

Your log files are very strange....

In your first log:

At first no user is created in openScale
Even if you reset your scale, openScale found a user on the scale Received user 1/1: USE (2000) So I assume your scale was not fully reset.
You created a user a user on the scale Create user: Dorian

second log file:

no users were found on the scale
openScale want to create a user on the scale but won't success (because there is already a user)

Are you using in parallel the vendors app or another app? It is again something wrong with yours user creation process? Did your scale work with the vendors app?

maniackcrudelis commented 4 years ago

First, to answer yours questions: I never used the vendor app. So I can't tell if it works with it or not. Not using any other app either. When creating the user, nothing seems to go wrong.

Ok, I reset everything again, and here step by step what I'm doing:

I start the app, which ask me to create an user.
Once the user created, I turn on the logging.
Turn on Bluetooth and GPS
Add the scale into the Bluetooth menu of the app.
Connect the app to the scale (with the Bluetooth button on the upper side of the app)
Wait for the app to connect and use the scale.
Everything's ok. Note that it usually works until then. The problem is more about what's going on after that.

After 5 minutes, Bluetooth and GPS turned off. I retried:

Start the app, Bluetooth turned on by the app.
I wait for the app to connect to the scale. (I quickly saw the error message about the max number of concurrent users)
The scale recognize the user and works as expected.
Nothing stored into the app, but I expect it's because of the 5 minutes only since the last measurement.

I'll retry this evening or tomorrow but don't expect it to work, since it always works fine at first but not after.

oliexdev commented 4 years ago

I'm at a bit of a loss. If you have reset the scale, you shouldn't see the max number of concurrent users error!? Just to be sure, did you really reset the scale? You have to push the reset button on the scale until a del message occurred on the scale display.

maniackcrudelis commented 4 years ago

That's indeed what I do. Also there's only one button on this scale. So I turned it on, hit the button until it says "del" Actually, the scale says that since the beginning, even if I never created more than 2 different users.

maniackcrudelis commented 4 years ago

Same behavior today than previously, the app connect to the scale, says the same error message about max number of concurrent users. Then the scale does the job, but nothing is stored into the app.

https://crudelis.fr/zerobin/?74cda247b6c0b788#fSdMjog3TuIdRpj4mK0v3AXWVwwX4geqf+FJsTHzfC4=

roerch commented 4 years ago

I am also affected by this bug. Same scale, same problem. Initialization has been done with this app, the vendors app was never installed. After two measurements I get the above error about maximum number of users on scale. Having a very quick look at the code it seems to me like the user defined in the app is never found on the scale and every time a new user is created (maybe it is as simple as a 'off by one' bug. Is there a way to debug this process of querying for the user, like logging it to the debug log?

maniackcrudelis commented 4 years ago

@oliexdev would you mind considering reopen this issue, as it's not solved. Also if there's anything else I could do to help find what the problem is, let me know. I would really love to eventually use the scale and this app.

roerch commented 4 years ago

Just as a follow-up here: In Issue #565 there is a reference to a comment in the Play Store with a working hint. Turning on the GPS before starting the app and connecting to the scale fixes the problem for me. Seems to be a permission issue.

gnaghi commented 3 years ago

@oliexdev : I have the same bug, with the latest version (openScale v2.3.1).

If I try multiple time (at least 6 or 7 times), without changing anything, the record is stored. The bug occured today, but the software has been working without error for 2 months, and I didn’t change anything on my phone.

It seems currentRemoteUser.localUserId get erased before going to the processSavedMeasurement function. Looks like a race condition when fetching information and saving weight at the same time.

Edit : I tested again, and it is likely a race bug, because I had no error, and strangely, all my previous (failed) records apperead.

oliexdev / openScale

Bug with Beurer BF700 #552