Music Assistant 2.0: Your Music, Your Players

I’ve been trying to get Music Assistant running for a few days now with no luck. It crashes my entire HA and I cant figure out exacly why. Could it be that my Raspberry Pi just isn’t strong enough? I want to play Spotify over Airplay. This is the log.

After this it restart my HA and I’ve made it so that MA won’t start on start-up.

2024-10-23 19:19:17.653 INFO (MainThread) [music_assistant] Starting Music Assistant Server (a5d2a8a9c37a47c5ac6333e09674c1f9) version 2.2.9 - HA add-on: True - Safe mode: False
2024-10-23 19:19:17.724 INFO (MainThread) [music_assistant.cache] Initializing cache controller...
2024-10-23 19:19:28.040 INFO (MainThread) [music_assistant.music] Using a sync interval of 180 minutes.
2024-10-23 19:19:44.315 INFO (MainThread) [music_assistant.streams] Detected ffmpeg version 6.1.1 with libsoxr support
2024-10-23 19:19:44.339 INFO (MainThread) [music_assistant.streams] Starting server on  0.0.0.0:8097 - base url: http://192.168.2.106:8097
2024-10-23 19:19:44.474 INFO (MainThread) [music_assistant.webserver] Starting server on  [ip removed]:8095 - base url: http://[ip removed]:8095
2024-10-23 19:20:44.166 INFO (MainThread) [music_assistant] Loaded music provider Music Assistant
2024-10-23 19:20:44.170 INFO (MainThread) [music_assistant] Loaded metadata provider fanart.tv
2024-10-23 19:20:44.172 INFO (MainThread) [music_assistant] Loaded metadata provider The Audio DB
2024-10-23 19:20:44.175 INFO (MainThread) [music_assistant] Loaded metadata provider MusicBrainz
2024-10-23 19:20:50.455 INFO (MainThread) [music_assistant] Loaded player provider Airplay
2024-10-23 19:20:52.766 INFO (MainThread) [music_assistant.players] Player registered: apb0672f029871/televisie
2024-10-23 19:20:52.777 INFO (MainThread) [music_assistant.players] Player registered: apb0672f1fc5f1/eetkamer
2024-10-23 19:20:52.785 INFO (MainThread) [music_assistant.players] Player registered: apb0672f0966a1/kantoor 
2024-10-23 19:21:03.930 INFO (MainThread) [music_assistant.spotify] Successfully logged in to Spotify as Adriaantje
2024-10-23 19:21:03.933 INFO (MainThread) [music_assistant] Loaded music provider Spotify
2024-10-23 19:21:09.226 INFO (MainThread) [music_assistant.music] Sync task for Music Assistant completed
2024-10-23 19:23:53.041 INFO (MainThread) [music_assistant.spotify] Attempt 1/5 failed: Spotify Rate Limiter
2024-10-23 19:23:53.076 INFO (MainThread) [music_assistant.spotify] Retrying in 1 seconds...
2024-10-23 19:23:54.124 INFO (MainThread) [music_assistant.spotify] Attempt 2/5 failed: Spotify Rate Limiter
2024-10-23 19:23:54.124 INFO (MainThread) [music_assistant.spotify] Retrying in 1 seconds...
2024-10-23 19:26:24.275 WARNING (MainThread) [music_assistant.webserver] Disconnected: Received non-Text message.
2024-10-23 19:29:46.292 WARNING (MainThread) [music_assistant.webserver] Disconnected: Received non-Text message.
2024-10-23 19:32:27.083 INFO (MainThread) [music_assistant.music] Sync task for Spotify: Adriaantje completed
2024-10-23 19:32:27.185 INFO (MainThread) [music_assistant.metadata] Starting metadata scanner
2024-10-23 19:58:05.807 WARNING (MainThread) [music_assistant.metadata] Error while creating playlist image: 

What Pi? how much RAM?

