Interest in specifying bleak adapter

[r-bt]

Hey, I was just wanted to check if you'd be interested in a PR to add the option to specify the specific Bluetooth adapter bleak should use?

[superfashi]

a PR will be more than welcomed. Sorry that I am quite busy recently so cannot reply to issues promptly.

[r-bt]

Awesome! Also when I was looking at bleak_adapter.py I noticed that you're passing the bluetooth device address as opposed to the BLEDevice to Bleak Client (e.g. bleak.BleakClient(address)). Is there a reason for this? In the bleak documentation there's a warning against doing so as it (from https://bleak.readthedocs.io/en/latest/api/client.html)

causes the connect() method to implicitly call BleakScanner.discover(). This is known to cause problems when trying to connect to multiple devices at the same time.

and

macOS does not provide access to the Bluetooth address for privacy/ security reasons. Instead it creates a UUID for each Bluetooth device which is used in place of the address on this platform.

which could actually be the cause of #35

[r-bt]

Also I'm just wondering about why a new event loop and thread are created for each BleakClient? From digging around this works fine when passing Bluetooth addresses but on macOS if I pass a BLEDevice it gives this error

got Future <Future pending> attached to a different loop

Apparently this is a known issue with Bleak (see hbldh/bleak#1191 and hbldh/bleak#242) so they recommend against having multiple threads and event loops

the design paradigm for bleak is to have multiple connections all under 1 event loop in 1 thread

I can make a PR to address these issues but I just wanted to check if that would be something you'd be interested in?

[superfashi]

Apparently BLEDevice uses future which attaches with a single event loop.

There is an async branch where I tried to write everything in async fashion. But the API is way too confusing.

I'm interested in your PR on this.