I'm trying to remap the same key to two different keys depending on the triggers "Did Lock Screen" and "Did Unlock Screen".
I have tried different "from keys" and different "to keys" but any key is never remapped correctly. .
It would be possible to remap keys before and after locking the screen?
*BTT 4,988 & Sonoma 14,7,2
I’ll have a look! Does the remapping action in general work for you? (you can test it with some other trigger to make sure it’s not a problem with the action)
Please find the attached preset to reproduce these steps:
Assign any shortcut as a trigger (Shift+Esc in the attached preset)
Set its action to "Cycle through multiple actions"
Set action 1 to remap the caps lock to 1 and a hud overlay showing CAPS=1
Set action 2 to remap the caps lock to 2 and a hud overlay showing CAPS=2
Press the shortcut
The hud overlay shows 1 and caps lock types 1
Press the shortcut
The hud overlay shows 2 and caps lock types 1
It seems that the problem is that the first value that a remapped key takes can’t be changed via actions anymore.
If you restart BTT, the issue is not fixed.
If you restart the computer, the caps lock will work as caps lock. If you press the shortcut in this scenario, the caps lock will take the value of 1 or 2. Once the value is assigned, it can’t be changed using the action of the shortcut, as described previously.
In the other hand, I can change the remapping key of the same key at anytime using the ”remap key” trigger in the automations section.
So the trigger can remap multiple times the same key, but the action can only remap a key for the first time.
Another issue I see for remapped keys:
remap key ”F1” to key ”a” in automations section
quit BTT or disable BTT
press F1 and ”b” will still be typed
So the remapping is not removed when BTT is quitted or disabled. If this behaviour is intended, it could be documented in the configuration sidebar to avoid potential problems to users.
If I try to remap keys a to z and 0 to 9 (not keypad numbers) to any other key in the automations section, this remapping is not working. Same for volume_up, volume_down, brightness_up, brightness_down. These keys are working fine in the "To Key: " configuration, but not in the "From Key: ".
REMAP KEY ACTION.bttpreset (9.4 KB)
More info:
So the summary of the current behaviour is:
Could you check whether it behaves as expected on 4.991 ? (uploading now)
Btw. if necessary you can reset all remappings here:
Version 4,991 works fine, but there is one unexpected behaviour.
Using the previous preset, try the following:
So it seems that there is a conflict when triggers and actions are remapping the same key if the frontmost app changes.
I understand that the correct behaviour would be that Caps is remapped to Caps=3 when starting BTT due the trigger, and if the shortcut is pressed then Caps would be remapped to Caps=1 or Caps=2 without loosing this last remapping after switching apps.
That's true, always the "last executed" will win. As the ones defined in automations will reload when the app changes, these would override any previously set.
I think it makes sense to give the predefined actions priority, I'll have a look.
Try this also:
The remapping actions are removed after switching apps even when there are no remapping triggers in automations.
4.992 should now always give priority to remappings done via action. However they will not persist BTT restarts - only the ones configured in automations will persist.
Installed 4,993, and key remapping works like a charm! 
I can now remap keys when screen is locked and unlocked perfectly.
I only detect one issue with the "Reload Remappings Now" button:
Other remarks:
yep, this is because it is using a system level function at a lower level than BTT. I'll make this more clear
//edit: ah well, maybe I'll just call reset whenever BTT quits.
- a to z and 0 to 9 can't be remapped (I can't test keypad keys as I only have small apple keyboards)
that is weird, I have remapped multiple of these but I'm on macOS 15, maybe there is a difference.
Running BTT v4,9551 and Sonoma 14,7,2
Let's say Caps Lock is remapped to 1.
If I quit BTT, Caps Lock toggles Caps Lock. That's correct.
But if I disable BTT, Caps Lock doesn't type 1 and doesn't toggle Caps Lock.
I think some users would prefer that the remapping keys persist when BTT quits or disables.
What do you think of adding two checkboxes in the remapping action side-bar:
If it's not possible a per-key-remapping config, it could be in global preferences.
I think most should be fine without that option, as BTT in general needs to stay running for its functionality I think it's good to disable the remappings as well when quitting BTT.
It adds quite a bit of complexity to have both options.
Yes, I agree, it makes sense.
So the only pending issue to fix is when disabling BTT: the remapped keys are removed, but they don't recover the original function, they are "frozen".
I have also tried the 3 buttons in the trigger sidebar and none of them are working as expected:
Example for Remove All Remapping button:
Example for Activate Remapping Now button:
Example for Reload Remappings Now button:
I have tried also (for the first time) the button "Reset All Low Level Key Remappings" in Prefs/Keyboard. It's also not working as expected:
The disabling will be supported with the next alpha! I think the buttons are not needed anymore as they would immediately be overridden again by the other logic. I'll remove them 
(but keep the reset all in the settings)
It would make sense to add an option for remapping to the default value?
In other words: is it ok to remap "caps lock" to "caps lock", or it would be better for BTT to remap "caps lock" to "default value"?
BTT recognizes key to same key remappings and automatically deletes them in this case. So this is fine!
Running version 4.998 and sonoma 14.7.2
FYI, disabling BTT is not disabling the remapped keys. The rest of things are working as expected.