It’s a Raspberry Pi 3B+ so it should be 1.4GHz 64-bit quad-core processor

Do you a bunch of other add ons running at the same time?

Version 2.3 has been released!

New Player Provider - Bluesound
New Music Provider - SiriusXM
New feature - Don’t Stop the Music (for those with supported streaming providers)
Major Update - Player Grouping and associated UI has been completely redone

Numerous bug fixes of course

Documentation updates are ongoing

6 Likes

Just wanna leave some positive Feedback. The new Player Grouping works just great (using Snapcast at least) and i love the Dynamic Members Feature which is just so much more versatile! Also the integration in Home Assistant for controlling MA Players is just way better the new way! Works like a Charm for my use-cases!

Thanks for all the hard work :heart:

2 Likes

You can at least put the name of the player in the url when opening. I use this on wall tablets to open now playing on the correct player

1 Like

Hello @tbrasser,

Thanks for the hint!!! It is indeed a very good idea.

I have ESPhome (with no current esp boards), file editor, google drive backup, mosquito broker, samba share and terminal and ssh

@MattTheBrofessor try with the latest version as there was an issue with resources.

For one second it seemed to be working. I could select the Airplay devices and select a song, but it crashed HA again before there was any music

2024-10-23 19:19:17.653 INFO (MainThread) [music_assistant] Starting Music Assistant Server (a5d2a8a9c37a47c5ac6333e09674c1f9) version 2.2.9 - HA add-on: True - Safe mode: False
2024-10-23 19:19:17.724 INFO (MainThread) [music_assistant.cache] Initializing cache controller...
2024-10-23 19:19:28.040 INFO (MainThread) [music_assistant.music] Using a sync interval of 180 minutes.
2024-10-23 19:19:44.315 INFO (MainThread) [music_assistant.streams] Detected ffmpeg version 6.1.1 with libsoxr support
2024-10-23 19:19:44.339 INFO (MainThread) [music_assistant.streams] Starting server on  0.0.0.0:8097 - base url: [ip]:8097
2024-10-23 19:19:44.474 INFO (MainThread) [music_assistant.webserver] Starting server on  172.30.32.1:8095 - base url: [ip]:8095
2024-10-23 19:20:44.166 INFO (MainThread) [music_assistant] Loaded music provider Music Assistant
2024-10-23 19:20:44.170 INFO (MainThread) [music_assistant] Loaded metadata provider fanart.tv
2024-10-23 19:20:44.172 INFO (MainThread) [music_assistant] Loaded metadata provider The Audio DB
2024-10-23 19:20:44.175 INFO (MainThread) [music_assistant] Loaded metadata provider MusicBrainz
2024-10-23 19:20:50.455 INFO (MainThread) [music_assistant] Loaded player provider Airplay
2024-10-23 19:20:52.766 INFO (MainThread) [music_assistant.players] Player registered: apb0672f029871/televisie
2024-10-23 19:20:52.777 INFO (MainThread) [music_assistant.players] Player registered: apb0672f1fc5f1/eetkamer
2024-10-23 19:20:52.785 INFO (MainThread) [music_assistant.players] Player registered: apb0672f0966a1/kantoor 
2024-10-23 19:21:03.930 INFO (MainThread) [music_assistant.spotify] Successfully logged in to Spotify as Adriaantje
2024-10-23 19:21:03.933 INFO (MainThread) [music_assistant] Loaded music provider Spotify
2024-10-23 19:21:09.226 INFO (MainThread) [music_assistant.music] Sync task for Music Assistant completed
2024-10-23 19:23:53.041 INFO (MainThread) [music_assistant.spotify] Attempt 1/5 failed: Spotify Rate Limiter
2024-10-23 19:23:53.076 INFO (MainThread) [music_assistant.spotify] Retrying in 1 seconds...
2024-10-23 19:23:54.124 INFO (MainThread) [music_assistant.spotify] Attempt 2/5 failed: Spotify Rate Limiter
2024-10-23 19:23:54.124 INFO (MainThread) [music_assistant.spotify] Retrying in 1 seconds...
2024-10-23 19:26:24.275 WARNING (MainThread) [music_assistant.webserver] Disconnected: Received non-Text message.
2024-10-23 19:29:46.292 WARNING (MainThread) [music_assistant.webserver] Disconnected: Received non-Text message.
2024-10-23 19:32:27.083 INFO (MainThread) [music_assistant.music] Sync task for Spotify: Adriaantje completed
2024-10-23 19:32:27.185 INFO (MainThread) [music_assistant.metadata] Starting metadata scanner

