Loxone Audio Server and Mini Server: Streaming and KNX Room Control

Loxone Audio Architecture

Loxone offers two audio paths: the Loxone Audio Server (standalone, 6 stereo zones, 50Wx2 per zone) and the Loxone Mini Server with Loxone Audio Extension (2 stereo zones per extension, up to 4 extensions = 8 zones). The Audio Server runs independently of a Miniserver — it has its own Ethernet connection and is configured in Loxone Config software.

For KNX integration: the Loxone Miniserver connects to KNX via the Loxone KNX Extension (DIN rail, KNX TP bus). All audio control objects from the Miniserver are exposed as KNX virtual inputs/outputs via the KNX Extension.

Loxone KNX Extension Setup

Loxone KNX Extension (100309): DIN rail device with KNX TP bus terminals. In Loxone Config: add KNX Extension to device tree and configure individual address (e.g. 1.1.20). The KNX Extension acts as a standard KNX device — program via ETS6 or directly within the Loxone Config KNX module.

In Loxone Config Audio: add Audio Server (enter Audio Server IP address). Loxone Config automatically discovers Audio Server zones. Drag 'Audio Player' blocks into each room in the building structure. Each room Audio Player exposes virtual IOs: 'Play/Pause' (digital), 'Volume' (analogue 0-100), 'Source' (analogue — source index), 'Track next/previous' (digital).

KNX Group Address Mapping

In Loxone Config KNX module: right-click Audio Player 'Volume' output and select 'Assign KNX address'. Set GA e.g. 5/1/1 (zone 1 volume, DPT 5.001). Assign 'Play/Pause' to GA 5/1/0 (DPT 1.001). Assign 'Source selection' to GA 5/1/2 (DPT 5.010, 0=radio, 1=line in, 2=Spotify, 3=AirPlay).

This mapping means any standard KNX wall panel with a value sender (e.g. MDT BE-GT2TW glass panel) can send volume changes and source commands directly to the Loxone Audio Server. KNX scene commands can trigger Loxone audio scenes.

Spotify Connect and Streaming Sources

Loxone Audio Server supports: Spotify Connect (premium account — Audio Server appears as a Spotify device in the app), AirPlay 2 (iPhone/iPad/Mac audio to any zone), TuneIn internet radio (configured in Loxone Config Audio library), and line-level RCA inputs (one per Audio Server zone, for CD/TV/turntable).

Spotify control from KNX: Loxone Miniserver runs Spotify control logic — KNX GA 5/1/10 (DPT 5.010 playlist index) triggers Loxone to start a configured Spotify playlist on zone 1. This requires Spotify Connect token setup in Loxone Config (Settings > Cloud Services > Spotify).

KNX wake-up scene: morning alarm in ETS6 KNX timer sends to GA 0/0/20 (scene trigger) — Loxone receives the scene number and activates the bedroom Audio Player at 20% volume on the TuneIn morning playlist source.

Multi-Room Synchronisation

Loxone Config 'Synchronise zones' block links multiple Audio Player volumes. When GA 5/2/50 (master volume, DPT 5.001) receives a value: Loxone scales and writes to all zone Audio Player volume inputs simultaneously. Individual zone override still works via zone-specific GA.

Party mode: KNX GA 0/0/21 (DPT 1.001, value 1) triggers Loxone logic to set all Audio Server zones to the same source (Spotify) and volume 60%, with synchronised playback. A single KNX pushbutton on any wall panel controls the entire house audio in one tap.

Loxone vs Dedicated KNX Audio

Loxone Audio Server advantage: tight integration with Loxone room automation (HVAC, blinds, lighting all in one software). Disadvantage: depends on the Loxone Miniserver ecosystem. For pure KNX buildings (non-Loxone), the Zennio ZAS-AUDIO8B or JUNG LS 990 audio module are KNX-native alternatives — no Miniserver required.