Fix BlueZ MTU Size Error #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a condition to check if Bleak Client is running on Bluez, and if it is, to set MTU Size. Mirrors suggestion by Bleak maintainers in `bleak/examples/mtu_size.py`
|
Thanks @glfharris! The connection issue on Linux has been pretty frustrating and I hadn’t been able to figure out how to solve it. Thank you for this. |
OkGoDoIt
pushed a commit
that referenced
this pull request
Mar 31, 2025
…doesn't do it automatically when using BlueZ backend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There seems to be a long running issue with Bleak and the default bluetooth stack on Linux BlueZ, where the MTU size isn't set correctly.
With respect to the Frame SDK, without correcting for MTU size, usually generates a
Payload length is too largeexception.I appreciate this is a pretty specific use case, but there doesn't seem to be way to easily do this on the user side, rather than modifying the library. Largely because the
__aenter__method both connects, and attempts to inject the library functions, which will fail if the MTU size is incorrect.Mirrors suggestion by Bleak maintainers in
bleak/examples/mtu_size.py, and is a little more reliable than adding a hard coded mtu size.Targets issue #1.