I assume you are using the local file system provider. Review the docs for image support. See the link above
Edit to add this is MA server version 2.3.5.
Edit 2: This seems to happen only with the Chromecast Audio and not the Google Nest Mini. Iām going to restart the CA and see if this still happens.
Edit 3: After a restart, same thing. This time I got 4 warning-like sounds from the CA and then one song played with nothing added to the queue. Next thing Iāll try is removing the player from MA and re-adding it.
Iāve been using MA successfully for about 2 weeks. I had about a dozen working Filesystem playlists. Today when I start a playlist on our Chromecast Audio, the Chromecast plays two piano-sounding tones weāve never heard before, then plays one song from the playlist and stops. The queue is empty. Selecting a playlist and then Add to Queue adds nothing to the queue.
I turned on debug logging and captured the log when I restarted the add-on and then tried to play a playlist. Hereās the relevant snippet (with background metadata searches removed:
2025-01-06 10:40:41.044 DEBUG (MainThread) [music_assistant.player_queues] Fetching tracks to play for playlist Jumping Jack
2025-01-06 10:40:41.064 DEBUG (MainThread) [music_assistant.audio] Getting streamdetails for filesystem_smb--R6rMpJEq://track/Beastie Boys/Solid Gold Hits/Beastie Boys - Sabotage.mp3
2025-01-06 10:40:41.118 DEBUG (MainThread) [music_assistant.audio] retrieved streamdetails for filesystem_smb--R6rMpJEq://track/Beastie Boys/Solid Gold Hits/Beastie Boys - Sabotage.mp3 in 54 milliseconds
2025-01-06 10:40:41.221 DEBUG (MainThread) [music_assistant.players] Handling command play_media for player Basement speaker
2025-01-06 10:40:41.221 INFO (ThreadPoolExecutor-0_2) [pychromecast] Quitting current app
2025-01-06 10:40:41.222 INFO (ThreadPoolExecutor-0_2) [pychromecast.controllers] Receiver:Stopping current app 'CC1AD845'
2025-01-06 10:40:41.229 DEBUG (zeroconf-ServiceBrowser-_googlecast._tcp-314) [music_assistant.chromecast] Chromecast removed: o - h
2025-01-06 10:40:41.241 DEBUG (ThreadPoolExecutor-0_2) [music_assistant.chromecast] Launching App C35B0678.
2025-01-06 10:40:41.241 INFO (ThreadPoolExecutor-0_2) [pychromecast.controllers] Receiver:Launching app C35B0678
2025-01-06 10:40:41.624 INFO (Thread-519) [pychromecast.controllers] Receiver:Launching app C35B0678 failed, retrying once
2025-01-06 10:40:41.625 INFO (Thread-519) [pychromecast.controllers] Receiver:Launching app C35B0678
2025-01-06 10:40:42.028 INFO (ThreadPoolExecutor-0_1) [pychromecast.controllers] Receiver:Launching app CC1AD845
2025-01-06 10:40:43.534 DEBUG (zeroconf-ServiceBrowser-_googlecast._tcp-314) [music_assistant.chromecast] Discovered new or updated chromecast CastInfo(services={MDNSServiceInfo(name='Chromecast-Audio-610020ab0b7eecc886dfe1b6b5d50ebe._googlecast._tcp.local.')}, uuid=UUID('610020ab-0b7e-ecc8-86df-e1b6b5d50ebe'), model_name='Chromecast Audio', friendly_name='Basement speaker', host='192.168.99.186', port=8009, cast_type='audio', manufacturer='Google Inc.')
2025-01-06 10:40:43.729 DEBUG (MainThread) [music_assistant.streams] Start serving audio stream for QueueItem Beastie Boys - Sabotage (filesystem_smb--R6rMpJEq://track/Beastie Boys/Solid Gold Hits/Beastie Boys - Sabotage.mp3) to Basement speaker
2025-01-06 10:40:43.738 DEBUG (MainThread) [music_assistant.audio.media_stream] start media stream for: filesystem_smb--R6rMpJEq://track/Beastie Boys/Solid Gold Hits/Beastie Boys - Sabotage.mp3
After that, the queue was empty and the music stopped after one song. I tried this with multiple fliesystem playlists and the 500 Random Tracks playlist and got the same results.
This looks similar to Playback stops after playing one song (Chromecast) Ā· Issue #2887 Ā· music-assistant/support Ā· GitHub. Is it possible this bug has resurfaced? If so, should I re-open that bug or start a new one?
As this has happened without an update to MA I wouldnāt raise an issue at this point. You can ask on discord or a Q&A on GitHub. If you use GH we can transfer it to an issue if needed. But do more fault finding and thinking about what might have changed on your network. Edit: to clarify my last point it looks like the player is getting lost
How do I add the players in music assistant? I do not see any menu point allowing this
In the settings. If you read the docs it is all in there.
This comes up with a 404 page not found error. The link is broken.
Thanks for the reply. As it turns out, restarting HA (again) made the Chromecast Audio start working (again) with MA. Who knows what was going wrong, but itās back to where it was now.
Link Fixed
Itās late at night so I havenāt done a great deal of troubleshooting beyond restarting HA and updating MAā¦ but Iām experiencing the same issue.
Local filesystem playlist files play one song (tested the same playlist from different songs) then stop playing with a return code of 0.
After a few hours of working fine last night, I woke up to the same problem. Playing anything to the Chromecast audio results in 2-4 āwarning chimesā (Iāve never heard these before so not sure how to describe them), then the normal chime and playback of 1 song starts. At the end of one song, MA shows the source as āExternal source: default media receiverā with nothing in the queue.
Given the multiple pieces of equipment involved, Iāve narrowed it down to either the Chromecast Audio or Music Assistant or Home Assistant or my RPi5 or the Unifi 24-port switch or the USG-4 or the cable modem or Jupiterās ascendance into Orion, etc.
I feel like the strange warning tones at the beginning of playback might offer a clue as to whatās going wrong, but I canāt seem to find information about that online. Nothing showing in the limited info I can see about the CCA in Google Home.
EDIT: I just discovered another data point: when I send a playlist to either the CCA or my Google Nest Mini, if I immediately hit the queue button I can see the whole playlist in the queue. Then a few seconds later the queue clears to zero songs. Playlists to the Sonos donāt experience this issue. To me this seems like the issue is more likely software. Iām going to update HA Core and see if that magically helps.
As reported on github, this was due to MAās server(s) being down. After restarting MA, itās working fine again.