[Windows/Wintercept] can't control keys with `deflocalkeys-wintercept`

[azizsayfiddin]

Description:
I am using Kanata with the wintercept driver on a ThinkPad T14s G3 (Windows 11). I am completely unable to control the keys in F4-F12 range.

The Problem:

1. Doesn't detect F4-F12 keys. Kanata detects only one hwid, even though there are 2 devices in device manager, HID Keyboard Device and Standard PS/2 Keyboard.
2. I tried to map brdn and brup in deflayer but got an error that these keys are unknown. When it comes to other keys, I tried to define them in deflocalkeys-wintercept, but Kanata said that it doesn't know those numbers.

Error Log:

[DEBUG] (2) kanata_state_machine::kanata: key press BrightnessDown
[ERROR] Trying to send unmapped oscode 'KEY_BRIGHTNESSDOWN', sending esc instead
[DEBUG] (2) kanata_state_machine::oskbd::windows::interception: kanata sending Keyboard { code: Esc, state: DOWN, information: 0 } to driver

Is there any way to send custom key codes like I can on Linux? Like, I can send a custom key code on Linux even though it's not defined as kanata-wintercept says. Or, does it work completely different on windows-wintercept?

[jtroo]

You could try arbitrary-code to send a subset but it looks like there isn't any VK for brightness.

https://learn.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes

Is there anything useful in debug logs when you try to press the keys that are not currently being discovered?

[azizsayfiddin]

You could try arbitrary-code to send a subset but it looks like there isn't any VK for brightness.

https://learn.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes

Is there anything useful in debug logs when you try to press the keys that are not currently being discovered?

No, there is nothing; media keys from F4 to F12 and the power button are completely ignored. It shows only one keyboard and doesn't show others that I have on Linux called "ThinkPad Extra Buttons" and "Video Bus".

[jtroo]

My guess on what's happening would be that the Windows mechanism for controlling stuff like brightness lies only in the driver layer and there is no userspace concept of it in Windows. Likely can't make it work as desired.