UPDATE: Bug is back with 9.0.32. Was: Incorrect CPath selection with multizone system since v~8.5.15

[OneBobone]

Premium acct

All sorts of devices and OS versions:

- Win10 App, iPhone 6,7,X  and iPad mini and Pro

-  iOS 9, 12, 13, 14

Problem summary:

Multi-zone systems typically have one playing app =" DeviceID", with audio distributed to several speakers (= "remoteName") with associated CPath.

After ~8.5.1, the client

1. first issues an incorrect GET, e.g. [GET /goform/spotifyConnect/zone/6?action=getInfo&version=2.7.1 HTTP/1.1\r\n]
2. followed by an incorrect POST [...] with the same wrong CPath upon selection of a speaker in the list of the transfering client (e.g. iOS app).

Response from GET:
2020-12-15 07:54:28,844 [21] DEBUG Services             [(null)] - MCDCT:SpC:GSR:AU:{"status":101,"statusString":"ERROR-OK","spotifyError":0,"version":"2.6.1","deviceID":"11224DB33B1B","deviceType":"SPEAKER","remoteName":"Kök","activeUser":null,"publicKey":null,"accountReq":null,"brandDisplayName":"AC","modelDisplayName":"Media Control Server","libraryVersion":"5.35.20191025.0","resolverVersion":null,"groupStatus":null,"tokenType":null,"clientID":null,"scope":null,"availability":null,"autonomic_fqn":null}

Highlight from the HTTP response to GET (log):

"deviceID":"11224DB33B1B","deviceType":"SPEAKER","remoteName":"Kök"

The system has one "deviceID", the MAC, with several MDNS endpoints. One for each speaker/"remoteName" with CPath = /goform/spotifyConnect/zone/[1 to x]

(e.g. CPath = /goform/spotifyConnect/zone/5)

However the app always issues:

/goform/spotifyConnect/zone/6... instead of "5"

(BTW, same result with version 276.1)

Problem details:

The originating spotify client correctly enumerates the speakers published on the network. See enclosed pictures.

Before ~8.5.15 a selected speaker/"remoteName" , will correctly use the associated CPath.

Today, only the CPath of the top item of the list of speakers is used instead of the one selected. Always! 

This happened from ~8.5.15 on and did not improve with ~8.5.40 when I believe that today´s alphabetic ordering was introduced.

Hypothesis:

Hopefully it is an easy fix to make sure that the CPath of the selected speaker is used  and not from the top item. It may have been overseen with the new releases.

Request:

Please confirm if this is a real bug?

Please indicate if you intend to fix it and when?

(It looks small to me..)

Finally,

The Airplay functionality per speaker works, but we all prefer to use Spotify rather than Apple..., right?

[santeri]

Hi, I'll have a look at this tomorrow, you don't happen to have dumps of the mdns packets the server is advertising itself with?

[OneBobone]

Hi,

Great, thank you!

Unfortunately do not have a dump. How could I produce one for you?

Attached are from the iPhone app Discovery (Bonjour,etc...)

BTW, are you a Spotify employee?

Cheers,

Bob

[OneBobone]

Zone 5

 

[santeri]

Yes, I'm a spotify employee working on connect.

If you have a mac you can do "dns-sd -Z _spotify-connect._tcp" in a terminal to find the spotify mdns devices.

[santeri]

btw, what kind of system do you have? It would be much easier if I can get hold of one to test on.

[santeri]

Actually, if you could run the desktop client with some extra arguments and send me the log, that would be helpful, for example on mac: "/Applications/Spotify.app/Contents/MacOS/Spotify --connect-debug-level=10 --show-console --log-file=~/spotify.log"

[OneBobone]

Fantastic, you are a connect specialist!

At last my troubles may be solved.

😁

Don’t have a Mac readily, but I attached(edited) a few screen shots from the Discover app.

See forum.

[OneBobone]

I am more familiar with Windows...

[santeri]

Please run the windows client from https://www.spotify.com/us/download/windows/ with the same arguments except change the log path to somewhere you can find it.

[OneBobone]

I feel uncomfortable posting a log.

Are you getting my emails?

[santeri]

**bleep**?

I haven't gotten any emails to my santeri.se address from you.

[OneBobone]

This is confusing...

I hit the "reply button" on the mails that I am getting from you/this forum.

[OneBobone]

A bug was identified and fixed by Spotify after a silly effort required by a paying user (me) to get attention.

Although the technical bug-fix is good,

Spotify's customer service is clearly dysfunctional and not at par with competition.

That major "bug" remains to get fixed.

[OneBobone]

This bug is back with 9.0.32.

Not present in 9.0.28.

Please address it swiftly and more graciously than last time…

It should be well documented and fast to fix.

[OneBobone]

This worked up until 9.0.30,

but fails thereafter.