[GH-ISSUE #1743] DDC values not being read on v.4.3.3 #964

New issue

Closed

opened 2026-05-05 06:56:35 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:56:35 -06:00

Owner

Originally created by @davidpulse24 on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1743

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

MonitorControl v4.3.3 does not read current DDC values from the monitor either at startup or when a new monitor is plugged in.

Steps to reproduce

Connect a new screen with brightness set at a level <100
or
with the screen connected, start up monitor control.

v4.2.2 will in both cases read the value from the screen and adjust the slider to the current brightness value.

v4.3.3 has the monitor brightness slider at 100% all the time until the slider is moved, then it sets the brightness value on the monitor.

Expected behavior

Both on startup and when connecting a new screen, the current DDC brightness value should be read. Worked on v4.2.0, not on v4.3.3.

Anything else?

DDC values are correctly read and set by ddcctl
Added config

Environment Information (please complete the following information)

- macOS version: Sonoma latest
- Mac model: 2020 MBP 13'', Intel, using thunderbolt cable.
- MonitorControl version: v4.2.0 / v4.3.3 
- Monitor(s): LG 27'' 4K 27UN850-W
- Apple Silicon/M1 (yes or no): no

Originally created by @davidpulse24 on GitHub (Mar 23, 2025). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1743 ### 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 MonitorControl v4.3.3 does not read current DDC values from the monitor either at startup or when a new monitor is plugged in. ### Steps to reproduce Connect a new screen with brightness set at a level <100 or with the screen connected, start up monitor control. v4.2.2 will in both cases read the value from the screen and adjust the slider to the current brightness value. v4.3.3 has the monitor brightness slider at 100% all the time until the slider is moved, then it sets the brightness value on the monitor. ### Expected behavior Both on startup and when connecting a new screen, the current DDC brightness value should be read. Worked on v4.2.0, not on v4.3.3. ### Anything else? - DDC values are correctly read and set by ddcctl - Added config <img width="698" alt="Image" src="https://github.com/user-attachments/assets/11b213bd-8d15-49c4-9f72-5a690b673b40" /> <img width="615" alt="Image" src="https://github.com/user-attachments/assets/e9bd7538-1452-4a6b-abf6-cbc65d69f752" /> ### Environment Information (please complete the following information) ```markdown - macOS version: Sonoma latest - Mac model: 2020 MBP 13'', Intel, using thunderbolt cable. - MonitorControl version: v4.2.0 / v4.3.3 - Monitor(s): LG 27'' 4K 27UN850-W - Apple Silicon/M1 (yes or no): no ```

gitea-mirror

2026-05-05 06:56:35 -06:00

closed this issue
added the
bug

Status: Abandoned
labels

gitea-mirror commented

2026-05-05 06:56:40 -06:00

Author

Owner

@stale[bot] commented on GitHub (Apr 11, 2026):

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 11, 2026): Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:56:42 -06:00

Author

Owner

@davidpulse24 commented on GitHub (Apr 18, 2026):

Not fixed as far as I’m aware. On 18 Apr 2026, at 01:27, stale[bot] @.***> wrote:
Closed #1743 as completed.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

@davidpulse24 commented on GitHub (Apr 18, 2026): Not fixed as far as I’m aware. On 18 Apr 2026, at 01:27, stale[bot] ***@***.***> wrote: Closed #1743 as completed. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>