Bluetooth BLE mouse keeps changing MAC, so won't automatically pair
by JamesNorris from LinuxQuestions.org on (#5C9RB)
I have a Logitech MX Anywhere 2 BLE Mouse and an (I know!) Intel ax200 Wi-Fi/Bluetooth adaptor. I'm not sure which of them has the problem, but it means that at every boot, I need to Alf+F2, fire up Konsole and reconnect. It seems to be cycling through addresses, so in my trusted list after four days I have:
Code:E6:7B:D0:31:D8:7A
E6:7B:D0:31:D8:7B
E6:7B:D0:31:D8:7C
E6:7B:D0:31:D8:7Dall of which are the same device.
Bluetoothctl info shows this:
Code:Device E6:7B:D0:31:D8:7D (random)
Name: MX Anywhere 2
Alias: MX Anywhere 2
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
Modalias: usb:v046DpB01Fd0003
Battery Percentage: 0x32 (50)I have searched around and not seen this problem elsewhere (aside from reference to this being a security feature of the BLE protocol, which means I am presuming that it is solvable...
TIA


Code:E6:7B:D0:31:D8:7A
E6:7B:D0:31:D8:7B
E6:7B:D0:31:D8:7C
E6:7B:D0:31:D8:7Dall of which are the same device.
Bluetoothctl info shows this:
Code:Device E6:7B:D0:31:D8:7D (random)
Name: MX Anywhere 2
Alias: MX Anywhere 2
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
Modalias: usb:v046DpB01Fd0003
Battery Percentage: 0x32 (50)I have searched around and not seen this problem elsewhere (aside from reference to this being a security feature of the BLE protocol, which means I am presuming that it is solvable...
TIA