Closed Force1ess closed 1 year ago
Solaar rules can only trigger on HID+ notifications, not regular input. So your device has to be able to changes the way a key works to produce notifications and you then have to enable the key to do this via the Key/Button Diversion setting. Looking at the output of solaar show
your mouse can only do this for Middle, Back, Forward, and Smart Shift and you have not enabled diversion for any of these keys. So no notifications - no triggering of rules.
From https://pwr-solaar.github.io/Solaar/rules
By the way, it is better to capture more output of solaar -ddd
and post that output instead of a screenshot of the output. The output that you post and show does not include the notification that started rule processing.
That's right, thank u for ur patience. I read this before but I didn't get that.
Information
uname -srmo
):Linux 6.1.31-1-MANJARO x86_64 GNU/Linux
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):Describe the bug Defined rules not working. As you can see below, I defined several rules. I clicked every button on my MX anywhere3, and nothing happened. Only one button click have effect in
solaar -ddd
, I marked this button below , and here is its print 2023-06-04 15:34:30,513,513 DEBUG [MainThread] logitech_receiver.diversion: evaluate rule: Rule[Key: Brightness Up (pressed), KeyPress: XF86_MonBrightnessUp click] 2023-06-04 15:34:30,513,513 DEBUG [MainThread] logitech_receiver.diversion: evaluate condition: Key: Brightness Up (pressed)Screenshots If applicable, add screenshots to help explain your problem.