Music Assistant 2.0: Your Music, Your Players

It is because the results are paged. Try scrolling to the bottom and then use CTRL-A

@SteveG82 that is correct. You have to view the MA media player

Thanks Oz. That takes a bit of time to scroll down with a large library, but I do like that you have the ā€œ500 Random tracks (from library)ā€ option that I just discovered and actually seems to work very well. I am moving over from the Sonos (v1) app to your Music Assistant so it is going to take some time to adjust. I see that you add-on does see my Plex play lists but not Sonos playlist, which is probably not possible to see or import due to proprietary rules of Sonos?

Sonos is not a music provider so you wonā€™t see anything that is solely in that app

Thats clear to me was just wondering if it would be possible to get a Album Artists option on the MA media player like the other additional options Artists,Albums,Tracks,Playlists,Radio Stations (compared to the HA media player).

As I said the HA media view is limited. That is controlled by HA not MA

I also found all tracks under playlist! Nice!

Hello, I installed Music Assistant and Home Assistant in Docker container using this Docker compose file:

services:
  homeassistant:
    container_name: homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
      - /home/user/HASS:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    restart: unless-stopped
    privileged: true
    network_mode: host
  nginxproxymanager:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443' 
    volumes:
      - ./nginx/data:/data
      - ./nginx/letsencrypt:/etc/letsencrypt
  music-assistant-server:
    image: ghcr.io/music-assistant/server:latest # <<< Desired release version here (or use beta to get the latest beta version)
    container_name: music-assistant-server
    restart: unless-stopped
    # Network mode must be set to host for MA to work correctly
    network_mode: host
    volumes:
      - ${USERDIR:-$HOME}/Docker/music-assistant-server/data:/data/
    # privileged caps (and security-opt) needed to mount smb folders within the container
    cap_add:
      - SYS_ADMIN
      - DAC_READ_SEARCH
    security_opt:
      - apparmor:unconfined
    environment:
      # Provide logging level as environment variable.
      # default=info, possible=(critical, error, warning, info, debug)
      - LOG_LEVEL=info

After installing I restarted home assitantā€™s container, and when looking in my integrations, I canā€™t seem to find my desired one:
image

does anyone know what I have missed?
thanks

Have you heard from @marcelveldt if the Nabu Casa and Home Assistant core/frontend team have any any informal or formal roadmap plans regarding with media views improvements or updates on if anyone of them plan to focus on the music playback experience on the Home Assistant core/frontend side?

I hope that making music playback a better experience in Home Assistant core/frontend side would be an important topic to follow-up now that the Home Assistant Voice Preview Edition has been released with a 3.5-inch audio-output jack to connect external speakers for music playback (and as such given many of us aspirations to someday use it for multi-room audio :wink: ).

The official Roadmap 2024 Year-end Update did not mention anything related to media or music playback:

@Amit1234 Music Assistant integration requires the Music Assistant add-on (i.e. the Music Assistant Server addon), and to run add-ons for Home Assistant you really need to be running Home Assistant Operating-System) (or alternatively at least ā€œSupervisedā€, which Home Assistant OS / HA OS also is), instead of just running only the Home Assistant Container or Home Assistant Core installations (which are referred to as ā€œadvanced installations methodsā€ that are only meant for experts and generally not recommended for most users). See the summarized explainations about the different limitations between installations here ā†’ Installation - Home Assistant

1 Like

I am not aware of any additions to the HA roadmap.

Why would my MA have unrelated artists on local tracks that are properly tagged?

Screenshot:

Screenshot 2025-01-21 at 18-26-32 Music Assistant

This is clearly wrong. Die Antwoord is neither on the tag nor a participant in the creation of this track.

Like that, I have thousands of tracks improperly artisted.

How can I fix?

EDIT: I am deleting the local filesystem provider and re-adding it to see if that fixes the issue, as my local collection was scanned quite a while ago with a very old version of MA. Please stand byā€¦

There is an issue with incorrect mapping when there are multiple artists on a track

Oh man, clearing and recreating the local filesystem provider basically slowed MASS to a crawl.

I have upgraded from beta 12 to beta 18 and it did something where the logs say ā€œclearing databaseā€, and now itā€™s back to adding tracks to my collection.

Letā€™s see if the Oggi problem manifests itself oggi.

EDIT: MASS is really slow to scan a local file system. Not sure why it canā€™t go full tilt. strace shows a fuck ton of accesses to the local SQLite database, but less than a file per second being scanned.

