[Work in Progress] Linux/BlueZ support #106
Closed
Conversation
This file contains 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
rickjansen-dev
changed the title
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.
Draft pull request for Linux/BlueZ support.
This in it's current form uses https://github.com/hashtagchris/DotNet-BlueZ. This is merely a small abstraction layer on top of DBus and uses Tdms.DBus underneath (https://github.com/tmds/Tmds.DBus) and i'm not sure it is actually supported/maintaned very well.
Currently this does not work properly because there's some issues with value notification setup in that library.
Also there's some issues in discovery of existing & new devices.
Now I tried to fix the value notification stuff in the library, and I have some success with some modifications to the library. But that would involve copying the code of the library, which is probably possible since it's licensed under the apache license, but not ideal. Since it is a rather small abstraction layer on top of dbus and most of the abstractions kind of overlap with the ones in place in sharpbrick/powered-up, I'd like to eventually do away with the DotNet-BlueZ dependency completely and directly use DBus instead (using Tmds.DBus)