Hello, bit of an almost XY issue.
I have a Xiaomi smart band 10, connected to my phone via notify for Xiaomi. While the app works great (and I like the accelerometer export), it seems that it doesn’t export the heart rate to SAA in real-time. So, I want to use the native Bluetooth option. This should work, since the watch has a “Share HR" feature which shares it over standard GATT protocols.
How it seems to work is the watch advertises a second BLE address which I can connect to. Using nRF connect, I can connect to it fine and it works (even while SAA/notify is using the accelerometer on the other address)
…But in SAA, it only shows the original address/the one connected to notify, and never shows this other address. This means I can’t connect to my watch for real-time HR tracking, as this address seemingly never connects from within SAA.
[I’d have an image here, but I’m limited to a max of 1. The address starts with F4:FB, which is what notify connects to.]
Through some weird bonding shenanigans, bonding only the heart rate address allows it to work. But then, notify can’t connect to the watch
[See above image issue. If my phone bonds with the DO:6E address, SAA can read from it perfectly fine.]
I would appreciate if a device that advertises multiple addresses to be individually selectable. If that’s not the issue, than it may be because this BLE address can’t be bonded to, only paired. I can provide further debugging if needed through nRF or anything else.