Shortcuts triggers do not identify Logi Options+ keystrokes

Describe the bug
When I manually input the keys bound to the trigger using my builtin or external keyboard, it works correctly. I have also tried software programs that can simulate virtual inputs such as python library pyautogui's function hotkey(), they can also trigger the shortcuts I configured in BTT. However, regardless what the key combination is, any keystroke set by Logi Options+ responding to a physical button on my mouse (which is Logitech MX Master 3) never managed to trigger BTT actions.

I have also tried a keystroke visualization to see the output of Logi Options+. It seems that the time of the simulated inputs is extremely short, and the visualization on the computer screen just flashes by, not like the manually pressed keys or the other virtual inputs. This is probably the potential reason of the buggy behavior? I saw BTT has a parameter called minimum hold time. However, even though I set it to 0s, it still doesn't recognize Logi Options+ inputs at all.

By the way, Logi Options+ can correctly trigger all the OS level shortcuts as well as the shortcuts I set in the other apps. BTT is the first one I found incompatibility. I hope we can find the solution and fix it soon! Really appreciate your effort in this amazing app.


Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):
Other Mouse (Logitech MX Master 3)


Screenshots
N.A.

Device information:

  • Type of Mac: MacBook Pro M2 Max
  • macOS version: Sonoma 14.0
  • BetterTouchTool version: 4.272
  • Logi Options+ Version: 1.54.466136

:cry: Is there any update on that?

Unfortunately Logitech options creates the events at a too high level for BTT to see them.

You can activate the old keyboard shortcut implementation, which should work with Logitech Options but comes with some limitations:

This looks like a answer for the issue I was trying to research.

I recently got the Logitech MX Creative Console, and was trying to have it trigger some BTT actions. Unfortunately it sounds like using the older implementation is the only option. I'll have to look into other ways to customize my Logi buttons.