Videos
What is the difference between MX Keys Mini and MX Mechanical Mini?
The total travel distance is different — MX Mechanical Mini is higher than MX Keys Mini: 3.2mm for MX Mechanical Mini and 1.8mm for MX Keys Mini.
How to swap between backlight effects on the MX Mechanical and MX Mechanical Mini
- Static (the default backlighting effect on MX Keys and MX Keys Mini)
- Breathing
- Reaction
- Contrast
- Wave
- Random
To swap between them, press Fn + the lightbulb key as shown:
Why are MX Mechanical Mini and MX Keys Mini different sizes?
I started having this issue a couple days ago without any idea why - there’s been no recent driver updates for the past month.
Anyway, as the title says my MX Mechanical keyboard seems to have a Bluetooth pairing issue. The “Easy Switch 1” will blink slowly until I access my computer’s Bluetooth settings and remove/re-pair it. I’m assuming that it’s a Bluetooth issue because when this happens, logi+ can’t detect the keyboard.
This repeats every time I turn the computer off/on, OR the computer enters into sleep mode. :( Any idea why this is occurring? Can I do anything to fix it? I’ve tried everything else (including resetting the keyboard) that I could find, and customer service isn’t being helpful.
This is what worked for my Logitech MX Keys Mini on Xubuntu (Ubuntu 20.04.3 LTS).
Open your terminal and run these commands:
bluetoothctl
power off
power on
agent KeyboardOnly
default-agent
pairable on
scan on
pair <mac address>
## the passkey will be printed, enter it on your keyboard ##
trust <mac address>
connect <mac address>
quit
I had the same kind of issue with a Lenovo keyboard. basically I could enter the pin code but after hitting return nothing happened.
$bluetoothctl
[bluetooth]# agent KeyboardDisplay
[bluetooth]# default-agent
[bluetooth]# scan on
[bluetooth]# pair <MAC-address>
Attempting to pair with <MAC-address>
[CHG] Device <MAC-address> Connected: yes
[agent] Passkey: xxxxxx
[agent] Passkey: xxxxx
[agent] Passkey: xxxx
[agent] Passkey: xxx
[agent] Passkey: xx
[agent] Passkey: x
[agent] Passkey:
[CHG] Device <MAC-address> Modalias: usb:<ALIAS>
[CHG] Device <MAC-address> UUIDs: <UUID>
[CHG] Device <MAC-address> ServicesResolved: yes
[CHG] Device <MAC-address> Paired: yes
Pairing successful
[CHG] Device <MAC-address> ServicesResolved: no
[CHG] Device <MAC-address> Connected: no
[CHG] Device <MAC-address> Class: 0x00000540
[CHG] Device <MAC-address> Icon: input-keyboard
[CHG] Device <MAC-address> Connected: yes
Authorize service
[agent] Authorize service <UUID> (yes/no): yes
It looks like the last step [agent] Authorize serviceis not shown in the GUI
I have linked the keyboard using Bluetooth to my PC but now I want to use the USB that comes with it, for some reason, it's not connecting, is there a button I need to use to switch from Bluetooth to wireless?
Hi,
I got myself MX Keys keyboard but I can not connect to it using Fedora 32 Plasma spin.
My steps:
Open System Settings > Bluetooth > Devices > "+" (Plus sign to add new device)
"MX Keys" device is shown in the "Bluetooth Device Wizzard" windw
Click on it and click next
"Connecting to MX Keys" progress is show for about 30 seconds
"The setup of MX Keys has failed" is shown, with no other info and options to restart the process or close
Any help would be appreciated. I'm not even sure how to debug this since nothing is shown when I do journalctl -f -u bluetooth nor dmesg -w.
Thank you