mirror of
https://github.com/gesellix/Bose-SoundTouch.git
synced 2026-08-18 00:26:29 +00:00
Tobias GesellchenandClaude Opus 4.8
56c4ae4e2d
Root cause of the failed TTS playback: the /speaker notification path makes the speaker validate the app_key via GET /v1/auth against the service, which returned 404 -> the speaker reports an invalid app key (HandleInvalidAppKeyCb) and refuses to play. Our /media/tts hosting was fine all along (confirmed by a direct GET returning the mp3). Two fixes: - TTS speak now plays the synthesized clip as a LOCAL_INTERNET_RADIO ContentItem via the /custom/v1/playback proxy (the same mechanism the "ding" health check uses), which needs no app_key. New buildCustomPlaybackURL helper + tts.Service.BaseURL(). - Add GET /v1/auth -> 200 so the /speaker notification path also works (we're the cloud replacement; a 404 there is read as "invalid app key"). Includes a TEMPORARY full-request debug dump on /v1/auth to learn how the speaker presents the app_key; to be removed later. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>