Hi Luiz, >>>>>> I'm having a problem using BLE through dbus where the GATT services >>>>>> don't appear after a BLE device has been found during a scan. What is >>>>>> available through dbus is a Device1 node with the correct address and a >>>>>> Name property of the name which was sent in the advertising beacons - >>>>>> however that's the only node available in the tree. >>>>> Are you running bluetoothd with the experimental (-E) flag? >>>> Yes: >>>> ~$ ps aux | grep bluetooth >>>> root 8277 0.0 0.1 4320 2628 ? Ss Sep21 0:00 >>>> /usr/libexec/bluetooth/bluetoothd -E >>> First and most important gatttool shall not be used along with >>> bluetoothd, it is a stand alone tool for testing. That being said you >>> need to connect in order to discover the attribute the remote device >>> has, without that we only know about the UUIDs advertised nothing >>> else. >> Yes - I was using gatttool to prove I could still connect without going >> through bluetoothd. Should I expect the GATT UUIDs, services and so on >> to be available through dbus once I've called Connect on the device? > > If you connect using gatttool it will prevent bluetoothd to discover > the attributes. > >> What I was seeing yesterday was that after calling Connect the nodes in >> dbus don't change so I still can't see the GATT bits. Is there a code >> path I could look through to see why this is? > > Start bluetoothd with -d option for printing the debugs, then start > btmon and finally use bluetoothctl to connect, if all goes fine > bluetoothctl will print the attributes found. I did this and it showed where I was going wrong: upon first discovery and connection, it takes approximately 15 seconds for the devices to register all their GATT services. I simply wasn't waiting long enough for all the dbus nodes to be populated. However I do have another issue and I'll post again if I can't figure it out. Thanks for the help! Regards Steven Davies -- 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
