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 13:14:54 -0500	[thread overview]
Message-ID: <20160111181454.GZ152924@redhat.com> (raw)
In-Reply-To: <CABBYNZ+bpQQH6XhM20d62wy5Y-PWw_Vq7_jhriHFmmLvJVHtAg@mail.gmail.com>

On Sun, Jan 10, 2016 at 07:13:56PM -0300, Luiz Augusto von Dentz wrote:
> Hi Don,
> 
> On Fri, Jan 8, 2016 at 7:26 PM, Don Zickus <dzickus@redhat.com> wrote:
> > Hi,
> >
> > Sorry for the newbie question.  I stumbled upon a TI sensortag and was able
> > to communicate with it using the gatttool.  Now I am trying to figure out
> > how to build an app around that.  Googling has shown me lots of examples of
> > folks using expect scripts (around the gatttool).
> >
> > I was hoping for something in C or python.  Is there an example
> > program/script around that I can copy and expand to get me started?
> >
> > Thanks!
> >
> > Cheers,
> > Don
> 
> bluetoothctl has some generic support for GATT attributes, in addition
> we have some examples in python under test/example-gatt-client and
> test/example-gatt-server.

Hi Luiz,

Hmm, the example program complains about no such interface 'org.bluez.GattService1'.

Originally I thought that was a generic bluez interface but now I am
wondering if that was specific to the example program.

Any tip on what the expected interface should be (so I know what to add)?

(by the way, I am using bluez-5.36 if that helps)

Cheers,
Don

  parent reply	other threads:[~2016-01-11 18:14 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 [this message]
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
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=20160111181454.GZ152924@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).