What server version of Music Assistant has the issue?
2.9.0
How is the MA server installed?
Home Assistant OS Addon
Mandatory: Carefully read the Troubleshooting FAQ and confirm that
As Applicable: Carefully read the Troubleshooting FAQ and confirm that
The problem
Music Assistant seems to retain player settings even after the player has been deleted from the MA app.
This occurs when installing a new firmware, after using the player in MA with another type of firmware.
- my case, it is migrating from Squeezelite to ESPHome/SendSpin, after the player has been discovered/used by MA as a Squeezelite client
---.
I have been using ESP32 players (Sonocotta ESP32 LOUD, LOUDER, LOUDER PLUS - not S3) with Music Assistant. After updating the firmware to ESPHome/SendSpin, MA discovers the players and resurrects the old player settings. See screenshot example of Squeezelite output protocol settings still showing up after MA rediscovers the player which is now using ESPHome firmware.
The issue seems to resolve eventually - but it is unclear why.
It may take hours or days, with HA restarts and reboots in between.
Any one particular restart may or may not clear the problem.
Note specifically in this log, HouseWaves-Three is the player in question. It was migrated from Squeezelite to ESPHome firmware before downloading the log. You can see MA attempts to use AirPlay, SendSpin bridge and the universal player settings on this speaker. The attached photo shows MA is still referring to the old player settings options for Squeezelite. It also recalled the original friendly name of the speaker that was changed when it was a Squeezelite client.
Note also, HouseWaves-Two 65ae54, is an ESPHome SendSpin client (also ESP32 Sonocotta board) that now works fine. It was also migrated from Squeezelite to ESPHome approx. 72 hours ago and experienced similar playback and settings issues that night. It is unclear what event(s) happened during the last 3 days that corrected this.
NOTE - I do use Pi-Hole, but there are no connection issues related to this problem. The logs clearly show MA is connected to the player, but simply attempting to use the "old" streaming protocols as it does not understand the player's firmware has changed since it was first discovered.
Also NOTE - I am using these devices only as MA devices. I have not adopted them into ESPHome.
How to reproduce
1 - Install Squeezelite firmware on ESP32 device
2 - Stream audio to the new player using MA
3 - Reflash the ESP32 device with ESPHome/SendSpin firmware
4 - delete the old player in MA
5 - Attempt to stream audio to the player in MA
Music Providers
I use only Spotify and SiriusXM - neither will stream to the player after migrating firmware
Player Providers
This only happens after using the ESP32 device as a Squeezelite client in MA first, and then change the firmware to ESPHome/SendSpin.
I have NO issues streaming to these identical boards - IF they are not migrated from one firmware to another.
Full log output
music-assistant.log
Also attached - ESP32 console log
NOTE - it connects as SendSpin client, but shows no status messages indicating playback/streaming while MA is attempting to stream using AirPlay, and SendSpin bridge protocols
ESP32 device.log
Additional information
What music source is in use when the problem is observed?
Spotify playlists and SiriusXM stations
What other music sources have you tried (if you have no others then make that clear - you can always try radio stations)
Those are the only 2 sources I use
What player provider is in use when the problem is observed?
SendSpin
What other player providers have you tried (if you have no others then make that clear - you can always use Sendspin)
Are the players grouped?
I have tried both individually and grouped
When grouped with other SendSpin players, the other players work; the newly migrated device is still silent
How is playback being instigated (e.g. automation or via the UI)
via the UI, clicking on a song or a music channel
If you aren’t using HAOS then exactly how you have installed MA
n/a - i use HAOS on RPi 4
What is working (e.g. player works with music source X but not Y)
all other players work
only players that are newly migrated from Squeezelite to ESPHome/SendSpin do not work
What you have tried from this page that hasn’t helped (This is very important!)
- restarting MA
- rebooting HA/MA with power reset
- rebooting the ESP32 device with power reset (unplug)
- repeatedly attempting to delete the player and allow MA to rediscover
- grouping/ungrouping
- changing the player settings options
- reset MA player settings to default
- verifying router connections to the device
- opening the device AP/portal to ensure connection status
-
- opening and saving the ESP32 device log to check for error messages
What version of Home Assistant Core (if used) are your running
Core 2026,6.2; Supervisor: 2026.6.1
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi
Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot
What server version of Music Assistant has the issue?
2.9.0
How is the MA server installed?
Home Assistant OS Addon
Mandatory: Carefully read the Troubleshooting FAQ and confirm that
As Applicable: Carefully read the Troubleshooting FAQ and confirm that
The problem
Music Assistant seems to retain player settings even after the player has been deleted from the MA app.
This occurs when installing a new firmware, after using the player in MA with another type of firmware.
---.
I have been using ESP32 players (Sonocotta ESP32 LOUD, LOUDER, LOUDER PLUS - not S3) with Music Assistant. After updating the firmware to ESPHome/SendSpin, MA discovers the players and resurrects the old player settings. See screenshot example of Squeezelite output protocol settings still showing up after MA rediscovers the player which is now using ESPHome firmware.
The issue seems to resolve eventually - but it is unclear why.
It may take hours or days, with HA restarts and reboots in between.
Any one particular restart may or may not clear the problem.
Note specifically in this log, HouseWaves-Three is the player in question. It was migrated from Squeezelite to ESPHome firmware before downloading the log. You can see MA attempts to use AirPlay, SendSpin bridge and the universal player settings on this speaker. The attached photo shows MA is still referring to the old player settings options for Squeezelite. It also recalled the original friendly name of the speaker that was changed when it was a Squeezelite client.
Note also, HouseWaves-Two 65ae54, is an ESPHome SendSpin client (also ESP32 Sonocotta board) that now works fine. It was also migrated from Squeezelite to ESPHome approx. 72 hours ago and experienced similar playback and settings issues that night. It is unclear what event(s) happened during the last 3 days that corrected this.
NOTE - I do use Pi-Hole, but there are no connection issues related to this problem. The logs clearly show MA is connected to the player, but simply attempting to use the "old" streaming protocols as it does not understand the player's firmware has changed since it was first discovered.
Also NOTE - I am using these devices only as MA devices. I have not adopted them into ESPHome.
How to reproduce
1 - Install Squeezelite firmware on ESP32 device
2 - Stream audio to the new player using MA
3 - Reflash the ESP32 device with ESPHome/SendSpin firmware
4 - delete the old player in MA
5 - Attempt to stream audio to the player in MA
Music Providers
I use only Spotify and SiriusXM - neither will stream to the player after migrating firmware
Player Providers
This only happens after using the ESP32 device as a Squeezelite client in MA first, and then change the firmware to ESPHome/SendSpin.
I have NO issues streaming to these identical boards - IF they are not migrated from one firmware to another.
Full log output
music-assistant.log
Also attached - ESP32 console log
NOTE - it connects as SendSpin client, but shows no status messages indicating playback/streaming while MA is attempting to stream using AirPlay, and SendSpin bridge protocols
ESP32 device.log
Additional information
What music source is in use when the problem is observed?
Spotify playlists and SiriusXM stations
What other music sources have you tried (if you have no others then make that clear - you can always try radio stations)
Those are the only 2 sources I use
What player provider is in use when the problem is observed?
SendSpin
What other player providers have you tried (if you have no others then make that clear - you can always use Sendspin)
Are the players grouped?
I have tried both individually and grouped
When grouped with other SendSpin players, the other players work; the newly migrated device is still silent
How is playback being instigated (e.g. automation or via the UI)
via the UI, clicking on a song or a music channel
If you aren’t using HAOS then exactly how you have installed MA
n/a - i use HAOS on RPi 4
What is working (e.g. player works with music source X but not Y)
all other players work
only players that are newly migrated from Squeezelite to ESPHome/SendSpin do not work
What you have tried from this page that hasn’t helped (This is very important!)
What version of Home Assistant Core (if used) are your running
Core 2026,6.2; Supervisor: 2026.6.1
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi
Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot