libratbag: Logitech MX Master 3 - Can't assign Macro

When using Logitech MX Master 3 I can’t map to macro, the default map for the “thumb” button is marked as UNKNOWN (it seems to be SUPER+TAB).

I would love to map this button to take screenshot as I do on Mac OS X.

I tried to map to other custom buttons, like (button 6) for example but it doesn’t work also.

All times it gave an error on piper the message I receive from ratbagd --verbose is:

ratbag error:     HID++ error from the device (3): ERR_INVALID_ARGUMENT (02)
ratbag error: Error while writing profile: 'Protocol error' (-71)
ratbag error: hidpp20: failed to update button (-71)
ratbagd error: error committing device (-1000)

Anyway, it worked to map the “thumb” button to back, left, right and middle click.

Built from git source: libratbag: 8c295479d887d379865fd0596a9d8fc5745f5ed8 piper: 4fab9ccdccbac296e866f9af1dd46a8979f192d1 Ubuntu 20.04

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Reactions: 8
  • Comments: 20 (4 by maintainers)

Most upvoted comments

Just as information for anyone that want to achieve this in the meantime: I’ve been using this other project: https://github.com/PixlOne/logiops to achieve custom mapping on my MX Master 3 thumb button. Is not as nice and user friendly as libratbag + piper, but I could fully configure all my mouse buttons the way I wanted.

same problem for Logitech MX Master 2S with v0.13.

ratbagctl cheering-viscacha button 5 action set macro KEY_A
Error: assigning a macro is not supported on this device

same here with MX Master 3 and ratbag 0.16 on Arch

same MX Master3 and ratbag 0.16 on Xubuntu

Seems like I have the same issue but with a MX Anywhere 2. Some macros work, the same that the author of this issue. I use libratbag 0.15-1 from Arch repo, 5.9.8-arch1-1 kernel. Using Unifying receiver.

Do I need to open a different issue ? Here is my logs :

I just updated from git master yesterday, head up on 8c29547.

Just to update this:

ratbagctl chanting-squirrel button 7 action set button 7

or any other button number, doesn’t give an error but also does nothing (the button keeps mapped from what I mapped previously on Piper).