Eine neue MuPiBox NG Alpha ist verfügbar: 0.2.0-alpha.47. Hier findest du die Änderungen und Fehlerbehebungen dieser Version.
Was ist neu?
MuPiBox-NG 0.2.0-alpha.47 – Bluetooth discovery and Spotify Started-tab resume
BLUETOOTH DISCOVERY
- Fix misleading "No devices found" after Bluetooth scan errors: BlueZ failures (including an unavailable/not-ready controller) are now reported rather than silently ignored.
- Include newly discovered [NEW] device events alongside the Bluetooth device list. This helps with temporary, not-yet-paired headsets which may disappear before the subsequent list command completes.
- A discovery already running (BlueZ InProgress) is accepted instead of being treated as a hard error.
- The touch UI now shows the concrete failure message returned by the backend, and the backend journal records scan failures and the number of discovered devices.
SPOTIFY AUDIOBOOKS: STARTED TAB
- Fix a started Spotify audiobook album restarting at 0:00 when opened from the Started tab, although the same audiobook resumed correctly from Continue.
- The album tile can now locate its saved chapter position even when Spotify stored a track-context checkpoint instead of an album-context checkpoint.
- A missing active username no longer discards an unambiguous checkpoint; ambiguous accounts remain isolated and cannot be silently mixed. Explicit restart still begins at 0:00.
- Fix: PR #71. Real Spotify account verification remains pending.
QUALITY AND TESTS
- New Go regression tests cover missing controllers, NotReady errors, temporary discovery events and concurrent discovery; Spotify tests verify the Started/Continue checkpoint paths and account separation.
- Standby short-press regression test stabilized for slow CI runners (PR #69; no runtime behavior changed).
- Bluetooth fix: PR #70. CI tests passed; full release checks run during publishing.
HARDWARE TEST STILL REQUIRED
- On Raspberry Pi 4 with MuPiHAT, pair each of the previously affected Bluetooth headset models from both the admin UI and the touchscreen.
- With a real Spotify account, start the same partially heard audiobook from Started and Continue; both must resume from the same saved chapter and time.
- Check that the selected output produces actual audio and reconnects after headset power cycling.
- If the scan fails again, use the displayed error and the MuPiBox diagnostics ZIP to distinguish a BlueZ/controller issue from the discovery UI.
- This alpha is not a claim of successful validation on the reporting device; no production boxes are automatically updated.