-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem connecting to BLE devices with Windows #70
Comments
Thank you for your ideas. I agree, I have thought about this as well. My initial idea had been to not have any keyword argument at all for the |
Thank you for your quick answer, I will look at v0.4.3 when it will be available :) |
Released 0.4.3 yesterday. Timeout keyword is now available in both BlueZ and .NET backend. |
I have a similar problem. Any idea? |
@sonus89 please create a new issue and add code and traceback of errors there. |
Description
On linux (
backends/bluezdbus/client.py
),connect()
function usesdiscover()
with a timeout :await discover(timeout=0.1, loop=self.loop)
(here).On windows (
backends/dotnet/client.py
),connect()
function usesdiscover()
with a defined value:devices = await discover(2.0, loop=self.loop)
(here), which leads to random errors due to the fact that Windows is unable to discover the device to connect to within 2 seconds.Since
discover()
has a timeout var, it can be good to usetimeout=2.0
instead of2.0
inclient.py
, so developers can adapt the value without having to manually change Bleak.The text was updated successfully, but these errors were encountered: