Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <YfAdnWn21MEHnwot@beta.private.mielke.cc>
In-Reply-To: <YfAdnWn21MEHnwot@beta.private.mielke.cc>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Tue, 25 Jan 2022 15:18:49 -0800
Message-ID: <CABBYNZJEB7-m38wktA4iK-HAy=9JLU9a7Y66MqXe6XEQwUx03Q@mail.gmail.com>
Subject: Re: bluetoothctl set-alias - how to select the device
To:     Dave Mielke <Dave@mielke.cc>
Cc:     Linux Bluetooth <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Dave,

On Tue, Jan 25, 2022 at 2:55 PM Dave Mielke <Dave@mielke.cc> wrote:
>
> Hi:
>
> It isn't clear to me how bluetoothctl set-alias decides which device to r=
ename. From a bit of a look at the code, it seemed like it might be the mos=
t recent connect, but that proved to be an incorrect conclusion. In the sam=
e way that select can be used to pick the active controller, is there a way=
 to explicitly pick the active device?

It only works while connected currently, we could in theory extend the
command to have an optional 2 parameter so one can enter an address.

> --
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: Dave@Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |


--=20
Luiz Augusto von Dentz