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: Wed, 13 Jan 2016 10:06:41 -0500 [thread overview]
Message-ID: <20160113150640.GH127976@redhat.com> (raw)
In-Reply-To: <CAExxLLBApkDFsPE_xbbcsQPq7CMs3a+iM7uSyM3yQzHyf3Fa0Q@mail.gmail.com>
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@redhat.com> 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@intel.com>
> > 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?
Cheers,
Don
next prev parent reply other threads:[~2016-01-13 15: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 [this message]
2016-01-13 21:44 ` Łukasz Rymanowski
2016-01-14 22:03 ` Don Zickus
2016-01-15 19:06 ` Don Zickus
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=20160113150640.GH127976@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.