A MagicMirror² module that shows now-playing information from a Music Assistant server: artist, album, song title, total length, elapsed/remaining time, a smooth progress bar, and album art — plus a short "next up" list.

Inspired by MMM-Mopidy-MPD and MMM-Spotify (blurred album-art background by default).

• Artist · song · album (album hidden automatically for radio streams)
• Total length, elapsed time and remaining time
• Smooth progress/slider bar that ticks locally every second (no network spam)
• Album / cover art from Music Assistant's image proxy
• Short Next up queue list
• Pinned + auto-fallback player selection: prefer your configured player, but automatically switch to any other player that is actively playing
• Hides itself when nothing is playing

cd ~/MagicMirror/modules
git clone https://github.com/egeekial/MMM-MusicAssistant
cd MMM-MusicAssistant
npm install

cd ~/MagicMirror/modules/MMM-MusicAssistant
git pull
npm install

Music Assistant requires a long-lived token to connect to its API (server schema version 28 and newer). Create one in the Music Assistant web UI under Settings → Security (long-lived tokens), and paste it into the module config.

Add the module to the modules array in ~/MagicMirror/config/config.js:

{
  module: "MMM-MusicAssistant",
  position: "bottom_left",
  config: {
    serverUrl: "http://192.168.1.50:8095",
    token: "<long-lived token from Music Assistant>",
    player: "Living Room", // name or player_id; auto-falls back to any playing player
    layout: "background",
    showNextUp: true,
    maxNextUp: 3,
  }
},

The module's node_helper connects to the Music Assistant WebSocket API (ws://<host>:8095/ws), authenticates with your token, and listens for queue/player events. It resolves the active player, normalizes the now-playing data (including a ready-to-load album-art URL), and pushes it to the frontend. The frontend renders the card and advances the progress bar locally so it stays smooth and in sync.

No Python dependency — the only runtime dependency is ws.

• Module stays hidden — nothing is playing, or the player name/ID doesn't match. Try leaving player empty to show whatever is currently playing.
• Authentication failed / requires a token — set a valid long-lived token.
• No album art — album-art URLs are built from serverUrl (the address you configured) by default, so make sure that URL is reachable from the mirror's browser. If your art must load from a different host, set imageBaseUrl.
• Check the MagicMirror logs (pm2 logs mm or the terminal) for [MMM-MusicAssistant] lines.

If the mirror's content goes black but you can still see the mouse cursor, the display is still powered on and the Wayland compositor is alive — what has crashed is the Electron/Chromium renderer or GPU process. (This is different from OS-level screen blanking/DPMS, which powers the whole panel off, cursor included.)

The blurred album-art background is this module's most GPU-expensive element and a likely trigger on low-power hardware like a Raspberry Pi. To test and/or work around it:

1. Disable the blurred layer — set backgroundBlur: false in the module config and restart MagicMirror. This drops the heavy GPU layer entirely and uses a flat dark panel. Run it for a few days; if the black screen stops, the layer was the trigger.
2. Confirm the crash in the logs — run MagicMirror from a terminal (or pm2 logs / journalctl --user -u <your-mm-unit>) and look for Chromium messages like GPU process exited unexpectedly, renderer process crashed, or Aw, Snap. Check dmesg -w / journalctl -k for OOM-killer entries against the Electron process.
3. Keep the blur but stop the crash — if you want the blurred look back, launch MagicMirror's Electron with --disable-gpu-compositing (or --use-gl=egl), a common fix for Chromium GPU-process crashes on Raspberry Pi / Wayland.

MIT