Is Hypridle not working with 26.08.21 my mistake or currently bugged?

[Zer0Key]

Essentially title. I've looked through the config and glanced at the wiki and couldn't find anything clearly stating: "This is broken with HyDE" or "This is broken upstream" or "This should work".
The fact that hypridle is still configured using hyprlang and not LUA makes me think this is broken upstream but maybe I have something misconfigured.
All I use it for is triggering hyprlock and turning off the screen. I don't even care for suspend or hibernate.
Any info would be much appreciated.

[XNinety9]

Not your mistake, and hypridle itself isn't broken: hypridle still uses its own hyprlang file, that part is fine. What broke is the screen-off listener shipped in 26.08.21:

on-timeout = hyprctl dispatch dpms off
on-resume  = hyprctl dispatch dpms on

Since Hyprland moved to Lua, hyprctl dispatch takes Lua, so the old syntax just errors out, for example:

$ hyprctl dispatch workspace e+0
Error: [string "return hl.dispatch(workspace e+0)"]:1: ')' expected near 'e'
 → Note: dispatch in lua is a shorthand for hl.dispatch(...), your syntax might need to be updated.

It's already fixed on master (7e5b75d, "use Lua DPMS dispatchers in hypridle"), just not in a release yet. Until then, change that listener in ~/.config/hypr/hypridle.conf to:

listener {
    timeout = 300
    on-timeout = hyprctl dispatch 'hl.dsp.dpms({ action = "disable" })'
    on-resume = hyprctl dispatch 'hl.dsp.dpms({ action = "enable" })'
}

and restart hypridle (pkill hypridle; hypridle &, or log out and back in).

The lock listener (loginctl lock-session) doesn't go through hyprctl dispatch, so it should work as is. If locking doesn't happen either, run hypridle in a terminal: it logs each timeout and the command it runs, which shows which step fails. Master also has a second fix in the same file (8afb4fa) adding inhibit_sleep = 3, so the session is actually locked before suspend.