First and most importantly, thank you Michael for providing an excellent plugin and for all of the other work you have done on the LMS ecosystem. It's been much appreciated by me over the years.
As it has taken about 4 days of ferreting around various parts of the forum and github to put this altogether, I thought I would post this here to make it a bit easier for anyone else dealing with this particular problem.
Working backwards from the solution. For multiple spotify accounts and multiple LMS players to work seamlessly on a local network with a Windows 10 server running LMS and spotty, the LMS server needs to have two in bound firewall rules added:
1) Allow UDP on port 5353 to spotty.exe.
2) Allow any TCP ports to spotty.exe. From my understanding this is for the web server that spotty provides for local comms with spotify apps; and the port number will be generated randomly by windows and probably won't be below 1024. Unfortunately, that is all the information I can find on it.
Note: These ports need to be opened on the machine running LMS/spotty (not the network router). I suspect this will work for any desktop windows running LMS and spotty.
This solves the following problem:
- Two or more spotify licenses (e.g. Family subscription or similar) on a network with multiple LMS players (in our case, several squeezeboxen, a couple of squeezelites and a couple of group players), with the LMS server on Windows 10.
- For the setup as installed, spotty works beautifully for the most part - no advanced features enabled, all spotify accounts registered with spotty, LMS players available as devices on spotify apps.
- However, when using spotify apps, the LMS player devices are only visible to one spotify account at a time, and this visibility can only be changed from the player spotty app menu. For example, we have 5 players on our network, and my partner can often see 3 players, while I can see the other 2. From Michael's terminology, I think is described as no local announcement/discovery of LMS. Without getting caught up in more detail, if this description makes sense, you may have this issue.
- Adding the firewall rule means that any spotify app/account on the local subnetwork can see and use any of the LMS spotty player devices.
Again, this is only about resolving local announcement on the local network that the LMS server sits in.
And finally, repeated thanks to Michael for his many responses about spotty, and also to the many contributors to librespot!
Cheers,
Larry
As it has taken about 4 days of ferreting around various parts of the forum and github to put this altogether, I thought I would post this here to make it a bit easier for anyone else dealing with this particular problem.
Working backwards from the solution. For multiple spotify accounts and multiple LMS players to work seamlessly on a local network with a Windows 10 server running LMS and spotty, the LMS server needs to have two in bound firewall rules added:
1) Allow UDP on port 5353 to spotty.exe.
2) Allow any TCP ports to spotty.exe. From my understanding this is for the web server that spotty provides for local comms with spotify apps; and the port number will be generated randomly by windows and probably won't be below 1024. Unfortunately, that is all the information I can find on it.
Note: These ports need to be opened on the machine running LMS/spotty (not the network router). I suspect this will work for any desktop windows running LMS and spotty.
This solves the following problem:
- Two or more spotify licenses (e.g. Family subscription or similar) on a network with multiple LMS players (in our case, several squeezeboxen, a couple of squeezelites and a couple of group players), with the LMS server on Windows 10.
- For the setup as installed, spotty works beautifully for the most part - no advanced features enabled, all spotify accounts registered with spotty, LMS players available as devices on spotify apps.
- However, when using spotify apps, the LMS player devices are only visible to one spotify account at a time, and this visibility can only be changed from the player spotty app menu. For example, we have 5 players on our network, and my partner can often see 3 players, while I can see the other 2. From Michael's terminology, I think is described as no local announcement/discovery of LMS. Without getting caught up in more detail, if this description makes sense, you may have this issue.
- Adding the firewall rule means that any spotify app/account on the local subnetwork can see and use any of the LMS spotty player devices.
Again, this is only about resolving local announcement on the local network that the LMS server sits in.
And finally, repeated thanks to Michael for his many responses about spotty, and also to the many contributors to librespot!
Cheers,
Larry