github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #296] Acer XB280HK works with ddctl but not with MonitorControl #234

New issue

Closed

opened 2026-05-05 05:28:15 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 05:28:15 -06:00

Owner

Originally created by @jonashaag on GitHub (Sep 29, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/296

Checklist

I have searched for existing issues
I have looked through the Monitor Troubleshooting wiki
I have updated MonitorControl to the latest version

Describe the issue
MonitorControl does not allow for changing brightness, but ddctl does.

Expected behavior
Brightness control should be available (disabled/greyed out).

Additional context
ddctl changes the brightness correctly, but reports errors.

$ ./ddcctl -d 1 -b 255
D: NSScreen #478281277 (1920x1080 0°) HiDPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.serial: #ASMkbeNoxMPd
I: got edid.name: Acer XB280HK
D: action: b: 255
D: setting VCP control #16 => 255
E: Failed to send DDC command!

Possible values seem to be in [0, 100].

Environment Information (please complete the following information):

macOS version: 10.15.6
MonitorControl version: 2.1.0
Monitor(s): Acer XB280HK
Mac model: MacBook Pro 2015
Monitor Cable(s)/Connection(s): (e.g. DisplayPort) DisplayPort -> DisplayPort

Originally created by @jonashaag on GitHub (Sep 29, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/296 **Checklist**  - [x] I have searched for existing issues - [x] I have looked through [the Monitor Troubleshooting wiki](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) - [x] I have updated MonitorControl to the latest version **Describe the issue** MonitorControl does not allow for changing brightness, but `ddctl` does. **Expected behavior** Brightness control should be available (disabled/greyed out). **Additional context** `ddctl` changes the brightness correctly, but reports errors. ``` $ ./ddcctl -d 1 -b 255 D: NSScreen #478281277 (1920x1080 0°) HiDPI I: found 1 external display I: polling display 1's EDID I: got edid.serial: #ASMkbeNoxMPd I: got edid.name: Acer XB280HK D: action: b: 255 D: setting VCP control #16 => 255 E: Failed to send DDC command! ``` Possible values seem to be in [0, 100]. **Environment Information (please complete the following information):** - macOS version: 10.15.6 - MonitorControl version: 2.1.0 - Monitor(s): Acer XB280HK - Mac model: MacBook Pro 2015 - Monitor Cable(s)/Connection(s): (e.g. DisplayPort) DisplayPort -> DisplayPort

gitea-mirror

2026-05-05 05:28:15 -06:00

closed this issue
added the
monitor Issue

feedback needed from reporter
labels

gitea-mirror commented

2026-05-05 05:28:21 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 30, 2020):

So if I understand correctly, ddcctl reports the sending of the command failed but it works anyways? I could perhaps try to provide a build where the check for ddc is disabled for you to test (or you could test it yourself if you know how).

Do keep in mind that we're not using ddcctl under the hood anymore but perhaps if we disable the ddc check it might work. If that's the case we could provide it as an "advanced prefs" setting.

@JoniVR commented on GitHub (Sep 30, 2020): So if I understand correctly, ddcctl reports the sending of the command failed but it works anyways? I could perhaps try to provide a build where the check for ddc is disabled for you to test (or you could test it yourself if you know how). Do keep in mind that we're not using ddcctl under the hood anymore but perhaps if we disable the ddc check it might work. If that's the case we could provide it as an "advanced prefs" setting.

gitea-mirror commented

2026-05-05 05:28:23 -06:00

Author

Owner

@jonashaag commented on GitHub (Sep 30, 2020):

I guess that would work!

@jonashaag commented on GitHub (Sep 30, 2020): I guess that would work!

gitea-mirror commented

2026-05-05 05:28:24 -06:00

Author

Owner

@jonashaag commented on GitHub (Sep 30, 2020):

And yes, the command seems to be executed correctly, even though an error is reported.

@jonashaag commented on GitHub (Sep 30, 2020): And yes, the command seems to be executed correctly, even though an error is reported.

gitea-mirror commented

2026-05-05 05:28:26 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

Hi, you might want to try the new version 3.0.0 to confirm that the issue is still present (or not). If it does not work please provide a screenshot of the Displays tab so we might see how MonitorControl recognizes the display (controllable or not). Thank you!

@waydabber commented on GitHub (Aug 21, 2021): Hi, you might want to try the new version 3.0.0 to confirm that the issue is still present (or not). If it does not work please provide a screenshot of the Displays tab so we might see how MonitorControl recognizes the display (controllable or not). Thank you!

gitea-mirror commented

2026-05-05 05:28:29 -06:00

Author

Owner

@jonashaag commented on GitHub (Aug 21, 2021):

Unfortunately I don’t have that particular display anymore so won’t be able to test :(

@jonashaag commented on GitHub (Aug 21, 2021): Unfortunately I don’t have that particular display anymore so won’t be able to test :(

gitea-mirror commented

2026-05-05 05:28:31 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

Ok, no problem. Thanks for the reply! Hope the new display works properly with MonitorControl. :)

I'll close this issue then.

@waydabber commented on GitHub (Aug 21, 2021): Ok, no problem. Thanks for the reply! Hope the new display works properly with MonitorControl. :) I'll close this issue then.

gitea-mirror referenced this issue

2026-05-05 06:28:25 -06:00

[GH-ISSUE #1127] LG monitor OSD flicker on keypress #666