From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 458b11: org.bluez.Device: Add Connectable property
Date: Mon, 28 Sep 2026 18:15:06 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1175652/000000-3ea197@github.com> (raw)
Branch: refs/heads/1175652
Home: https://github.com/bluez/bluez
Commit: 458b112944943c3c20a349edb3f51b1ccabd6436
https://github.com/bluez/bluez/commit/458b112944943c3c20a349edb3f51b1ccabd6436
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-09-29 (Tue, 29 Sep 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: c358a6e18be841bc42682a1112b8694b9c51c571
https://github.com/bluez/bluez/commit/c358a6e18be841bc42682a1112b8694b9c51c571
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-09-29 (Tue, 29 Sep 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: 3ea1977cdc6527711d50236b966904ef50873100
https://github.com/bluez/bluez/commit/3ea1977cdc6527711d50236b966904ef50873100
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-09-29 (Tue, 29 Sep 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Print Connectable in info
This prints the Connectable property with the likes of info command:
bluetoothctl> info <addr>
...
Connectable: yes
Compare: https://github.com/bluez/bluez/compare/458b11294494%5E...3ea1977cdc65
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-29 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/1175652/000000-3ea197@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox