Eine neue MuPiBox NG Alpha ist verfügbar: 0.2.0-alpha.14. Hier findest du die Änderungen und Fehlerbehebungen dieser Version.
Was ist neu?
New since Alpha 13
- Display the currently connected physical audio output in the Admin Quick Controls volume card and the MuPiBox companion app volume card, with a readable device name and output-type symbol.
- Follow the actual PipeWire links from the MuPiBox playback bus to the active sink rather than showing the default virtual bus or a previously selected, disconnected Bluetooth headset.
- Automatically refresh the displayed output, including Bluetooth reconnection and fallback to local speakers. An unavailable or unlinked output is explicitly marked as not detected.
- Read-only information: no changes to playback, the audio route, or automatic Bluetooth switching. The new status endpoint is also available to paired apps over encrypted remote access.
- App cache and asset integrity hashes have been updated; the separately hosted companion app must be deployed from this release source to show the new field.
Tests
- Go unit tests cover physical PipeWire link selection, Bluetooth transitions, disconnected devices, missing graphs, and avoidance of raw BlueZ MAC addresses.
- Full Go test suite, Go vet, JavaScript syntax, translations and PWA asset SRI validated before release.
Hardware acceptance still required
- On an actual Pi, verify the displayed speaker/Bluetooth names during local, Spotify and Music Assistant playback, Bluetooth disconnect/reconnect and fallback, and compare against audible output.
- Confirm the app update and live remote access independently. This is an alpha release; create a backup before installing and report anomalies with device details.