Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <92dfa5c7-90db-8100-b481-2bd4972a0ec1@voxel.at>
Date:   Thu, 17 Nov 2022 17:09:30 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.4.1
From:   Simon Vogl <simon@voxel.at>
Subject: Connecting to a BR/EDR+BLE device a via dbus?
To:     linux-bluetooth@vger.kernel.org
Content-Language: it
Organization: VoXel Interaction Design
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Dear all,

we are communicating with a headset-ish device that offers classic 
bluetooth services and BLE characteristics in parallel.

We have code to talk to the Bluetooth classic part via bluetoothd/dbus, 
and we have code for talking to the BLE parts based on the C-library / 
gatt-client code ; both run in parallel for some time but not 
super-stable, so I'd like to move the code over to a dbus version.

As the device starts advertising BLE characteristics only after a 
classic connection has been established, it appears as a Bluetooth 
classic device on the system bus, and I did not find a way to start GATT 
discovery via the 'official' dbus-API.

I don't fear to tweak bluetoothd nor ~ctl, but would like to know if 
someone already some development going in that direction?

Simon

-- 

VoXel Interaction Design  |www.voxel.at
DI Dr.techn. Simon Vogl   |simon@voxel.at
Tomaschekweg 46           |  +43 650 2323 555
A-4040 Linz - Austria     |
Office address: Industriezeile 35, 4020 Linz (2nd floor)