-
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
Handle a device already being connected with the BlueZ Dbus backend #994
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a changelog entry too.
For the record, there are a couple of pitfalls with this:
In spite of these, this seems like a step in the right direction. |
The workaround I'm using for that is https://github.com/Bluetooth-Devices/bleak-retry-connector/blob/e8bb72257a4e58a55a839525b2762d7db8dcab0c/src/bleak_retry_connector/__init__.py#L246 Note: its not so pretty and I'd like to get rid of it |
This also need to handle the device not being in the history anymore
|
Still doing testing. Will do another turn once done testing |
054e365
to
ea39b73
Compare
Additional testing looks good |
Co-authored-by: David Lechner <david@lechnology.com>
Fixes #992