[PATCH BlueZ 0/3] Add Connectable property to org.bluez.Device

[Kevin Dewald <kevin@simpleble.org>]

bluetoothd records whether each advertising report was connectable,
from the Device Found event's Not Connectable flag, and uses it
internally, for example to pick the bearer to connect and to drop
temporary non-connectable devices when discovery stops. Applications
cannot read it over D-Bus, so they have to guess, e.g. from whether the
device has a name, which is wrong for named beacons and for unnamed
peripherals.

This series exposes it as a read-only Connectable property on
org.bluez.Device1, emitted when it first becomes known and whenever it
changes, and prints it in bluetoothctl info.

Tested with an nRF52840 switching between ADV_IND, ADV_SCAN_IND and
ADV_NONCONN_IND advertising: the property follows each change,
including PropertiesChanged in both directions on a device kept by
continuous discovery.

Kevin Dewald (3):
  org.bluez.Device: Add Connectable property
  device: Add Connectable property
  client: Print Connectable in info

 client/main.c            |  1 +
 doc/org.bluez.Device.rst | 11 +++++++++++
 src/device.c             | 36 ++++++++++++++++++++++++++++++++++++
 3 files changed, 48 insertions(+)

-- 
2.54.0 (Apple Git-157)