sonn docs GitHub

documentation

What sonn is

sonn is a complete multiroom audio solution: a self-hosted server that collects your music — local files, streaming services, radio, line-in — and plays it in sync on the speakers you already own, over almost any protocol they speak.

It runs in one of two shapes, and can be both at once. As a content server it makes everything you listen to available to other apps and devices — DLNA TVs, Subsonic apps, the built-in web player. As a multiroom system it owns fixed zones — up to 24, one device per room — that you name, group and control centrally, from the web player, the Admin UI, or a Loxone app.

How it fits together

sonn has three sides, each configured independently in the Admin UI:

sidewhat it isrequired?
Content Where the music comes from: local library, Spotify, Apple Music, Tidal, Deezer, radio, line-in Yes
Access How other apps and devices reach the server: DLNA/UPnP, Subsonic API, network drive, Loxone Pick at least one way to listen
Zones The devices this server drives itself, one per room Optional

Content plus Access is already a working audio server: point a DLNA TV or a Subsonic app at it and browse your library, Apple Music or Tidal straight from the device — no zones involved, nothing to configure per room.

Zones are for the other model: devices the server owns and controls centrally. Add them when you want to name your rooms, group them to play in sync, and drive them from one place — or when you want to give a device features it has no support for itself (see receivers).

The Loxone integration is zone-driven, so with it on, zones are always active: the Miniserver supplies them and expects to control them. See Loxone.

Where to start

  1. Install — one container, running before the coffee is.
  2. First setup — the admin account and the three steps.
  3. Content — your library, streaming accounts, radio and line-in.
  4. Zones — only if you want rooms; Loxone if a Miniserver supplies them.

Status

sonn core is at 4.0 beta: in active use and actively developed. Releases are tagged from the beta branch, and breaking changes can still land between betas — check the release notes before updating. The project is open source under Apache-2.0, on GitHub.