[Bug] Mouse schema is not displayed anymore

[guilamu]

Mouser version

Since 3.5.0

Operating system

Windows 11

OS version details

LTSC

Mouse connection type

USB receiver (Bolt / Unifying)

Logitech Options+ status

• I have confirmed that Logitech Options+ is not running

What happened?

Expected behavior

It was working on the previous version and is working on my own build (the one you used to make 3.5.0).

Steps to reproduce

1. Open Mouser
2. Mouse is detected "Mx Master Family"
3. No Mouse schema / image.

Device info JSON

{
  "device_key": "usb_receiver",
  "display_name": "USB Receiver",
  "product_id": "0xC52B",
  "product_name": "USB Receiver",
  "transport": "hidapi",
  "ui_layout": "generic_mouse",
  "supported_buttons": [
    "middle",
    "xbutton1",
    "xbutton2"
  ],
  "gesture_cids": [
    "0x00C3",
    "0x00D7"
  ],
  "dpi_range": [
    200,
    8000
  ],
  "discovered_features": {
    "REPROG_V4 (0x1B04)": "index 0x09",
    "ADJUSTABLE_DPI (0x2201)": "index 0x0C",
    "SMART_SHIFT (0x2110)": "index 0x0D",
    "BATTERY (0x1000)": "index 0x08"
  },
  "reprog_controls": [
    {
      "index": 0,
      "cid": "0x0050",
      "task": "0x0038",
      "flags": "0x0401",
      "mapped_to": "0x0050",
      "mapping_flags": "0x0000"
    },
    {
      "index": 1,
      "cid": "0x0051",
      "task": "0x0039",
      "flags": "0x0401",
      "mapped_to": "0x0051",
      "mapping_flags": "0x0000"
    },
    {
      "index": 2,
      "cid": "0x0052",
      "task": "0x003A",
      "flags": "0x0531",
      "mapped_to": "0x0052",
      "mapping_flags": "0x0000"
    },
    {
      "index": 3,
      "cid": "0x0053",
      "task": "0x003C",
      "flags": "0x0531",
      "mapped_to": "0x0053",
      "mapping_flags": "0x0000"
    },
    {
      "index": 4,
      "cid": "0x0056",
      "task": "0x003E",
      "flags": "0x0531",
      "mapped_to": "0x0056",
      "mapping_flags": "0x0000"
    },
    {
      "index": 5,
      "cid": "0x00C3",
      "task": "0x00A9",
      "flags": "0x0531",
      "mapped_to": "0x00C3",
      "mapping_flags": "0x0000"
    },
    {
      "index": 6,
      "cid": "0x00C4",
      "task": "0x009D",
      "flags": "0x0531",
      "mapped_to": "0x00C4",
      "mapping_flags": "0x0000"
    },
    {
      "index": 7,
      "cid": "0x00D7",
      "task": "0x00B4",
      "flags": "0x03A0",
      "mapped_to": "0x00D7",
      "mapping_flags": "0x0000"
    }
  ],
  "gesture_candidates": [
    "0x00C3",
    "0x00D7"
  ]
}

Log file contents

Screenshots or screen recordings

Additional context

No response

[TomBadash]

Hey @guilamu, thanks for the heads up!

While preparing Mouser to support more devices, I discovered that the USB receiver reports the same product ID regardless of which mouse is connected. This makes it difficult to distinguish between devices — so this is currently an open issue.

As a temporary workaround, I’ve set the default layout to MX Master 3S.

Could you please try version 3.5.1 and let me know if it works for you?

Thanks again, and sorry for the mess 🙏

[guilamu]

Hey @TomBadash ,

No problem for "the mess" ^^.

Just installed 3.5.1 and still no schema. Everything is working as intended though, this is just visually broken.

[TomBadash]

Hey @guilamu,

Good news! We found the root cause and pushed a fix in v3.5.2.

The issue was that your USB receiver reports a generic PID and name ("USB Receiver") to the OS regardless of which mouse is connected, so Mouser couldn't identify the actual device. The fix queries the mouse directly over HID++ to get its real name (e.g. "MX Master 3S"), which lets us load the correct layout and schema.

Could you grab the latest release and let us know if the schema shows up correctly now?

Thanks again for the detailed report -- the device info JSON you shared made this much easier to diagnose!

[guilamu]

Hey @TomBadash ,

Nope still no schema:

