Compare commits

..

2 Commits

Author SHA1 Message Date
Markus Köbele
969f3ffb3c Merge branch 'initial' 2023-11-05 16:36:06 +01:00
Markus Köbele
b3f2cddec1 initial findings 2023-11-05 16:35:12 +01:00
4 changed files with 261 additions and 1 deletions

116
README.md
View File

@@ -1,2 +1,116 @@
# amazfit-scale-openscale-support # Measurments for Logs
* 15:03 Pairing
* 15:03 88,6 Kg
* 15:04 Firmware Update
* 15:06 Update done
* 15:07 Avatar selected
* 15:08 88,6kg 0,0kg change 104bpm 30,3%
* 15:09 92,3kg 108 bpm (not connected)
* 15:11 20,65kg not connected 102bpm
## Findings
Timestamps seem to be off by a few minutes in logs, investigate further
## Data received from scale through advertisements
Wireshark filter: `bthci_evt.bd_addr == 70:87:9e:38:52:27`
There are lots of packages sent as bluetooth advertisement.
> Theory: Some of those packages already contain weight measurements. This explains, why the Zepp App could show
measurements so fast.
The advertisement packages are mostly 54 and 60 bytes in length. Both those packages seem to be sent right after each other.
Example 54 byte message:
```text
0000 04 3e 33 0d 01 1b 00 00 27 52 38 9e 87 70 01 00 .>3.....'R8..p..
0010 ff 7f b9 00 00 00 00 00 00 00 00 00 19 0e 09 41 ...............A
0020 6d 61 7a 66 69 74 20 53 63 61 6c 65 09 ff 57 01 mazfit Scale..W.
0030 70 87 9e 38 52 27 p..8R'
```
Example 60 byte message:
```text
0000 04 3e 39 0d 01 13 00 00 27 52 38 9e 87 70 01 00 .>9.....'R8..p..
0010 ff 7f b9 00 00 00 00 00 00 00 00 00 1f 02 01 06 ................
0020 03 02 e0 fe 17 16 e0 fe ba 00 e7 67 8b e3 cc 2e ...........g....
0030 45 4a 65 2a 00 00 43 5d cb a5 01 00 EJe*..C]....
```
### Decoding the 54 byte message
Packet: 1332
| byte(s) | Meaning |
| --- | --- |
| 04 | HCI Packet Type: HCI Event |
| 3e | Event Code: LE Meta |
| 33 | Total lenght: 51 |
| 0d | Sub Event: LE Extended Advertising Report |
| 01 | Num Reports: 1 |
| 1b 00 | Connectable, Scannable, Scan Response, Legacy, Data Status: Complete |
| 00 | Peer Address Type: Public Device Address |
| 27 52 38 9e 87 70 | BD_ADDR: 70:87:9e:38:52:27 (Bluetooth adress of device) |
| 01 | Primary PHY: LE 1M (?) |
| 00 | Secondary PHY: No packets on secondary advertising channel |
| ff | Advertising SID: not available |
| 7f | TX Power: 127dBm (not available) |
| b9 | RSSI: -71 dBm |
| 00 00 | Periodic Advertising Interval: None |
| 00 | Direct Address Type: Public Device Address |
| 00 00 00 00 00 00 | Direct BD_ADDR: 00:00:00:00:00:00 |
| 19 | Data length: 25 |
| 0e 09 41 6d 61 7a 66 69 74 20 53 63 61 6c 65 | Device Name: Amazfit Scale |
| 09 | Length: 9 |
| ff | Type: Manufacturer Specific |
| 57 01 | Company ID: Anhui Huami Information Technology Co., Ltd. |
| **70 87 9e 38 52 27** | **Data** |
The first 45 bytes seem to be meta information, only the last 9 bytes contain relevant data.
> Idea: Use first 45 bytes to identify device and message type, interpret message correctly.
### Decoding the 60 byte message
| byte(s) | Meaning |
| --- | --- |
| 04 | HCI Packet Type: HCI Event |
| 3e | Event Code: LE Meta |
| 38 | Total lenght: 57 |
| 0d | Sub Event: LE Extended Advertising Report |
| 01 | Num Reports: 1 |
| 13 00 | Connectable, Scannable, Legacy, Data Status: Complete |
| 00 | Peer Address Type: Public Device Address |
| 27 52 38 9e 87 70 | BD_ADDR: 70:87:9e:38:52:27 (Bluetooth adress of device) |
| 01 | Primary PHY: LE 1M (?) |
| 00 | Secondary PHY: No packets on secondary advertising channel |
| ff | Advertising SID: not available |
| 7f | TX Power: 127dBm (not available) |
| b9 | RSSI: -71 dBm |
| 00 00 | Periodic Advertising Interval: None |
| 00 | Direct Address Type: Public Device Address |
| 00 00 00 00 00 00 | Direct BD_ADDR: 00:00:00:00:00:00 |
| 19 | Data length: 31 |
| 02 | Length: 2 |
| 01 | Type: Flags |
| 06 | Simultaneous LE and BR/EDR to Same Device Capable (Host): false <br> Simultaneous LE and BR/EDR to Same Device Capable (Controller): false, BR/EDR Not Supported: true (0x1) <br> LE General Discoverable Mode: true <br> LE Limited Discoverable Mode: false |
| 03 02 e0 fe | 16-bit Service Class UUIDs (incomplete): Anhui Huami Information Technology Co., Ltd. |
| 17 | (Service Data) Length: 23 |
| 16 | Type: Serice Data - 16 bit UUID |
| eo fe | UUID 16: Anhui Huami Information Technology Co., Ltd. |
| ba 00 e7 67 8b e3 cc 2e 45 4a 65 2a 00 00 43 5d cb a5 01 00 | Service Data |
Again the first block of bytes seem to be meta data and there are 20 bytes of "Service Data" which might contain interesting
information for our use case.
> TODO: Take a look how these service data entries change over time
> TODO: Compare with findings of https://github.com/custom-components/ble_monitor/issues/910

