Native Sendspin Web Player missing from Sync Group member selection

[Suenee]

Before you begin

• I have searched the open and closed issues and this hasn't been reported yet.
• I have read the troubleshooting guide and it did not solve my problem.
• I am running a supported installation (Home Assistant add-on or Docker container).

What happened?

Problem

A native Sendspin Web Player that is online and working normally is no
longer available for selection as a member of a Sync Group Player.

This appears to be a regression because the same Browser Player could
previously be selected as a Sync Group member.

Environment

• Music Assistant Server: 2.10.2 Stable
• Also reproduced on: 2.9.13
• Installation: Home Assistant OS Add-on
• Home Assistant Core: 2026.8.0
• Client OS: Windows 11
• Browser: Google Chrome
• Player: Google Inc. / Web Player
• Output protocol: SENDSPIN (Native)

Player

Player name: LovePeace

The player is:

• online
• visible in Music Assistant
• identified as Google Inc. / Web Player
• using SENDSPIN
• shown in player settings as Configure Sendspin - Native
• able to play music normally when addressed directly

Direct playback to LovePeace works correctly.

Actual behavior

An existing Sync Group Player named Synca currently has 0 members.

When editing Synca and opening:

Configure Sync Group Player -> Group members

there are no players available for selection.

The same problem occurs when creating a completely new Sync Group Player:
the Group members selector contains no selectable players.

Therefore this does not appear to be a corrupted configuration of the
existing Synca group.

Expected behavior

LovePeace should appear as an eligible Sync Group member because it is
an online native Sendspin player.

Regression

This Browser Player was previously selectable as a Sync Group member.

I previously reported a related issue in #5756 using Music Assistant
2.9.4.

At that time multiple Browser Players using Sendspin could be selected
and saved as Sync Group members. The problem in #5756 occurred later:
only one configured member became active during playback.

The current problem occurs earlier: the native Sendspin Web Player is
not offered in the Group members selector at all.

The problem was first confirmed again on Music Assistant 2.9.13.

I then upgraded to Music Assistant 2.10.2 Stable and tested again.
The problem is still present in 2.10.2.

How to reproduce

1. Start a Music Assistant Browser Player.
2. Verify that the player is online and shows SENDSPIN / Native.
3. Play music directly to the Browser Player.
4. Verify that direct playback works.
5. Go to Settings -> Players.
6. Create a new Sync Group Player.
7. Open Group members.

Result

No player is available for selection.

Expected result

The online native Sendspin Web Player should be available as a Sync Group
member.

Related issues

• Sync Group with Browser Players (Sendspin) only activates one member #5756 - Sync Group with Browser Players (Sendspin) only activates one member
• Native Sendspin player cannot group with Sendspin bridge players #5901 - Native Sendspin player cannot group with Sendspin bridge players
• Sync groups don't survive transient disconnects: cast-bridge members permanently ejected (no re-join path); 30-s cleanup of a disconnected group leader kills the queue with no resume #6191 - Sync groups don't survive transient disconnects

A full Music Assistant log is attached.

How to reproduce

Use new or old group player

Music Assistant version

2.10.2

How do you run Music Assistant?

Home Assistant add-on

Diagnostics report or log file

music-assistant.log

music-assistant-diagnostics-2026-09-05-155754.json

Anything else?

No response

[musicassistant-bot]

Hi, and thanks for taking the time to report this! 🙏

In short

• Doing: Trying to add an online native Sendspin Web Player as a member of a Sync Group Player
• Happened: No player is available for selection in the Group members selector
• Expected: The online native Sendspin Web Player should be available as a Sync Group member

_{Condensed from the report above by a bot, so it may be wrong — the reporter's own words are below.}

Version: 2.10.2 · Install: HA add-on · Python: 3.14.7 · Platform: Linux-6.18.39-haos-aarch64-with-glibc2.41 · Players: 2

Here's what I found in the attached diagnostics:

🟠 Captured exceptions

The diagnostics captured these recurring errors, most frequent first:

• SetupFailedError ×2 — music_assistant/providers/hass/__init__.py:273 in handle_async_init: Error loading provider(instance) Home Assistant: 502, message='Invalid response status', url='ws://supervisor/core/api/websocket' (will be retried later)

🤖 AI assessment — possible root cause (for maintainers; may be wrong)

Reporter states a native Sendspin Web Player ('LovePeace'), confirmed online and playable directly, no longer appears in the member selector when configuring a Sync Group Player on MA 2.10.2 (also reproduced on 2.9.13). Two prior related issues (#​5756, #​5901) document earlier Sendspin/sync-group interoperability problems.

Likely cause: Likely a regression in the eligibility filtering logic used to populate Sync Group 'Group members' selection for Sendspin-based players — possibly tied to how SUPPORTED_GROUP_COMMANDS or group-command feature checks in music_assistant/providers/sendspin/player.py are evaluated for native Sendspin players versus bridge/AirPlay-style Sendspin clients. The pattern of two prior related Sendspin+sync-group issues (#​5756, #​5901) suggests this area has had repeated regressions across releases rather than a one-off user misconfiguration.

Evidence considered:

• Issue body: player confirmed online, playable directly, absent from Sync Group member selector in both new and existing groups (2.10.2 and 2.9.13)
• SOURCE music_assistant/providers/sendspin/player.py L124-126: SUPPORTED_GROUP_COMMANDS list defines which group commands Sendspin players advertise, directly relevant to member-selection eligibility
• RELATED #​5756: prior Sendspin sync-group issue (browser players only one member activates) on 2.9.4, same provider area
• RELATED #​5901: prior issue on native Sendspin players failing to group with Sendspin bridge players
• DOC player-support/sendspin#​supported-clients: confirms Web Browser client is an official supported Sendspin client type, supporting that this is a legitimate eligible player type

Maintainer next step: Reproduce with a native Sendspin Web Player on 2.10.2: check the sync-group member candidate filter (likely near SUPPORTED_GROUP_COMMANDS usage in music_assistant/providers/sendspin/player.py and the group-member enumeration logic in music_assistant/models/player.py) to confirm whether a recent change to group-command/feature checks excludes native Sendspin players from the eligible members list, and compare behavior/log output against the 2.9.4 code path referenced in #​5756.

category: bug · confidence: 45%

📖 Provider documentation

• Sendspin

🔁 Similar past reports

These earlier issues or discussions look related and might already have an answer (or indicate a duplicate):

• #5756: Sync Group with Browser Players (Sendspin) only activates one member (closed)
• #5901: Native Sendspin player cannot group with Sendspin bridge players (closed)

---

🤖 I'm an AI-powered triage assistant. I can make mistakes, and a human maintainer will still review this issue. This automation helps the small Music Assistant team keep up with the high volume of reports on this open-source project — thanks for your patience and for helping us help you!

[OzGav]

I can't recreate this.

Use a different browser or an incognito window, not a second tab and open MA so a second Web Player is created. Then check if both Web Browser tabs are shown and can be grouped.

[MarvinSchenkel]

Can you check the player's settings and make sure this checkbox is unticked