oliexdev
RENPHO ES-CS20M Issues with scales with no device name reported while scanning
Related to #769
OpenScale can't list certain models of this scale since it search devices that reports name, but in my case and others as far as I can read, it reports none.
I tried to build a custom apk for debugging and force to connect with a fake device name and a mac address with the QN Scale driver and Trisa Body Analyze 4.0 one, but it gave me always a connection error.
2022-08-23 19:38:07.312 Debug [2] MainActivity: All Bluetooth permissions granted
2022-08-23 19:38:07.334 Debug [2] OpenScale: Trying to connect to bluetooth device [ED:67:39:BF:80:EA] (Renpho)
2022-08-23 19:38:07.338 Debug [2] BluetoothCommunication: Do LE scan before connecting to device
2022-08-23 19:38:07.346 Info [2] BluetoothCentralManager: scan started
2022-08-23 19:38:07.347 Debug [2] BluetoothCommunication: Stop machine state
2022-08-23 19:38:08.735 Debug [2] BluetoothCommunication: Found peripheral ''
2022-08-23 19:38:08.739 Info [2] BluetoothCentralManager: scan stopped
2022-08-23 19:38:09.741 Debug [2] BluetoothCommunication: Try to connect to BLE device ED:67:39:BF:80:EA
2022-08-23 19:38:09.851 Info [2] BluetoothPeripheral: connect to '' (ED:67:39:BF:80:EA) using transport LE
2022-08-23 19:38:09.860 Info [2] BluetoothPeripheral: peripheral 'ED:67:39:BF:80:EA' is connecting
2022-08-23 19:38:14.889 Info [116] BluetoothPeripheral: connection failed with status 'CONNECTION_FAILED_ESTABLISHMENT'
2022-08-23 19:38:14.903 Info [116] BluetoothCentralManager: connection to '' (ED:67:39:BF:80:EA) failed
2022-08-23 19:38:14.908 Error [2] BluetoothCommunication: connection '' failed with status 62
2022-08-23 19:38:14.920 Debug [2] MainActivity: Bluetooth connection lost
It seems I can't even make any successful pairing with the device outside the official app. Will report any progress.
Edit: Yes, the scale it is not made for pairing. My fault. Probably it is broadcasting a message that must be captured in BLE advertising packets. I suppose that it was trying to do when it says: BluetoothPeripheral: connect to '' (ED:67:39:BF:80:EA) using transport LE.
Frame 3097: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Bluetooth
Bluetooth HCI H4
Bluetooth HCI Event - LE Meta
Event Code: LE Meta (0x3e)
Parameter Total Length: 57
Sub Event: LE Extended Advertising Report (0x0d)
Num Reports: 1
Event Type: 0x0010, Legacy, Data Status: Complete
.... .... .... ...0 = Connectable: False
.... .... .... ..0. = Scannable: False
.... .... .... .0.. = Directed: False
.... .... .... 0... = Scan Response: False
.... .... ...1 .... = Legacy: True
.... .... .00. .... = Data Status: Complete (0x0)
0000 0000 0... .... = Reserved: 0x000
Peer Address Type: Public Device Address (0x00)
BD_ADDR: ed:67:39:bf:80:ea (ed:67:39:bf:80:ea)
Primary PHY: LE 1M (0x01)
Secondary PHY: No packets on the secondary advertising channel (0x00)
Advertising SID: 0xff (not available)
TX Power: 127 dBm (not available)
RSSI: -51 dBm
Periodic Advertising Interval: 0x0000 (no periodic advertising)
Direct Address Type: Public Device Address (0x00)
Direct BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)
Data Length: 31
Advertising Data
Flags
Length: 2
Type: Flags (0x01)
000. .... = Reserved: 0x0
...0 .... = Simultaneous LE and BR/EDR to Same Device Capable (Host): false (0x0)
.... 0... = Simultaneous LE and BR/EDR to Same Device Capable (Controller): false (0x0)
.... .1.. = BR/EDR Not Supported: true (0x1)
.... ..1. = LE General Discoverable Mode: true (0x1)
.... ...0 = LE Limited Discoverable Mode: false (0x0)
Manufacturer Specific
Length: 27
Type: Manufacturer Specific (0xff)
Company ID: For use in internal and interoperability tests (0xffff)
Data: aabbed6739bf80ead53a05630000000200b8064c0903d615
[Expert Info (Note/Undecoded): Undecoded]
[Undecoded]
[Severity level: Note]
[Group: Undecoded]
