MuPiBox Documentation MuPiBox NG

Troubleshooting

Common MuPiBox problems and their solution – black display, no sound, Wi-Fi drops, Spotify, battery level, standby, updates and how to get help.

The most common problems and what helps. For everything else the logs show the cause.

The admin interface cannot be reached

  • Same network? The phone or PC must be in the same home network.
  • Address with port: http://<IP>:8090/admin/. Your router shows the IP.
  • <boxname>.local does not work in every network – use the IP then.

The display stays black or touch does not react

  • Is the display profile right? Restart after a change.
  • Has the interface hung? Restart it under Touch interface.
  • In standby the display is dark and touch off – press the power button briefly.

The display does not turn fully black in standby

That is due to the display's backlight, see Display & touch. Newer Waveshare 5″ displays can only be dimmed.

No sound

  • Check the audio hardware, play the test tone.
  • Is a Bluetooth device connected? The sound then goes there.
  • Is the maximum volume too low?
  • After enabling the MuPiHAT a restart is needed.

Wi-Fi drops

  • Switch Wi-Fi power saving off (Network).
  • Use a USB Wi-Fi stick and make it preferred.
  • With rtw88 sticks, "disable deep power save".
  • Check the power supply – too little power causes dropouts.

Spotify does not play

  • Has the box been selected as a device in the Spotify app once?
  • Soloist key expired or wrong? → Spotify
  • If the page reports a block because of too many requests, wait – the box holds back by itself afterwards.
  • Over Bluetooth only with the Soloist backend.

The battery level jumps

Unplug and plug the cable once so the box measures the internal resistance. See MuPiHAT.

The box switches off on a button press instead of going into standby

  • Is standby enabled? → Display & power
  • "Power button diagnostics" shows whether systemd-logind still handles the button itself or another program reads it.
  • A long press always switches the MuPiHAT off hard.

An update fails

  • The update log under Logs shows the reason.
  • If an update fails, the box starts with the previous version – nothing is lost.

Getting help

Open an issue on GitHub with the version (see About), your hardware, a description and the downloaded log. Check beforehand that it contains nothing personal – the box redacts passwords and tokens itself.