Music Assistant 2.0: Your Music, Your Players

Today, exactly five years ago, I, Marcel, started working on Music Assistant . What began as a quick script, to sync my playlists so I could switch between streaming providers, grew into a beast on its own.

Music Assistant is what I’d like to call a “music library manager” – it gives you full control of playing YOUR music on your players. Just like Home Assistant centralizes all your devices and services to work together, Music Assistant does the same with your music sources and smart audio-playing devices.

To just play with Music Assistant without reading what it is (yes, we know you!):

Rainbow Connection

What is Music Assistant?

Your music, your players. Click and play. It should be as simple as that.

From source to Music Assistant to speaker

Connect and play anywhere

Music Assistant allows you to quickly connect some of the most popular streaming providers like Spotify and Tidal, with your local media files. Importing your liked tracks, artists, albums, and playlists, all displayed with the correct artwork.

It supports the most ubiquitous streaming protocols and devices like Airplay, Cast and DLNA, letting you play media on almost any device - if an old speaker doesn’t support new services, Music Assistant can bring it back to life.

Read more…

Unified music library with advanced features

Your local and cloud libraries will be seamlessly merged together. If you have the same track on multiple place, it will appear once while helping you find the highest-quality version. You can even have multiple accounts from the same provider, allowing everyone in the house to have their playlists in one place.

It can group supported players for synchronized playback. It also supports advanced playback features such as crossfade and volume normalization - regardless of whether the device supports them.

Read more…

Built for Home Assistant

Connecting this with the Home Assistant integration - automation and voice control supercharges the whole experience.

Read more…

Start me up

How to install Music Assistant

After many years of development and testing with the amazing community, we can finally say this is ready for daily use.

Even though Music Assistant is an HA Add-on, it can be installed from start to finish via HACS . You simply install the integration, which will automatically install and manage the add-on for you. The integration allows you to control your devices with automations and voice control.

Music Assistant is distributed as a Home Assistant add-on – our way to easily extend your Home Assistant installation with third party applications. To install it as a Docker container, follow the MA installation instructions .

Fight the power

Why Music Assistant?

I started Music Assistant out of frustration about the mainstream available options;

  • You buy into an all-in-one ecosystem (such as Sonos), and then it’s up to that ecosystem to decide which music sources to support now and in the future.

  • You choose a music streaming provider, and then somehow that streaming provider decides where/how you play their music.

  • You want to switch between streaming providers and keep your carefully curated playlists, regardless of which provider you want to play it with.

  • You still have your CD music collection that you’ve painstakingly ripped into high-quality files on local storage, and you want to play them, maybe even mix them with choices from streaming providers.

  • Or maybe you fall into the category of users who don’t want any subscriptions and have a carefully curated local media collection you want to play on these shiny new playback devices.

When we pay for our music or devices, we shouldn’t be limited by arbitrary limitations. We are slowly moving into a world of greater walled gardens and more vendor lock-in, and it’s time we took back control. 

Tidal on a Google Home

I spent a long time and a good bit of my money looking at existing solutions to fill these gaps. They were either expensive, closed, or lacked the home approval factor - or a combination of all of these.

Freedom of choice

Connecting any sources and play anywhere

Music Assistant connects to your favorite streaming providers and local music files, letting you play them on almost any connected playback equipment from the past 20 years. It’s basically a translator of music protocol A towards speaker/player protocol B.

For instance, I have a traditional amplifier + speakers setup in my living room that allows for high-quality music playback, where I can sit down and hear every detail. I also have Sonos speakers in a very noisy kitchen and some DIY speakers that can only accept Airplay. I can play my music to all of these speakers without being tied down to any single ecosystem.

Some people might say that the best way to prevent all that frustration is by buying into an ecosystem like Sonos which takes care of this for you entirely. While I am a big fan of Sonos (and I will recommend them to friends and family for ease of use), I am not a big fan of the vendor lock-in that comes with it. If Sonos or a streaming service decide to part ways, I don’t have to be locked out of my music. Also, they don’t make speakers at every price point, meaning you don’t get the advantages of the new higher-fidelity or more affordable hardware out there.

Come together

Unifying all your music in one library

In the same interface as I can stream my kids’ music to their speakers, I can stream my Hi-Res favorites to my high-fidelity setup. It is an all-in-one interface. Gone are the days of needing five different apps to get playback going in multiple parts of the house or switching who is connected just to access their playlists.

When you search in Music Assistant, it searches all your libraries. Every streaming service, or the local files you add, are available to choose for playback.

We are family

Built for Home Assistant

Music Assistant has always been closely linked to Home Assistant (more on that below). I now even work for Nabu Casa , partly because of my work on Music Assistant (but now I’m the Matter guy). 

