David Lechner
David Lechner
> ```python > loop = asyncio.get_event_loop() > loop.run_until_complete(scanner()) > print(ADDRESS) > # scan loop complete here > loop.run_until_complete(run(ADDRESS)) > ``` There should only be one event loop that runs for...
This error comes from the WIndows OS. I have found that logging Bluetooth packets with Wireshark (see troubleshooting page of Bleak docs) is the best way to debug these sorts...
Does #1062 fix the `WinError -2147483629` error?
Based on https://github.com/hbldh/bleak/issues/411#issuecomment-755783668, I'm starting to think that maybe we should just remove the battery service workaround instead and recommend that users disable the BlueZ battery plugin if they want...
I assume you are advocating for leaving the Battery Service workaround in place? In that case, we still should fix Bleak so that it depends on the D-Bus object being...
Up until now, we missed https://github.com/bluez/bluez/commit/713f6f09f017abfccc2da9dbf2b32adf9ecb8e58 which exposes the battery service in BlueZ again starting in BlueZ v5.55. The version check for this is fixed in #976. So eventually, we...
> have to read the weight from a Mi Smart Scale 2 scale via Mac. This issue is about Android. If you have a problem on macOS, please start a...
Possibly related to #883.
Interesting. I guess you will have to implement some kind of prioritization so that one device does not hog the asyncio event loop.
In #970 this was shown to be a problem with the devices themselves (when to devices transmit at the same time, one can hog the connection), so closing.