HASS.Agent
HASS.Agent copied to clipboard
Bug: Higher function keys not working as quick action hotkeys
Description: Quick actions are not working when using F13-F16 function keys. I'm using a Keychron keyboard with multiple function keys, the hotkey input box recognizes it correctly, but nothing happens when I press it. Setting it as F17-F24 works. Standard function keys work as expected. Used keyboard: Keychron V6
Steps to reproduce the behavior:
- Have a keyboard with higher F keys.
- Assign key between F13 and F16 to quick actions
- Press button
- Nothing happens
Expected behavior: Quick action should fire on pressing the key.
Misc info:
- Windows build: Win10 22H2, 19045.3208
- Windows' UI language: Hungarian
- HASS.Agent version: 2022.14.0
Please check what's applicable (multiple answers possible):
- [x] Installed via installer
- [ ] Installed manually
- [x] Problem occurs in HASS.Agent
- [ ] Problem occurs in Satellite Service
Additional context
Logs
Hello, thanks for reporting this! We're using the WK.HotKeyListener (https://github.com/Willy-Kimura/HotkeyListener) to handle the hotkeys. Currently the 1.3.0 version is baked into the HASS.Agent (newest nuget package is 1.9.0 and we should probably switch to using this).
Most likely will need to test with the newest version of the library (although I cannot see any notes regarding aforementioned keys not working) but may take me some time as I lack the keyboard with F keys higher then 12 :)
Would you in the meantime test if those keys are working with any other software allowing for key->action mapping? Preferably not keychron made.
Thanks for the quick reply!
A few bigger applications came to my mind:
- VLC: None of the F13+ keys work
- Word: F13-F16 works, F17-F24 don't
- Photoshop: All the keys work
- Fusion360: None of the F13+ keys work
It seems like this is not at all standardized, not suprised why some listeners won't recognize it. Some source say you can input F13, F14, F15 as Shift+F1, F2, F3 etc, but it doesn't seem to work on my keyboard, probably because it has a custom firmware (QMK), maybe you can test it that way if yours behaves like that.
I was also able to verify the same issue. It would be super handy for custom macro pads. Thanks!