{
"device_key": "mx_master_3",
"display_name": "MX Master 3",
"product_id": "0xC52B",
"product_name": "Wireless Mouse MX Master 3",
"transport": "hidapi",
"ui_layout": "mx_master_3",
"supported_buttons": [
"middle",
"gesture",
"gesture_left",
"gesture_right",
"gesture_up",
"gesture_down",
"xbutton1",
"xbutton2",
"hscroll_left",
"hscroll_right",
"mode_shift"
],
"gesture_cids": [
"0x00C3",
"0x00D7"
],
"dpi_range": [
200,
8000
],
"discovered_features": {
"REPROG_V4 (0x1B04)": "index 0x09",
"ADJUSTABLE_DPI (0x2201)": "index 0x0C",
"SMART_SHIFT (0x2110)": "index 0x0D",
"BATTERY (0x1000)": "index 0x08"
},
"reprog_controls": [
{
"index": 0,
"cid": "0x0050",
"task": "0x0038",
"flags": "0x0401",
"mapped_to": "0x0050",
"mapping_flags": "0x0000"
},
{
"index": 1,
"cid": "0x0051",
"task": "0x0039",
"flags": "0x0401",
"mapped_to": "0x0051",
"mapping_flags": "0x0000"
},
{
"index": 2,
"cid": "0x0052",
"task": "0x003A",
"flags": "0x0531",
"mapped_to": "0x0052",
"mapping_flags": "0x0000"
},
{
"index": 3,
"cid": "0x0053",
"task": "0x003C",
"flags": "0x0531",
"mapped_to": "0x0053",
"mapping_flags": "0x0000"
},
{
"index": 4,
"cid": "0x0056",
"task": "0x003E",
"flags": "0x0531",
"mapped_to": "0x0056",
"mapping_flags": "0x0000"
},
{
"index": 5,
"cid": "0x00C3",
"task": "0x00A9",
"flags": "0x0531",
"mapped_to": "0x00C3",
"mapping_flags": "0x0000"
},
{
"index": 6,
"cid": "0x00C4",
"task": "0x009D",
"flags": "0x0531",
"mapped_to": "0x00C4",
"mapping_flags": "0x0000"
},
{
"index": 7,
"cid": "0x00D7",
"task": "0x00B4",
"flags": "0x03A0",
"mapped_to": "0x00D7",
"mapping_flags": "0x0000"
}
],
"gesture_candidates": [
"0x00C3",
"0x00D7"
]
}

[TomBadash]

Hey @guilamu, thanks for testing v3.5.2! The device identification fix is working (we can see "MX Master 3" instead of "USB Receiver"), but we need to dig into why the image isn't rendering.

Could you help me with two things?

Try with a fresh config: Rename your existing config file (don't delete it -- we might need it):

Navigate to %APPDATA%\Mouser
Rename config.json to config.json.bak
Restart Mouser and see if the mouse image appears
Share your config: Could you paste the contents of your config.json (the original, before renaming)? This will help us check if a stale setting is causing the issue.

Check the install path: Does the folder where you extracted Mouser contain any special characters, spaces, or accented letters in the path? (e.g. C:\Users\Prénom...)

Thanks for your patience, its a hard one but I will get it to work as soon as possible

[guilamu]

I renamed the old config file.

C:\Users\Guillaume\AppData\Roaming\Mouser

config.json

Still no mouse schema.

[guilamu]

Oh and BTW, you still have the bug (which I think was also fixed in my version) of the app not re-detecting the mouse after the computer went to sleep.

[guilamu]

Just tried 3.5.3, still no luck witch the schema. Thanks for your efforts though.

[thisislvca]

Hey @guilamu , Luca here, I took a look at this from my side.

I think Tom’s HID++ fix in v3.5.2 actually did land, but there’s probably a second issue in the packaged Windows build: Mouser seems to identify the mouse correctly, but still fails to load the actual mouse image, which is why the schema area ends up blank.

I opened #99 with a small fix for how the packaged app resolves that local image path.

Could you try a build with that change and let me know whether the mouse image/schema shows up properly now?

Thanks 🙏

[guilamu]

Hey @thisislvca, your version actually works! I haven't tried to build the exe, but just tried "python main_qml.py" which should be the same.

BTW, I think it's impossible to see which version of the app we are running in the app itself ("Mouser v3.5.3").

Anyhow, thanks for the fix!

Bests