using it

Loxone

sonn is a complete Loxone Audioserver implementation — not an add-on that talks to Loxone. Pair it with a Miniserver and it behaves like the real thing: zones, sources, favourites, alerts and the native Loxone app, with up to 24 zones — the same ceiling as the original.

Enabling the integration

Under Zones, choose Loxone integrated. The server starts listening immediately, then:

Add the AudioServer in Loxone Config using the serial and host shown in the Admin UI.
Split the stereo outputs into 4 zones and drag them into your project.
Deploy the changes and reboot the Miniserver to start pairing.

When pairing succeeds, the Audio Server icon in Loxone Config turns green and the Miniserver pushes its zones. You still configure each zone's output and receivers in the Admin UI.

Any zones you set up yourself are kept while Loxone is connected and return when you disconnect. Enabling or disabling the integration starts and stops only the Loxone protocol stack — it takes effect without a restart.

Ports

The integration uses 7091 (native Loxone app protocol) and 7095 (Miniserver protocol) — but only while it is enabled. Port 7090 carries everything else, always.

How services appear to Loxone

Non-Spotify streaming services are presented to the Miniserver as virtual Spotify accounts — that is the only vocabulary the Loxone clients have for them. Everywhere else (web player, DLNA, Subsonic) they keep their own name.

Alerts

With the integration on, native Loxone alerts work as they do on the original hardware, alongside the server's own text-to-speech and alert sounds — see the alert engine.

Credentials

When the Loxone integration is connected, Miniserver credentials work as an additional login next to sonn's own local accounts.