Announcements

Help Wizard

Step 1

NEXT STEP

player transfer to Echo-Dot-Groups failing

Solved!

player transfer to Echo-Dot-Groups failing

I can use the /v1/me/player/devices endpoint to get the IDs of all my groups, including the echo dots. It is noteable that the IDs look very different. While the spotify computer/tablet/phone apps generate a hex-number, the Alexa Dots generate a GUID-style ID whiht "-" inbetween.

When I use those IDs on the /v1/me/player endpoint I get "404: Device not found". The spotify app can switch and the currenlty-playing endpoint returns the exact sme ID for the device....

Reply

Accepted Solutions
Marked as solution

It works if you remove the "_amzn_1" from the end of the id:

 

```javascript

deviceid = deviceid.split("_")[0];
deviceid = deviceid.replace(/_/g, "");

```

 

I only just figured that out, getting the clue from this thread that the id format has changed.

View solution in original post

Marked as solution

okay this is weird but it seems like it's been fixed now, just ignore the whole trimming the end thing now and it does work again as expected...

 

I'm not sure if the problem QAScenario described still exists.

 

Is there a way to remove the "Marked as solution" from my previous answer?

View solution in original post

10 Replies

I have the same Problem when starting to play a playlist on an Echo device. Please let me know if you find a fix for this

I am also now having troubles. Transferring from one device to another is failing. Also, using the Spotify Integration plug-in from my Elgato Stream Deck, I am no longer able to start or stop playback on any Echo devices. It works fine if I choose a non-Echo device.

 

While actions like Volume up or down, next track, etc. are still functioning, any attempt to start or stop playback results in an error.

 

2023-02-21 11:04:22.8334|WARN|com.barraider.spotify|7|[7] SpotifyQuery returned with StatusCode: NotFound Command: me/player/play Error: {
"error" : {
"status" : 404,
"message" : "Device not found"
}
}

 

A review of the logs for the Stream Deck plugin show the following error:

EDIT: I have now taken some additional steps to confirm this issue:

 

I went to https://developer.spotify.com/console/get-users-available-devices/, then retrieved an OAuth token, clicked "Try it" and successfully listed all of my devices. 

 

I then went to https://developer.spotify.com/console/put-pause/  and pasted in the device ID for a device that was currently playing Spotify. When clicking on "Try it", I once again got a 404, as seen.

 

 

 

 

mW8GMW9kCZ.png

All Echo devices seem to have a new style of id. They were random letters and numbers before and now they have dashes and end with "-amzn". Maybe this is not agreeing with their API. I use the Web API. I first get a list of all available devices then i get the right deviceID and every time i want to change to an Echo device i get the "device not found" error.

Marked as solution

It works if you remove the "_amzn_1" from the end of the id:

 

```javascript

deviceid = deviceid.split("_")[0];
deviceid = deviceid.replace(/_/g, "");

```

 

I only just figured that out, getting the clue from this thread that the id format has changed.

I can confirm this using both "put-pause" and "put-play" while removing "_amzn_3" from the end of the device ID.

With the end trimmed, both work perfect.

 

https://developer.spotify.com/console/put-pause/

https://developer.spotify.com/console/put-play/

 

yeah that works thanks.

in javascript this would be:

 

var deviceIDwithoutAMAZONstuff = deviceid.split("_", 1);

 

I hope this helps.

While the workaround "fixing" the ID as suggested above does seem to work towards transferring devices, we've found that trying to run a GET method through the /v1/me/player endpoint still resulted in us getting a 500. Is anyone else getting this? I figure this should prove quite worrisome if widespread throughout all Amazon devices...

Captura_de_Tela_2023-02-24_as_16.19.20.png

I've also found another problem with this solution. It doesn't always end up with a unique name for the echo groups, there could be two with the same ID but one ends with _AMZN_1 and the other ends in _AMZN_2

So trimming the end of the ID gives you no way to address the second one...

Marked as solution

okay this is weird but it seems like it's been fixed now, just ignore the whole trimming the end thing now and it does work again as expected...

 

I'm not sure if the problem QAScenario described still exists.

 

Is there a way to remove the "Marked as solution" from my previous answer?

Update 06.03.2023, I still receive "_amzn_" suffixes for alexad evices, but not alexa-device groups in the list anymore.

I wonder who is messing aroud here. Spotify or Amazon?

Suggested posts