Hi Don, On 13 January 2016 at 16:06, Don Zickus <dzickus@xxxxxxxxxx> wrote: > On Tue, Jan 12, 2016 at 10:52:47PM +0100, Łukasz Rymanowski wrote: >> Hi Don, >> >> On 11 January 2016 at 23:22, Don Zickus <dzickus@xxxxxxxxxx> wrote: >> > On Mon, Jan 11, 2016 at 03:43:40PM -0300, Luiz Augusto von Dentz wrote: >> >> Hi Don, >> >> >> >> >> >> You will need to pass -E to bluetoothd to enable the experimental >> >> intefaces, btw there is a recent change to GATT server/peripheral so I >> >> suggest you try with the current version on git. >> > >> > Hi Luiz, >> > >> > I passed the -E and compiled and installed the latest git version of bluez >> > >> > commit e81aeaea21db84042ee0c30159290ca56d250111 >> > Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> >> > Date: Wed Jan 6 12:20:45 2016 -0300 >> > >> > I installed d-feet to help me with the d-bus interfaces as I was struggling >> > with that. With the -E option I now see 'GattManager1' pop up under >> > '/org/bluez/hci0'. >> > >> > I guess I was expecting to see a 'GattService1' and 'GattCharacteristic1', >> > but I don't. >> > > > Hi Łukasz, > > Thanks for the feedback! > >> >> Start discovery from org.bluez.Adapter1. After that find device object >> of your device. Then connect to this device form org.bluez.Device1. >> Once connected GattServices and GattCharacteristincs should be visible for you. >> >> All this you can do with d-feet of course. > > So, I tried your suggestions from within d-feet and made good progress, but > I don't think I am quite there yet. Here is what I did inside d-feet: > > Under /org/bluez/hci0 -> Interfaces -> org.bluez.Adapter1 -> Methods -> > StartDiscovery --> double clicked and 'executed' this > > Under /org/bluez/hci0/dev_XXXXX -> Interfaces -> org.bluez.Device1 -> > Methods -> Connect --> double clicked and 'executed' this > > Under /org/bluez/hci0/dev_XXXX -> Interfaces -> > org.freedesktop.DBus.Properties -> GetAll ---> double clicked, entered > '"org.bluez.Device1"' and 'executed' this > ---> received valid UUIDs, GattServices, etc as output > > Thank you! > > > I did _not_ see GattCharacteristic1 in the output, nor do I see either > GattService or GattCharacteristic1 show up as an interface in either > /org/bluez/hci0/dev_XXXXX or /org/bluez/hci0. > > > Did I miss a step or misunderstand your suggestion? You got it well. To be more clear. If your bluetoothd runs with -E option and you connect to BLE device which expose any GATT services, after connect you should see new objects paths. Smth like this: a) /org/bluez/hci0/dev_XXXXX/servicexxxx b) /org/bluez/hci0/dev_XXXXX/servicexxxx/charyyyy c) /org/bluez/hci0/dev_XXXXX/servicexxxx/charzzzz etc. Inside a) you should see GattService1 and inside b) and c) GattCharacteristic1 Just make sure -E is there and if still not work, provide btmon.log > > > Cheers, > Don -- BR / Pozdrawiam Łukasz -- 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