Running MA 2.3.6, HAOS 2025.1.2 in Proxmox. Getting the following error in MA log every 60-90 seconds.

Any ideas?

Also, I got no repeat. Related?

2025-01-22 12:18:02.570 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 478, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aiohttp/web_app.py", line 567, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aioslimproto/cli.py", line 300, in _handle_jsonrpc_client
    cmd_result = await self._handle_command(command_msg["params"])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aioslimproto/cli.py", line 653, in _handle_command
    cmd_result = await cmd_result
                 ^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aioslimproto/cli.py", line 808, in _handle_serverstatus
    if len(players) > limit:
       ^^^^^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'int' and 'str'
2025-01-22 12:19:22.735 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 478, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aiohttp/web_app.py", line 567, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aioslimproto/cli.py", line 300, in _handle_jsonrpc_client
    cmd_result = await self._handle_command(command_msg["params"])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aioslimproto/cli.py", line 653, in _handle_command
    cmd_result = await cmd_result
                 ^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.12/site-packages/aioslimproto/cli.py", line 808, in _handle_serverstatus
    if len(players) > limit:
       ^^^^^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'int' and 'str'

Your statement confuses me a little. Arenā€™t add-ons really just containers anyway? I run Home Assistant in a container and I was able to add the Music Assistant integration, but it fails to connect to my Music Assistant container. Iā€™ve used similar setups in the past, for example, Jellyfin, and didnā€™t have any issues. I have many other Docker containers that play well with HA.
I actually posted last week, after getting frustrated and giving up, but I had posted in the ā€œConfigurationā€ thread because I didnā€™t realize there was a dedicated thread for Music Assistant. Hereā€™s the post:
Hi,
Iā€™m having a hell of a time trying to get Music Assistant Server set up and I have no idea where I could be going wrong.

  • I have a Pi4 running Home Assistant (2024.12.0) in Docker on my LAN but it can only be controlled through DuckDNS. I can SSH the system for maintenance over the LAN. Aside from HA sometimes locking me out of my own system if I turn off my VPN on my desktop PC, itā€™s generally running pretty smoothly.*

  • I have a mini PC running Music Assistant Server in Docker on the same LAN (in host network mode, of course). The logs state: ā€œLoaded plugin provider Home Assistantā€.*

  • I am able to load both the HA webserver page and the Music Assistant Server webpage from a third PC, however I run into problems trying to link the two during configuration ā€“ While trying to set up Home Assistant as a plugin provider using the Music Assistant page, I am brought to a new tab to log into Home Assistant. After entering my credentials, it asks for a confirmation number from my two-factor authentication app. I have tried countless times and every single time Iā€™m either told that my code was no good, or that there was a ā€œtimeout while waiting for authentication callbackā€. The same message is mirrored in the MA Docker log.*

  • ā€œError handling message: config/providers/get_entries: Timeout while waiting for authentication callback.ā€*

-The Home Assistant Music Assistant integration claims that it is successfully configured after adding it, but then fails setup and continually re-tries to reach MA (probably because of the lack of authentication, Iā€™m guessing).

Iā€™m pretty sure Iā€™ve followed the setup directions to the T so I thought Iā€™d ask here before throwing in the towel.
Thanks.

Let me know if thereā€™s any detail Iā€™ve left out that might be helpful in determining the cause, aside from not running HA OS.

From the docs

Probably the most common issue is people trying to run MA with complicated network setups. Running behind VPNs, across subnets or VLANs, behind firewalls, local SSL, using reverse proxies or inside containers is not supported (it might work but we canā€™t troubleshoot for you as MA is run by a small team who donā€™t have the resources to help with non-MA issues).

To be clear a simple docker container on an otherwise simple network is supported. Otherwise not.

Iā€™m not sure that my network is ā€œcomplicatedā€. Is it considered complicated if I have Home Assistant using a DuckDNS domain? My Android companion app doesnā€™t seem to mind, both HA and MA are on the same LAN with reserved addresses. I have no subnets or VLANs, neither machine is running a firewall. The only machine I have using a VPN is my main desktop PC, and I donā€™t have difficulty reaching either of the other machines over my network.

Have you got it set up like the instructions here? Installation - Music Assistant

And those instructions make it clear that docker is supported.

Yes. That is the Docker Compose file that I used.

I have a old iPad mini 2. MA shows a blank screen as shown in attached. Working fine on my PC and all my Android devices. I think that maybe iso 12.5.7 is just too old? :thinking: :man_shrugging: