Return-Path: Date: Thu, 14 Jan 2016 17:03:47 -0500 From: Don Zickus To: =?utf-8?Q?=C5=81ukasz?= Rymanowski Cc: Luiz Augusto von Dentz , "linux-bluetooth@vger.kernel.org" Subject: Re: example GATT code to talk with a sensortag Message-ID: <20160114220347.GK127976@redhat.com> References: <20160108222608.GU152924@redhat.com> <20160111181454.GZ152924@redhat.com> <20160111222207.GE152924@redhat.com> <20160113150640.GH127976@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Sender: linux-bluetooth-owner@vger.kernel.org List-ID: On Wed, Jan 13, 2016 at 10:44:02PM +0100, Łukasz Rymanowski wrote: > > 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 Some days are better than others. After rebooting yesterday, my bluetooth device stopped working... so while I am excited to test your suggestion, I am stuck trying to make it work again. So I apologize if my response comes later. I do appreciate the tips and patience! Hopefully tomorrow things will work again.. :-/ Cheers, Don