Spotify doesn't work properly with Amazon Echo Dot 4th Generation

[QAScenario]

Plan

Premium Family

Country

Brazil

Device

Amazon Echo Dot 4th Generation

My Question or Issue

Hi, I've been having issues connecting to my Amazon Echo Dot (4th Gen). I use it often as a speaker for Spotify along with my other Amazon devices (namely other 3rd Gen Echo Dot), and recently I've noticed that when I try using the 'Play' command through the Spotify API to start streaming on my 4th Gen, there's simply no answer.
I've checked my Amazon Alexa settings to make sure that the Spotify skill was properly linked to my account (it was), and I have also noticed that it's only when I try opening the "Connect to a device" screen on my Spotify app and leaving it open for a few seconds that my 4th Gen Echo Dot shows up and becomes available for selection. This particular behavior gives me the impression that this proccess of searching for devices "wakes" the Echo Dot up, and only then makes it available for streaming.
Again, this seems to be a problem exclusively related to the 4th Gen, as this behavior is not observable in any of my other devices (i.e the 3rd Gen Echo Dot).

[QAScenario]

Hi, sorry for chiming in, but I believe I might be able to provide a bit of info regarding your questions: 

- As I've gathered on other threads at the developer boards, it seems that establishing a connection with the Echo Dot via Spotify Connect device picker works just fine, the problem arises exclusively when trying to retrieve the devices through the API request (more specifically, through the /v1/me/player/devices endpoint). 

Something curious we've noticed is that after connecting to the Echo device through the Spotify Connect, there is a short time frame where the API request will work as intended in retrieving the available devices, including the Echo Dot. This only happens shortly after using the Spotify Connect and only lasts for a short amount of time before not being able to retrieve them anymore. 

Some time ago I've opened a thread about this over at the developer boards, if you're interested in retrieving more details: https://community.spotify.com/t5/Spotify-for-Developers/v1-me-player-devices-doesn-t-return-Amazon-Echo-Dot-devices-4th/td-p/5213016 

We've been eager to have this looked at by someone for some time. If you have any more questions, feel free to ask and I'll do my best to give any details that you think might be of some help towards fixing this issue. Thanks! 

[QAScenario]

I've recorded a video to further demonstrate the issue:

https://photos.app.goo.gl/yPmtg6yqd9pdngxQ9

As you can see, there's a slight delay while the Spotify app is trying to search the network for available speakers. During this time-frame, it's possible to see that the 4th Gen. Echo Dot ('Echo Dot de Tiago') is being listed, but it's not available for selection, as it stays greyed out for a couple seconds. Note that this happens exclusively with the 4th Gen: the 3rd Gen ('2º Echo Dot de Tiago'), in turn, does not display such behavior.

[Eni]

Hey there @QAScenario, 

Thanks for getting in touch about this here in the Community. 

First up, it's well worth running a clean reinstall to get rid of any cached files that might be causing trouble. This one is more thorough than the usual one. 

Additionally, we suggest that you restart your router to check if that does the trick. 

Lastly, could you let us know if this issue started happening after a specific event such as an update?

Keep us posted on how it goes. 

[QAScenario]

Hi, @Eni, thank you for providing support.  

Unfortunately, after trying all of your recommendations, the referred behavior still persists.  

I do have some more info that might help describing the issue more accurately: 

I currently work with a company that integrates Spotify with one of our products. Our application relies on retrieving a list of the user's available devices through the Spotify API.  

The problem is that, apparently after some time, the 4th Gen Echo Dot speakers (and exclusively the 4th Gen ones) stop being retrieved by this process. The only way to make these speakers 'available' again is through the method already mentioned in previous posts: it's necessary to open the Spotify app and go to the device selection screen. 

This is a problem for us because, as stated before, we rely on this list of 'available devices' that are retrieved through the API to provide our users with complete integration without having to leave our own app. 

Based on the behavior we've been observing, we postulate that when performing this procedure (opening the Spotify app and waiting for the available devices list), the 4th Gen Echo Dots receive a 'wake up' command of some sort, and if that's the case, we would be interested in learning what the specific command is. 

[Eni]

Hi @QAScenario, 

Thanks for getting back in touch. 

If you have any doubts about the integration you're developing for your company, we suggest that you head over to the developer board. You can can find more info about this here. 

However, we can help you here to find out what's going on with your Amazon device. 

Would you mind checking if the firmware of your device has any pending updates?

Additionally, we suggest that you try unlinking and linking your accounts again to check if that makes any difference. 

Lastly, you mentioned that you're able to use the device via Connect, could you let us know if you can use the voice commands after that?

We'll be on the lookout for your reply.

[QAScenario]

Hi @Eni, I'll be sure to check the developer board, thank you for the suggestion.

Regarding the device:
Last I checked, the device's firmware was up to date and we did try linking and unlinking the accounts several times, but the issue kept happening anyway.

And yes, the device works fine when paired via Connect, including voice commands (albeit it does present a slight delay of a few seconds to become 'available' for selection).

It's only when I try retrieving the devices through the API command that the 4th Gen Echo Dot in particular seems to be unresponsive.

Once again, thanks for the response.

