jishi
commented
6 years ago Sonos has made several changes to how they handle user accounts. Most of them was making it harder to get a hold of the account info, but sounds like they did something more to pandora.
The code makes the assumption that metadata with the tracks are created from the username, like this: SA_RINCON3_username but maybe that has changed.
I can't use Pandora here from Sweden, so I can't verify this, I need someone with Pandora to provide me with a sample of the metadata that is added when you start Pandora from the official client. There are no tools currently in the http api to read that out, which is a bit unfortunate at the moment. Maybe would make sense to add a debug endpoint that would print out useful information for me...
jacobwtyler
I'm getting an error when trying to invoke a station on Pandora. My credentials are entered correctly both on the server side in the settings.json file and in the Pandora Service Settings in the Sonos app so that shouldn't be the problem but when I try to invoke a Pandora station with the command:
http://localhost:5005/RoomName/pandora/play/{station name}I get:{"status":"error","error":"Got status 500 when invoking /MediaRenderer/AVTransport/Control","stack":"Error: Got status 500 when invoking /MediaRenderer/AVTransport/Control\n at Object.invoke (/sonos/node-sonos-http-api/node_modules/sonos-discovery/lib/helpers/soap.js:99:10)\n at Player.play (/sonos/node-sonos-http-api/node_modules/sonos-discovery/lib/models/Player.js:443:15)\n at pandoraAPI.then.then.then.then (/sonos/node-sonos-http-api/lib/actions/pandora.js:105:42)\n at <anonymous>\n at process._tickCallback (internal/process/next_tick.js:182:7)"}and I get a popup message on all of my Sonos controller interfaces which I've included a screenshot of here:
And on the log output for the node server, I get:
May 01 11:57:05 jacobwtyler node[572]: Error: Got status 500 when invoking /MediaRenderer/AVTransport/Control May 01 11:57:05 jacobwtyler node[572]: at Object.invoke (/sonos/node-sonos-http-api/node_modules/sonos-discovery/lib/helpers/soap.js:99:10) May 01 11:57:05 jacobwtyler node[572]: at Player.play (/sonos/node-sonos-http-api/node_modules/sonos-discovery/lib/models/Player.js:443:15) May 01 11:57:05 jacobwtyler node[572]: at pandoraAPI.then.then.then.then (/sonos/node-sonos-http-api/lib/actions/pandora.js:105:42) May 01 11:57:05 jacobwtyler node[572]: at <anonymous> May 01 11:57:05 jacobwtyler node[572]: at process._tickCallback (internal/process/next_tick.js:182:7) �Any help would be greatly appreciated. The Spotify credentials in my settings.json file must be working because I can invoke all Spotify playlists/songs/albums and every other command has worked flawlessly so I think my setup is good. I can call up a Pandora station by using the:
http://localhost:5005/RoomName/favorite/{favorite name}but that feels a bit hacky. One possible issue is that I changed my email address that was associated with Pandora recently and my Sonos was still logged in with the old email address where the settings.json had my new email address and password. I removed my Sonos login and reauthenticated but I wonder if something got out of sync there. Today, I tried changing my Pandora password and then updating credentials on Sonos and Node side but got the same error. Sonos is clearly receiving the command but it doesn't seem to think my credentials are matching up. Btw, Pandora stations do play just fine in the Sonos Controller apps both before and after updating the credentials if I just use the stock search and click on a station method.Update: I'm starting to think it might be the Sonos side of the equation because I sent a command to invoke a station that I hadn't listened to in a long time (so it was toward the bottom of my stations in the list in Pandora app) and it gave me the error message again but it moved the station to the top of my list so this plugin must've been logged in and called the station up. Still haven't solved it though.
Update to the update: I'm not seeing this effect anymore when picking old stations that I haven't listened to in a long time so maybe I just imagined this. Sorry for the confusion.
Anyone have any ideas on what might be going on here? I've tried absolutely everything I can think of. Luckily, WebCoRE (SmartThings Rules Engine that I use for automation) can play Pandora stations through SmartThings' (mostly broken) implementation of the Sonos' API so I have a workaround but at this point I'm just frustrated with myself that I can't implement this one element of @jishi Sonos HTTP API.