I wonder if it’s an issue with the (Linked) xxxx devices; I wonder if those are some sort of virtual device maybe?
Before doing any of the below, try the update to v1.0.30 first. It might solve the issue. If it doesn’t, then …
At this point, we need to find out with of those 9 devices is giving use the 503 status error. To do this, it’s a matter of issuing a getInfo request via a desktop browser to each instance name in the dns-sd -B _spotify-connect local list and send me the results. The getInfo request will be a little bit different for each instance name, as the IP Address, Port, and CPath could / will be different.
Using my environment as an example …
Step 1 - Get all Spotify Connect instances available on the network. You already completed this step:
Browsing for _spotify-connect._tcp.local.
Timestamp A/R Flags if Domain Service Type Instance Name
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. Living Room Left
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. Garage
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. Media Player
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. (Linked) Media Player
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. Living Room
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. (Linked) Living Room
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. Patio
10:18:46.967 Add 3 21 local. _spotify-connect._tcp. Home Theater Room
10:18:46.967 Add 2 21 local. _spotify-connect._tcp. sonosRINCON_347E5C35D9DA01400
Step 2 - Issue a mDNS List command for each “Instance Name” to get the IP Address, Host, and CPath of each instance. So for my “Bose-ST10-1” instance, the command would be:
dns-sd -L "Bose-ST10-1" _spotify-connect._tcp local
and the output would look like:
C:\Users\thluc>dns-sd -L "Bose-ST10-1" _spotify-connect._tcp local
Lookup Bose-ST10-1._spotify-connect._tcp.local
6:30:52.606 Bose-ST10-1._spotify-connect._tcp.local. can be reached at Bose-SM2-341513fbeeae.local.:8200 (interface 5)
CPath=/zc VERSION=1.0
The mDNS List command for your first device instance would be:
dns-sd -L "Living Room Left" _spotify-connect._tcp local
Step 3 - Issue a getInfo http request url from a desktop browser to retrieve the Spotify Connect device information for the instance. From the information obtained in step 2, the request url would look like:
http://Bose-SM2-341513fbeeae.local.:8200/zc?action=getInfo
and the output would look like:
{"status":101,"statusString":"OK","spotifyError":0,"version":"2.7.1","deviceID":"30fbc80e35598f3c242f2120413c943dfd9715fe","remoteName":"Bose-ST10-1","activeUser":"31l77y2al5lnn7mxfrmd4bpfhqke","publicKey":"zd0izOw8jxpj/ijpB/KWS/vU4WGoZYYSXC7VVesZ+jmVTRzGYnibTWGs0pdSIzIc6gA4HzA7QkDvkmEJWeDAfPJYGzyGuEGRARw1laEmqQ3tTAsNOmwCxLFl6MEo4qxV","deviceType":"SPEAKER","libraryVersion":"3.88.29-gc4d4bb01","accountReq":"DONTCARE","brandDisplayName":"Bose","modelDisplayName":"Soundtouch","resolverVersion": "0","groupStatus": "NONE","tokenType": "accesstoken","clientID": "79ebcb219e8e4e9a892e796607931810","productID":70001,"scope": "streaming","availability": "","voiceSupport": "YES"}
repeat Step 2 and Step 3 for each “Instance Name” in the dns-sd -B list. One of those entries should generate a “503” error.
Note that if you don’t want to do the above, I can show you how to set up a SmartInspect Trace that would capture what the SpotifyPlus integration is doing to a trace file. You could then send that file to me for diagnosis.
Either way, we have to determine which device instance is failing and why before I can offer a solution (or fix a bug if need be).
