Skip to content

dbus_api, need help with profile implementation  #2

Description

@priyankguddu

Hi,
Thanks for writing a clean API for bluez python dbus with GATT profiles. I was using the library and things are good for Genric services and Device information services, but when I implement vender specific services from which the data need to be extracted
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (46a970e0-0d5f-11e2-8b5e-0002a5d5c51b)

I did following:
a) I created a python file in profiles folder with the uuid mentioned in vendor specific. I made the service class and then it detect the device.

Issues:
a) How to get the characteristics, like in service (using d-feet) I see 2 characteristics (char0017 & char 001a) corresponding to my device services, so how to identify them uniquely as different charachterstics
b) Startnotify and stopnotify methods API, how to use that cleanly, i.e I see in some example u have set .notifying = True in service rather than characteristics.
c) I see some methods like notifyx which can take callback and error back, how to use thos

I must say, its a great wrapper for direct using bluez, and if some good examples to use a new device specifically how to register a callback function on notify and how to set some raw values would be helpful.
I am meanwhile understanding other aspects in the code.

Thanks for help

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions