AprilNEA / AprilNEA/OpenLogi

[Device]: Signature M650 (non-L) is labelled "Signature M650 L" — the catalog carries one display name for model id 2b02a

Open
#1,332 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
21k
Forks
675
Avg merge
2d 5h
Merged PRs (30d)
172

Description

### Device model

Signature M650 (the plain one, not the L)

### Connection

Bluetooth (BLE direct, no receiver)

### What's the problem?

Detected, but reported as the wrong model

### `openlogi list` output

Not available: the Windows MSI installs `OpenLogi.exe`, `openlogi-agent.exe` and `openlogi-overlay.exe` only, with no CLI binary, so I pasted the config below instead.

### Details

My mouse is a plain Signature M650, but OpenLogi shows it as "Signature M650 L". Two things in OpenLogi's own data disagree with that label.

From `config.toml`:

```toml
display_name = "Signature M650 L"
codename = "Signature M650 Mouse"
model_ids = [45098, 0, 0] # 0xB02A
extended_model_id = 8
```

The catalog (`@logi-assets/catalog@0.1.0`) has a single entry for this model id:

```json
"signature_m650": { "modelId": "2b02a", "displayName": "Signature M650 L", "extendedDisplayName": "Signature M650 L" }
```

so every `2b02a` device gets the L name whatever variant it is. Its `manifest.json` does split the variants, but only for artwork: `2b02a` plus `ext1`-`ext17`, where `ext6`/`ext7` resolve to `core_metadata_left.json` (left-handed) and mine, `ext8`, resolves to `front_core.png` / `side_core.png`, the non-L artwork. So the extended model id already separates the variants for images, there is just no display name to go with it.

The device's own codename is the second signal: it reports `Signature M650 Mouse`, with no L.

One fix would be to prefer the device-reported codename when it disagrees with the catalog name, another would be per-ext display names. I cannot tell which side owns it since I do not know whether the catalog is generated here or vendored.

Everything else works on this mouse: the side buttons remap over HID++ divert and volume up/down runs fine on Windows over BLE.

### Environment

- OpenLogi 0.8.3 (winget, `AprilNEA.OpenLogi`)
- Windows 11, x86_64
- Signature M650, Bluetooth direct (`direct:046d:b02a`)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating how the vendored @logi-assets/catalog@0.1.0 data, manifest.json, and config.toml model metadata feed device display names. Compare the 2b02a ext8 path and the device-reported codename with the L and left-handed variants. Done means the plain Signature M650 is displayed without the L while other variants retain their correct names, with coverage for the model-id lookup.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.