David Lechner

> Why doesn't it work? Because the backend can't handle multiple connection requests at the same time??? It can be an OS limitation like BlueZ returning "operation already in progress"...

The busy error is specific to the BlueZ backend. The lock works cross-platform - and avoids the error in the first place.

> read_gatt_char(0x2A29): > Characteristic with UUID 10793 could not be found! This is expected since `int` values are treated as a "handle" rather than a UUID. The "correct" way to...

It could be that the Bluetooth adapter (or the driver) on the "problem" computer is the one limiting the MTU. https://bleak.readthedocs.io/en/latest/troubleshooting.html#enable-logging explains how to enable logging.

Thanks for the logs. This looks like a race condition where on this particular adapter/computer, the `max_pdu_size_changed` event is received after services are enumerated. On everything else I've seen before,...

From the logs, it looks like the device never responded to the read request for Peripheral Preferred Connection Parameters. So this is likely why Windows is timing out. 

Is this still a problem with Bleak v0.22.0?

Bleak is meant to be run as a normal user, not root. If you run the service explorer example, is the 2A24 characteristic listed?

Then either the device doesn't have that characteristic or BlueZ is hiding it. You could log Bluetooth packets to see if the device actually provides this characteristic.

> This was caused by the BleakScanner class being instanced too often and not being shutdown properly by bleak or at least the dbus part. We solved this using an...