omarchy-asus plugin

One panel for your ASUS laptop's hardware, in the Omarchy bar.

From omarchy-asus: ASUS fixes for Omarchy. A signed pacman repo carries the kernel, NVIDIA and Omarchy fixes that make an ASUS laptop work properly: the Fn+Super Win-lock keys, the touchpad, sleep with an HDMI monitor attached, the NVIDIA hibernate hang, USB-C charging profiles and more. This plugin is the control panel. → omarchy-asus.github.io · repository

Written and tested on the ASUS ROG Zephyrus G16 (GA605). Everything goes through asusd and the kernel's ASUS drivers, and each section hides when your laptop doesn't have it, so other ASUS models get what they support. The lid Slash LEDs, for example, appear only on models that have them.

What it does

• Keyboard backlight: a level for the barrel charger and one for battery / USB-C, applied on every plug and unplug; colour; and the boot/awake/sleep/shutdown lighting.
• Lid Slash LEDs: on/off, brightness, pattern (keyboard navigation: arrows or h/j/k/l, then Enter), and when it shows.
• Internal panel refresh rate per power source, a gaming rate, or pinned (60/240/Auto). It's set again after a monitor hotplug or hyprctl reload.
• Screen backlight: optionally dimmed on leaving the barrel charger, and restored on return.
• CPU power limits per charger (a USB-C charger; a weak third-party barrel that keeps dropping out), and panel overdrive per source.
• Battery charge limit (60/80/100 %).
• Fn+Super (Win-lock) mode: toast or auto-unlock, with the omarchy-asus Win-lock helper.

Install

omarchy-plugin-add https://github.com/omarchy-asus/omarchy-asus-plugin --enable

Update with omarchy-plugin-update io.github.omarchy-asus.panel; the shell reloads it by itself.

Needs: stock Omarchy (Python and PyGObject are already there). Optional:

• asusd (asusctl): the keyboard, Slash, charge limit and power limits. Without it those sections hide.
• the Fn+Super switch: asus-rog-nkey-winlock and the Win-lock kernel patch, both from omarchy-asus.

Remove

/usr/bin/python3 -I ~/.config/omarchy/plugins/io.github.omarchy-asus.panel/bridge/asus_bridge.py release   # only if you set power limits or the charge hold
omarchy-plugin-remove io.github.omarchy-asus.panel

release turns off the fan curves and asusd PPT tuning groups the plugin turned on for power limits, so no limit outlives it, and puts back a charge limit a charge hold left behind. The plugin leaves your settings in place; delete them if you want a clean slate:

• ~/.config/omarchy/omarchy-asus.conf;
• ~/.local/state/omarchy/omarchy-asus*;
• ~/.config/systemd/user/g16-winlock.service.d/mode.conf, if you changed the Fn+Super mode.

What it touches

• One process: /usr/bin/python3 -I -B bridge/asus_bridge.py, started by the shell with a cleared, allow-listed environment. It spawns nothing and uses no network.
• D-Bus (system bus):
  • asusd: reads and sets the keyboard, Slash, charge limit, panel overdrive, PPT attributes, CPU fan-curve enable and the PPT tuning group. The last three only for power-limit keys you set.
  • UPower: read only.
  • logind SetBrightness: the screen backlight, only if you set BRIGHT_BATTERY.
• D-Bus (session bus): the systemd user manager, to reload, enable and restart g16-winlock.service when you change the Fn+Super mode.
• Hyprland's IPC sockets: the monitor list, hl.monitor() for the internal panel's refresh rate, and hotplug/reload events.
• Files: it reads and writes only ~/.config/omarchy/omarchy-asus.conf, ~/.local/state/omarchy/ and the Win-lock drop-in above, and reads ~/.config/hypr/monitors.lua.
  • In ~/.local/state/omarchy/toggles/hypr/ it keeps one file, omarchy-asus-refresh.lua: the panel's refresh rate as an hl.monitor() line that Omarchy loads on every Hyprland reload. Only while the bridge runs, a rate is set and monitors.lua has a rule for the panel; the bridge removes it when it stops.
  • Directories are walked from / one component at a time without following symbolic links; each must be yours or a root-owned system directory, and none of yours may be writable by your group or others.
  • Writes go to a new private (0600) temporary file that is atomically renamed into place. A file is never left writable by anyone but you.
  • A file your group or others can write is not read (the log says so).
  • A symbolic link is never read or written through: keep a real omarchy-asus.conf (copy it from your dotfiles), and the log says so if it is a link.
• Nothing runs as root, and the plugin installs nothing system-wide.

Per power source: keyboard, refresh rate, panel overdrive

The widget applies these itself on every plug and unplug. They live in ~/.config/omarchy/omarchy-asus.conf, as plain KEY=VALUE lines (never run as a script):

This is the beginning of the README. Read the rest at the original. Read the full README ↗