Not an issue because I haven't bit the bullet yet...

[KraigoMpls]

I'm confused about what is available for multiple streams with SnapCast. Badaix has this in his description of the JSON API:

Snapcast can be controlled using a JSON-RPC API:

Set client's volume
Mute clients
Rename clients
Assign a client to a stream
<<

I have multiple SnapServers set up, but all but one are neutered with Mopidy and SnapServer disabled. Right now I live alone so having a single stream is fine, but I'd live to have each client able to dynamically connect to a different server.

The above suggests that one can do that today via JSON API. Yet in his roadmap Badaix lists "Groups support multiple Groups of clients ("Zones")" as implemented but "JSON-RPC Possibility to add, remove, rename streams" as not yet.

I could ask Badaix, but since you've actually created a client for the JSON-RPC API, you probably have a pretty good idea of where the features stand.

Thanks in advance for any information you can provide. I know that sooner or later I'm going to have to roll up my sleeves and learn to code this stuff, but for now I've been able to get by enjoying the fruits of others' labors.

KO

[atoomic]

Thanks for your details explanations. I clearly understand your request but unfortunately I've not played yet with this API call, I'm currently using one single snapcast server.

But this would make sense to give all of my boxes the ability to be client or server, and join any stream at any time.

Unfortunately I do not have a quick answer to your question, but you probably want to use the Group.SetStream query, more details from
https://github.com/badaix/snapcast/blob/master/doc/json_rpc_api/v2_0_0.md