-
Notifications
You must be signed in to change notification settings - Fork 32
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
Develop #82
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
First implementation of obtaining DBus objects with dbus-next
trasnfer object definitions for services and characterstics to dbus-next format
A potential problem with dbus-next object implementation is that there seemse to be a requirement that object members are static. Advertisement objects may or may not need all of its members. For example, is solicit UUIDs is empty, the BlueZ backend requires that it not be present at all
Currently, there may be an issue with writting. Anecdotally, writing sometimes causes the peripheral to disconnect
macOS mypy was complaining of not finding stubs
Issue61 uuid case sensitivity
64 dynamic service objects
Typo
…not-used #67 initial values in gatt tree not used
…ure-match 59 corebluetooth abstract signature match
This eliminates the need for altering privledges.
This is because bleak-winrt failes to compile. Bleak dropped support for python 3.6 with version 0.13.0
60 dbus next
Revert test server names
CoreBluetooth specification dictates that only 28 bytes of data are available for advertising over BLE. This limits the amout of data used for the local application name. These warnings are provided to indicate to the user/developer that the BLE application may not behave as expected if given long names and UUIDs for advertising.
The prioritize local name argument helps automatically display the BLE application local name over advertised UUIDs
Follow through with bleak drop
78 corebluetooth adv name
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.
Added
Changed
CoreBluetooth
backend now adjusts advertisement data based on local name length priority by default ( GATT Server name no longer advertising correctly #78 )Fixed
CoreBluetooth
characteristic class signature now matches more closes with the base class ( BlessGATTCharacteristicCoreBluetooth initialization doesn't match parent #59 )