[GH-ISSUE #1768] Sometimes external keyboard does not trigger MonitorControl

gitea-mirror commented

2026-05-05 06:58:18 -06:00

Owner

Originally created by @faximan on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1768

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

Originally created by @faximan on GitHub (Jul 14, 2025). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1768 ### Before opening the issue, have you...? - [x] Searched for existing issues - [x] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [x] 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) ```markdown - 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 ```

gitea-mirror added the

bug

unable to reproduce

labels

2026-05-05 06:58:18 -06:00

gitea-mirror commented

2026-05-05 06:58:23 -06:00

Author

Owner

@johha commented on GitHub (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.

@johha commented on GitHub (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.

gitea-mirror commented

2026-05-05 06:58:24 -06:00

Author

Owner

@faximan commented on GitHub (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.

@faximan commented on GitHub (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.

gitea-mirror commented

2026-05-05 06:58:26 -06:00

Author

Owner

@VishalDhayalanN15 commented on GitHub (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.

@VishalDhayalanN15 commented on GitHub (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.

gitea-mirror commented

2026-05-05 06:58:29 -06:00

Author

Owner

@clementquentin commented on GitHub (Aug 29, 2025):

Same here.

@clementquentin commented on GitHub (Aug 29, 2025): Same here.

gitea-mirror commented

2026-05-05 06:58:31 -06:00

Author

Owner

@clementquentin commented on GitHub (Sep 25, 2025):

Any update @VishalDhayalanN15 @faximan @johha ?

@clementquentin commented on GitHub (Sep 25, 2025): Any update @VishalDhayalanN15 @faximan @johha ?

gitea-mirror commented

2026-05-05 06:58:32 -06:00

Author

Owner

@johha commented on GitHub (Sep 30, 2025):

I tried different kinds of keyboards (apple vs non app/ wired vs bluetooth) but could not reproduce the issue 🤷

@johha commented on GitHub (Sep 30, 2025): I tried different kinds of keyboards (apple vs non app/ wired vs bluetooth) but could not reproduce the issue 🤷

gitea-mirror commented

2026-05-05 06:58:35 -06:00

Author

Owner

@clementquentin commented on GitHub (Sep 30, 2025):

Did you change anything since Aug 6, when you reported having this problem ?

@clementquentin commented on GitHub (Sep 30, 2025): Did you change anything since Aug 6, when you reported having this problem ?

gitea-mirror commented

2026-05-05 06:58:37 -06:00

Author

Owner

@faximan commented on GitHub (Sep 30, 2025):

Did you change anything since Aug 6, when you reported having this problem ?

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...

@faximan commented on GitHub (Sep 30, 2025): > Did you change anything since Aug 6, when you reported having this problem ? 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...

gitea-mirror commented

2026-05-05 06:58:39 -06:00

Author

Owner

@johha commented on GitHub (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.

@johha commented on GitHub (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.

gitea-mirror commented

2026-05-05 06:58:41 -06:00

Author

Owner

@clementquentin commented on GitHub (Sep 30, 2025):

OK. I'm on 15.6.1 but the issue is still here...

@clementquentin commented on GitHub (Sep 30, 2025): OK. I'm on 15.6.1 but the issue is still here...

gitea-mirror commented

2026-05-05 06:58:43 -06:00

Author

Owner

@waydabber commented on GitHub (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 Accessibility or tccutil reset All.

@waydabber commented on GitHub (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](https://betterdisplay.pro)) 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 Accessibility` or `tccutil reset All`.

gitea-mirror referenced this issue

2026-10-02 22:05:12 -06:00

[GH-ISSUE #978] Shift Brightness Curve for Each Display #594

gitea-mirror changed title from ~~[GH-ISSUE #1768] External keyboard does not trigger MonitorControl~~ to [GH-ISSUE #1768] Sometimes external keyboard does not trigger MonitorControl

2026-10-02 22:07:04 -06:00

gitea-mirror added

known Issue

and removed

bug

unable to reproduce

labels

2026-10-02 22:07:04 -06:00

gitea-mirror commented

2026-10-02 22:07:05 -06:00

Author

Owner

@waydabber commented on GitHub (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.

@waydabber commented on GitHub (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.

gitea-mirror commented

2026-10-02 22:07:05 -06:00

Author

Owner

@syzygyinteractivemedia commented on GitHub (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.

  Modelnaam:	MacBook Pro
  Model-ID:	Mac17,8
  Modelnumber:	Z1MW001P8N/A
  Chip:	Apple M5 Pro
  Total cores:	18 (6 super en 12 prestaties)
  Memory:	64 GB
  Version systemfirmware:	20457.1.29
  Version OS-loader:	20457.1.29

after executing tccutil reset Accessibility my 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 commented on GitHub (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. ``` Modelnaam: MacBook Pro Model-ID: Mac17,8 Modelnumber: Z1MW001P8N/A Chip: Apple M5 Pro Total cores: 18 (6 super en 12 prestaties) Memory: 64 GB Version systemfirmware: 20457.1.29 Version OS-loader: 20457.1.29 ``` after executing `tccutil reset Accessibility` my 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.

gitea-mirror commented

2026-10-02 22:07:05 -06:00

Author

Owner

@syzygyinteractivemedia commented on GitHub (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 + Q to 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 commented on GitHub (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 + Q` to 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)

gitea-mirror commented

2026-10-02 22:07:05 -06:00

Author

Owner

@syzygyinteractivemedia commented on GitHub (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...

@syzygyinteractivemedia commented on GitHub (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...

gitea-mirror commented

2026-10-02 22:07:05 -06:00

Author

Owner

@faximan commented on GitHub (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.

@faximan commented on GitHub (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.

Rows
Columns

[GH-ISSUE #1768] Sometimes external keyboard does not trigger MonitorControl #978

Before opening the issue, have you...?

Describe the bug

Steps to reproduce

Expected behavior

Anything else?

Environment Information (please complete the following information)