@MattTheBrofessor the fix is in the beta only at the moment. It will be pushed to stable soon. Also please check the MA Spotify docs to fix your rate limiter problem

Hello,
I would like to have your advice, I am running MA in docker within a stack with other containers.
When not streaming music the RAM with all dockers running is about 10% but when streaming it goes up to 70-80% and sometimes it runs out of RAM, result the stack is restarting.
The available RAM of the machine is 4 GB, so while idle the RAM used is about 400 MB, but when streaming is practically fully used.

As far I could find we need 2 GB RAM for MA correct?
Does the use depends on number of streaming as well?
Does the RAM usage depends on players and provider as well?
Should I limit the MA Docker meamory to 2?
Can anyone share his experience?
Any suggestion is appreciated.

BTW MA is great!

It is a MIN of 2GB. Having said that what version are you running? I thought I recalled someone else suggesting excessive memory use but I can’t find it now but I’ll keep looking. If you can give MA some more of the RAM that would be a good test to see if you can get it to stabilise

Edit: I have found the report on Discord. So this is being looked into. If you can advise what music and player provider you have installed and if you have noticed this memory increase happening with any particular combination

Hello,

HA 2024.10.4
MA 2024.10.1

The issue seems to be mainly when I stream to volumio that is a player provided by HomeAssistant.
It does not seem to be an issue when streaming toward an ESP32 with Squeezebox.
I have to confirm the second case.

The music provider is a jellyfin server.

The stack stops with another container in exit code 137 so probably out of memory, always esphome going out of memory.
I believe this confirms it is RAM related issue.

I will do some further testing and post the findings.
Unfortunately I don’t have more RAM, time to upgrade maybe :slightly_smiling_face:
Thanks.

Hello @OzGav,

will do more tests, but I’m 99 % sure the problem was not caused by music assistant but from the some strange stuff that happened after the OS host update.
I had to uninstall and tidy up all folder related to docker and rebuild the stack with a docker fresh install.

Now stack is stable, not maxing out memory and can stream from MA to two speaker with no issues.
RAM and CPU usage are present but within expected performance.

Thanks for your answer!

1 Like

Does it work yet?

I’m getting an error after updating the add-on to 2.3.2. and reinstalling the old add-on version backup.

2024-11-03 11:51:06.551 ERROR (MainThread) [music_assistant.webserver] Error handling message: config/providers/reload: Failed to install package hass-client==1.2.0
error: Failed to download `hass-client==1.2.0`
  Caused by: Request failed after 3 retries
  Caused by: error sending request for url (https://files.pythonhosted.org/packages/71/19/e60ea7c8cc22a85f484106087634623dab686adb521e2fb756de57c12048/hass_client-1.2.0-py3-none-any.whl.metadata)
  Caused by: operation timed out

It’s probably a server error from “files.pythonhosted.org” that’s just temporary, but just thought I would ask.

Edit: after many hours of trouble shooting. it was due to a dns error that was fixed simply by assigning a different domain name server.

Has there been any progress on the Alexa echo that you bought? I have 7 speakers, all amazon echo. And I have no other smart speakers. So I’d very much like a solution on this.

Thanks,
Mike

Sorry no update as yet for Alexa players.