From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Peter Belau <pbelau1@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Problems reading characteristics with Bluez 5.52
Date: Thu, 2 Jan 2020 17:30:09 -0800 [thread overview]
Message-ID: <CABBYNZLe=ZmiPXg8mrU2BxY9H0hv_WvkvigyJBAs_wnq5ct_Cg@mail.gmail.com> (raw)
In-Reply-To: <CAAERL8RHaWGAg5FOwts_pdDmagSdDj-Ui3ittmop+beVj9y6dQ@mail.gmail.com>
Hi Peter,
On Thu, Jan 2, 2020 at 5:22 PM Peter Belau <pbelau1@gmail.com> wrote:
>
> I'm trying to get a Qardio ARM BP monitor working with Linux/Bluez but
> cannot seem to read any device characteristics with Bluez. My
> interaction through bluetoothctl looks like this:
>
> # menu gatt
> # attribute-info 00002a35-0000-1000-8000-00805f9b34fb
> Characteristic - Blood Pressure Measurement
> UUID: 00002a35-0000-1000-8000-00805f9b34fb
> Service: /org/bluez/hci0/dev_B0_49_5F_02_B5_61/service0400
> Value:
> 16 7f 00 49 00 5b 00 00 00 00 00 00 00 00 35 00 ...I.[........5.
> 00 00 ..
> Notifying: no
> Flags: indicate
> # select-attribute 00002a35-0000-1000-8000-00805f9b34fb
> # read
> # Attempting to read /org/bluez/hci0/dev_B0_49_5F_02_B5_61/service0400/char0410
> Failed to read: org.bluez.Error.Failed
>
> I have bluetoothd running with debug flags but nothing appears in the
> debug logs. What am I doing wrong?
Look at the flags, it only has indicate so it doesn't support reading directly.
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2020-01-03 1:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 1:20 Problems reading characteristics with Bluez 5.52 Peter Belau
2020-01-03 1:30 ` Luiz Augusto von Dentz [this message]
2020-01-03 1:57 ` Peter Belau
2020-01-03 2:03 ` Luiz Augusto von Dentz
2020-01-03 2:10 ` Peter Belau
2020-01-03 2:19 ` Luiz Augusto von Dentz
2020-01-03 2:29 ` Peter Belau
2020-01-03 2:39 ` Luiz Augusto von Dentz
2020-01-03 2:47 ` Peter Belau
2020-01-03 4:04 ` Peter Belau
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='CABBYNZLe=ZmiPXg8mrU2BxY9H0hv_WvkvigyJBAs_wnq5ct_Cg@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pbelau1@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).