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;
Date:   Tue, 25 Jan 2022 19:43:29 -0500
From:   Dave Mielke <Dave@mielke.cc>
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     Linux Bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: bluetoothctl set-alias - how to select the device
Message-ID: <YfCZMSCW2IhtKT78@beta.private.mielke.cc>
References: <YfAdnWn21MEHnwot@beta.private.mielke.cc>
 <CABBYNZJEB7-m38wktA4iK-HAy=9JLU9a7Y66MqXe6XEQwUx03Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABBYNZJEB7-m38wktA4iK-HAy=9JLU9a7Y66MqXe6XEQwUx03Q@mail.gmail.com>
User-Agent: Mutt/2.1.3 (2021-09-10)
Precedence: bulk

[quoted lines by Luiz Augusto von Dentz on 2022/01/25 at 15:18 -0800]

>It only works while connected currently, 

Even then, it's unpredictable when more than one device is connected. In my case, for example, it can be my Bluetooth speaker as well as a braille device. I assumed, at first, that maybe it's the most recently connected device, but that, too, wasn't true. When I connected the second device it still changed the alias of the first device.

>we could in theory extend the command to have an optional 2 parameter so one can enter an address.

That, I think, would be very helpful. As I understand it, isn't set-alias only updating local (host-resident) data anyway? Also, given that set-alias isn't predictable anway when more than one device is connected, I think there definitely needs to be a way to explicitly say what one is wanting to do.

-- 
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   |