{{ message }}
Repository navigation
Sometimes external keyboard does not trigger MonitorControl #1768
Description
Before opening the issue, have you...?
- Searched for existing issues
- Looked through the wiki
- Updated MonitorControl to the latest version (if applicable)
Describe the bug
I have MonitorControl set to use "Standard keyboard brightness keys" and "Screen to control" set to "Depends on mouse pointer position". But whatever I do, when I use the brightness keys on my external Apple wired keyboard, it is always the internal MacBook display that is changing brightness.
However, when I use the keys on the MacBook keyboard, everything works as expected and MonitorControl does its thing.
This is a somewhat new bug (maybe a few months?) It used to work well with the same hardware.
Steps to reproduce
Press brightness keys on external wired Apple extended keyboard while mouse pointer position is on the external display.
Expected behavior
Brightness is changed on external display. Actually happens: brightness is changed on Macbook internal display.
Anything else?
No response
Environment Information (please complete the following information)
- macOS version: Sequoia 15.5
- Mac model: M2 MacBook Air 2022
- MonitorControl version: 4.3.3
- Monitor(s): Dell P2720DC
- Apple Silicon/M1 (yes or no): yes
Activity
johha commentedon Aug 6, 2025
I have the same issue using a MacBook M4 Pro running MacOS 15.6. It used to work for me as well a couple of weeks ago.
I tried to connect my keyboard via Bluetooth and USB while restarting MonitControl before/after connecting the keyboard but always the same issue.
faximan commentedon Aug 6, 2025
It actually started working for me again. No idea why, I thought maybe it was the update to Sequoia 15.6 but sounds like that might not be it then.
VishalDhayalanN15 commentedon Aug 27, 2025
I am experiencing the exact same problem, it works using Mac keyboard but not with external magic keyboard connected via bluetooth. It was working fine a few months ago consistently, but now it doesn't work anymore.
clementquentin commentedon Aug 29, 2025
Same here.
clementquentin commentedon Sep 25, 2025
Any update @VishalDhayalanN15 @faximan @johha ?
johha commentedon Sep 30, 2025
I tried different kinds of keyboards (apple vs non app/ wired vs bluetooth) but could not reproduce the issue 🤷
clementquentin commentedon Sep 30, 2025
Did you change anything since Aug 6, when you reported having this problem ?
faximan commentedon Sep 30, 2025
If that's a question for me I don't think I have changed anything except the recent update to macOS Tahoe. Same hardware for sure. But I cannot reproduce this issue anymore so yeah...
johha commentedon Sep 30, 2025
I upgraded to macOS 15.6.1 on August 22 but can't remember when the keyboard shortcuts worked correctly again. At the moment everything is working fine.
clementquentin commentedon Sep 30, 2025
OK. I'm on 15.6.1 but the issue is still here...
waydabber commentedon Sep 30, 2025
I could never reproduce this issue myself and even those who could reported it being fixed by itself after a while with no apparent extra effort on their part. So maybe a reboot, re-pairing or resetting something (?) helps. I just leave this ticket open here so those who have this can join up and maybe figure out what's going on. I don't think it's macOS version specific as reports like this are with as from the dawn of time lol.
It might be useful to try other similar apps (like BetterDisplay) to see if that has the problem as well or the issue is specific to accessibility permissions granted to MonitorControl.
An other thing one can try is to reset the transparancy/content/control permissions database
tccutil reset Accessibilityortccutil reset All.[-]External keyboard does not trigger MonitorControl[/-][+]Sometimes external keyboard does not trigger MonitorControl[/+]waydabber commentedon Sep 15, 2026
Since this is an unexplained, but from time-to-time recurring issue, I will treat it as "known issue" - future events like this can be reported here.
syzygyinteractivemedia commentedon Sep 18, 2026
i got the same problem right after upgrading to MacOS 27.0 (26A428) (Golden Gate)
my external apple keyboard (via usb or bluetooth) can only change internal display of Macbook pro M5 Pro.
after executing
tccutil reset Accessibilitymy input of all keyboards and mouse/trackpad (clicking) was disabled so i would not recommend doing this action...And after hard reboot i had to allow the App again in Acccessibility but it did not solve the problem....
the only way i got the external keyboard to work with the cursor option is:
MonitorControl -> Settings -> Keyboard
Brightness and Contrast adjustment -> Both Standard and custom shutcut keys
and then set F13 for Lower brightnes and F14 for higher brightness
check " do not use alternative brightness keys"
Now i use F13 and F14 to change the brightness of my external displays with my bluetooth apple keyboard.
syzygyinteractivemedia commentedon Sep 18, 2026
Oooh i found another thing.... because i also had a problem with my logitech logi options+ mouse keyboard shortcuts in VSCode i stubbled on this post.. as i could not re-enter my shortcuts: "Cmd + [ " and "Cmd + ]" (the [ and ] would not get filled in)
the app showed me an error and referred me to this website:
https://support.logi.com/hc/en-us/articles/360023189334-Logitech-Options-and-Options-issues-when-Secure-Input-is-enabled
i killed the process (although i could not find it...) in my case
sudo kill -9 391(process 391)and then used:
Cmd + Ctrl + Qto lock the screen. and logged in with my password (not touchID).and voila. i could use the original brightness keys under F1 and F2 of my bluetooth keyboard.
perhaps this also helps other people when you have this issue. Also closed my Password Manager as it looks like it has to do with secureinput (passwords as well)
syzygyinteractivemedia commentedon Sep 18, 2026
on further inspection.. it was my password manager which had a the "unlock master key" window open. which caused to start this SecureInput and at that point the brightness keys of the external keyboard gets blocked...
faximan commentedon Sep 18, 2026
Oooh nice find! This could also explain my situation. I think around the time I filed this bug, macOS had a tendency to enable secure input too often and don't turn it off. I remember often seeing the secure input warning in my terminal.