linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: example GATT code to talk with a sensortag
Date: Mon, 11 Jan 2016 17:22:07 -0500	[thread overview]
Message-ID: <20160111222207.GE152924@redhat.com> (raw)
In-Reply-To: <CABBYNZ+9ETX4zxBWvZL_G6_8WXND0W4rGVPj+6YKyrCOzuUUhQ@mail.gmail.com>

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.

I tried poking the 'GetAll' interfaces under my device
'/org/bluez/hci0/dev_XXXXXX' using 'org.bluez.Device1' as my interface.
That got me some device info but my UUIDs were empty [].  I tried using the
'Connect' Method in the same interface but that didn't seem to change
anything.

I am scratching my head trying to understand how this works.  Looking
through the documentation in the bluez tree it appears I need a gatt-server
that provides 'GattServices1'?  Did I read that wrong?

Again, my goal was to simply read temperature data out of my sensor.  I know
the UUID and the handle (from my successful use of the gatttool), I just
don't know how to connect to the DBus correctly??? to get the same info.

Perhaps I falsely assumed that if gatttool can get it, then there was an
interface that I can use to get the same info.

I apologize for all the newbie questions.  And thank you for your patience
and help so far.

Cheers,
Don



  parent reply	other threads:[~2016-01-11 22:22 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 [this message]
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
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=20160111222207.GE152924@redhat.com \
    --to=dzickus@redhat.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).