i’m not sure I understand. When configured as hyper key it doesn’t act as caps lock anymore, thus the LED will also not keep enabled
Ah alright.
I thought it would work as hyper key when using with another key but still function as caps lock if only enabled alone.
I do have HyperKey app enabled that achieves this but if I configure a key shortcut with HyperKey without adding caps lock as hyper key in BTT, it doesn’t trigger.
For example:
Caps lock is not configured as hyper key in BTT
But I have HyperKey app enabled so caps lock should be detected as cmd+ctrl+opt+shift.
Now if I configure a shortcut (cmd+ctrl+opt+shift + H) and try to trigger it with Caps+H, it doesn’t work.
Most likely that app sends the events at a too high level, you could try enabling this option but it will not always help:
That didn't work but thank you!
For years, I've been able to use the Caps Lock Hyperkey functionality to use Hyperkey shortcuts when holding Caps Lock and pressing the additional key associated with a shortcut. I could also just tap Caps Lock and use it normally. However, as of two days ago, if I triggered a Hyperkey Shortcut, it would simultaneously toggle Caps Lock. Very frustrating of course!
This "Use higher level modifier recognition" setting has now disabled Caps Lock functionality, and all of my Hyperkey Shortcuts are working. This is a step forward. However, I'm curious if anything changed that would have messed with the implementation, leading to the issue with toggling Caps Lock when this setting is disabled.
Thanks for any help, and your amazing continued work, Andreas!
EDIT — Hm, now after disabling that setting, the Caps Lock key is not toggling : (
are you on the 4.999 or 5.00 build? They both should work fine for standard hyper key
This issue started for me in the last 1-2 months too and it's driving me CRAZY. Issue persists on Sequoia with BTT 5.157 - before I could hit CAPS LOCK by itself and it would work like normal, and hitting it in conjunction with another key would make it go into Hyper mode. That was great.
But in the last few months, I don't know what else changed, but no longer can I use CAPS LOCK as just CAPS LOCK as long as BTT is running.
I'm glad I'm not the only one with this issue, but a bit concerning that it doesn't seem so common. I tried the "higher level modifier key recognition" toggle but that didn't help.
I've been having this issue for a couple of months, also. I used Caps Lock as Hyper Key and also as Caps Lock for years. Now Caps Lock doesn't stay on anymore. Something broke it.
2025/02/04 16:35:51:674|ASL|performing 293|
2025/02/04 16:35:51:674|ASL|triggering action Act as Hyper Key - 5C55645D-0EBB-4423-BA30-89FBAB7C6822|
2025/02/04 16:35:51:675|ASL|already replied 103|
2025/02/04 16:35:52:325|ASL|sending ctrl up|
2025/02/04 16:35:52:325|ASL|sending ctrl up|
2025/02/04 16:35:52:326|ASL|sending shift up|
2025/02/04 16:35:52:326|ASL|sending opt up|
2025/02/04 16:35:52:326|ASL|sending cmd up|
2025/02/04 16:35:52:338|ASL|disable capslock|
1 Like
Thank you for the quick reply. I added that Toggle Caps Lock On/Off action for 'hyperkey release' as your screenshot shows, it makes no difference - I still can't use Caps Lock normally. At first the green caps lock light would light for a millisecond, now I don't see the light toggle at all
do you maybe have something else configured still? Maybe check the recently used section in BTT for anything weird to show up. Maybe delete the trigger completely and add it again.
No luck. The recently used section is normal, just shows me alternating between using the hyper key (e.g. to show windows) and hitting Caps Lock to no avail.
I deleted the Caps Lock hyper key trigger, but I noticed BTT still was preventing use of the caps lock key until I killed and restarted BTT. Caps Lock then started functioning correctly, but the second I re-created the Caps Lock hyper trigger (and the 'unused' action), the issue came back.
Issue happens both with the internal keyboard and external keyboards. I have a very boring/vanilla BTT setup that has gone unchanged for 1+ year, so I'm convinced it's a bug/regression issue with BTT - everything worked great until one day it didn't.
Which version of macOS and BTT are you currently on? The hyper key was completely reimplemented in recent BTT versions, personally I have only tested it on macOS 15 and I think macOS 14 was also reported to work fine - but I'm not sure about older versions.
Ah wait you mention already you are on Sequoia? Then it's really weird because I know many people are using it fine there. I can't really think of a reason why it would break there :-/
One thing: The current implementation allows the toggle only if the key is pressed for less than 0.5 seconds, maybe that's the issue?
Using latest MacOS Sequoia 15.3, upgraded to 15.0 back at release time.
Issue happens with this M1 MacBook Pro with a USB-C dock, external keyboard, BT mouse at my desk, but also with no peripherals attached (just standalone laptop.)
Please let me know if any logs or screenshots or other info (e.g. startup daemons etc) that could help trace the issue.
And no, rapid hitting of Caps Lock does nothing - I can never get the caps lock light to light up on my internal or external keyboard no matter how quickly I tap Caps Lock. The second I kill BTT it works fine again.
Also, if I remove the Hyper action from Caps Lock and configure Caps Lock to purely just 'toggle caps lock off/on', Caps Lock also stops working in that scenario - which is maybe very telling.
very weird, I just tried again on a few on my systems, but it works on all of them. Just to be sure, could you try to delete your capslock config in BTT and import this one? (maybe restart BTT afterwards)
hyperkey.bttpreset (1.9 KB)
Really appreciate your timely assistance. I will be stepping away from my keyboard for a while soon.
I erased my trigger and imported yours - same issue, Hyper key works fine but no luck with Caps Lock - the OS seems to be completely oblivious about it.
I would be OK to back up and then blow away my entire BTT setup in case some gremlins are hiding, if you want to explore that. Any tips on how to do a full backup + wipe would be appreciated.
maybe you could go to help => export diagnostic debug information and send the result to me (andreas@folivora.ai). Possibly some of the logs show why it's not working.
Hey for anyone who finds this thread, I was struggling with this - on two devices - running 5.199 and macOS 15.3.1. I deleted and recreated the hyper key shortcut, and even installed the version linked above, all to no avail. What finally fixed it for me was realizing that the old named trigger from the previous method was still configured, even though it was ostensibly not being called. Deleting it immediately solved my problem on both machines. Hopefully that helps some of you!
2 Likes