sendspin 7.5.0 (current release) declares:
aiosendspin[server]~=6.0.1
~=6.0.1 resolves to >=6.0.1, <6.1.0, so a fresh pip install sendspin can never receive aiosendspin 6.1.x.
That matters because 6.1.0 added seek and seek_relative to MediaCommand, and servers have started advertising them. Loxone/Sonn Core 4.0.0-beta.21 puts both into controller.supported_commands for any track with a known duration. On aiosendspin 6.0.x that value cannot be parsed, and since supported_commands is typed list[MediaCommand], the whole server/state message is thrown away:
ERROR:aiosendspin.client.client:Failed to parse server message: {"type":"server/state","payload":{"controller":{"supported_commands":[...,"seek","seek_relative"],"volume":10,...,"seek_max_ms":310000}}}
ValueError: 'seek' is not a valid MediaCommand
mashumaro.exceptions.InvalidFieldValue: Field "supported_commands" of type list[MediaCommand] in ControllerStatePayload has invalid value [...]
The daemon then never starts a stream — the room is simply silent, while volume commands (a different message) still apply, so the client looks alive. Live streams with no duration keep working, which makes it look source-specific rather than protocol-specific.
Installing aiosendspin==6.1.1 fixes it completely (verified here across 5 rooms: Stream started with codec pcm immediately after the restart, audio at the card), but leaves the install outside the daemon's own declared range:
ERROR: pip's dependency resolver ... sendspin 7.5.0 requires aiosendspin[server]~=6.0.1, but you have aiosendspin 6.1.1 which is incompatible.
Would you consider relaxing the pin to >=6.0.1,<7 (or cutting a 7.5.1 that does)? The 6.0.5 → 6.1.1 delta is additive on the client side — two enum members, the matching ControllerStatePayload fields, and small server-role changes.
Server-side context and the interop side of this: sonn-audio/core#382.
sendspin7.5.0 (current release) declares:~=6.0.1resolves to>=6.0.1, <6.1.0, so a freshpip install sendspincan never receiveaiosendspin6.1.x.That matters because 6.1.0 added
seekandseek_relativetoMediaCommand, and servers have started advertising them. Loxone/Sonn Core 4.0.0-beta.21 puts both intocontroller.supported_commandsfor any track with a known duration. Onaiosendspin6.0.x that value cannot be parsed, and sincesupported_commandsis typedlist[MediaCommand], the wholeserver/statemessage is thrown away:The daemon then never starts a stream — the room is simply silent, while volume commands (a different message) still apply, so the client looks alive. Live streams with no duration keep working, which makes it look source-specific rather than protocol-specific.
Installing
aiosendspin==6.1.1fixes it completely (verified here across 5 rooms:Stream started with codec pcmimmediately after the restart, audio at the card), but leaves the install outside the daemon's own declared range:Would you consider relaxing the pin to
>=6.0.1,<7(or cutting a 7.5.1 that does)? The 6.0.5 → 6.1.1 delta is additive on the client side — two enum members, the matchingControllerStatePayloadfields, and small server-role changes.Server-side context and the interop side of this: sonn-audio/core#382.