I did a diff of "bluetoothctl show [addr]" between Bluetooth 4.0 and 5.1.
Address was random for 5.1 (will that always be the case)?
SupportedIncludes: tx-power was additional for 5.1.
What other API's could be used in a program to discern this?
John Klug
Hi John,
On Mon, Aug 22, 2022 at 9:23 AM John Klug <[email protected]> wrote:
>
> I did a diff of "bluetoothctl show [addr]" between Bluetooth 4.0 and 5.1.
>
> Address was random for 5.1 (will that always be the case)?
>
> SupportedIncludes: tx-power was additional for 5.1.
>
> What other API's could be used in a program to discern this?
So you want to figure out via D-Bus or perhaps you can just use
bluetoothctl --version if you want to know the tools version, in most
cases the tools version shall match the daemon version.
>
>
>
>
> John Klug
>
>
--
Luiz Augusto von Dentz
No.? I want the hardware version of the device as specified by Bluetooth SIG.
Or at least the manufacturer and model of the local device.
Not the bluez version.
John Klug
Hi John,
On Mon, Aug 22, 2022 at 10:57 AM John Klug <[email protected]> wrote:
>
> No. I want the hardware version of the device as specified by Bluetooth SIG.
>
> Or at least the manufacturer and model of the local device.
That is normally exposed by the bus/driver under sysfs.
> Not the bluez version.
>
>
>
>
>
> John Klug
--
Luiz Augusto von Dentz