They’re not identical paths, but both are normal, graceful OS shutdowns in typical setups (sync, systemd stopping services, power off).
What differs is Volumio’s own shutdown step: when you use Shutdown in the UI, the backend runs plugin hooks (onVolumioShutdown) before calling systemctl poweroff. In current upstream code, the important one is networkfs: it unmounts NAS/SMB (etc.) shares that Volumio manages.
If you press PSW while the system is on, shutdown is initiated by systemd (same kind of shutdown as poweroff), but that Node.js hook doesn’t run first — the volumio service is just stopped like other services.
So:
Not “unsafe” vs menu in the sense of skipping kernel sync - both go through standard shutdown.
Yes, there can be a real difference if you rely on NAS mounts: menu shutdown tries to umount those explicitly first; PSW does not run that Volumio-specific step.
If you don’t use NAS mounts, the practical difference is usually small. If you do, menu shutdown is the safer habit until behaviour is aligned (e.g. via a systemd ExecStop or similar - that would be a product/feature discussion).
(This matches how the backend chains onVolumioShutdown → sync → systemctl poweroff in the Volumio codebase.)
sort of always thought I’d have to be using the volumio shutdown. Just got to work a solution for a single case button to start from standbye and trigger the correct shutdown method. Hmmmm a small signal relay, com connected to the push button, nc to psw and no to a gpio, powered by the 5v from the usb. That should do it