@@ -40,7 +40,8 @@ void Connect()
are skip and check latest seen bearer.
3. Connect last seen bearer, in case the timestamps are the same BR/EDR
- takes precedence.
+ takes precedence, or in case **PreferredBearer** has been set to a
+ specific bearer then that is used instead.
Possible errors:
@@ -346,3 +347,29 @@ array{object, dict} Sets [readonly, experimental]
:byte Rank:
Rank of the device in the Set.
+
+string PreferredBearer [readwrite, optional, experimental]
+``````````````````````````````````````````````````````````
+
+ Indicate the preferred bearer when initiating a connection, only
+ available for dual-mode devices.
+
+ When changing from "bredr" to "le" the device will be removed from the
+ 'auto-connect' list so it won't automatically be connected when
+ adverting.
+
+ Note: Changes only take effect when the device is disconnected.
+
+ Possible values:
+
+ :"last-seen":
+
+ Connect to last seen bearer first. Default.
+
+ :"bredr":
+
+ Connect to BR/EDR first.
+
+ :"le":
+
+ Connect to LE first.
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> This introduces PreferredBearer property which can be used to indicate what bearer shall be connected first rather than just using last seen bearer which may not work always since it seems some devices sometimes advertises on LE bearer but expects connections over BR/EDR e.g: https://github.com/bluez/bluez/issues/1092 Also with the introduction of LE Audio this might become even more of a problem since most likely users would like to select which bearer to use rather than using the last-seen policy. --- doc/org.bluez.Device.rst | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-)