Documentation: Document configuration when running against a splitted (S1/S2) system about sonos2mqtt HOT 5 CLOSED

Two versions (S1 and S2) means two instances of this app. Since a lot depends on the speakers talking to each other there is no other way. The app starts by asking which speaker the current speaker knows. The JoinGroup command also uses that endpoint.

You're right that there will be some issues with the events. Take a look at the getting started and the sonos event listener configuration

My guess that if you use these settings, you'll get a working solution. You create 2 instances of this app with these environment variables:

You then expose port 6239 to instance 1 (as in the example docker compose) and port 6238 to instance 2.

This will have all the messages from/to the v1 system starting with topic sonos/ and sonosv2/ for the v2 speakers.

Would you care to send a PR with your findings? this file could be improved for this exact situation.

I also own some old play5 speakers, but I don't see the point in splitting my system so I cannot test this out.

from sonos2mqtt.

Works out of the box as described :-)
Many thanks.

But I have no idea how to create a PR :-(

from sonos2mqtt.

🎉 This issue has been resolved in version 3.1.1-beta.7 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from sonos2mqtt.

I've also setup building the documentation from the beta branch. Which can be found here https://sonos2mqtt-beta.svrooij.io/

Info about a splitted system can be found at this page https://sonos2mqtt-beta.svrooij.io/splitted-system.html

from sonos2mqtt.

🎉 This issue has been resolved in version 3.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from sonos2mqtt.