BIN
btsnooz_hci.log Normal file

Binary file not shown.

BIN
btsnooz_hci.log.last Normal file

Binary file not shown.

View File

@@ -0,0 +1,146 @@
2023-11-05 15:14:33.667 Debug [2] AboutPreferences: Debug log enabled, openScale v2.5.2 (64), SDK 33, Fairphone FP4
2023-11-05 15:14:33.673 Debug [2] AboutPreferences: Selected user id(1) name(Markus) birthday(Mon Oct 24 01:00:00 GMT+01:00 1988) age(35) body height(170.00) scale unit(kg) gender(male) initial weight(89.00) goal enabled(true) goal weight(75.00) goal date(Thu Oct 24 02:00:00 GMT+02:00 2024) measure unt(cm) activity level(0) assisted weighing(false)
2023-11-05 15:14:43.554 Debug [2] BluetoothSettingsFragment: Bluetooth settings Bluetooth permission check
2023-11-05 15:14:43.560 Debug [2] BluetoothSettingsFragment: SDK >= 31 request for Bluetooth Scan and Bluetooth connect permissions
2023-11-05 15:14:43.563 Debug [2] BluetoothSettingsFragment: Permission is not granted: android.permission.BLUETOOTH_SCAN
2023-11-05 15:14:45.751 Info [2] BluetoothCentralManager: scan started
2023-11-05 15:14:45.755 Debug [2] BluetoothSettingsFragment: Bluetooth settings Bluetooth permission check
2023-11-05 15:14:45.756 Debug [2] BluetoothSettingsFragment: SDK >= 31 request for Bluetooth Scan and Bluetooth connect permissions
2023-11-05 15:14:45.757 Debug [2] BluetoothSettingsFragment: Permission already granted: android.permission.BLUETOOTH_SCAN
2023-11-05 15:14:45.759 Debug [2] BluetoothSettingsFragment: Permission already granted: android.permission.BLUETOOTH_CONNECT
2023-11-05 15:14:45.767 Info [2] BluetoothCentralManager: scan started
2023-11-05 15:14:47.000 Debug [2] BluetoothSettingsFragment: Found unsupported device Amazfit Scale [70:87:9E:38:52:27]
2023-11-05 15:14:49.040 Info [2] BluetoothCentralManager: scan stopped
2023-11-05 15:14:49.043 Debug [2] OpenScale: Trying to connect to bluetooth device [70:87:9E:38:52:27] in debug mode
2023-11-05 15:14:49.054 Debug [2] BluetoothCommunication: Do LE scan before connecting to device
2023-11-05 15:14:49.078 Info [2] BluetoothCentralManager: scan started
2023-11-05 15:14:49.081 Debug [2] BluetoothCommunication: Stop machine state
2023-11-05 15:14:49.135 Debug [2] BluetoothCommunication: Found peripheral 'Amazfit Scale'
2023-11-05 15:14:49.152 Info [2] BluetoothCentralManager: scan stopped
2023-11-05 15:14:50.156 Debug [2] BluetoothCommunication: Try to connect to BLE device 70:87:9E:38:52:27
2023-11-05 15:14:50.275 Info [2] BluetoothPeripheral: connect to 'Amazfit Scale' (70:87:9E:38:52:27) using transport LE
2023-11-05 15:14:50.300 Info [2] BluetoothPeripheral: peripheral '70:87:9E:38:52:27' is connecting
2023-11-05 15:14:50.637 Info [126] BluetoothPeripheral: connected to 'Amazfit Scale' (NONE) in 0.3s
2023-11-05 15:14:50.650 Debug [2] BluetoothPeripheral: discovering services of 'Amazfit Scale' with delay of 0 ms
2023-11-05 15:14:51.220 Debug [126] BluetoothPeripheral: connection parameters: interval=7.5ms latency=0 timeout=5s
2023-11-05 15:14:51.594 Info [126] BluetoothPeripheral: discovered 5 services for 'Amazfit Scale'
2023-11-05 15:14:51.609 Debug [2] BluetoothCommunication: connected to 'Amazfit Scale'
2023-11-05 15:14:51.617 Debug [2] BluetoothCommunication: Successful Bluetooth services discovered
2023-11-05 15:14:51.636 Debug [2] BluetoothCommunication: Invoke read bytes on 0x2a00 "device name"
2023-11-05 15:14:51.643 Debug [2] BluetoothDebug: Service 0x1800 "generic access"
2023-11-05 15:14:51.647 Debug [2] BluetoothDebug: |- characteristic 0x2a00 "device name" (#3): READ
2023-11-05 15:14:51.650 Debug [2] BluetoothDebug: |- characteristic 0x2a01 "appearance" (#5): READ
2023-11-05 15:14:51.653 Debug [2] BluetoothDebug: Service 0x1801 "generic attribute"
2023-11-05 15:14:51.655 Debug [2] BluetoothDebug: Service 0x180a "device information"
2023-11-05 15:14:51.657 Debug [2] BluetoothDebug: |- characteristic 0x2a25 "serial number string" (#9): READ
2023-11-05 15:14:51.658 Debug [2] BluetoothDebug: |- characteristic 0x2a27 "hardware revision string" (#11): READ
2023-11-05 15:14:51.660 Debug [2] BluetoothDebug: |- characteristic 0x2a28 "software revision string" (#13): READ
2023-11-05 15:14:51.662 Debug [2] BluetoothDebug: |- characteristic 0x2a26 "firmware revision string" (#15): READ
2023-11-05 15:14:51.665 Debug [2] BluetoothDebug: |- characteristic 0x2a23 "system id" (#17): READ
2023-11-05 15:14:51.666 Debug [2] BluetoothDebug: |- characteristic 0x2a50 "pnp id" (#19): READ
2023-11-05 15:14:51.668 Debug [2] BluetoothDebug: Service 00001530-0000-3512-2118-0009af100700
2023-11-05 15:14:51.670 Debug [2] BluetoothDebug: |- characteristic 00001531-0000-3512-2118-0009af100700 (#22): NOTIFY, WRITE*
2023-11-05 15:14:51.671 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.673 Debug [2] BluetoothDebug: |- characteristic 00001532-0000-3512-2118-0009af100700 (#25): WRITE_NO_RESPONSE*
2023-11-05 15:14:51.674 Debug [2] BluetoothDebug: |- characteristic 0x2a04 "peripheral preferred connection parameters" (#27): NOTIFY, READ, WRITE*
2023-11-05 15:14:51.675 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.677 Debug [2] BluetoothDebug: |- characteristic 00001542-0000-3512-2118-0009af100700 (#30): NOTIFY, READ, WRITE*
2023-11-05 15:14:51.678 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.679 Debug [2] BluetoothDebug: |- characteristic 00001543-0000-3512-2118-0009af100700 (#33): NOTIFY, READ, WRITE*
2023-11-05 15:14:51.681 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.682 Debug [2] BluetoothDebug: Service 0xfee0
2023-11-05 15:14:51.684 Debug [2] BluetoothDebug: |- characteristic 00000016-0000-3512-2118-0009af100700 (#37): NOTIFY, READ, WRITE_NO_RESPONSE*
2023-11-05 15:14:51.685 Debug [126] BluetoothPeripheral: connection parameters: interval=45.0ms latency=0 timeout=2s
2023-11-05 15:14:51.689 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.690 Debug [2] BluetoothDebug: |- characteristic 00000017-0000-3512-2118-0009af100700 (#40): NOTIFY, READ, WRITE_NO_RESPONSE*
2023-11-05 15:14:51.692 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.693 Debug [2] BluetoothDebug: |- characteristic 00000018-0000-3512-2118-0009af100700 (#43): NOTIFY, READ, WRITE*
2023-11-05 15:14:51.695 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.696 Debug [2] BluetoothDebug: |- characteristic 0x0019 (#46): READ, WRITE*
2023-11-05 15:14:51.698 Debug [2] BluetoothDebug: |- characteristic 0x0021 (#48): INDICATE, WRITE*
2023-11-05 15:14:51.700 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:14:51.701 Debug [2] BluetoothCommunication: Bluetooth disconnect
2023-11-05 15:14:51.702 Info [2] BluetoothCentralManager: no scan to stop because no scan is running
2023-11-05 15:14:51.703 Info [2] BluetoothPeripheral: peripheral '70:87:9E:38:52:27' is disconnecting
2023-11-05 15:14:51.704 Debug [2] BluetoothCommunication: Resume machine state
2023-11-05 15:14:51.705 Debug [2] BluetoothCommunication: Step Nr 0
2023-11-05 15:14:51.706 Debug [2] BluetoothCommunication: Invoke delayed disconnect in 60s
2023-11-05 15:14:51.708 Debug [2] OpenScale: Disconnecting from bluetooth device
2023-11-05 15:14:51.709 Debug [2] BluetoothCommunication: Bluetooth disconnect
2023-11-05 15:14:51.709 Info [2] BluetoothCentralManager: no scan to stop because no scan is running
2023-11-05 15:14:51.738 Info [2] BluetoothPeripheral: force disconnect 'Amazfit Scale' (70:87:9E:38:52:27)
2023-11-05 15:14:51.739 Info [126] BluetoothPeripheral: disconnected 'Amazfit Scale' on request
2023-11-05 15:14:51.751 Debug [2] BluetoothCommunication: disconnected 'Amazfit Scale' with status 0
2023-11-05 15:14:59.378 Info [2] BluetoothCentralManager: no scan to stop because no scan is running
2023-11-05 15:14:59.380 Debug [2] OpenScale: Trying to connect to bluetooth device [70:87:9E:38:52:27] in debug mode
2023-11-05 15:14:59.386 Debug [2] BluetoothCommunication: Do LE scan before connecting to device
2023-11-05 15:14:59.414 Info [2] BluetoothCentralManager: scan started
2023-11-05 15:14:59.417 Debug [2] BluetoothCommunication: Stop machine state
2023-11-05 15:14:59.473 Debug [2] BluetoothCommunication: Found peripheral 'Amazfit Scale'
2023-11-05 15:14:59.489 Info [2] BluetoothCentralManager: scan stopped
2023-11-05 15:15:00.494 Debug [2] BluetoothCommunication: Try to connect to BLE device 70:87:9E:38:52:27
2023-11-05 15:15:00.620 Info [2] BluetoothPeripheral: connect to 'Amazfit Scale' (70:87:9E:38:52:27) using transport LE
2023-11-05 15:15:00.646 Info [2] BluetoothPeripheral: peripheral '70:87:9E:38:52:27' is connecting
2023-11-05 15:15:00.997 Info [116] BluetoothPeripheral: connected to 'Amazfit Scale' (NONE) in 0.4s
2023-11-05 15:15:01.005 Debug [2] BluetoothPeripheral: discovering services of 'Amazfit Scale' with delay of 0 ms
2023-11-05 15:15:01.586 Debug [118] BluetoothPeripheral: connection parameters: interval=7.5ms latency=0 timeout=5s
2023-11-05 15:15:01.974 Info [116] BluetoothPeripheral: discovered 5 services for 'Amazfit Scale'
2023-11-05 15:15:01.984 Debug [2] BluetoothCommunication: connected to 'Amazfit Scale'
2023-11-05 15:15:01.988 Debug [2] BluetoothCommunication: Successful Bluetooth services discovered
2023-11-05 15:15:01.992 Debug [2] BluetoothCommunication: Invoke read bytes on 0x2a00 "device name"
2023-11-05 15:15:02.000 Debug [2] BluetoothDebug: Service 0x1800 "generic access"
2023-11-05 15:15:02.004 Debug [2] BluetoothDebug: |- characteristic 0x2a00 "device name" (#3): READ
2023-11-05 15:15:02.008 Debug [2] BluetoothDebug: |- characteristic 0x2a01 "appearance" (#5): READ
2023-11-05 15:15:02.012 Debug [2] BluetoothDebug: Service 0x1801 "generic attribute"
2023-11-05 15:15:02.016 Debug [2] BluetoothDebug: Service 0x180a "device information"
2023-11-05 15:15:02.018 Debug [2] BluetoothDebug: |- characteristic 0x2a25 "serial number string" (#9): READ
2023-11-05 15:15:02.021 Debug [2] BluetoothDebug: |- characteristic 0x2a27 "hardware revision string" (#11): READ
2023-11-05 15:15:02.024 Debug [2] BluetoothDebug: |- characteristic 0x2a28 "software revision string" (#13): READ
2023-11-05 15:15:02.028 Debug [2] BluetoothDebug: |- characteristic 0x2a26 "firmware revision string" (#15): READ
2023-11-05 15:15:02.032 Debug [2] BluetoothDebug: |- characteristic 0x2a23 "system id" (#17): READ
2023-11-05 15:15:02.034 Debug [2] BluetoothDebug: |- characteristic 0x2a50 "pnp id" (#19): READ
2023-11-05 15:15:02.036 Debug [2] BluetoothDebug: Service 00001530-0000-3512-2118-0009af100700
2023-11-05 15:15:02.037 Debug [116] BluetoothPeripheral: connection parameters: interval=45.0ms latency=0 timeout=2s
2023-11-05 15:15:02.043 Debug [2] BluetoothDebug: |- characteristic 00001531-0000-3512-2118-0009af100700 (#22): NOTIFY, WRITE*
2023-11-05 15:15:02.045 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.047 Debug [2] BluetoothDebug: |- characteristic 00001532-0000-3512-2118-0009af100700 (#25): WRITE_NO_RESPONSE*
2023-11-05 15:15:02.049 Debug [2] BluetoothDebug: |- characteristic 0x2a04 "peripheral preferred connection parameters" (#27): NOTIFY, READ, WRITE*
2023-11-05 15:15:02.050 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.052 Debug [2] BluetoothDebug: |- characteristic 00001542-0000-3512-2118-0009af100700 (#30): NOTIFY, READ, WRITE*
2023-11-05 15:15:02.054 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.056 Debug [2] BluetoothDebug: |- characteristic 00001543-0000-3512-2118-0009af100700 (#33): NOTIFY, READ, WRITE*
2023-11-05 15:15:02.058 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.060 Debug [2] BluetoothDebug: Service 0xfee0
2023-11-05 15:15:02.062 Debug [2] BluetoothDebug: |- characteristic 00000016-0000-3512-2118-0009af100700 (#37): NOTIFY, READ, WRITE_NO_RESPONSE*
2023-11-05 15:15:02.064 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.066 Debug [2] BluetoothDebug: |- characteristic 00000017-0000-3512-2118-0009af100700 (#40): NOTIFY, READ, WRITE_NO_RESPONSE*
2023-11-05 15:15:02.068 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.070 Debug [2] BluetoothDebug: |- characteristic 00000018-0000-3512-2118-0009af100700 (#43): NOTIFY, READ, WRITE*
2023-11-05 15:15:02.071 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.073 Debug [2] BluetoothDebug: |- characteristic 0x0019 (#46): READ, WRITE*
2023-11-05 15:15:02.075 Debug [2] BluetoothDebug: |- characteristic 0x0021 (#48): INDICATE, WRITE*
2023-11-05 15:15:02.076 Debug [2] BluetoothDebug: |--- descriptor 0x2902 "client characteristic configuration"
2023-11-05 15:15:02.078 Debug [2] BluetoothCommunication: Bluetooth disconnect
2023-11-05 15:15:02.079 Info [2] BluetoothCentralManager: no scan to stop because no scan is running
2023-11-05 15:15:02.080 Info [2] BluetoothPeripheral: peripheral '70:87:9E:38:52:27' is disconnecting
2023-11-05 15:15:02.081 Debug [2] BluetoothCommunication: Resume machine state
2023-11-05 15:15:02.082 Debug [2] BluetoothCommunication: Step Nr 0
2023-11-05 15:15:02.084 Debug [2] BluetoothCommunication: Invoke delayed disconnect in 60s
2023-11-05 15:15:02.085 Debug [2] OpenScale: Disconnecting from bluetooth device
2023-11-05 15:15:02.086 Debug [2] BluetoothCommunication: Bluetooth disconnect
2023-11-05 15:15:02.087 Info [2] BluetoothCentralManager: no scan to stop because no scan is running
2023-11-05 15:15:02.127 Info [118] BluetoothPeripheral: disconnected 'Amazfit Scale' on request
2023-11-05 15:15:02.130 Info [2] BluetoothPeripheral: force disconnect 'Amazfit Scale' (70:87:9E:38:52:27)
2023-11-05 15:15:02.138 Debug [2] BluetoothCommunication: disconnected 'Amazfit Scale' with status 0
2023-11-05 15:15:05.755 Info [2] BluetoothCentralManager: no scan to stop because no scan is running
2023-11-05 15:15:11.055 Info [2] BluetoothCentralManager: no scan to stop because no scan is running
2023-11-05 15:15:11.536 Debug [2] BluetoothSettingsFragment: Found unsupported device F48F921F606A30AEE9 [F3:33:28:82:68:AA]
2023-11-05 15:15:14.551 Debug [2] BluetoothSettingsFragment: Bluetooth settings Bluetooth permission check
2023-11-05 15:15:14.557 Debug [2] BluetoothSettingsFragment: SDK >= 31 request for Bluetooth Scan and Bluetooth connect permissions
2023-11-05 15:15:14.560 Debug [2] BluetoothSettingsFragment: Permission already granted: android.permission.BLUETOOTH_SCAN
2023-11-05 15:15:14.562 Debug [2] BluetoothSettingsFragment: Permission already granted: android.permission.BLUETOOTH_CONNECT
2023-11-05 15:15:14.582 Info [2] BluetoothCentralManager: scan started
2023-11-05 15:15:14.644 Debug [2] BluetoothSettingsFragment: Found unsupported device Amazfit Scale [70:87:9E:38:52:27]
2023-11-05 15:15:14.818 Debug [2] BluetoothSettingsFragment: Found unsupported device F48F921F606A30AEE9 [F3:33:28:82:68:AA]
2023-11-05 15:15:15.370 Info [2] BluetoothCentralManager: scan stopped
2023-11-05 15:15:21.181 Debug [2] AboutPreferences: Debug log disabled