Because of this strong link, Home Assistant seamlessly links with Music Assistant, unlocking several advanced features. MA players are exposed to HA and can be controlled via your dashboards, automations, and scripts. This allows HA users to control their music players and access MA’s powerful music search function. Players can provide TTS (Text-to-Speech) announcements and can be controlled by Home Assistant connected voice assistants.

Liner notes

So, I started working on Music Assistant exactly five years ago , at first for my own personal use. It started as a learning exercise - thanks to it, I learned asyncio Python programming as well as the Vue frontend framework. I had the project on GitHub just to host the code, but it was not really meant to be used by others.

At some point, it became clear to me that there was a real demand, and I posted some info on how to install it, which gained a little attention. In June 2022, we released the 1.0 version of Music Assistant, and it was still in rough shape but already suitable for many users. We even organized a Livestream, “Let’s get Loud ” hosted by Home Assistant, to promote audio support for ESPHome and the super cool things you can build when you combine these three open-source projects.

Version 1.0 was not everything we hoped it would be. It had some structural bugs, specifically running as a custom component in Home Assistant. HA was created to give you the best experience for automating your home; it was never optimized for real-time audio streaming. On top of that, at some point, the dependencies of both projects got so conflicted that Music Assistant stopped working completely in the March 2023 release of HA.

Six months after its initial version 1.0 launch, the project was beginning to look like it was going to die, so I decided to start over and go back to the drawing board. The engine of MA needed to be its own isolated component, responsible for giving you the best possible experience of streaming music (where audio quality and latency are very important), and the HA-side should be responsible for automating your house and music.

So, the Music Assistant Server was born. It is a standalone application that you can run in docker (or Home Assistant add-on), all connected to HA via a HACS integration. The project was split up into multiple self-contained parts. 

Music Assistant Server has its own web interface, a modern interface written in Vue. Thanks to HA’s add-on system, this web interface can be securely accessed from HA. The web interface is a Progressive Web App (PWA), so you can also visit it directly and install it on your device . We also have an (experimental) desktop app .

Over the past year, we have been iterating on this with an impressive number of beta testers. So, while technically this is a 2.0 release, to me personally this is the first real release, as this is finally something that feels good and has the right foundation. What is also super is that we attracted contributors to the project, folks helping create and maintain music integrations while providing support or translations. Even more exciting there are some really big features and streaming services on the horizon. My sincere thanks to everyone who has helped bring this release home.

This is a companion discussion topic for the original entry at

Awesome release!!! :muscle:
I didn’t see it mentioned so I figured I’ll ask
Are bluetooth speakers supported?


Not directly (as bluetooth is not a very great way for permanent streaming, more for temporary/mobile) but if you really want, there are lots of folks running squeezelite as add-on or esp32 board connected to Music Assistant (so squeezelite acts as a translator between bluetooth and the slimproto streaming protocol)



Nice, will try! :slight_smile:

Excellent! Great work! Was there a big announcement/stream on this that I somehow missed?

Why does the docker implementation require the “–privileged” option? That’s a pretty heavy requirement.


Whoa! I was not expecting this in the slightest, but if I’m understanding it correctly, it means that the only thing standing between me and streaming music from my Navidrome server to various speakers in my house is now… having those speakers?

I can’t describe how cool it is to realize a smart home goal of mine is suddenly right within reach.

1 Like

Also, kudos for having the song titles in the images match the section headings. Real nice touch. :slight_smile:


Because we require those elevated rights.

1 Like

This is the announcement :wink:

So, stop calling it BETA now! It does deserve better! :stuck_out_tongue:

1 Like

A use case example would be great. For example, How would I play an audible book through my Sonos system without using the Sonos app?

1 Like

Uh, I was hoping for an actual reason. What does music assistant do that requires these elevated privileges? No other containers that I run require that privilege, and I think it’s worth knowing why it’s necessary.


Well, for example because we need to increase the pipe size on linux and mount SMB/NFS filesystems (optional). If somebody can figure out how to do that in a more fine grained way, please PR the fix.

For HA supervisor we have setup app armor to specify the rights, the standalone docker container gets less dev attention but feel free to propose changes. Its open source.


This is awesome. Is there a way to use Google Home or similar voice devices to play music from your local library? Asking to play a specific song or playlist is one of the few things we actually use our voice assistant for and it sucks to be locked in to one of their pre-approved monthly music services.

1 Like

There are ways to do it with Google/Siri/Alexa but we are more focused on getting it all to work with your own local voice assistant pipeline. It still a bit experimental but with a bit of patience you can het it to work. There are some examples in the documentation and some folks in the music assistant discord are pretty far with it.

1 Like

You guys. Just stop posting good stuff. There goes the weekend. Sigh


Super awesome, easy to get started with. I’d love for player targets to have different icons or be differentiated visually in some way. Mostly because some speakers like Sonos support multiple options (airplay and sonos) therefor show up several times under the same name.

Great job!

Kick ass. Thanks for the hard work, mate. Do you have a link to buy you a coffee?