mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-26 06:45:47 +03:00
[GH-ISSUE #132] Finally getting started: No speakers through MA #73
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#73
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 @tobsch on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/132
Hi,
I finally got the chance to install everything (:beta-latest)- great software so far!
I added the Audioserver, configured the MA instance but then I basically don't get any feedback.
My speakers are all in MA (right now snapcast, soon potentially sendspin) and I thought it would auto-expose the zones from there?
Under Zones, I do not see anything.
More details:
Any ideas? There are no log lines from MA in the log.
@rudyberends commented on GitHub (Jan 24, 2026):
Hi,
If you do not see anything under Zones, this usually means the zones have not yet been pushed by your Loxone Miniserver.
Zones are created automatically based on the Audio Server outputs that are configured in Loxone Config. Each Audio Server output becomes a zone.
To make this work, you need to add the Audio Server outputs to your Loxone configuration:
• Drag the Audio Server outputs into your project in Loxone Config.
• This will create a Player block linked to the corresponding output.
• If you need more zones, you can split outputs and add Stereo Extensions, allowing up to 24 zones per Audio Server.
Because this Audio Server is emulated, you can ignore the mono/stereo labeling. Mono outputs work perfectly fine and will still produce stereo audio. The labeling is only relevant for the Miniserver’s internal configuration.
After saving your configuration, the Miniserver will reboot and push its audio configuration to the Audio Server. Once that is done, the zones should appear.
I am not sure whether this fully matches your situation, or if you already see the zones in the web admin but are running into configuration issues. Let me know if you need further assistance.
@tobsch commented on GitHub (Jan 25, 2026):
Right - that does the trick.
Follow up q's:
@rudyberends commented on GitHub (Jan 25, 2026):
Ignore STEREO in loxone. This is for their native implementation only. We only need an output for communication. Even though they list as mono in Loxone-config, it will still be stereo.
On the Audioserver itself, you can have 4 zones by splitting the built-in outputs.
Each stereo extension adds 2 additional zones when its outputs are split.
You can add up to 10 stereo extensions, which gives a total of 24 zones per Audioserver.
To add a stereo extension:
1. Go to Zones and click “Add extension”.
2. This creates an empty extension with a new serial number.
3. Use that serial number in Loxone Config to add the extension on the Miniserver side.
Snapcast and Sendspin clients will appear automatically once they connect to the lox-audioserver.
In most cases they connect automatically; if you are running multiple sendspin/snapcast servers, you may need to point the client to the correct server manually.
Once connected, the clients will show up in the list and can be assigned to a zone.
@tobsch commented on GitHub (Jan 25, 2026):
Ah, perfect. Smells like RTFM? Or does the manual not exist yet? All works out.
And on snapcast/sendspin: I thought they'd be discovered through MA too. But this does not seem to be the case. I will check how I can thell them to connect.
@tobsch commented on GitHub (Jan 25, 2026):
Just to be sure: Do I need to run a Snapcast server on the Lox-Audioserver device too and then tell the clients to connect to that one? I am still a bit lost here.
@rudyberends commented on GitHub (Jan 25, 2026):
No lox-audioserver runs a custom snapcast (and sendspin) server implementation on both tcp and ws. If you want to use tcp you can use auto discover and it wil find the server. for ws you need to use ws://192.168.1.1:7090
@tobsch commented on GitHub (Jan 25, 2026):
Ok - as autodiscover did not work, claude code discovered port 1704... ;-) thank you!