Music Assistant Addon providers access/development

Hello guys!

I’m new here, that’s my first post! Yay!
As of IT knowledge I’d classify myself as very high.

I’m quite new to Home Assistant (2 months) and as my setup I am using

  • Home Assistant Green (I don’t want to have it on my power machine running to be able to control my home at all times)
  • Current topic is Music Assistant with Sonos S1 provider (multiroom audio project, working well)
  • Ecosystem is Android only

And there I am hitting a wall…

Most important in advance: I have enabled root access to my Green on port 22222. The reason for it:

As of Ecosystem Android I am interested in adding this provider

To be able to test this I need the ominous providers folder. As the Music Assistant is on Home Assistant Green, and I want to keep it there and test the plugin, I am not sure how I could add that provider to my Music Assistant without hacking the system…

With root access, I can see the mounts of the docker container and the only interesting is the /data mount, but, not holding the /app/venv/lib/python3.13/site-packages/music_assistant/providers/ target which I would like to add that plugin to.

Now what I would like to avoid

  • root access (that should actually not be needed)
  • docker cp (ephemeral? too hacky)
  • modify Music Assistant docker container to use additional mount for /app/venv

Is there a way to add/develop providers manually to Music Assistant running in Docker as addon without these hacks?

Hello Us3r,

You might want to ask here…
Music assistant
The people that are watching that thread are all either interested. users of, or authors of Music Assistant.
They are likely your best resource.
Also there is a Discord: Music Assistant

Hello @Us3r

I’m the developer of that Plugin
I opened a pull request but requirements are kinda… let’s say exaggerated
I’m working on it tho
In the meantime, if you’d like to help. I released the standalone version, both in python and go

I’d love to hear your feedback about how this is working for you