Get brightness keys working on an Apple Studio Display or Pro Display XDR
Read /usr/share/omarchy/bin/omarchy-brightness-display, -display-apple and omarchy-hyprland-monitor-focused-apple on this machine: routing, the make Apple Computer Inc, the model regex, the sudo asdcontrol call shapes and the No Apple Display HID device found message all match. Commit df819a6f (2026-08-30) deletes etc/sudoers.d/omarchy-asdcontrol, and the tag trees confirm v4.0.1 has the file and v4.0.2 does not. The omarchy-pkgs asdcontrol.sudoers is a %wheel NOPASSWD grant restricted to the three hiddev shapes, the PKGBUILD is 1:0.6.0-2, and pacman -Ql asdcontrol here shows /etc/sudoers.d/50-asdcontrol (unreadable without root, not opened). Issue 8532 supports the scoping. The record does not add security detail beyond it. Default bindings in /usr/share/omarchy/default/hypr/bindings/media.lua match the o.bind form used. One defect: the not-routed fallback unbinds the plain brightness keys and points them at the Apple script for every monitor, which on a laptop silently breaks the built-in panel's brightness keys. The fix now uses a separate CTRL combination on laptops, which no Omarchy default binds. Issue 2278 is an Omarchy 3.0.2 report about /usr/local/bin/asdcontrol and is historical only. No Apple display was available, so nothing was exercised.
Adding a user to wheel gives that account full sudo, far more than brightness control. Only do it for an account that should administer the machine.
Symptom
Apple Studio Display or Pro Display XDR on Omarchy 4. The brightness keys do nothing, or the OSD appears with no level. omarchy-brightness-display prints nothing and exits 1, or prints No Apple Display HID device found. Running sudo asdcontrol by hand in a terminal works.
Cause
Omarchy 4 sends brightness for these displays through omarchy-brightness-display-apple, which runs sudo asdcontrol against the display's USB HID node. Three things must all hold, and each fails silently from a keybinding.
- **Routing.**
omarchy-brightness-displayonly takes the Apple path whenomarchy-hyprland-monitor-focused-applematches, which needs Hyprland to report makeApple Computer Incand a model matchingStudioDisplay|ProDisplayXDR|Studio XDRon the focused monitor. Anything else falls through to DDC/CI, which these displays do not answer.
- **The sudo grant.** Omarchy stopped shipping its own
/etc/sudoers.d/omarchy-asdcontrolin commit df819a6f (2026-08-30, the 4.0.2 security changes). The grant now comes from theasdcontrolpackage, 1:0.6.0-2, as/etc/sudoers.d/50-asdcontrol: NOPASSWD for%wheelonly, and only for--detect <hiddev>...,<hiddev>and<hiddev> -- [+-]N%. With an older package, or a user outsidewheel, sudo asks for a password a keybinding cannot type.
- **The HID node.**
/dev/usb/hiddev*exists only while the display's USB side is connected, which on these displays rides the same Thunderbolt cable as the picture.
Fix
**1. Check each gate:**
hyprctl monitors -j | jq -r '.[] | "\(.name) make=\(.make) model=\(.model) focused=\(.focused)"'
omarchy-hyprland-monitor-focused-apple && echo "routed to asdcontrol" || echo "NOT routed to asdcontrol"
pacman -Q asdcontrol # want 1:0.6.0-2 or newer
id -nG | tr ' ' '\n' | grep -x wheel # the package grant covers %wheel only
ls /dev/usb/hiddev* /dev/hiddev* 2>/dev/null
sudo -n asdcontrol --detect /dev/usb/hiddev*; echo "exit $?" # must not say a password is required
**2. Fix the gate that failed.**
asdcontrolmissing or older than 1:0.6.0-2: runomarchy update -y.- Not in
wheel: the package grants nothing to other users. Run brightness from an account inwheel, or add yours withsudo gpasswd -a "$USER" wheeland log out and back in (read the danger note). - No hiddev node: connect the display's Thunderbolt cable to a port that also carries USB, and check the display's camera or speakers appear in
lsusb. - Not routed (Hyprland reports a different make or model): bind keys to the Apple script directly in
~/.config/hypr/bindings.lua, and report the model string upstream.
On a laptop, keep the plain brightness keys for the built-in panel and give the Apple display its own combination:
o.bind("CTRL + XF86MonBrightnessUp", "Apple display brightness up", "omarchy-brightness-display-apple +5%", { locked = true, repeating = true })
o.bind("CTRL + XF86MonBrightnessDown", "Apple display brightness down", "omarchy-brightness-display-apple 5%-", { locked = true, repeating = true })
On a desktop where the Apple display is the only screen, replacing the plain keys is fine:
hl.unbind("XF86MonBrightnessUp")
hl.unbind("XF86MonBrightnessDown")
o.bind("XF86MonBrightnessUp", "Brightness up", "omarchy-brightness-display-apple +5%", { locked = true, repeating = true })
o.bind("XF86MonBrightnessDown", "Brightness down", "omarchy-brightness-display-apple 5%-", { locked = true, repeating = true })
Do not write a broader sudoers rule for asdcontrol, and do not run sudo omarchy-brightness-display-apple: the script calls sudo itself, and sudo strips OMARCHY_PATH.
**Plain Arch:** the Omarchy scripts do not exist there. Omarchy packages asdcontrol from https://github.com/omakasui/asdcontrol, and the same calls work by hand: sudo asdcontrol --detect /dev/usb/hiddev* to find the node, then sudo asdcontrol /dev/usb/hiddevN -- +5%.
Verify
With the Apple display focused, omarchy-brightness-display prints a percentage, the keys change the brightness, and the OSD shows the new level.
Sources
- https://github.com/omacom/omarchy/issues/8532
- https://github.com/omacom/omarchy/commit/df819a6f
- https://github.com/omacom-io/omarchy-pkgs/blob/master/pkgbuilds/asdcontrol/asdcontrol.sudoers
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-brightness-display
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-brightness-display-apple
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-hyprland-monitor-focused-apple
- https://github.com/omacom/omarchy/issues/2278
- https://github.com/omacom-io/omarchy-pkgs/blob/master/pkgbuilds/asdcontrol/PKGBUILD