Same problem here, it has been broken for months, they did apply a fix for it in the last update but still come up with that warning.
YTM is working in the beta. Stable cannot be fixed. We are working on releasing a new stable version but that is still some weeks away.
2 Likes
Thanks. I look forward to the fix
Here’s a fun one - and I’ve even made sure I’ve got the latest version installed. Running Music Assistant on Docker and using the Voice blueprint for it.
It works great using voice command to have it play on any connected speaker.
It works great using voice command to play to a speaker group (though VLC and Google Home will be out of sync of course).
The problem arises after you’ve played to a group of speakers. After that it will ONLY play on that group regardless of what you tell it to do. “Play playlist christmas on office speaker” “Okay, playing Christmas on Office Speaker”. And the entire group starts playing…
So far the only way I’ve found to make it stop doing that is to restart docker (i.e. have you tried turning it off and on again?) While it’s stuck on this, you can use the web interface to manually trigger something to play on a specific speaker or your browser, but anything triggered directly from an HA automation will always go to the speaker group regardless of designated target.
Just updated to the last beta, but the integration seems not compatible yet?
Invalid server version: Schema version is incompatible: 28, the server requires at least 28 - update the Music Assistant client to a more recent version or downgrade the server.
As per the release note, you need HA 2025.12.0
Ah, wrong order. Just started the update to 2025.12.0. 
Works like a charm. Awesome update again.
Will there be a new blog post to match the upcoming Music Assistent 2.7 release party video? https://www.youtube.com/watch?v=-sUA7v1TEzY
3 Likes
It’s shaping up to be an amazing release, so you can take a guess 
2 Likes