[Stephan73]

I have the same problem. I was in contact with Amazon, but they reject any guilt. supposedly the problem is with Spotify. is there a solution in the meantime? what i don't understand why it only echoes the 4th. Generation concerns. Funnily enough, Amazon cannot understand the matter itself

Pls Spotify help us

😉

[Elena]

Hey @Stephan73!

Thanks for reaching out on the Community 

Could you confirm for us if you're trying to start playback on your Echo dot directly via the API or are you using the app Spotify itself and aren't able to connect even when using the Connect device picker?

Keep us in the loop here.

[QAScenario]

Hi, sorry for chiming in, but I believe I might be able to provide a bit of info regarding your questions: 

- As I've gathered on other threads at the developer boards, it seems that establishing a connection with the Echo Dot via Spotify Connect device picker works just fine, the problem arises exclusively when trying to retrieve the devices through the API request (more specifically, through the /v1/me/player/devices endpoint). 

Something curious we've noticed is that after connecting to the Echo device through the Spotify Connect, there is a short time frame where the API request will work as intended in retrieving the available devices, including the Echo Dot. This only happens shortly after using the Spotify Connect and only lasts for a short amount of time before not being able to retrieve them anymore. 

Some time ago I've opened a thread about this over at the developer boards, if you're interested in retrieving more details: https://community.spotify.com/t5/Spotify-for-Developers/v1-me-player-devices-doesn-t-return-Amazon-E... 

We've been eager to have this looked at by someone for some time. If you have any more questions, feel free to ask and I'll do my best to give any details that you think might be of some help towards fixing this issue. Thanks! 

[Stephan1973]

Hi Elenea, Hi @all
As we can see, there are definitely problems with 4th generation Amazon Echo devices.

For me it is also the case that the device seems to fall asleep after a short period of inactivity and it is no longer possible to operate it via the Spotify app.

the device only wakes up when the app is restarted, or alexa command " Alexa start Spotify"
This is for sure a problem, which i cannot solve myself.
I was already in contact with Amazon about this, but they say Spotify must take action.

[Alex]

Hi folks,

@QAScenario, thanks for the details you've submitted. No need to be sorry as welcome all info.

From what we can see in the linked dev thread and what @ohej has also linked to, it seems there are several issues with newer firmwares on the Echo devices. We as moderators aren't too familiar with the API, but that we'll get in touch with ohej, to see if he has any updates on the matter and ask him to post again in the linked dev thread 🙂

@Stephan1973, this issue is already being discussed on the dev boards and the right folks at Spotify are aware of it. Without wanting to pass the ball, it really does sound as something in the newest firmware and the 4th gen echoes has caused issues to appear, as no other devices seem to be experiencing this. This is outside of our control to rectify. All we can do is check our API for any optimization opportunities. 

Hope you find this info helpful. Don't hesitate to reach out again if you have questions.

[QAScenario]

Hi @Alex, thanks for being so helpful.

I understand that this info might not be available for you to disclose, but we'd really like to know if there's any sort of deadline towards fixing these issues that were raised. I ask this because, as you might've noticed back at the thread @ohej linked, they seem to have some idea of what might be causing these problems (back in June they've already pointed out this faulty Echo Dot firmware hypothesis), but since then we've had no real follow-up. I say this in the nicest way possible because we really like and appreciate the platform, but it's been over three months and we're still trying to find ways to work around this issue without success.

[Stephan1973]

Hi Alex

first of all I want to say thank you for your help,

and I am glad that things (hopefully) are moving forward now.

By the way, when it comes to firmware, I'm with you.

I suspect that too, but I'm not a software specialist.

Am**on won't be entirely innocent 🤔

API optimization sounds good and is urgently needed anyway.

This will be the next thing we get on your nerves with 😁

but that should not be the topic here
One after the other.

just that there is no boredom 😃

Please stay tuned and don't give up💪👨‍🔧

[Stephan1973]

when can a solution be expected?
it's getting embarrassing
also for Amazon

[Stephan1973]

with every new software update, the hope flares up in me, that I will finally be able to use my Spotify the way I want it to be.

5 minutes later, this little **bleep**ing device list brings me back to earth. 😫

c´mon Spotify, iam sure you can fix this! pls

[Stephan1973]

looks like the user is a solo entertainer here.😞

Hello Spotify here is a customer who pays monthly

even real money, and no buttons.

[Nossnatas]

I have the same problem but reading trough this thread it does not seem that Spotify or Amazon care too much about this issue. So that's a bit sad.

[Stephan1973]

embarrassing is better.😂

what Amazon probably says, that their devices cannot be used in connection with Spotify

I can also play games👺

[Stephan1973]

Spotify Free works just as badly as Spotify Premium works.

So why pay?

And just as a reminder of how sloppy work is being done at Spotify, the following upload.

[SAPReApEr]

I have similar issues. I can only use spotify on browser and phone app. I have 3 different generations of echo devices and they all just stopped working within the past 3 days. My firmware was not updated on 8 different devices in the past 3 days... I have cleared cache etc, and also disabled spotify skill, then i enabled and re-linked etc. It see's all the devices but cannot play on any of them.