How to transfer playback to Sonos Arc after using zeroconf apis? #22
Replies: 13 comments 24 replies
-
|
@andrew-kennedy Everything in your Questions:
Note that if you don't have a password setup for your Spotify account (e.g. you utilize the "Continue with Google" or other non-password methods for login), then you will need to define a "device password" in order to use the ZeroConf Connect service; use the Spotify Set Device Password page to define a device password. You will then use your Spotify username and the device password to Connect to the device.
Other things to try: Do whatever you need to do to get the Sonos device back in the Spotify Connect device list (reboot Sonos maybe?), and start playing a track on it (from Spotify mobile app | desktop app | web | etc - whatever works). If the above works then we know that the IP address, port, CPath, and Version parameters are good, so it's a matter of your Spotify user credentials. |
Beta Was this translation helpful? Give feedback.
-
|
To answer your first question, there is no specific configuration to set up spotify connect with sonos, sonos works locally over DLNA so the spotify app just recognizes them on the same network and can play audio to the sonos over spotify connect from the spotify app. Without more logging within the spotify plus zeroconf connect service I may not be able to say what specifically is wrong. |
Beta Was this translation helpful? Give feedback.
-
|
Interestingly, disconnect does work when I have spotify playing on the sonos via local spotify connect, but it gives a |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried this with the latest v1.0.30 version of SpotifyPlus? If not, can you give that a try please. It might fix the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I hit the same point... Then I get this response from my sonos speaker (using a ikea symfonisk) Failed to call service spotifyplus.zeroconf_device_connect. ZeroconfResponse: SpotifyError="0" Status="103" StatusString="ERROR-UNKNOWN" Let me know if you have any other ideas... It would be sooo sick getting this to work Note: using the .31 release from a few hours ago |
Beta Was this translation helpful? Give feedback.
-
|
@s00500 This should return information for the Spotify Connect device - something like this (my device example): |
Beta Was this translation helpful? Give feedback.
-
|
The response I get looks like this: {
"status": 101,
"statusString": "OK",
"spotifyError": 0,
"version": "2.9.0",
"deviceID": "4f3990f476a5eff1772c93aa8272ddc5480a4124",
"publicKey": "GjrPPGrvblfRB1RDlYM4uCy1rgj0KUh3juT8StZ1aMUuR22M8G7Y9a0QOEo1KPXMm9M76OMN46o2ro3iopyB6aYHQRrw0Xq/17NdX3QEDJIzwa/pxvgWez4md3ej3zsc",
"deviceType": "SPEAKER",
"libraryVersion": "3.199.414-gea87b026",
"resolverVersion": "0",
"groupStatus": "NONE",
"tokenType": "authorization_code",
"clientID": "9b377073ea334637b1406f329ce005de",
"productID": 1233,
"scope": "streaming",
"availability": "",
"supported_drm_media_formats": [
{
"drm": 1,
"formats": 70
}
],
"supported_capabilities": 3,
"modelDisplayName": "Bookshelf",
"brandDisplayName": "Sonos",
"remoteName": "Workroom"
} |
Beta Was this translation helpful? Give feedback.
-
|
@s00500 The thing that worries me about your response is the Will keep you posted. |
Beta Was this translation helpful? Give feedback.
-
|
Just noting I tested again with your latest changes and got the same error as @s00500 , let me know if you need any more data! |
Beta Was this translation helpful? Give feedback.
-
|
@thlucas1 awesome! and very understandable. I could also do some wiresharking to the speaker theoretically as the symfonisk speakers have a nice ethernet port, might leak some of my auth data though so not sure yet =D |
Beta Was this translation helpful? Give feedback.
-
|
Did another update to .34 today. Again moving from sonos to my mac works fine, the other way around I get this error again Failed to call service media_player/select_source. SAM0001E - An unhandled exception occured while processing method "PlayerTransferPlayback". SAM1003E - Spotify ZeroConf API returned an error status while processing the "Connect" method. Status: 103 - ERROR-UNKNOWN Message: "ZeroconfGetInfo: SpotifyError="0" Status="103" StatusString="ERROR-UNKNOWN" ActiveUser="" Aliases=[] Availability="" SupportedDrmMediaFormats=[] Version="2.9.0"" |
Beta Was this translation helpful? Give feedback.
-
|
@s00500 He was able to provide the mDNS activity between his desktop Spotify player and the Roku device. It really helped to see the data that was being exchanged between the 2 devices, and I was able to mirror that flow with my underlying SpotifyWebApiPython library. The data flow between the Spotify desktop player and the Spotify Connect device can vary by manufacturer. It's REALLY hard to code a solution when I don't have the physical device to experiment on. With that said ... What I'm looking for is the mDNS activity for the For example, the below Wireshark trace led me to change the way the It was also helpful to send a SmartInspect Trace log (SIL) file; however, that one will reveal detailed information about the SpotifyPlus integration and its configuration options that contain your userid and password. If it comes to me asking for that, I would suggest you create a temporary password for your Spotify userid that can be used for our testing. The SIL file can be encrypted so that it's secure to attach to a forum post. WireShark Trace Example (sensitive data changed): |
Beta Was this translation helpful? Give feedback.
-
|
@andrew-kennedy [ 1.0.41 ] - 2024/07/18
This should give you the ability to transfer playback to another Spotify Connect device, including Sonos devices; use the Player Transfer Playback service, specifying the Spotify Connect device name to transfer to. Like so: I also put together a Spotify Connect Brand Notes page that documents some of the quirks and oddities that I have ran into trying to control Sonos Spotify Connect devices. Note that I only have a Sonos Symfonisk (gen 2) device to test with, so let me know if it works with any other Sonos device types. I would like to document the specific Sonos device types it does / does not work with. Give it a try and let me know how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
It seems to work! I was surprised because I first went right back to the ZeroConf service calls and noticed they still don't work for the ZeroConf Connect Device call using username and password, but turns out they aren't needed anymore because you have the Sonos devices directly showing up in the Get Spotify Connect Devices service! |
Beta Was this translation helpful? Give feedback.
-
|
That is correct. I have not figured out how the |
Beta Was this translation helpful? Give feedback.
-
|
@andrew-kennedy @s00500 [ 1.0.44 ] - 2024/07/24
@andrew-kennedy - please let me know if this is still working for you, and I will close Issue #27. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Hey Todd, Thank you soo much! 🎉🎉🎉 Only on the very first move it failed, but I assume that is cause I had users reset on the sonos devices I will go and test the .44 update right away Greetings |
Beta Was this translation helpful? Give feedback.
-
|
Hi Lukas, Andrew - can you guys verify that the SpotifyPlus integration v1.0.45 still works for you? I apparently broke something in the v1.0.43-4 releases that impacted some users. If you guys have a minute, please confirm it still works for you. I appreciate it - thanks! FYI - just released a new version of the SpotifyPlus integration . [ 1.0.45 ] - 2024/07/30
This should fix the transfer playback issues. Please see the Sonos Limitations wiki documentation for detailed information on Sonos device limitations. You may still have to switch the music source via the Spotify Desktop / Mobile app if you use multiple music sources on your Sonos device(s). |
Beta Was this translation helpful? Give feedback.
-
|
Hi @thlucas1 Did an updated and everything seems to be functional as before :-) Still super excited about this, I finally can use my streamdeck to move playback between my speakers ! Thanks for all your great work, I am also checking all the notes you are collecting together, great stuff for future experiments as well!!! 🎉🎉🎉 |
Beta Was this translation helpful? Give feedback.
-
|
Meanwhile: to me this discussion is successfully solved and also my ticket in case you want to close any of these :-) |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Thanks for confirming Lukas. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @thlucas1 ! As of 1.0.50 transferring playback using your new oauth method seems to properly use the spotify connect queue and all is almost perfect. I am able to transfer playback and the spotify app shows the state as playing, the track appear to continue to advance, etc, but I don't get any audio until I pause and resume the music once I call the player transfer playback service. I have tried with "start playback" both on and off, to no avail. My workaround right now is to add a pause call, a wait, and a resume call: It's working well enough for me, but I figured you may want to know! |
Beta Was this translation helpful? Give feedback.
-
|
@andrew-kennedy [ 1.0.51 ] - 2024/08/18
Give this release a try. I added a current_transport_info check of the Sonos device after play is transferred to pause / play as needed. Just be sure to test without your pause / play logic in the script you mentioned. Let me know how it goes - I appreciate your help and patience. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
1.0.51 works! Now playback actually begins after transferring. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, though I just noticed even though I set up the oauth2 token so that spotify connect transferring worked properly (under 1.0.50) it now goes back to copying the queue and using the sonos queue on 1.0.51. Do I need to re-acquire a token between updates? EDIT: I see the issue. It looks like |
Beta Was this translation helpful? Give feedback.
-
|
Ok, once I re-acquire the tokens, playing on transfer works perfectly on the Arc. So the only issue remaining is making sure tokens.json isn't deleted on upgrade! |
Beta Was this translation helpful? Give feedback.
-
|
Ahhhhh - did not even think about the I will need to either move the path of the token cache into the base config folder, or maybe there is a way via HACS to omit the deletion of the Thanks for catching that! |
Beta Was this translation helpful? Give feedback.
-
|
FYI - just released a new version of the SpotifyPlus integration [ 1.0.52 ] - 2024/08/19
To avoid having to regenerate the OAuth2 token, move and rename the Give this release a try and let me know how it goes. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Just tested, works great ! (have not tested the audiobook features though) |
Beta Was this translation helpful? Give feedback.
-
|
@s00500 Thanks - Todd |
Beta Was this translation helpful? Give feedback.
-
|
Hey Todd, yes certainly! Again currently not home but in about a week I am, I noted it to my todo :-) Greetings, Lukas |
Beta Was this translation helpful? Give feedback.
-
|
@andrew-kennedy Thanks - Todd |
Beta Was this translation helpful? Give feedback.
-
I'm trying to set up an automation to dynamically move playback from my iPhone to my home sonos speakers. Here's an example of the output from the zeroconf discover devices service:
Given this, I made a call to zeroconf getinformation service which yields this (redacted private info):
Given this info didn't add anything else, I tried to call zeroconf device connect to put the zeroconf sonos speaker in my spotify connect devices list:
But this just gives me an internal server error. Am I doing something wrong? does this not work with sonos? I'm basically hoping using these zeroconf apis I can avoid having to run this proxy spotify connect device in a docker container: https://github.com/philippe44/SpotConnect
Beta Was this translation helpful? Give feedback.
All reactions