From: Don Zickus <dzickus@redhat.com>
To: "Łukasz Rymanowski" <lukasz.rymanowski@codecoup.pl>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: example GATT code to talk with a sensortag
Date: Fri, 15 Jan 2016 14:06:34 -0500 [thread overview]
Message-ID: <20160115190634.GW127976@redhat.com> (raw)
In-Reply-To: <CAExxLLBo+Aytnztc1BhMjExeThZiG_NDey1JQq37+eknsBv3HA@mail.gmail.com>
On Wed, Jan 13, 2016 at 10:44:02PM +0100, Łukasz Rymanowski wrote:
> >> 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
Hi Łukasz,
Yup, I see those now and the expected GattService1/Characteristic1
interfaces.
Thanks! I'll use that with the example-gatt-client to get me going. Thanks
again!
Cheers,
Don
next prev parent reply other threads:[~2016-01-15 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 22:26 example GATT code to talk with a sensortag Don Zickus
2016-01-09 8:08 ` Barry Byford
2016-01-10 22:13 ` Luiz Augusto von Dentz
2016-01-11 14:57 ` Don Zickus
2016-01-11 18:45 ` Bastien Nocera
2016-01-11 19:58 ` Don Zickus
2016-04-01 20:21 ` Don Zickus
2016-01-11 18:14 ` Don Zickus
2016-01-11 18:43 ` Luiz Augusto von Dentz
2016-01-11 19:57 ` Don Zickus
2016-01-11 22:22 ` Don Zickus
2016-01-12 21:52 ` Łukasz Rymanowski
2016-01-13 15:06 ` Don Zickus
2016-01-13 21:44 ` Łukasz Rymanowski
2016-01-14 22:03 ` Don Zickus
2016-01-15 19:06 ` Don Zickus [this message]
2016-01-18 22:29 ` Don Zickus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160115190634.GW127976@redhat.com \
--to=dzickus@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=lukasz.rymanowski@codecoup.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.