BLE-direct devices not detected (MX Vertical + MX Keys Mini)

[Michediana]

BLE-direct devices not detected (MX Vertical + MX Keys Mini)

OpenLogi version: v0.2.0
macOS: Mac mini, Apple Silicon M2
Connection: Bluetooth direct (BLE) — no Logi Bolt receiver

Devices

• MX Vertical — Vendor ID 0x046D, Product ID 0xB020, Firmware MPM16.00_0009
• MX Keys Mini — Vendor ID 0x046D, Product ID 0xB369, Firmware RBK73.04_0016

Both devices are connected, paired, and working normally (confirmed via system_profiler SPBluetoothDataType).
Both devices connect via BLE (Services: 0x400000 < BLE >), not Bluetooth Classic.

~ % system_profiler SPBluetoothDataType | grep -A10 "MX"
          MX Keys Mini:
              Address: DE:E3:A5:24:FD:C6
              Vendor ID: 0x046D
              Product ID: 0xB369
              Battery Level: 100%
              Firmware Version: RBK73.04_0016
              Minor Type: Keyboard
              Services: 0x400000 < BLE >
          MX Vertical:
              Address: EE:5A:10:0F:8B:29
              Vendor ID: 0x046D
              Product ID: 0xB020
              Battery Level: 100%
              Firmware Version: MPM16.00_0009
              Minor Type: Mouse
              Services: 0x400000 < BLE >

Expected behavior

v0.2.0 release notes state that Bluetooth-direct devices are now first-class. I expected both devices to appear in the GUI and be configurable.

Actual behavior

Neither device appears in the GUI. Debug log shows HID++ candidate interfaces count=0 repeatedly:

DEBUG openlogi_hid::inventory: HID++ candidate interfaces count=0
INFO  openlogi_gui::app: no devices with HID++ model info — using synthetic silhouette

The CLI also confirms no support yet:

% openlogi list
No Logitech HID++ receivers found.

Notes:
  - hidpp 0.2 only recognises Logi Bolt receivers (PID 0xC548).
  - Devices paired directly over Bluetooth are not enumerated yet.

Notes

• Logi Options+ is not running
• Accessibility permission is granted
• No Logi Bolt receiver is connected — devices are paired via Bluetooth direct only

Happy to test any builds or provide further diagnostics if helpful 😊.

[linear-code]

OLG-18

[AprilNEA]

v0.3.4 contains more Bluetooth-LE/HID++ fixes and should be worth testing for the MX Vertical path. Please try v0.3.4 or newer once available, with Input Monitoring permission granted.

The MX Keys Mini part is separate from the mouse BLE fixes and is tracked under #30. If the MX Vertical still doesn't appear after v0.3.4, please share OPENLOGI_LOG=debug openlogi output around the scan.

[Michediana]

Checked now with v0.4.1, it recognizes devices properly. Even custom settings seems to work right (for MX Vertical).
Now I only have these bugs:

MX Vertical:

1. broken device image
2. broken "buttons" page image preview
3. doesn't fetch battery percentage status
4. duplicate "dpi toggle" and "gesture button": MX Vertical only has one button on top

MX Keys Mini:

1. "buttons" page doesn't let customize any key (seems broken)

[AprilNEA]

Tracking thread for "device not detected"

Using this as the tracker for BLE-direct (Bluetooth, no receiver) detection. Related reports, grouped by transport:

BLE-direct — same root as here:

• UX improvements, docs clarification, missing configuration options for MX Anywhere 3S #82 — MX Anywhere 3S (Bluetooth)
• MX Master 3s Not Detected #35 — MX Master 3S (connection unconfirmed)
• MX Anywhere 2S not detected over Bluetooth on macOS #87 — MX Anywhere 2S (connection unconfirmed)
• Doesn't work with Logitech MX Mechanical Mini #33 — MX Mechanical Mini (keyboard, like the MX Keys Mini above; connection unconfirmed)

Different transport — tracked separately, NOT this issue:

• [Bug]: Cannot add MX Vertical using dongle #115 — MX Vertical via Bolt receiver (Bolt pairing path)
• M585/M590 seems not to be detected #86 — M585 / M590 (Unifying receiver)

Note: 0.5.3 changed device admission during enumeration (is_peripheral now also admits lighting-only devices and reuses the probed feature table), so every report here is worth a fresh check on 0.5.3.

[johannesrave]

If you're still looking for confirmation:
I have a MX Mechanical Mini connexted to my MacBook Pro via Bluetooth but can't see it in OpenLogi (at all). An MX Master 4 is recognized without problems.

❯ brew list --cask --versions openlogi 
openlogi 0.6.16

❯ system_profiler SPBluetoothDataType | grep -A10 "MX"
          MX Master 4:
              Address: D6:18:41:0B:4B:C2
              Vendor ID: 0x046D
              Product ID: 0xB042
              Firmware Version: RBM27.00_0015
              Minor Type: Mouse
              Services: 0x400000 < BLE >
          MX MCHNCL M:
              Address: DB:58:42:24:29:6C
              Vendor ID: 0x046D
              Product ID: 0xB367
              Firmware Version: RBK72.02_0012
              Minor Type: Keyboard

[Michediana]

Hi @AprilNEA, a few more things for version 0.6.16:

MX Vertical:

1. Buttons 4 and 5 labels are not properly aligned
2. Battery status is not yet visible
3. The "gesture button" is not fully customizable — clicking "Back" or "Central" swaps the functions of buttons 4 and 5, which doesn't make sense. The gesture button should be independently customizable, just like the other buttons.

Missing feature:

The area screenshot action (on Mac: Cmd+Shift+4) is missing from the function list. It would be great to have it with copy to clipboard as the default behavior (instead of saving to file). Would you consider adding it?

[AprilNEA]

Hi @AprilNEA, a few more things for version 0.6.16:

MX Vertical:

1. Buttons 4 and 5 labels are not properly aligned
2. Battery status is not yet visible
3. The "gesture button" is not fully customizable — clicking "Back" or "Central" swaps the functions of buttons 4 and 5, which doesn't make sense. The gesture button should be independently customizable, just like the other buttons.

Missing feature:

The area screenshot action (on Mac: Cmd+Shift+4) is missing from the function list. It would be great to have it with copy to clipboard as the default behavior (instead of saving to file). Would you consider adding it?

Thanks for the detailed follow-up. These observations were made on v0.6.16; the current status is:

• Capture Region to Clipboard was added in v0.6.17 via feat: add Capture Region to Clipboard button action #296. On macOS it uses Cmd+Shift+Ctrl+4.
• Legacy HID++ 0x1000 battery support was added in v0.6.24 via feat(battery): support legacy 0x1000 BatteryStatus and its charging quirk #312. Current MX Vertical diagnostics can report battery percentage. Please retest the Bluetooth-direct connection on the latest release and open a focused battery issue with diagnostics if it is still missing.
• The misleading Back/Forward geometry and missing independently configurable top DpiToggle button are tracked in Missing top button on MX Vertical #103. PR Map SLOT_NAME_DPI_BUTTON to DpiToggle and add verification tests #703 addresses the missing control, but it has not been merged or released yet. Please retest the reported button swap after that fix ships.