Hi Johannes, I'm not sure, but I think you accidently mixed up something and thus got misleading answers. If you want to run a peripheral, you add a GATT hierarchy as described at doc/gatt-api.txt to the dbus. Then you call bluez RegisterApplication to tell bluez to have a look at it and to setup a services. This method is available via the org.bluez.GattManager1 interface provided by the org.bluez Service. Other steps include powering up your device and advertising this service via the according org.bluez interfaces and methods. But if I understood correctly you do not want to setup a peripheral, but a central. In this case you do not need the RegisterApplication call. As a client you want to scan, to connect, and to use the Services and Characteristics provided by the remote devices. /org/bluez/hcix Use org.bluez.Adapter1 for scanning, scan filters and to power up. --> Interact with the adapter --> adapter-api.txt Use org.bluez.GattManager1 to autoconnect (RegisterProfile API... do not use RegisterApplication here) --> gatt-api.txt /org/bluez/hcix/dev_12_23_34_34_35_53 (devices will show up after scanning) Use org.bluez:Device1 to interact with the remote device: Connect/Disconnect, Pair, ConnectProfile, Name, UUIDs, RSSI, ... -->device-api.txt Below the devices you'll find full service hierarchies --> gatt-api.txt You can discover and browse them by using the ObjectManager API and Signals. For example: /org/bluez/hcix/dev_12_23_34_34_35_53/Service0002 Use the org.bluez.GattService1 API to check out the service UUID of the service that can be found at this object path. I recommend using d-feet and just browse and click on the dbus to get startet as a client. Once you got a feeling for the API by using manual calls, go on implementing whatever you need. This d-feet also helps checking if the API is still what you expect it to be (not running the bluetoothd version you expected) or if the -E flag on bluetoothd got lost. Cheers, Markus > -----Original Message----- > From: linux-bluetooth-owner@xxxxxxxxxxxxxxx [mailto:linux-bluetooth- > owner@xxxxxxxxxxxxxxx] On Behalf Of Kropf Johannes > Sent: Friday, July 08, 2016 1:45 PM > To: linux-bluetooth@xxxxxxxxxxxxxxx > Subject: bluez 5.40 - RegisterApplication as Client > > Hi, > > I have registered an application as a Gatt client using the GattManager1 interface > with an ObjectManager providing the profiles as implementations of the > GattProfile1 interface. > > As soon as I register one profile, any other profile gets accepted as well, e.g. I > registered a blood pressure profile with the supported services, but bluetoothd is > also accepting data from a weight scale device without having its service > registered on the application side. > > Is this a bug? > > Kind regards, > Johannes > > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the > body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at > http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
