[bluez/bluez] 5b5da0: org.bluez.Device: Add Connectable property

["github-actions[bot]" <noreply@github.com>]

  Branch: refs/heads/1178077
  Home:   https://github.com/bluez/bluez
  Commit: 5b5da032abbf80920c45bf059792bd8577a46e82
      https://github.com/bluez/bluez/commit/5b5da032abbf80920c45bf059792bd8577a46e82
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M doc/org.bluez.Device.rst

  Log Message:
  -----------
  org.bluez.Device: Add Connectable property

This adds Connectable property which indicates whether the remote
device accepts connections, as reported by its last advertising report
or inquiry result.

bluetoothd already tracks this per bearer from the Device Found event,
but it is not exposed over D-Bus, so applications cannot tell
connectable advertisers such as peripherals from non-connectable ones
such as beacons without attempting a connection.


  Commit: 435cee00b1f51dd1dda29f31c1b45d6a5c8680c8
      https://github.com/bluez/bluez/commit/435cee00b1f51dd1dda29f31c1b45d6a5c8680c8
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M doc/org.bluez.Bearer.BREDR.rst
    M doc/org.bluez.Bearer.LE.rst

  Log Message:
  -----------
  org.bluez.Bearer: Add Connectable property

This adds Connectable property to org.bluez.Bearer.LE1 and
org.bluez.Bearer.BREDR1, so it is possible to tell which bearer of a
dual-mode device accepts connections, since Device1.Connectable is
always true for them as BREDR is always considered connectable.


  Commit: 79c9fa3b88de364c38dafeaf3facc913b417c96b
      https://github.com/bluez/bluez/commit/79c9fa3b88de364c38dafeaf3facc913b417c96b
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M src/device.c

  Log Message:
  -----------
  device: Add Connectable property

This implements Connectable property using device_is_connectable, which
reports whether the last advertising report on the device's bearer was
connectable, and emits PropertiesChanged from device_update_last_seen
when the value changes or first becomes known.


  Commit: 82b1143abb3d5f54871f692955d0e465fa58019d
      https://github.com/bluez/bluez/commit/82b1143abb3d5f54871f692955d0e465fa58019d
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M src/bearer.c
    M src/bearer.h
    M src/device.c
    M src/device.h

  Log Message:
  -----------
  bearer: Add Connectable property

This implements Connectable property for both bearers. For LE it
reflects whether the last advertising report was connectable, and
PropertiesChanged is emitted from device_update_last_seen when it
changes or first becomes known. BREDR always reports it as true.


  Commit: 7ad376befa6757249cc4d7f674691d5c989eba92
      https://github.com/bluez/bluez/commit/7ad376befa6757249cc4d7f674691d5c989eba92
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M client/main.c

  Log Message:
  -----------
  client: Print Connectable in info

This prints the Connectable property of the device and its bearers with
the likes of info command:

bluetoothctl> info <addr>
...
        Connectable: yes
...
        LE.Connectable: yes


  Commit: 0ad9be996396ded044d29187cf756c3b0b053478
      https://github.com/bluez/bluez/commit/0ad9be996396ded044d29187cf756c3b0b053478
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M client/main.c

  Log Message:
  -----------
  client: Print discoverable broadcasters in red

This prints devices in red when they set the discoverable flags but are
not connectable, to warn the user they cannot be connected to despite
being discoverable.


Compare: https://github.com/bluez/bluez/compare/5b5da032abbf%5E...0ad9be996396

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications