LAB02-Research / HASS.Agent

Windows-based client for Home Assistant. Provides notifications, quick actions, commands, sensors and more.
https://hassagent.lab02-research.org
MIT License
1.6k stars 74 forks source link

Bug: Higher function keys not working as quick action hotkeys #334

Open petakii opened 1 year ago

petakii commented 1 year ago

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:

  1. Have a keyboard with higher F keys.
  2. Assign key between F13 and F16 to quick actions
  3. Press button
  4. Nothing happens

Expected behavior: Quick action should fire on pressing the key.

Misc info:

Please check what's applicable (multiple answers possible):

Additional context

Logs

amadeo-alex commented 1 year ago

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.

petakii commented 1 year ago

Thanks for the quick reply!

A few bigger applications came to my mind:

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.

adub08 commented 11 months ago

I was also able to verify the same issue. It would be super handy for custom macro pads. Thanks!

cashea commented 1 month ago

The app isn't recognizing Ctl-F12. Setup recognizes it.