Polkassist turns off every time media is played

[ThreepE0]

What version of Music Assistant has the issue?

2.1.0

What version of the Home Assistant Integration have you got installed?

No response

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

• [X] Yes

The problem

MA Server version 2.1.0, Integration version 2024.6.2

When I try and play music on a Polkassist speaker via google cast, the HA entity turns off. If I enable auto-resume and power up the underlying speaker in HA, the music starts playing. If I start with the underlying speaker off and press play in MA, then I get an error that pops up at the bottom "failed to execute play."

This does not happen with the google home mini speaker.

How to reproduce

try and play media on a polk assist speaker

Music Providers

Spotify

Player Providers

Polkassist

Full log output

2024-07-25 10:08:57.777 INFO (MainThread) [music_assistant] Loaded plugin provider Home Assistant 2024-07-25 10:09:17.544 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Resume queue requested but queue Studio speaker is empty 2024-07-25 10:09:32.355 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Resume queue requested but queue Studio speaker is empty 2024-07-25 10:09:33.367 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Resume queue requested but queue Studio speaker is empty 2024-07-25 10:09:41.406 INFO (MainThread) [music_assistant.streams] Start Queue Flow stream for Queue Studio speaker - crossfade: True 2024-07-25 10:13:25.881 INFO (MainThread) [music_assistant.music] Sync task for Music Assistant completed 2024-07-25 10:13:27.999 WARNING (ThreadPoolExecutor-0_19) [pychromecast.controllers] PLAY command requested but no session is active. 2024-07-25 10:13:28.000 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Failed to execute play. 2024-07-25 10:14:14.640 INFO (MainThread) [music_assistant.music] Sync task for Spotify completed 2024-07-25 10:16:29.095 INFO (MainThread) [music_assistant.providers.spotify] Successfully logged in to Spotify as oceanscrashing 2024-07-25 10:16:33.120 WARNING (ThreadPoolExecutor-0_8) [pychromecast.controllers] PLAY command requested but no session is active. 2024-07-25 10:16:33.121 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Failed to execute play. 2024-07-25 10:17:15.237 WARNING (ThreadPoolExecutor-0_8) [pychromecast.controllers] PLAY command requested but no session is active. 2024-07-25 10:17:15.238 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Failed to execute play. 2024-07-25 10:17:24.693 WARNING (ThreadPoolExecutor-0_25) [pychromecast.controllers] PLAY command requested but no session is active. 2024-07-25 10:17:24.694 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Failed to execute play. 2024-07-25 10:17:48.346 WARNING (ThreadPoolExecutor-0_1) [pychromecast.controllers] PLAY command requested but no session is active. 2024-07-25 10:17:48.347 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Failed to execute play. 2024-07-25 10:17:49.168 WARNING (ThreadPoolExecutor-0_30) [pychromecast.controllers] PLAY command requested but no session is active. 2024-07-25 10:17:49.169 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play: Failed to execute play.

Additional information

No response

What version of Home Assistant Core are your running

2024.6.4

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Linux

[OzGav]

Per the instructions please ATTACH not paste the FULL log

[OzGav]

Please attach the full log or we will have to close this due to no followup

[ThreepE0]

There are no other relevant log entries. I included everything for the time period that I was testing. Im not comfortable sharing other data in the log unnecessarily.

[OzGav]

Support will be limited then if we can't see the whole start up sequence. I do note you are running an out of date version of the Integration

[ThreepE0]

Support will be limited then if we can't see the whole start up sequence. I do note you are running an out of date version of the Integration

I've included everything that is relevant and that occurred during the time I was testing. There is literally no other information that is remotely related in the logs.
Regarding the out of date version of the integration, I'm running the latest version that has been released that isn't beta. It is marked "latest" in the github. If I'd been running a beta version, I'm sure the reply would be to try a non-beta version. I get that this is an open-source project, but let's not be Microsoft or Apple support here.

If there is a technical reason that I should try the beta, please let me know. I'd prefer that to being told that I'm not following instructions, for no other reason that the instructions weren't followed (following them in this case would not be helpful.)

I'm not expecting an extraordinary level of support or a resolution here really; The speaker is apparently quite old and will not be receiving an update to its chrome version. However, I've now noticed similar behavior with other speakers, albeit less breaking. For example, I have a Wiim streamer that shows as "off" in the Music Assistant if I initiate playing from my phone. If I set the wiim up as a Linkplay endpoint instead of Chromecast, then it behaves as expected.

I suspect that this is a Chrome implementation problem, and the different devices are on different versions of the Chrome firmware, or otherwise just implemented differently in a way that MA can or cannot compensate for. That's more what I'm looking for here, as I think a fix might not be a reasonable expectation.

Could you point me in a direction to look at messaging coming from the MA endpoint to the underlying HA endpoint, or otherwise share any insight you might have with varying behavior associated with Chromecast firmware releases?