Feature Request: Hypridle different timeout actions for battery vs AC power

[TomSchimana]

Hypridle should support different actions based on power source. On battery, screensavers drain power unnecessarily. Just turning off the display would be better. When plugged in, screensavers are fine.

Example:

listener {
    timeout = 150                                             # 2.5min
    on-timeout = sh -c 'if cat /sys/class/power_supply/BAT*/status 2>/dev/null | grep -q "Discharging"; then hyprctl dispatch dpms off; else pidof hyprlock || omarchy-launch-screensaver; fi'
    on-resume = hyprctl dispatch dpms on && brightnessctl -r # screen on when activity is detected
}

[dhh]

I think that idea. Should be extracted into a omarchy-* bin. Please do explore a PR.

[Ojisan1]

Idle now lives in the Quickshell service and shell.json, not hypridle, so the helper-bin sketch from 2025 does not have a home anymore.

Opened #8595 against that service. Optional idle.ac / idle.battery objects override the existing screensaver / lock pair from the same UPower signal the battery service already uses. Stock battery timings stay 150/300; AC becomes 5 minutes of screensaver and 30 minutes before lock.

That is different deadlines, not the original different actions (screensaver on AC, DPMS-only on battery). The timeout split is what a docked laptop actually needs; the action split is still a follow-up if you want it.