Has anyone else had strange behavior with favorites? It appears that anytime I restart Music Assistant it randomly favorites about 80% of Artists, Albums, Tracks, and Radio. I’ve disabled all favorites multiple times but now I’m tired of it.
Also, the select multiple would be more useful with a “select all” feature.
I also have some weird behavior with favorites, but havent noticed that.
What would be very helpfull is to dont select any playlist as favorite by default, instead what is doing now: when i instaled MA all playlists were favorited, and I had to ‘un-favorite’ more than 900 playlists.
This probably depends on what provider they are coming from. Ask on Discord or GitHub discussions for more details jphelp.
God I saved so much automation and Node-RED code thanks to Music Assistant. Thank you folks!
Could the AirPlay reciever code from AirCast and AirSonos addons or other AirPlay client be ported into a reciever for Music Assistent so that it could have a music provider which could present virtual AirPlay targets that would in turn forward the stream to selected player provider?
Will it in the future also be possible to make MA a Google Cast target too as in presenting virtual Google Nest speakers / Chromecast Audio reciever?
Is such a Google Cast reciever as music provider also on the roadmap for Music Assistent?
Not at the moment. You can open a feature request for it
@marcelveldt Do you mean adding a normal Media_player.shuffle_set just before the mass.play_media command?
It works on one if my playlist, but the other one always starts on the same track and I have not figured out why yet 
This is my script on the one that works, it’s exactly the same as the one that always start on the same track. I’m sick of hearing Kings of Leon every time 
alias: "Cast Playlist: Spotify Hip-Hop"
sequence:
- service: media_player.volume_set
metadata: {}
data:
volume_level: 0.35
target:
device_id:
- 7f71010cea099eb324bc5d766152b345
- service: media_player.volume_set
metadata: {}
data:
volume_level: 0.09
target:
device_id:
- c6adc84bbedcbdd51de683f525ba9a8a
- service: media_player.volume_set
metadata: {}
data:
volume_level: 0.2
target:
device_id:
- 3585d7849b97b87d8b59d818a2135a42
- service: media_player.shuffle_set
metadata: {}
data:
shuffle: true
target:
entity_id: media_player.overallt_2
- service: media_player.play_media
target:
entity_id: media_player.overallt_2
data:
media_content_id: library://playlist/36
media_content_type: playlist
metadata:
title: Hip-Hop 92-00 bästa
thumbnail: null
media_class: playlist
children_media_class: track
navigateIds:
- {}
- media_content_type: mass
media_content_id: playlists
- media_content_type: music
media_content_id: library://playlist/36
enabled: true
mode: single
Out of interest why do you use device_id rather than entity_id and why do you add the metadata block?
Look at the MA UI after you send the shuffle set command and confirm that the queue does have shuffle enabled. Then look at the tracks when they are added and see if they are indeed shuffled.
I have Music Assistant running in Synology/Docker-Container streaming to Shairport-Sync running in Portainer on a RPi3B+ and see loads (like 1 per second) of info-messages saying
2024-05-25 13:44:15.628 INFO (MainThread) [music_assistant.providers.airplay] Unknown DACP request for B827EB7B8FB3@RPi3B-01-bureau._raop._tcp.local.: /ctrl-int/1/getproperty?properties=dmcp.volume
Any idea how to get rid of these (as it snows under other more relevant messages)
Unless it is causing a problem you can ignore it.
I just had to deinstall this addon as im running HA in a VM with only 2GB RAM. The systame became unstable due to maxed resources. I might try again after altering my HA environment.
It won’t run with 2GB RAM
Adding the empty metadata block is something the GUI does
I find it odd as the docs don’t mention it being supported at that level? Anyway doesn’t seem to hurt anything…. Media player - Home Assistant
It does that on every service call