AmpliPi

Music Assistant has support for the AmpliPi multi-zone audio controller from MicroNova. Each enabled zone of the controller is exposed as an individual Music Assistant player, with native AmpliPi zone grouping and source management. This provider is contributed and maintained by Nathaniel McAuliffe

NOTE

This provider is currently considered experimental.

Features

• Each enabled zone of the AmpliPi controller is exposed as a separate Music Assistant player
• Multiple AmpliPi controllers can be added (the provider supports multiple instances)
• Zones on the same controller can be grouped and will play in sync, using AmpliPi’s native zone grouping
• Power, volume and mute control per zone
• The AmpliPi controller’s own sources can be selected and routed to a zone (and any grouped zones), including its native streams (Spotify Connect, AirPlay, Pandora, DLNA, Internet Radio, Plexamp, Bluetooth, LMS) and its physical inputs (the RCA line inputs and the front-panel Aux input)

Configuration

1. In Music Assistant, go to Settings → Player Providers, click Add a player provider and select AmpliPi.
2. Confirm the Host setting. Controllers on your local network are found automatically and the field is prefilled with the first one that is not set up yet; if yours was not found, enter its hostname or IP address. See Settings below for the details.

Settings

In addition to the Player Provider Settings when setting up this provider the following settings are available:

• Host. The hostname or IP address of the AmpliPi controller (e.g. amplipi.local or 192.168.1.50). A full URL may also be provided. This is asked when you add the provider and is required. Controllers on the local network are discovered over mDNS and the field is prefilled with the first one not yet set up in Music Assistant, so normally you only need to confirm it. Enter the address by hand when the controller is on another subnet or reachable only through a custom DNS name

Each controller can be set up only once: adding a controller that is already configured is refused. To change its address, reconfigure the existing provider instance instead.

Each zone on the controller becomes its own player. AmpliPi zones use the standard Individual Player Settings, including the settings shared by most protocols.

AmpliPi zones always play the queue as one continuous stream, so there is no flow mode setting to change.

Known Issues / Notes

• An AmpliPi controller has 4 audio sources shared across all of its zones (which can number 6 or more). This means a maximum of 4 independent streams (or groups) can play at the same time. If all sources are in use, additional playback will fail with an “All AmpliPi sources are currently in use” error
• AmpliPi has no native pause for streamed audio, so pause is emulated by stopping the stream. On resume, Music Assistant continues from the saved position
• AmpliPi does not report playback position and plays a single stream URL, so these players always use queue flow mode
• Selecting one of the controller’s own sources (a native stream or a physical RCA/Aux input) is routing only — the wired input or the owning app drives the audio, so Music Assistant does not provide transport controls for those sources
• Announcement / text-to-speech playback to AmpliPi zones is not yet supported