sonn docs GitHub

using it

Content

Sources are configured under Content, and every source is available to every consumer of the server — the web player, Loxone, DLNA devices and Subsonic apps alike. Configure it once, reach it from everywhere.

Local library

  • Local folders and mounted network shares (SMB/CIFS)
  • Tag-based index (albums, artists, tracks, folders) in SQLite, with cover art
  • Artist pictures fetched automatically from MusicBrainz → Wikidata → Wikimedia Commons — no API key
  • Incremental indexing: a dropped or copied file is picked up on its own, without a full rescan
  • Browse, search and delete tracks from the Admin UI
  • Add music by drag-and-drop in the browser, or by mounting the folder as a network drive

Streaming services

Spotify, Apple Music, Tidal, Deezer, YouTube Music, YouTube, SoundCloud — and Music Assistant as a source, exposing its own providers.

Each configured account becomes its own browsable service, so several accounts of the same service can coexist. The Loxone integration presents non-Spotify services to the Miniserver as virtual Spotify accounts, since that is the only vocabulary the Loxone clients have for them; everywhere else they appear under their own name.

Radio

  • TuneIn — adding a TuneIn username exposes your personal presets, while search scans the full directory
  • Radio Paradise — curated, listener-supported streams (toggleable)
  • Custom streams you manage yourself, with your own cover art

Line-in

Play a turntable, CD player or any other analog or digital source through your zones, with optional Shazam track recognition. Play, pause and skip are forwarded to the device that owns the source — when that device can be driven over the network. B&O Masterlink can: a Beosound 9000 changes discs on command.

Line-in audio reaches the server one of two ways:

  • The line-in bridge — a small Linux helper that captures the audio and sends it to the server. It runs on the machine the source is plugged into — typically a Raspberry Pi next to the equipment — and is distributed as a prebuilt binary for x86-64 and ARM. It finds the server and registers itself, so there is nothing to configure by hand; once registered, its inputs appear under Content.
  • Sendspin's source role — a Sendspin endpoint can carry audio into the server as well as out of it, on a dedicated endpoint or riding along with a player.

Alert engine

  • Text-to-speech, using the built-in engine or LoxBerry TTS over MQTT
  • Built-in alert sounds
  • Native Loxone alerts when the integration is on