Skip to content
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

More information on client for callback (read and write) #132

Open
mklemarczyk opened this issue May 10, 2024 · 0 comments
Open

More information on client for callback (read and write) #132

mklemarczyk opened this issue May 10, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mklemarczyk
Copy link

mklemarczyk commented May 10, 2024

Describe the solution you'd like
I work on the specific application for BLE logging device. I would like to have several dedicated characteristics, that are write only. I would like to track device MAC without need to add extra data into the exchange.

Describe alternatives you've considered
Alternativly I can add each time the device name or device MAC directly into the value wrote to the characterisitics. That will be against BLE, as it will make payload bigger.

Additional context
The data is already on the BLUEZ transport object. But it is not forwarded into the bless API.
I wonder how is situation for other platforms. I work primarlly with linux based servers.

Extract of the options that are available from bluez {'device': <dbus_next.signature.Variant ('o', /org/bluez/hci0/dev_44_03_2C_91_DF_39)>, 'link': <dbus_next.signature.Variant ('s', LE)>, 'mtu': <dbus_next.signature.Variant ('q', 517)>} logged from the BlueZGattCharacteristic.ReadValue method.

@kevincar kevincar added the enhancement New feature or request label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants