Recover an audio device that vanished after WirePlumber state went bad
The state path is right on WirePlumber 0.5.15 and I confirmed it on this machine, not only from a source. ~/.local/state/wireplumber/ exists here and holds default-nodes, default-routes and stream-properties, and the shipped Lua in /usr/share/wireplumber/scripts/ names every state file explicitly: State ("default-nodes") in default-nodes/state-default-nodes.lua, State ("default-routes") in device/state-routes.lua, State ("stream-properties") in node/state-stream.lua and StateMetadata ("default-profile") in device/state-profile.lua. So the 0.4-era worry does not apply: the record names no file that stopped existing. Both cited Arch pages still say what the record claims, checked as raw wikitext, and the WirePlumber page's 'Delete corrupt settings' section gives the same stop, delete, start sequence. wpctl set-default is still a real subcommand in 0.5.15. Four things were wrong for Omarchy 4. First the fix jumps straight to rm -rf of the whole directory when the distribution ships a narrower repair: omarchy restart audio restarts all three units and, when WirePlumber still does not answer, strips only the USB lines from default-nodes and default-routes after copying each to a timestamped .bak, which I read in /usr/share/omarchy/bin/omarchy-restart-audio rather than running. Second, the record gives no way to delete less than everything, even though the symptom points at one file, and Omarchy's own install/user/hardware/asus/fix-audio-mixer.sh demonstrates the targeted form by removing only default-routes. Third, it does not say why the stop has to come first, which is the part people skip: WirePlumber saves state on a timeout and on shutdown, so a delete while it runs is written straight back. Fourth, the pipewire-media-session cleanup is presented as a general step. That package is still in Arch extra as deprecated 1:0.4.3-1 but is not in omarchy-base.packages or omarchy-other.packages and ~/.config/pipewire does not exist on this install, so it belongs behind a condition rather than in the main path. I also checked that nothing Omarchy installs lives in the state directory, so the speaker tuning from omarchy audio tuning on, which writes to ~/.config/pipewire/ and ~/.config/systemd/user/, survives the deletion. NOT exercised: per the safety rule I did not stop wireplumber.service, delete any state file, or change a default, so the recovery itself is unverified on this machine and rests on the two Arch pages plus the shipped scripts.
Deleting the whole state directory loses every remembered per device volume, mute, card profile, route and default device choice, plus per application volumes, and you will have to set them again. Deleting one file loses only that category. There is no system level risk and no data outside the state directory is touched. Stop wireplumber.service before deleting, otherwise the file is written back from memory on shutdown and you will conclude the fix did not work.
Symptom
An audio device that used to work has vanished from wpctl status / pavucontrol, or auto-switching and the remembered default sink stopped working entirely after an update. Sometimes a device shows up but is stuck at profile "Off".
Cause
WirePlumber 0.5 persists per device state as plain text under $XDG_STATE_HOME/wireplumber, which is ~/.local/state/wireplumber by default, in four files: default-nodes for the configured default sink and source, default-routes for per profile route selection, volumes and mute, default-profile for the chosen card profile, and stream-properties for per application volume, mute and target. That state can be left inconsistent by an interrupted update, by a device whose ALSA node name changed so the stored key no longer matches anything, or by a stored profile of off that is restored on every boot. WirePlumber rewrites these files on a save timer and again on shutdown, which is why a deletion made while it is running comes straight back.
Fix
Try the shipped repair before deleting anything. On Omarchy 4, omarchy restart audio restarts pipewire.service, pipewire-pulse.service and wireplumber.service, and if PipeWire still does not answer it resets a stuck USB audio device and strips only the USB entries from default-nodes and default-routes, backing up each file first:
omarchy restart audio
If the device is still missing, delete state. Stop WirePlumber first, or the file is rewritten from memory on shutdown and your deletion is undone:
systemctl --user stop wireplumber.service
Delete only the file that matches the symptom:
~/.local/state/wireplumber/default-profile card stuck at profile "Off"
~/.local/state/wireplumber/default-routes wrong port, volume or mute per profile
~/.local/state/wireplumber/default-nodes chosen default sink or source will not stick
~/.local/state/wireplumber/stream-properties one application starts at the wrong volume or device
rm -f ~/.local/state/wireplumber/default-profile
If you cannot tell which, remove the whole directory:
rm -rf ~/.local/state/wireplumber/
Start it again and look at the graph:
systemctl --user start wireplumber.service
wpctl status
Re-set your defaults. On Omarchy 4 the shipped commands also move streams that are already playing, and they take the node id and the node name, both of which wpctl status prints:
omarchy-audio-output-set-default <node-id> <sink-name>
omarchy-audio-input-set-default <node-id> <source-name>
omarchy audio output switch cycles outputs without you having to read an id at all.
On plain Arch, take the ids from wpctl status:
wpctl set-default <sink-id>
wpctl set-default <source-id>
Only on a machine that once ran the deprecated pipewire-media-session is there anything else to clear. Omarchy 4 has never installed it, so skip this unless the directory is actually there:
rm -rf ~/.config/pipewire/media-session.d/
Nothing Omarchy installs lives in the state directory. Its audio configuration sits in ~/.config/wireplumber/wireplumber.conf.d/ and ~/.config/pipewire/, so a speaker tuning installed by omarchy audio tuning on survives all of this. Confirm with omarchy audio tuning status.
Verify
wpctl status lists every device again after the restart, the card is no longer on profile Off, and the default you set still holds after a reboot. ls ~/.local/state/wireplumber/ shows the files being written again, which is what tells you WirePlumber restarted and is saving state rather than failing early.