search

oliexdev / openScale

Open-source weight and body metrics tracker, with support for Bluetooth scales
GNU General Public License v3.0
1.72k stars 298 forks source link

Problems with Sanitas SBF70 #319

Closed cherocee closed 6 years ago

cherocee commented 6 years ago

Hello, Many thanks for developing openscale. This development was the reason for my buyig the SBF70. At the time of my purchase I did not notice the issues with the SBF 70 - I was happy that is labelled as supported.

Since issue 252 was closed I am starting here a new issue. I hope this is fine.

I am experiencing problems with the Sanitas SBF70. I am using Android 7.0 Kernel 3.18.31

After going throrugh the different issues in this depository, I started with version 1.7.1 - hoping this would work with the SBF70. I could select the scale in the bluetooth settings - and weight readings were retrieved from the scale. No user was created in the balance. No further data were downloaded from the balance. I stepped on the scale three time with an interval of 1 minute in between.

Then I registered a user with the healthcoach app (after uninstalling openscale) weight and further reading were read out from the balance.

I could not obtain any reading with openscale 1.7.1.

Then I changed to the dev version dated 2018-08-20 19:26:52 UTC (obtained from https://github.com/oliexdev/openScale/releases). I could choose the sbf 70 from the bluetooth settings. , When try to retrieve any data, I could not get any readings either. Resetting the balanced did not help. When trying to retrieve data I did obtain in German something like "connection established", and than something like "connection lost" I tried in the dev version to create a bt log (https://forums.lenovo.com/t5/Moto-G5-Moto-G5-Plus/Bluetooth-BLE-problem-on-moto-G5/m-p/3961770/highlight/true#M18512) and subsequently an error log of openscale.

Can this be fixed? best che btsnoop_hci.log openScale_2018-08-27_12-37.txt

erijo commented 6 years ago

The openScale does not contain anything useful unfortunately. Please recreate it by first enabling the debug log, then going to settings -> bluetooth and search for your scale. Once found click on it and when the extra logging is done, go back to the main screen and click the bluetooth icon. Then disable logging once you get "connection lost" and resubmit the log here.

cherocee commented 6 years ago

Thanks for your prompt reply. Sorry for my late answer - currently I am on night shift. With active debug logging I do obtain a dialog box "Fetching info, please wait while we fetch extended info from you scale". In my first attempts the screen lock became active after som seconds and the screen turned black. When unlocking the screen with the fingerprint sensor the dialog box was gone. But I could not find any additional information on the scale in the logfile. So I set the display lock to five minute. I am not sure what my Moto G5 Plus does - because the screen turns black anyway. But after unlocking it the device with the fingerprint sensor the dialog box was still visible. To move on, with deactivated screen lock, I activated the debug lock, searched for the bluetooth scale. After selecting the SBF70 I saw the dialog box "Fetching info, please wait while we fetch extended info from you scale" waited for about 20 minutes and then cancelled it, but I did not see any bluetooth icon in the openscale main window. Please see attached screen shot. Then I deactivated the openscale log

For all the steps describe above I did create a bluetooth lock - this seems to be in hex and I do not know how to read it. Both log files and the screenshot are attached. Hope one of the is useful.

At the moment I am not sure how to proceed. Please advise

btsnoop_hci.log openScale_2018-08-29_12-42.txt screenshot_20180829-131137

cherocee commented 6 years ago

I just realized from one of my previous attempts this morning, when the "Fetching info, please wait while we fetch extended info from you scale" was terminated by the screenlog I could connect to the scale. The respective log file of this attempt is provided here. sorry for forgetting this previously. I hope it is not too messy this way. I should mention, that currently there is no user "registered" on the scale. previous attempts with the sanitad healthcoach app failed. thanks for your efforts. openScale_2018-08-29_12-32.txt

cherocee commented 6 years ago

under: https://www.amazon.de/Sanitas-Diagnosewaage-Vernetzung-Smartphone-K%C3%B6rperdaten/product-reviews/B00NABN36E (sorry about the German) I read that one customer calls himself "Kunde" was able to use this balance with openscale. That post is date Sept 13, 2017. I tried to use openScale 1,5,4. that was released in Aug 19, 2017. But that attempt did not succeed either. Might it be possible that Sanitas changed the BT communiation?

erijo commented 6 years ago

BLE on Android is, as far as I can tell, unfortunately a mess. Different phones needs different work-arounds to make it work.

Please try restarting your phone and changing the batteries in the scale to see if that makes any difference. You can also try pulling the power from the Samsung TV you have around.

If it still doesn't work, try clicking the bluetooth icon on the main screen. I have in some cases seen it disappear as on your screenshot, but it still there even if it isn't visible. Try clicking to the left of the "+" and see if that triggers any bluetooth communication.

If it still doesn't work, please install the original app and try to capture a btsnoop log when you do a measurement that is successfully transferred to the phone.

cherocee commented 6 years ago

Many thanks for you reply and your suggestion. I can not unplug the Samsung TV - it belongs to my neighbor.... I did as you suggested. After uninstalling the dev version of openscale, I restarted my phone, removed during the booting of the phone the battery from the scale and even reset the scale. After installation of the latest dev version of open scale, I created a user, selected the sanitas sbf70. this time the bluetooth icon was visible. However, not data were read out and no user was created on the scale.

I can not connect to the sbf70 with the original app anymore. I tried after restarting the phone and resetting the balance after battery removal. The scale is found and coupled, but I can not assign a user to this device. Accordingly no data are assigned to a registered user and not data is transferred to the phone. So there is no point to produce any btsnoop. This impairment of the communication between the original app and the balance seems to be the case ever since I fist connected to the sbf 70 for the first time with openscale. I was once able to connect with the original app to the scale and transfer data. The previous attempt with openscale failed. I feel the balance is bricked - I guess I should return it ASAP.

erijo commented 6 years ago

You can also go to the Bluetooth settings on your phone and remove the scale from the list of paired devices (if it's listed there).

If you have access to another phone you could try openScale on that and see if that works.

cherocee commented 6 years ago

Well, the scale is not listed under the aired bluetooth devices. For the pairng of the phone and the scale a key is required. There are three different floating around on different amazon sites, but from what I can tell none of them works. My old phone does not support the bluetooth required by openscale or healthcoach. I am reluctant of asking friends to install any apps on their phone they do not need. And ultimately I would appreciate the data on the current phone and do not have to be concerned that anything will not work with the next phone.
I went through the issue 252 and found your reply https://github.com/oliexdev/openScale/issues/252#issuecomment-392289201 to ReidarHH, He seems to be using a Moto G5. I do use a Moto G5 Plus. An a dev version provided on or briefly before May 25 worked for ReidarHH. Do you still have that dev version or could re-create it easyly from a git or snapshot of your development?

I feel it might be worth giving this version a trial.

ReidarHH commented 6 years ago

Hi Cherokee. I had a version that was working. But after an Android security update it stopped working. I think openscale is a great program. But I kind of gave up on using because of android and phone developers keep changing things so openscale stops working. I'm not able to help with the software (lack of knowledge about this area). If the app gets an update and works I definitely use it again.

oliexdev commented 6 years ago

it seems a Moto G5 specific issue. Do you have problems with other Bluetooth connections with your smartphone? Are you asked for granting Bluetooth permissions when you have a fresh installed openScale? Some users on the internet reports problem after securtiy updates on the Moto G5 that they messed up the permissions on the smartphone.

ReidarHH commented 6 years ago

Hi. Just to clarify. My first problem was that the and phone only stay paired for 15 seconds and no data was retrieved. Then Erijo fixed the problem. And after the security updated I was back to the first problem. I have no other Bluetooth connection problems. Openscale connects with out any problems, it says connection established, but after 15 seconds it says connection lost.

I will attach the log from openscale below.

2018-09-18 09:02:09.031 Debug [1] AboutPreferences: Debug log enabled, openScale (dev) v1.8.1-dev_ef1632dc_2018-09-17 (1537198711), SDK 24, motorola Moto G (5)
2018-09-18 09:02:29.271 Debug [1] BluetoothPreferences: Start discovery
2018-09-18 09:02:29.306 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.adapter.action.DISCOVERY_STARTED
2018-09-18 09:02:34.828 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:37.651 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:37.678 Debug [1] BluetoothPreferences: Found supported device SANITAS SBF70 [C8:FD:19:9D:0B:68] (driver: Sanitas SBF70/SilverCrest SBF75, type: 2)
2018-09-18 09:02:37.719 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:37.867 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:37.906 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:37.921 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:37.976 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.033 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.086 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.149 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.157 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.200 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.315 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.474 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.530 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.588 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.614 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.646 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.767 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.918 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:38.970 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:40.351 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:41.721 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:41.777 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:43.148 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:43.187 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-09-18 09:02:48.589 Debug [1] BluetoothPreferences: Discovery: android.bluetooth.adapter.action.DISCOVERY_FINISHED
2018-09-18 09:02:48.592 Debug [1] BluetoothPreferences: Start LE scan
2018-09-18 09:02:49.861 Debug [1] BluetoothPreferences: Stop discovery
2018-09-18 09:02:49.871 Debug [1] BluetoothPreferences: Stop LE scan
2018-09-18 09:02:49.933 Debug [1] OpenScale: Trying to connect to bluetooth device [C8:FD:19:9D:0B:68] in debug mode
2018-09-18 09:02:49.947 Debug [1] BluetoothCommunication: BT is enabled, state=12, scan mode=21, is not discovering
2018-09-18 09:02:49.963 Debug [1] BluetoothCommunication: Starting LE scan for device [C8:FD:19:9D:0B:68]
2018-09-18 09:02:50.076 Debug [1] BluetoothCommunication: Found LE device SANITAS SBF70 [C8:FD:19:9D:0B:68]
2018-09-18 09:02:50.077 Debug [1] BluetoothCommunication: Stopping LE scan
2018-09-18 09:02:50.083 Info [1] BluetoothCommunication: Connecting to [C8:FD:19:9D:0B:68] (driver: Debug)
2018-09-18 09:02:50.513 Debug [10150] BluetoothCommunication$GattCallback: onConnectionStateChange: status=0, newState=2
2018-09-18 09:03:11.334 Debug [10151] BluetoothCommunication$GattCallback: onConnectionStateChange: status=8, newState=0
2018-09-18 09:03:11.337 Debug [1] OpenScale: Disconnecting from bluetooth device
2018-09-18 09:03:11.337 Info [10151] BluetoothCommunication: Disconnecting
2018-09-18 09:03:21.905 Debug [1] OpenScale: Trying to connect to bluetooth device [C8:FD:19:9D:0B:68] (SANITAS SBF70)
2018-09-18 09:03:21.917 Debug [1] BluetoothCommunication: BT is enabled, state=12, scan mode=21, is not discovering
2018-09-18 09:03:21.930 Debug [1] BluetoothCommunication: Starting LE scan for device [C8:FD:19:9D:0B:68]
2018-09-18 09:03:22.139 Debug [1] BluetoothCommunication: Found LE device SANITAS SBF70 [C8:FD:19:9D:0B:68]
2018-09-18 09:03:22.142 Debug [1] BluetoothCommunication: Stopping LE scan
2018-09-18 09:03:22.150 Info [1] BluetoothCommunication: Connecting to [C8:FD:19:9D:0B:68] (driver: Sanitas SBF70/SilverCrest SBF75)
2018-09-18 09:03:22.440 Debug [10150] BluetoothCommunication$GattCallback: onConnectionStateChange: status=0, newState=2
2018-09-18 09:03:22.451 Debug [1] MainActivity: Bluetooth connection successful established
2018-09-18 09:03:43.215 Debug [10159] BluetoothCommunication$GattCallback: onConnectionStateChange: status=8, newState=0
2018-09-18 09:03:43.218 Info [10159] BluetoothCommunication: Disconnecting
2018-09-18 09:03:43.225 Debug [1] MainActivity: Bluetooth connection lost
2018-09-18 09:03:47.301 Debug [1] OpenScale: Disconnecting from bluetooth device
2018-09-18 09:03:49.147 Debug [1] OpenScale: Trying to connect to bluetooth device [C8:FD:19:9D:0B:68] (SANITAS SBF70)
2018-09-18 09:03:49.161 Debug [1] BluetoothCommunication: BT is enabled, state=12, scan mode=21, is not discovering
2018-09-18 09:03:49.175 Debug [1] BluetoothCommunication: Starting LE scan for device [C8:FD:19:9D:0B:68]
2018-09-18 09:03:49.261 Debug [1] BluetoothCommunication: Found LE device null [48:E2:44:74:98:10]
2018-09-18 09:03:49.278 Debug [1] BluetoothCommunication: Found LE device null [48:E2:44:74:98:10]
2018-09-18 09:03:49.283 Debug [1] BluetoothCommunication: Found LE device SANITAS SBF70 [C8:FD:19:9D:0B:68]
2018-09-18 09:03:49.285 Debug [1] BluetoothCommunication: Stopping LE scan
2018-09-18 09:03:49.294 Info [1] BluetoothCommunication: Connecting to [C8:FD:19:9D:0B:68] (driver: Sanitas SBF70/SilverCrest SBF75)
2018-09-18 09:03:49.597 Debug [10150] BluetoothCommunication$GattCallback: onConnectionStateChange: status=0, newState=2
2018-09-18 09:03:49.607 Debug [1] MainActivity: Bluetooth connection successful established
2018-09-18 09:04:10.418 Debug [10159] BluetoothCommunication$GattCallback: onConnectionStateChange: status=8, newState=0
2018-09-18 09:04:10.421 Info [10159] BluetoothCommunication: Disconnecting
2018-09-18 09:04:10.432 Debug [1] MainActivity: Bluetooth connection lost
2018-09-18 09:04:20.656 Debug [1] AboutPreferences: Debug log disabled
oliexdev commented 6 years ago

I don't know why its always disconnected and as I don't own this scale I can't reproduce it. Additionally, we didn't change anything particular in the Bluetooth communication. So, since it began after a security update it guess it has to do something with the Android security system or timing problems with Motorola smartphones!? For example an older model has some Bluetooth issues or see here. You find a quite of similar problem reports with the Motorola smartphone. I don't know if this is the reason or not.

P.S.: please attach next time the log file on GitHub or paste the log file with code tags. Thanks in advance.

ReidarHH commented 6 years ago

Maybe it's only a Motorola issue. I have tried the above fixes but still the same issue. I don't have any other Bluetooth problem. Thank you for trying anyway.

oliexdev commented 6 years ago

Please create a btsnoop_hci.log with the original app, see step 1 in the wiki for how to do it.

Alejandro131 commented 6 years ago

Hello,

First I would like to thank you for the work you have done on this project and to note that for me it was the reason to buy SBF70 as well.

I can neither create a new user on a reset scale, nor get any readings (even simple weight) from it even with the development version of the project.

I'm using a Nexus 4 with android 8.1.0 - LineageOS version 15.1

I tried to do step 1 from the wiki, but since my only way to access the btsnoop_hci.log is through generating a bug report with adb bugreport bugreport.zip I can't seem to create 3 clean files so that it might be easier to look at them. I managed to get 1 file which includes the initial communication (from a reset scale) with the original app which creates a user, weighs it and returns the data, but there might be some trash in it.

What I gathered from the decimal site is somewhat inconclusive and I couldn't find the true date with the DCode tool since I wanted to make your job a little bit easier. This is a particular section that stood out to me with possible scale data:

0000   02 03 20 16 00 12 00 04 00 1b 22 00 e7 42 02 02   .. .......".çB..
0010   c4 01 4c 00 e4 05 e3 06 c5 00 ef                  Ä.L.ä.ã.Å.ï

The data that is used is: Username - ALE (dunno if it is lowercase or uppercase) gender - female height - 170 cm birth date - 4 oct 1993 activity level - probably 1 (but I didn't see if it was 3 since that was the default one on the app) weight - 69.2 kg - which I could find as b4 02 in 3 packets in the file bmi - 23.9 - which I found as ef at the end of the packet body fat - 29.4 - 26 01 which I couldn't find water - 45.2 - which I found as c4 01 in the upper packet muscle - 33.2 - 4c 01 which I couldn't find, but found 4c 00 in the packet above bone - 25.1 - fb which I couldn't find as well bmr - 1,507 cal amr - 1,733 kcal supposed true date of weighing - 10.04.2018 (4 oct, not 10 april) 02:29 pm utc +2:00

Hopefully this helps you resolve the issue and I can try to supply more data if needed, but can't guarantee that it would be a clean file.

btsnoop_hci.log

Edit: Also I forgot to mention that if there is some communication in between the user creation and weight / extra data, I saw in the original app there is a screen which shows the intermediate weight (which changes if you move, until you don't and doesn't change for some seconds) which was on the scale, so it seems that it is sent to the app as well and only after that it goes to the final screen with the final weight and more stats.

erijo commented 6 years ago

Can some of you please try the steps in #335?

kuleszdl commented 6 years ago

Hi folks,

first of all - many thanks for creating this great app!

I bought a SBF70 as well and wanted to report my experience with it.

My setup:

Issues discovered so far:

[1] https://www.howtoforge.com/tutorial/building-and-flashing-a-secured-aosp-build-with-verified-boot-and-separate-lockscreen-password-for-the-nexus-5x/

oliexdev commented 6 years ago

I will close this issue. Please continue in issue #341 if it still an issue

Olangu commented 5 years ago

I'm still facing this issue even in the dev version.

First it seem like we have a off by one issue in month. My user always has February as birthday, but scale says month 1.

Tried to change my openscale user but it still won't fetch the saved weights.

I'll attach one log from ordinary version and one from dev.

Olangu commented 5 years ago 
2018-11-24 13:02:49.598 Debug [2] AboutPreferences: Debug log enabled, openScale v1.8.3 (31), SDK 27, samsung SM-G960F
2018-11-24 13:02:50.109 Debug [2] BluetoothCommunication: Device not found in LE scan, connecting directly
2018-11-24 13:02:50.110 Info [2] BluetoothCommunication: Connecting to [50:8C:B1:57:E5:16] (driver: Sanitas SBF70/SilverCrest SBF75)
2018-11-24 13:02:54.147 Debug [558] BluetoothCommunication$GattCallback: onConnectionStateChange: status=0, newState=2
2018-11-24 13:02:54.149 Debug [2] BluetoothCommunication: Stopping LE scan
2018-11-24 13:02:54.171 Debug [2] MainActivity: Bluetooth connection successful established
2018-11-24 13:02:55.161 Debug [558] BluetoothCommunication$GattCallback: onServicesDiscovered: status=0 (5 services)
2018-11-24 13:02:56.166 Debug [2] BluetoothCommunication: INIT STATE: 0
2018-11-24 13:02:56.167 Debug [2] BluetoothCommunication: Set notification on for 0000ffe1-0000-1000-8000-00805f9b34fb
2018-11-24 13:02:56.170 Debug [2] BluetoothCommunication: Write descriptor 00002902-0000-1000-8000-00805f9b34fb: 01 00 (queue: 0 0)
2018-11-24 13:02:56.307 Debug [2] BluetoothCommunication: INIT STATE: 1
2018-11-24 13:02:56.311 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E6 01 (type: 2; queue: 0 0)
2018-11-24 13:02:56.391 Debug [558] BluetoothCommunication$GattCallback: onCharacteristicChanged 0000ffe1-0000-1000-8000-00805f9b34fb: E6 00 20
2018-11-24 13:02:56.393 Debug [2] BluetoothBeurerSanitas: ACK Scale is ready
2018-11-24 13:02:56.396 Debug [2] BluetoothCommunication: INIT STATE: 2
2018-11-24 13:02:56.451 Debug [2] BluetoothCommunication: INIT STATE: 3
2018-11-24 13:02:56.453 Debug [2] BluetoothBeurerSanitas: Write new Date/Time: 1543060976 (5B F9 3D F0)
2018-11-24 13:02:56.455 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E9 5B F9 3D F0 (type: 2; queue: 0 0)
2018-11-24 13:02:56.598 Debug [2] BluetoothCommunication: INIT STATE: 4
2018-11-24 13:02:56.600 Debug [2] BluetoothBeurerSanitas: Setting unit kg
2018-11-24 13:02:56.603 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E7 4D 01 (type: 2; queue: 0 0)
2018-11-24 13:02:56.745 Debug [2] BluetoothCommunication: INIT STATE: 5
2018-11-24 13:02:57.074 Debug [558] BluetoothCommunication$GattCallback: onCharacteristicChanged 0000ffe1-0000-1000-8000-00805f9b34fb: E7 F0 4D 00
2018-11-24 13:02:57.075 Debug [2] BluetoothBeurerSanitas: ACK Unit set
2018-11-24 13:02:57.076 Debug [2] BluetoothCommunication: INIT STATE: 6
2018-11-24 13:02:57.077 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E7 33 (type: 2; queue: 0 0)
2018-11-24 13:02:57.233 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:02:57.367 Debug [558] BluetoothCommunication$GattCallback: onCharacteristicChanged 0000ffe1-0000-1000-8000-00805f9b34fb: E7 F0 33 00 02 08
2018-11-24 13:02:57.368 Debug [2] BluetoothBeurerSanitas: ACK Got general user information
2018-11-24 13:02:57.369 Debug [2] BluetoothBeurerSanitas: Count: 2, maxUsers: 8
2018-11-24 13:02:57.369 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:02:57.416 Debug [558] BluetoothCommunication$GattCallback: onCharacteristicChanged 0000ffe1-0000-1000-8000-00805f9b34fb: E7 34 02 01 00 00 00 00 00 12 91 12 4C 49 4E 5B
2018-11-24 13:02:57.418 Debug [2] BluetoothBeurerSanitas: Ack Get UUIDSs List of Users
2018-11-24 13:02:57.418 Debug [2] BluetoothBeurerSanitas: Send ack gotUser
2018-11-24 13:02:57.419 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E7 F1 34 02 01 (type: 2; queue: 0 0)
2018-11-24 13:02:57.562 Debug [558] BluetoothCommunication$GattCallback: onCharacteristicChanged 0000ffe1-0000-1000-8000-00805f9b34fb: E7 34 02 02 00 00 00 00 00 00 00 13 41 4E 44 52
2018-11-24 13:02:57.564 Debug [2] BluetoothBeurerSanitas: Ack Get UUIDSs List of Users
2018-11-24 13:02:57.564 Debug [2] BluetoothBeurerSanitas: Send ack gotUser
2018-11-24 13:02:57.565 Debug [2] BluetoothCommunication: Request pending (queue 0 1)
2018-11-24 13:02:57.573 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E7 F1 34 02 02 (type: 2; queue: 0 0)
2018-11-24 13:02:57.720 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:02:57.721 Debug [2] BluetoothBeurerSanitas: Request getUserInfo 19
2018-11-24 13:02:57.722 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E7 36 00 00 00 00 00 00 00 13 (type: 2; queue: 0 0)
2018-11-24 13:02:57.724 Debug [2] BluetoothBeurerSanitas: scaleuserid: 19, registered users: 2, extracted users: 2
2018-11-24 13:02:57.855 Debug [558] BluetoothCommunication$GattCallback: onCharacteristicChanged 0000ffe1-0000-1000-8000-00805f9b34fb: E7 F0 36 00 41 4E 44 52 01 1A B7 82
2018-11-24 13:02:57.856 Debug [2] BluetoothBeurerSanitas: Ack Get User Info Initials
2018-11-24 13:02:57.857 Debug [2] BluetoothBeurerSanitas: Name: AND, YY-MM-DD: 82-1-26, Height: 183, Sex: male, activity: 2
2018-11-24 13:02:57.858 Debug [2] BluetoothCommunication: Request pending (queue 0 1)
2018-11-24 13:02:57.867 Debug [2] BluetoothCommunication: Write characteristic 0000ffe1-0000-1000-8000-00805f9b34fb: E7 4F 00 00 00 00 00 00 00 13 (type: 2; queue: 0 0)
2018-11-24 13:02:58.000 Debug [558] BluetoothCommunication$GattCallback: onCharacteristicChanged 0000ffe1-0000-1000-8000-00805f9b34fb: E7 F0 4F 00 64 14 DC 01 00 00 00 05
2018-11-24 13:02:58.002 Debug [2] BluetoothBeurerSanitas: Ack Get scale status
2018-11-24 13:02:58.004 Debug [2] BluetoothBeurerSanitas: BatteryLevel: 100, weightThreshold: 2,00, BodyFatThreshold: 22,00, Unit: 1, userExists: true, UserReference Weight Exists: true, UserMeasurementExists: true, scaleVersion: 5
2018-11-24 13:02:58.012 Debug [2] BluetoothCommunication: INIT STATE: 8
2018-11-24 13:03:44.993 Debug [2] OpenScale: Select user 1
2018-11-24 13:04:57.792 Debug [2] AboutPreferences: Debug log disabled
Olangu commented 5 years ago 
2018-11-24 13:27:59.578 Debug [2] AboutPreferences: Debug log enabled, openScale (dev) v1.8.3-dev_4d09351f_2018-11-21 (1542794810), SDK 27, samsung SM-G960F
2018-11-24 13:28:04.301 Debug [2] BluetoothPreferences: Start discovery
2018-11-24 13:28:04.367 Debug [2] BluetoothPreferences: Discovery: android.bluetooth.adapter.action.DISCOVERY_STARTED
2018-11-24 13:28:11.010 Debug [2] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-11-24 13:28:11.059 Debug [2] BluetoothPreferences: Found supported device SANITAS SBF70 [50:8C:B1:57:E5:16] (driver: Sanitas SBF70/SilverCrest SBF75, type: 2)
2018-11-24 13:28:13.134 Debug [2] BluetoothPreferences: Discovery: android.bluetooth.device.action.FOUND
2018-11-24 13:28:17.147 Debug [2] BluetoothPreferences: Discovery: android.bluetooth.adapter.action.DISCOVERY_FINISHED
2018-11-24 13:28:17.153 Debug [2] BluetoothPreferences: Start LE scan
2018-11-24 13:28:19.567 Debug [2] BluetoothPreferences: Stop discovery
2018-11-24 13:28:19.571 Debug [2] BluetoothPreferences: Stop LE scan
2018-11-24 13:28:19.622 Debug [2] OpenScale: Trying to connect to bluetooth device [50:8C:B1:57:E5:16] in debug mode
2018-11-24 13:28:19.628 Debug [2] BluetoothCommunication: BT is enabled, state=12, scan mode=21, is not discovering
2018-11-24 13:28:19.633 Debug [2] BluetoothCommunication: Starting LE scan for device [50:8C:B1:57:E5:16]
2018-11-24 13:28:29.643 Debug [2] BluetoothCommunication: Device not found in LE scan, connecting directly
2018-11-24 13:28:29.650 Info [2] BluetoothCommunication: Connecting to [50:8C:B1:57:E5:16] (driver: Debug)
2018-11-24 13:28:31.478 Debug [643] BluetoothCommunication$GattCallback: onConnectionStateChange: status=0, newState=2
2018-11-24 13:28:31.486 Debug [2] BluetoothCommunication: Stopping LE scan
2018-11-24 13:28:32.516 Debug [643] BluetoothCommunication$GattCallback: onServicesDiscovered: status=0 (5 services)
2018-11-24 13:28:33.528 Debug [2] BluetoothCommunication: INIT STATE: 0
2018-11-24 13:28:33.539 Debug [2] BluetoothCommunication: Read characteristic 0x2a00 "device name"
2018-11-24 13:28:33.639 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a00 "device name" (status=0): 53 41 4E 49 54 41 53 20 53 42 46 37 30
2018-11-24 13:28:33.708 Debug [2] BluetoothCommunication: INIT STATE: 1
2018-11-24 13:28:33.719 Debug [2] BluetoothCommunication: Read characteristic 0x2a01 "appearance"
2018-11-24 13:28:33.828 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a01 "appearance" (status=0): 00 00
2018-11-24 13:28:33.898 Debug [2] BluetoothCommunication: INIT STATE: 2
2018-11-24 13:28:33.910 Debug [2] BluetoothCommunication: Read characteristic 0x2a02 "peripheral privacy flag"
2018-11-24 13:28:34.023 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a02 "peripheral privacy flag" (status=0): 00
2018-11-24 13:28:34.092 Debug [2] BluetoothCommunication: INIT STATE: 3
2018-11-24 13:28:34.107 Debug [2] BluetoothCommunication: Read characteristic 0x2a04 "peripheral preferred connection parameters"
2018-11-24 13:28:34.220 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a04 "peripheral preferred connection parameters" (status=0): 50 00 A0 00 00 00 E8 03
2018-11-24 13:28:34.289 Debug [2] BluetoothCommunication: INIT STATE: 4
2018-11-24 13:28:34.302 Debug [2] BluetoothCommunication: Read descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:34.415 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2902 "client characteristic configuration" (status=0): 00 00
2018-11-24 13:28:34.484 Debug [2] BluetoothCommunication: INIT STATE: 5
2018-11-24 13:28:34.499 Debug [2] BluetoothCommunication: Read characteristic 0x2a23 "system id"
2018-11-24 13:28:34.611 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a23 "system id" (status=0): 16 E5 57 00 00 B1 8C 50
2018-11-24 13:28:34.679 Debug [2] BluetoothCommunication: INIT STATE: 6
2018-11-24 13:28:34.691 Debug [2] BluetoothCommunication: Read characteristic 0x2a24 "model number string"
2018-11-24 13:28:34.807 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a24 "model number string" (status=0): 4D 6F 64 65 6C 20 4E 75 6D 62 65 72
2018-11-24 13:28:34.874 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:28:34.891 Debug [2] BluetoothCommunication: Read characteristic 0x2a25 "serial number string"
2018-11-24 13:28:35.002 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a25 "serial number string" (status=0): 53 65 72 69 61 6C 20 4E 75 6D 62 65 72
2018-11-24 13:28:35.069 Debug [2] BluetoothCommunication: INIT STATE: 8
2018-11-24 13:28:35.083 Debug [2] BluetoothCommunication: Read characteristic 0x2a26 "firmware revision string"
2018-11-24 13:28:35.198 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a26 "firmware revision string" (status=0): 46 69 72 6D 77 61 72 65 20 52 65 76 69 73 69 6F 6E
2018-11-24 13:28:35.266 Debug [2] BluetoothCommunication: INIT STATE: 9
2018-11-24 13:28:35.283 Debug [2] BluetoothCommunication: Read characteristic 0x2a27 "hardware revision string"
2018-11-24 13:28:35.393 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a27 "hardware revision string" (status=0): 48 61 72 64 77 61 72 65 20 52 65 76 69 73 69 6F 6E
2018-11-24 13:28:35.460 Debug [2] BluetoothCommunication: INIT STATE: 10
2018-11-24 13:28:35.474 Debug [2] BluetoothCommunication: Read characteristic 0x2a28 "software revision string"
2018-11-24 13:28:35.588 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a28 "software revision string" (status=0): 53 6F 66 74 77 61 72 65 20 52 65 76 69 73 69 6F 6E
2018-11-24 13:28:35.656 Debug [2] BluetoothCommunication: INIT STATE: 11
2018-11-24 13:28:35.671 Debug [2] BluetoothCommunication: Read characteristic 0x2a29 "manufacturer name string"
2018-11-24 13:28:35.783 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a29 "manufacturer name string" (status=0): 4D 61 6E 75 66 61 63 74 75 72 65 72 20 4E 61 6D 65
2018-11-24 13:28:35.850 Debug [2] BluetoothCommunication: INIT STATE: 12
2018-11-24 13:28:35.865 Debug [2] BluetoothCommunication: Read characteristic 0x2a2a "ieee 11073 20601 regulatory certification data list"
2018-11-24 13:28:35.976 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a2a "ieee 11073 20601 regulatory certification data list" (status=0): FE 00 65 78 70 65 72 69 6D 65 6E 74 61 6C
2018-11-24 13:28:36.044 Debug [2] BluetoothCommunication: INIT STATE: 13
2018-11-24 13:28:36.060 Debug [2] BluetoothCommunication: Read characteristic 0x2a50 "pnp id"
2018-11-24 13:28:36.170 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0x2a50 "pnp id" (status=0): 01 0D 00 00 00 10 01
2018-11-24 13:28:36.237 Debug [2] BluetoothCommunication: INIT STATE: 14
2018-11-24 13:28:36.252 Debug [2] BluetoothCommunication: Read characteristic 0xffe4
2018-11-24 13:28:36.361 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0xffe4 (status=0): 01
2018-11-24 13:28:36.430 Debug [2] BluetoothCommunication: INIT STATE: 15
2018-11-24 13:28:36.444 Debug [2] BluetoothCommunication: Read descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:36.564 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2901 "characteristic user description" (status=0): 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 31
2018-11-24 13:28:36.630 Debug [2] BluetoothCommunication: INIT STATE: 16
2018-11-24 13:28:36.642 Debug [2] BluetoothCommunication: Read characteristic 0xffe2
2018-11-24 13:28:36.734 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicRead 0xffe2 (status=0): 02
2018-11-24 13:28:36.802 Debug [2] BluetoothCommunication: INIT STATE: 17
2018-11-24 13:28:36.815 Debug [2] BluetoothCommunication: Read descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:36.939 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2901 "characteristic user description" (status=0): 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 32
2018-11-24 13:28:37.006 Debug [2] BluetoothCommunication: INIT STATE: 18
2018-11-24 13:28:37.020 Debug [2] BluetoothCommunication: Read descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:37.138 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2901 "characteristic user description" (status=0): 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 33
2018-11-24 13:28:37.205 Debug [2] BluetoothCommunication: INIT STATE: 19
2018-11-24 13:28:37.219 Debug [2] BluetoothCommunication: Read descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:37.333 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2902 "client characteristic configuration" (status=0): 00 00
2018-11-24 13:28:37.400 Debug [2] BluetoothCommunication: INIT STATE: 20
2018-11-24 13:28:37.413 Debug [2] BluetoothCommunication: Read descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:37.488 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2901 "characteristic user description" (status=0): 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 34
2018-11-24 13:28:37.555 Debug [2] BluetoothCommunication: INIT STATE: 21
2018-11-24 13:28:37.571 Debug [2] BluetoothCommunication: Read descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:37.687 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2901 "characteristic user description" (status=0): 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 35
2018-11-24 13:28:37.754 Debug [2] BluetoothCommunication: INIT STATE: 22
2018-11-24 13:28:37.770 Debug [2] BluetoothCommunication: Read descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:37.884 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2902 "client characteristic configuration" (status=0): 00 00
2018-11-24 13:28:37.951 Debug [2] BluetoothCommunication: INIT STATE: 23
2018-11-24 13:28:37.966 Debug [2] BluetoothCommunication: Read descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.087 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2901 "characteristic user description" (status=0): 49 6D 67 20 49 64 65 6E 74 69 66 79
2018-11-24 13:28:38.154 Debug [2] BluetoothCommunication: INIT STATE: 24
2018-11-24 13:28:38.170 Debug [2] BluetoothCommunication: Read descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:38.283 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2902 "client characteristic configuration" (status=0): 00 00
2018-11-24 13:28:38.351 Debug [2] BluetoothCommunication: INIT STATE: 25
2018-11-24 13:28:38.364 Debug [2] BluetoothCommunication: Read descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.435 Debug [643] BluetoothCommunication$GattCallback: onDescriptorRead 0x2901 "characteristic user description" (status=0): 49 6D 67 20 42 6C 6F 63 6B
2018-11-24 13:28:38.502 Debug [2] BluetoothCommunication: INIT STATE: 26
2018-11-24 13:28:38.516 Debug [2] BluetoothCommunication: CMD STATE: 0
2018-11-24 13:28:38.523 Debug [2] BluetoothDebug: Service 0x1800 "generic access"
2018-11-24 13:28:38.531 Debug [2] BluetoothDebug: |- characteristic 0x2a00 "device name" (#3): READ
2018-11-24 13:28:38.540 Debug [2] BluetoothDebug: |--> value: 53 41 4E 49 54 41 53 20 53 42 46 37 30 (SANITAS SBF70)
2018-11-24 13:28:38.545 Debug [2] BluetoothDebug: |- characteristic 0x2a01 "appearance" (#5): READ
2018-11-24 13:28:38.551 Debug [2] BluetoothDebug: |--> value: 00 00 (??)
2018-11-24 13:28:38.557 Debug [2] BluetoothDebug: |- characteristic 0x2a02 "peripheral privacy flag" (#7): READ, WRITE*
2018-11-24 13:28:38.562 Debug [2] BluetoothDebug: |--> value: 00 (?)
2018-11-24 13:28:38.566 Debug [2] BluetoothDebug: |- characteristic 0x2a03 "reconnection address" (#9): WRITE*
2018-11-24 13:28:38.569 Debug [2] BluetoothDebug: |- characteristic 0x2a04 "peripheral preferred connection parameters" (#11): READ
2018-11-24 13:28:38.574 Debug [2] BluetoothDebug: |--> value: 50 00 A0 00 00 00 E8 03 (P?�???�?)
2018-11-24 13:28:38.577 Debug [2] BluetoothDebug: Service 0x1801 "generic attribute"
2018-11-24 13:28:38.582 Debug [2] BluetoothDebug: |- characteristic 0x2a05 "service changed" (#14): INDICATE
2018-11-24 13:28:38.583 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:38.586 Debug [2] BluetoothDebug: |-----> value: 00 00 (??)
2018-11-24 13:28:38.588 Debug [2] BluetoothDebug: Service 0x180a "device information"
2018-11-24 13:28:38.590 Debug [2] BluetoothDebug: |- characteristic 0x2a23 "system id" (#18): READ
2018-11-24 13:28:38.592 Debug [2] BluetoothDebug: |--> value: 16 E5 57 00 00 B1 8C 50 (?�W??��P)
2018-11-24 13:28:38.594 Debug [2] BluetoothDebug: |- characteristic 0x2a24 "model number string" (#20): READ
2018-11-24 13:28:38.597 Debug [2] BluetoothDebug: |--> value: 4D 6F 64 65 6C 20 4E 75 6D 62 65 72 (Model Number)
2018-11-24 13:28:38.599 Debug [2] BluetoothDebug: |- characteristic 0x2a25 "serial number string" (#22): READ
2018-11-24 13:28:38.601 Debug [2] BluetoothDebug: |--> value: 53 65 72 69 61 6C 20 4E 75 6D 62 65 72 (Serial Number)
2018-11-24 13:28:38.603 Debug [2] BluetoothDebug: |- characteristic 0x2a26 "firmware revision string" (#24): READ
2018-11-24 13:28:38.606 Debug [2] BluetoothDebug: |--> value: 46 69 72 6D 77 61 72 65 20 52 65 76 69 73 69 6F 6E (Firmware Revision)
2018-11-24 13:28:38.608 Debug [2] BluetoothDebug: |- characteristic 0x2a27 "hardware revision string" (#26): READ
2018-11-24 13:28:38.610 Debug [2] BluetoothDebug: |--> value: 48 61 72 64 77 61 72 65 20 52 65 76 69 73 69 6F 6E (Hardware Revision)
2018-11-24 13:28:38.611 Debug [2] BluetoothDebug: |- characteristic 0x2a28 "software revision string" (#28): READ
2018-11-24 13:28:38.614 Debug [2] BluetoothDebug: |--> value: 53 6F 66 74 77 61 72 65 20 52 65 76 69 73 69 6F 6E (Software Revision)
2018-11-24 13:28:38.615 Debug [2] BluetoothDebug: |- characteristic 0x2a29 "manufacturer name string" (#30): READ
2018-11-24 13:28:38.617 Debug [2] BluetoothDebug: |--> value: 4D 61 6E 75 66 61 63 74 75 72 65 72 20 4E 61 6D 65 (Manufacturer Name)
2018-11-24 13:28:38.618 Debug [2] BluetoothDebug: |- characteristic 0x2a2a "ieee 11073 20601 regulatory certification data list" (#32): READ
2018-11-24 13:28:38.620 Debug [2] BluetoothDebug: |--> value: FE 00 65 78 70 65 72 69 6D 65 6E 74 61 6C (�?experimental)
2018-11-24 13:28:38.622 Debug [2] BluetoothDebug: |- characteristic 0x2a50 "pnp id" (#34): READ
2018-11-24 13:28:38.623 Debug [2] BluetoothDebug: |--> value: 01 0D 00 00 00 10 01 (???????)
2018-11-24 13:28:38.624 Debug [2] BluetoothDebug: Service 0xffe0
2018-11-24 13:28:38.625 Debug [2] BluetoothDebug: |- characteristic 0xffe4 (#37): READ, WRITE*
2018-11-24 13:28:38.627 Debug [2] BluetoothDebug: |--> value: 01 (?)
2018-11-24 13:28:38.628 Debug [2] BluetoothDebug: |--- descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.630 Debug [2] BluetoothDebug: |-----> value: 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 31 (Characteristic 1)
2018-11-24 13:28:38.631 Debug [2] BluetoothDebug: |- characteristic 0xffe2 (#40): READ
2018-11-24 13:28:38.632 Debug [2] BluetoothDebug: |--> value: 02 (?)
2018-11-24 13:28:38.633 Debug [2] BluetoothDebug: |--- descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.635 Debug [2] BluetoothDebug: |-----> value: 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 32 (Characteristic 2)
2018-11-24 13:28:38.636 Debug [2] BluetoothDebug: |- characteristic 0xffe3 (#43): WRITE*
2018-11-24 13:28:38.637 Debug [2] BluetoothDebug: |--- descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.639 Debug [2] BluetoothDebug: |-----> value: 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 33 (Characteristic 3)
2018-11-24 13:28:38.640 Debug [2] BluetoothDebug: |- characteristic 0xffe1 (#46): NOTIFY, WRITE*
2018-11-24 13:28:38.640 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:38.641 Debug [2] BluetoothDebug: |-----> value: 00 00 (??)
2018-11-24 13:28:38.643 Debug [2] BluetoothDebug: |--- descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.645 Debug [2] BluetoothDebug: |-----> value: 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 34 (Characteristic 4)
2018-11-24 13:28:38.646 Debug [2] BluetoothDebug: |- characteristic 0xffe5 (#50): READ
2018-11-24 13:28:38.646 Debug [2] BluetoothDebug: |--- descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.648 Debug [2] BluetoothDebug: |-----> value: 43 68 61 72 61 63 74 65 72 69 73 74 69 63 20 35 (Characteristic 5)
2018-11-24 13:28:38.649 Debug [2] BluetoothDebug: Service f000ffc0-0451-4000-b000-000000000000
2018-11-24 13:28:38.650 Debug [2] BluetoothDebug: |- characteristic f000ffc1-0451-4000-b000-000000000000 (#54): NOTIFY, WRITE_NO_RESPONSE*, WRITE
2018-11-24 13:28:38.651 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:38.652 Debug [2] BluetoothDebug: |-----> value: 00 00 (??)
2018-11-24 13:28:38.652 Debug [2] BluetoothDebug: |--- descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.654 Debug [2] BluetoothDebug: |-----> value: 49 6D 67 20 49 64 65 6E 74 69 66 79 (Img Identify)
2018-11-24 13:28:38.654 Debug [2] BluetoothDebug: |- characteristic f000ffc2-0451-4000-b000-000000000000 (#58): NOTIFY, WRITE_NO_RESPONSE*, WRITE
2018-11-24 13:28:38.655 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2018-11-24 13:28:38.656 Debug [2] BluetoothDebug: |-----> value: 00 00 (??)
2018-11-24 13:28:38.657 Debug [2] BluetoothDebug: |--- descriptor 0x2901 "characteristic user description"
2018-11-24 13:28:38.658 Debug [2] BluetoothDebug: |-----> value: 49 6D 67 20 42 6C 6F 63 6B (Img Block)
2018-11-24 13:28:38.659 Info [2] BluetoothCommunication: Disconnecting
2018-11-24 13:28:38.663 Debug [2] OpenScale: Disconnecting from bluetooth device
2018-11-24 13:28:45.805 Debug [2] OpenScale: Trying to connect to bluetooth device [50:8C:B1:57:E5:16] (SANITAS SBF70)
2018-11-24 13:28:45.809 Debug [2] BluetoothCommunication: BT is enabled, state=12, scan mode=21, is not discovering
2018-11-24 13:28:45.813 Debug [2] BluetoothCommunication: Starting LE scan for device [50:8C:B1:57:E5:16]
2018-11-24 13:28:55.825 Debug [2] BluetoothCommunication: Device not found in LE scan, connecting directly
2018-11-24 13:28:55.831 Info [2] BluetoothCommunication: Connecting to [50:8C:B1:57:E5:16] (driver: Sanitas SBF70/SilverCrest SBF75)
2018-11-24 13:29:01.248 Debug [657] BluetoothCommunication$GattCallback: onConnectionStateChange: status=0, newState=2
2018-11-24 13:29:01.262 Debug [2] BluetoothCommunication: Stopping LE scan
2018-11-24 13:29:01.292 Debug [2] MainActivity: Bluetooth connection successful established
2018-11-24 13:29:02.282 Debug [657] BluetoothCommunication$GattCallback: onServicesDiscovered: status=0 (5 services)
2018-11-24 13:29:03.290 Debug [2] BluetoothCommunication: INIT STATE: 0
2018-11-24 13:29:03.297 Debug [2] BluetoothCommunication: Set notification on for 0xffe1
2018-11-24 13:29:03.309 Debug [2] BluetoothCommunication: Write descriptor 0x2902 "client characteristic configuration": 01 00 (queue: 0 0)
2018-11-24 13:29:03.457 Debug [2] BluetoothCommunication: INIT STATE: 1
2018-11-24 13:29:03.462 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E6 01 (type: 2; queue: 0 0)
2018-11-24 13:29:03.546 Debug [657] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E6 00 20
2018-11-24 13:29:03.550 Debug [2] BluetoothBeurerSanitas: ACK Scale is ready
2018-11-24 13:29:03.555 Debug [2] BluetoothCommunication: INIT STATE: 2
2018-11-24 13:29:03.603 Debug [2] BluetoothCommunication: INIT STATE: 3
2018-11-24 13:29:03.608 Debug [2] BluetoothBeurerSanitas: Write new Date/Time: 1543062543 (5B F9 44 0F)
2018-11-24 13:29:03.612 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E9 5B F9 44 0F (type: 2; queue: 0 0)
2018-11-24 13:29:03.755 Debug [2] BluetoothCommunication: INIT STATE: 4
2018-11-24 13:29:03.760 Debug [2] BluetoothBeurerSanitas: Setting unit kg
2018-11-24 13:29:03.764 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 4D 01 (type: 2; queue: 0 0)
2018-11-24 13:29:03.896 Debug [2] BluetoothCommunication: INIT STATE: 5
2018-11-24 13:29:04.224 Debug [657] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 4D 00
2018-11-24 13:29:04.226 Debug [2] BluetoothBeurerSanitas: ACK Unit set
2018-11-24 13:29:04.227 Debug [2] BluetoothCommunication: INIT STATE: 6
2018-11-24 13:29:04.229 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 33 (type: 2; queue: 0 0)
2018-11-24 13:29:04.382 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:29:04.517 Debug [657] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 33 00 02 08
2018-11-24 13:29:04.519 Debug [2] BluetoothBeurerSanitas: ACK Got general user information
2018-11-24 13:29:04.520 Debug [2] BluetoothBeurerSanitas: Count: 2, maxUsers: 8
2018-11-24 13:29:04.521 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:29:04.566 Debug [657] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 34 02 01 00 00 00 00 00 12 91 12 4C 49 4E 5B
2018-11-24 13:29:04.568 Debug [2] BluetoothBeurerSanitas: Ack Get UUIDSs List of Users
2018-11-24 13:29:04.569 Debug [2] BluetoothBeurerSanitas: Send ack gotUser
2018-11-24 13:29:04.570 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 F1 34 02 01 (type: 2; queue: 0 0)
2018-11-24 13:29:04.712 Debug [657] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 34 02 02 00 00 00 00 00 00 00 13 41 4E 44 52
2018-11-24 13:29:04.714 Debug [2] BluetoothBeurerSanitas: Ack Get UUIDSs List of Users
2018-11-24 13:29:04.715 Debug [2] BluetoothBeurerSanitas: Send ack gotUser
2018-11-24 13:29:04.716 Debug [2] BluetoothCommunication: Request pending (queue 0 1)
2018-11-24 13:29:04.722 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 F1 34 02 02 (type: 2; queue: 0 0)
2018-11-24 13:29:04.870 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:29:04.872 Debug [2] BluetoothBeurerSanitas: Request getUserInfo 19
2018-11-24 13:29:04.874 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 36 00 00 00 00 00 00 00 13 (type: 2; queue: 0 0)
2018-11-24 13:29:04.879 Debug [2] BluetoothBeurerSanitas: scaleuserid: 19, registered users: 2, extracted users: 2
2018-11-24 13:29:05.004 Debug [657] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 36 00 41 4E 44 52 01 1A B7 82
2018-11-24 13:29:05.006 Debug [2] BluetoothBeurerSanitas: Ack Get User Info Initials
2018-11-24 13:29:05.007 Debug [2] BluetoothBeurerSanitas: Name: AND, YY-MM-DD: 82-1-26, Height: 183, Sex: male, activity: 2
2018-11-24 13:29:05.008 Debug [2] BluetoothCommunication: Request pending (queue 0 1)
2018-11-24 13:29:05.015 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 4F 00 00 00 00 00 00 00 13 (type: 2; queue: 0 0)
2018-11-24 13:29:05.151 Debug [657] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 4F 00 64 14 DC 01 00 00 00 05
2018-11-24 13:29:05.152 Debug [2] BluetoothBeurerSanitas: Ack Get scale status
2018-11-24 13:29:05.154 Debug [2] BluetoothBeurerSanitas: BatteryLevel: 100, weightThreshold: 2,00, BodyFatThreshold: 22,00, Unit: 1, userExists: true, UserReference Weight Exists: true, UserMeasurementExists: true, scaleVersion: 5
2018-11-24 13:29:05.160 Debug [2] BluetoothCommunication: INIT STATE: 8
2018-11-24 13:29:18.234 Debug [2] OpenScale: Disconnecting from bluetooth device
2018-11-24 13:29:18.235 Info [2] BluetoothCommunication: Disconnecting (with cleanup)
2018-11-24 13:29:18.236 Debug [2] BluetoothCommunication: CLEANUP STATE: 0
2018-11-24 13:29:18.238 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: EA 02 (type: 2; queue: 0 0)
2018-11-24 13:29:18.240 Debug [2] BluetoothCommunication: CLEANUP STATE: 1
2018-11-24 13:29:18.404 Debug [2] BluetoothCommunication: CLEANUP STATE: 2
2018-11-24 13:29:18.408 Info [2] BluetoothCommunication: Disconnecting
2018-11-24 13:29:36.838 Debug [2] OpenScale: Trying to connect to bluetooth device [50:8C:B1:57:E5:16] (SANITAS SBF70)
2018-11-24 13:29:36.844 Debug [2] BluetoothCommunication: BT is enabled, state=12, scan mode=21, is not discovering
2018-11-24 13:29:36.849 Debug [2] BluetoothCommunication: Starting LE scan for device [50:8C:B1:57:E5:16]
2018-11-24 13:29:46.859 Debug [2] BluetoothCommunication: Device not found in LE scan, connecting directly
2018-11-24 13:29:46.864 Info [2] BluetoothCommunication: Connecting to [50:8C:B1:57:E5:16] (driver: Sanitas SBF70/SilverCrest SBF75)
2018-11-24 13:29:53.865 Debug [643] BluetoothCommunication$GattCallback: onConnectionStateChange: status=0, newState=2
2018-11-24 13:29:53.869 Debug [2] BluetoothCommunication: Stopping LE scan
2018-11-24 13:29:53.903 Debug [2] MainActivity: Bluetooth connection successful established
2018-11-24 13:29:54.886 Debug [643] BluetoothCommunication$GattCallback: onServicesDiscovered: status=0 (5 services)
2018-11-24 13:29:55.893 Debug [2] BluetoothCommunication: INIT STATE: 0
2018-11-24 13:29:55.899 Debug [2] BluetoothCommunication: Set notification on for 0xffe1
2018-11-24 13:29:55.910 Debug [2] BluetoothCommunication: Write descriptor 0x2902 "client characteristic configuration": 01 00 (queue: 0 0)
2018-11-24 13:29:56.080 Debug [2] BluetoothCommunication: INIT STATE: 1
2018-11-24 13:29:56.089 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E6 01 (type: 2; queue: 0 0)
2018-11-24 13:29:56.166 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E6 00 20
2018-11-24 13:29:56.169 Debug [2] BluetoothBeurerSanitas: ACK Scale is ready
2018-11-24 13:29:56.172 Debug [2] BluetoothCommunication: INIT STATE: 2
2018-11-24 13:29:56.225 Debug [2] BluetoothCommunication: INIT STATE: 3
2018-11-24 13:29:56.230 Debug [2] BluetoothBeurerSanitas: Write new Date/Time: 1543062596 (5B F9 44 44)
2018-11-24 13:29:56.236 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E9 5B F9 44 44 (type: 2; queue: 0 0)
2018-11-24 13:29:56.424 Debug [2] BluetoothCommunication: INIT STATE: 4
2018-11-24 13:29:56.427 Debug [2] BluetoothBeurerSanitas: Setting unit kg
2018-11-24 13:29:56.432 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 4D 01 (type: 2; queue: 0 0)
2018-11-24 13:29:56.566 Debug [2] BluetoothCommunication: INIT STATE: 5
2018-11-24 13:29:56.896 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 4D 00
2018-11-24 13:29:56.898 Debug [2] BluetoothBeurerSanitas: ACK Unit set
2018-11-24 13:29:56.899 Debug [2] BluetoothCommunication: INIT STATE: 6
2018-11-24 13:29:56.902 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 33 (type: 2; queue: 0 0)
2018-11-24 13:29:57.055 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:29:57.189 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 33 00 02 08
2018-11-24 13:29:57.191 Debug [2] BluetoothBeurerSanitas: ACK Got general user information
2018-11-24 13:29:57.192 Debug [2] BluetoothBeurerSanitas: Count: 2, maxUsers: 8
2018-11-24 13:29:57.193 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:29:57.239 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 34 02 01 00 00 00 00 00 12 91 12 4C 49 4E 5B
2018-11-24 13:29:57.240 Debug [2] BluetoothBeurerSanitas: Ack Get UUIDSs List of Users
2018-11-24 13:29:57.241 Debug [2] BluetoothBeurerSanitas: Send ack gotUser
2018-11-24 13:29:57.243 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 F1 34 02 01 (type: 2; queue: 0 0)
2018-11-24 13:29:57.384 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 34 02 02 00 00 00 00 00 00 00 13 41 4E 44 52
2018-11-24 13:29:57.386 Debug [2] BluetoothBeurerSanitas: Ack Get UUIDSs List of Users
2018-11-24 13:29:57.387 Debug [2] BluetoothBeurerSanitas: Send ack gotUser
2018-11-24 13:29:57.388 Debug [2] BluetoothCommunication: Request pending (queue 0 1)
2018-11-24 13:29:57.395 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 F1 34 02 02 (type: 2; queue: 0 0)
2018-11-24 13:29:57.541 Debug [2] BluetoothCommunication: INIT STATE: 7
2018-11-24 13:29:57.543 Debug [2] BluetoothBeurerSanitas: Request getUserInfo 19
2018-11-24 13:29:57.544 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 36 00 00 00 00 00 00 00 13 (type: 2; queue: 0 0)
2018-11-24 13:29:57.547 Debug [2] BluetoothBeurerSanitas: scaleuserid: 19, registered users: 2, extracted users: 2
2018-11-24 13:29:57.675 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 36 00 41 4E 44 52 01 1A B7 82
2018-11-24 13:29:57.677 Debug [2] BluetoothBeurerSanitas: Ack Get User Info Initials
2018-11-24 13:29:57.678 Debug [2] BluetoothBeurerSanitas: Name: AND, YY-MM-DD: 82-1-26, Height: 183, Sex: male, activity: 2
2018-11-24 13:29:57.679 Debug [2] BluetoothCommunication: Request pending (queue 0 1)
2018-11-24 13:29:57.688 Debug [2] BluetoothCommunication: Write characteristic 0xffe1: E7 4F 00 00 00 00 00 00 00 13 (type: 2; queue: 0 0)
2018-11-24 13:29:57.822 Debug [643] BluetoothCommunication$GattCallback: onCharacteristicChanged 0xffe1: E7 F0 4F 00 64 14 DC 01 00 00 00 05
2018-11-24 13:29:57.824 Debug [2] BluetoothBeurerSanitas: Ack Get scale status
2018-11-24 13:29:57.825 Debug [2] BluetoothBeurerSanitas: BatteryLevel: 100, weightThreshold: 2,00, BodyFatThreshold: 22,00, Unit: 1, userExists: true, UserReference Weight Exists: true, UserMeasurementExists: true, scaleVersion: 5
2018-11-24 13:29:57.835 Debug [2] BluetoothCommunication: INIT STATE: 8
2018-11-24 13:30:05.900 Debug [2] AboutPreferences: Debug log disabled
erijo commented 5 years ago

I have some ideas about this. Once I have something to show I'll ask you to test it.

erijo commented 5 years ago

@Olangu: please try this dev version and attach the log (i.e. please don't paste it in the comment field).

Olangu commented 5 years ago

@Olangu: please try this dev version and attach the log (i.e. please don't paste it in the comment field).

Yes, this version does work. I can now see both users stored in the scale in the log.

Yeah, sorry for pasting the log like that. But I'm yet to find a way to upload files to github comments from the phone. I'll attach the new log when I get to a computer.

erijo commented 5 years ago

You can paste the log here https://gist.github.com/ and post a link.

Olangu commented 5 years ago

openScale_2018-11-26_08-33[1].txt

erijo commented 5 years ago

Thanks @Olangu! Looks like expected, and glad to hear that it worked.

Please try it a few more times and report back if you encounter any issues/strange things. I will do some more testing myself before merging it back to master.

Olangu commented 5 years ago

Thanks @Olangu! Looks like expected, and glad to hear that it worked.

Please try it a few more times and report back if you encounter any issues/strange things. I will do some more testing myself before merging it back to master.

The dev version won't connect in low energy mode, even if the scale is on. It always fall back to device scanning. The stable version connects right away.

erijo commented 5 years ago

It's not that you haven't granted the stable version the location permission? If that is missing, openScale will try to connect without scanning first (which works for some scales but not all).

Olangu commented 5 years ago

It's not that you haven't granted the stable version the location permission? If that is missing, openScale will try to connect without scanning first (which works for some scales but not all).

You where right. I had revoked location permission for stable version. Doing the same for dev version did speed up the connection to the scale.