Replies: 1 comment
-
Generally, the way it works is that you scan with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
bluetoothctl -v
) in case of Linux: 5.53Description
Pairing a device using a Resolvable Private Address works perfectly through the normal process, and then the device MAC is accessible. Using this MAC address to connect to the device in Bleak fails because a device with that address isn't found - it only sees the private address. The device name is also not resolved, so I can't find a way to connect to the device short of hardcoding a private address that changes every 15 minutes.
The behaviour I expected was that it would work similarly to bluetoothctl on linux, where it can connect to the proper MAC address.
What I Did
Pair an iPhone or Android device to the computer running a recent enough version to have bluetooth privacy enabled, and then try to access that device from bleak using
BleakClient.connect(address)
.The device isn't found because the address it's broadcasting doesn't match the true MAC address.
I'm not sure if I'm just overlooking something, but I can't see any way to connect to the device.
Beta Was this translation helpful? Give feedback.
All reactions