mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-26 06:45:47 +03:00
[GH-ISSUE #69] Add support for recorded announcements via app #27
Labels
No labels
bug
enhancement
pull-request
released
released on @beta
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lox-audioserver#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ds556 on GitHub (Nov 16, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/69
The Loxone app provides the ability to record an announcement and then play on one or more players.
@rudyberends commented on GitHub (Nov 16, 2025):
yes, this is implemented in the testing branch
@ds556 commented on GitHub (Nov 17, 2025):
Not fully working yet..
@rudyberends commented on GitHub (Nov 17, 2025):
I don’t think this issue is related to lox-audioserver.
Everything on the Loxone side works exactly as expected.
We request playback of the original wav file. lox-audioserver sends this request to Music Assistant:
RPC request players/cmd/play_announcement → params={"player_id":"RINCON_B8E937806BED02300","url":"http://192.168.1.11:7090/alerts/cache/audio_recording.wav}But MA responds with:
RPC failed for players/cmd/play_announcement: Error: Unable to retrieve info for http://192.168.1.31:8098/announcement/RINCON_B8E937806BED02300.mp3?pre_announce=NoneSo it looks like MA is either:
1. Trying to play a pre-announcement file, or
2. Re-encoding the uploaded WAV into an MP3 before sending it to your device.
That re-encoding step fails on your system, and the error originates from the Music Assistant server, not lox-audioserver.
In my setup the WAV is streamed directly and plays fine, so the underlying issue is specific to MA's player provider. Maybe we can fix it on our side, but we need some additional info. Why is it reencoding in the first place? Can you reproduce it directly on MA?
@ds556 commented on GitHub (Nov 17, 2025):
Hmm.. there is nothing being served at "/alerts/cache/audio_recording.wav". Also, looking closer at the logs it seems there is never anything uploaded. I guess at some point we should see this:
github.com/rudyberends/lox-audioserver@419607135d/src/http/loxoneHttp/handlers/commands/uploadCommands.ts (L30)..which doesn't show up in my log. I assume there is a PUT or POST expected after the OPTIONS request which apparently never happens. FYI, I am running 16.1.11.6 .@rudyberends commented on GitHub (Nov 17, 2025):
yes, like this;
@ds556 commented on GitHub (Nov 17, 2025):
Right, do you have the OPTIONS request as well? Maybe it is picky about the OPTIONS response? Which Loxone version are you running?
@rudyberends commented on GitHub (Nov 17, 2025):
hmm, i do have the OPTIONS request and this works for me, but I was not on the latest Loxone version.
Looks like the new one needs a proper cors response.
Please try the latest testing branch again. It should also contain your queue fixes
@ds556 commented on GitHub (Nov 17, 2025):
Yep, pesky CORS. Works like a charm now, awesome!