-
Notifications
You must be signed in to change notification settings - Fork 305
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
(Win11) Random error messages on every execution #1701
Comments
Sounds like it could be a not well-behaving Bluetooth adapter. Perhaps Intel integrated wireless/bluetooth? You can see what is going on better at a low level by logging Bluetooth packets with Wireshark as described in the troubleshooting page of the docs. |
Hi, I've got the packet log using Wireshark. The log is from the environment above
Meanwhile, I've found that using python 3.12 (where the dependencies are not bleak-winrt, but uses several packages) makes consistent error message. I'll try to log that in advance. |
If that's the case, I don't understand why directly connecting to the same computer-peripheral pair works properly but using bleak doesn't. also sorry for closing and reopening; my mistake |
Also if somebody sees this issue with Windows11 working environment, please give me
This would help a lot 👍 |
BlueZ version (: No Linux Requiredbluetoothctl -v
) in case of LinuxDescription
I'm trying to connect a remote controller to PC. The remote uses 'Just Connected' protocol.
I've built the project using python venv.
Bleak gives random error messages each time I execute it.
(It's strange because I've used bleak with no problem on this very same environment, but one day it stopped working)
Libraries I'm using on venv (checked with
pip list
):What I Did
I used this code;
Logs
Error 1 :
asyncio.exceptions.CancelledError
Error 2 :
asyncio.exceptions.TimeoutError
Error 3 :
OSError: [WinError -2147483629] The object is closed
Error 4 :
OSError: [WinError -2147023673] The operation was canceled by the user
Error 5 :
OSError: [WinError -2147024809] The parameter is incorrect.
The text was updated successfully, but these errors were encountered: