After some recent update to Music Assistant (currently on 2.8.1) I noticed that my third party Chromecast devices such as soundbars had their MA entity names changed from something like soundbar_ma to soundbar_2. This caused some of my player cards to disappear. That was easy to fix by renaming the devices back to soundbar_ma.
However, these third party devices seem to have lost the power toggle in the MA device.
The official Chromecast devices such as the Google Home Mini still have their power toggle in MA. It is only the third party devices that seem to have lost it. Furthermore over in the Chromecast integration all the devices have a functional power toggle so it seems to be only the MA duplicate the has lost that function.
Does anyone else have this issue?
Update: I think it is this issue.
opened 05:29PM - 27 Mar 26 UTC
airplay
triage
Chromecast
spotify
youtube_music
hass
needs-attention
### What version of Music Assistant has the issue?
2.8.0
### How is the MA ser… ver installed?
Home Assistant OS Addon
### Mandatory: Carefully read the Troubleshooting FAQ and confirm that
- [x] I have examined the logs and tried to resolve this issue
- [x] I have fixed any errors or warnings in the logs that relate to tags
- [x] I am not running MA across a VPN, VLAN, subnet, behind a firewall, or using local SSL or have any other complex network setup
- [x] I am not using or have disabled tools such as AdGuard, Pi-hole or pfSense and retested
- [x] I have checked my network setup to ensure mDNS/multicast is not being blocked
- [x] I have reviewed the [Open](https://github.com/music-assistant/support/issues) and [Closed](https://github.com/music-assistant/support/issues?q=is%3Aissue%20state%3Aclosed) Issues and [Discussions](https://github.com/orgs/music-assistant/discussions)
- [x] I have reviewed the applicable [player](https://www.music-assistant.io/player-support/) or [music provider](https://www.music-assistant.io/music-providers/) documentation
- [x] I have reviewed the [MA Status Page](https://github.com/orgs/music-assistant/discussions/709)
- [x] I have tried restarting MA and rebooting the host
### As Applicable: Carefully read the Troubleshooting FAQ and confirm that
- [x] If using HA, I have confirmed the internal URL is set correctly
- [ ] I have tried a wired connection for issues related to interrupted or poor playback quality
- [x] If the problem relates to a device then I have checked the device settings
- [ ] If it is a frontend issue, I have tried a different widely used browser
- [ ] For voice problems, I have sought help elsewhere before returning here
- [ ] For playback problems, I have recycled power to the physical device
### The problem
Hi.
After updating MA to 2.8.0 my LG S90TY soundbar connected to MA via Chromecast shows incorrect state.
When?
It appears as `idle` at the time the input is not currently over Chromecast (MA, Spotify, etc...). Current input is HDMI/E-ARC means TV is now streaming audio.
MA integration:
<img width="304" height="254" alt="Image" src="https://github.com/user-attachments/assets/9f4a2d12-82f9-40a0-bbe1-00c3cde0418f" />
LG soundbar integration (current input):
<img width="440" height="750" alt="Image" src="https://github.com/user-attachments/assets/9400fcf5-f221-4c0b-bda1-a02efdaf7b6b" />
In `Google cast integration` at the same time the soundbar correctly reports as `off` so this is for sure related to latest 2.8.0 release.
<img width="313" height="169" alt="Image" src="https://github.com/user-attachments/assets/1ec62520-450d-40d1-aa4a-19f0bbf3b5ce" />
Now another part of this issue is that even thou I turn off physically the soundbar it still stays idle in MA.
Also I am not able to turn off the soundbar at this state via MA results in error below:
```
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:321
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 18:05:09 (1 occurrence)
Last logged: 18:05:09
[140664941723712] Entity media_player.living_room_audio_mass does not support action media_player.turn_off
```
### How to reproduce
Have LG soundbar with Chromecast built-in or maybe even other soundbars will behave the same and update MA to 2.8.0.
### Music Providers
At this point no music is streamed to soundbar but using Spotify and YTMusic otherwise.
### Player Providers
Chromecast. There is also possibility to use airplay with 2.8.0 for the soundbar but it's the same behavior.
### Full log output
[d5369777_music_assistant_2026-03-27T17-26-24.561Z.log](https://github.com/user-attachments/files/26311098/d5369777_music_assistant_2026-03-27T17-26-24.561Z.log)
### Additional information
There was similar issue with chromecast with release 2.7.0
#4533
Simple things like reboot the MA add-on and reload the integration doesn't work this time.
At this point I have to go back to 2.7.11 to keep my automations working.
### What version of Home Assistant Core (if used) are your running
2026.3.4
### What type of installation are you running?
Home Assistant OS
### On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)
### Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot
- [x] Yes
KoenL
April 13, 2026, 12:20pm
3
I experienced exactly the same issue today after the update. The solution was simple in my case: restart Music Assistant via Settings > Apps > Music Assistant. After that, all broken connections with the speakers were automatically restored.