Announcements

Help Wizard

Step 1

NEXT STEP

Amazon removed the command "Alexa, spotify connect"

Solved!

Amazon removed the command "Alexa, spotify connect"

Did Amazon Echo just removed the 'Alexa, Spotify Connect' command? On one hand, if you have a single listener at home, and the Amazon account is linked with that single account, the echo device are always there. Nevertheless, if you have a family account with multiple listeners, and use echo devices as smart speakers, you just lost the ability to different family members, with different accounts, to stream to different speakers at the same time. I am devastated and consider leaving Spotify.
Reply

Accepted Solutions
Marked as solution

Found the solution, or at least a temporary workaround! > Try “Alexa connect my Spotify account” https://twitter.com/bradgillespie/status/1132133563560710146 It's clunky, and long and I hope they fix it in the next release. (I'm pointing my finger at Amazon, since they're in control of what Alexa does when it hears the word "connect".)

View solution in original post

8 Replies

Not working for me either. Alexa just tries to search for Bluetooth devices.

This just happened to me as well, but I can't find anything online that states that this is a known feature change.  Hopefully it is a bug?  We've got a Spotify Family account and each family member has their own account on their own device, with a couple of Amazon Echos, and we use the Spotify Connect command all the time.  I was just trying to add an Echo Input to our main AV system, but without this command there is no point.  The Echos are all on a single Amazon account, with the last of our Spotify Family accounts tied to it (so we don't block each other when away from using the Echos by direct voice command) and that means that the Echo speakers don't show up as available Devices in Spotify without doing the Spotify Connect command.

Rick, what you describe is my exact situation and use case.
This morning, Amazon support didn't know how to detangled what I was complaining about it and "escalated it to an engineer".
This afternoon, Spotify's support specialist were no good either. They directed me to using a single account across all. Unfortunately, this means that different family members can no longer use their different accounts to listen to music through the different Amazon Echo speakers.

Thanks for providing the update that you already contacted Amazon and Spotify - I was about to do the same after removing and adding accounts didn't fix the problem!  Using a single account is not a viable solution at all, as we sometimes each listen to music on separate devices in different locations and we would just be blocking each other.  If this isn't a temporary bug, and is acutally how they intend the service to work going forward, we are going to have to find a different music provider.

Tracking it here in Amazon forums:

https://www.amazonforum.com/forums/devices/echo-alexa/512974-echo-devices-search-for-spotify-connect...

 

I'm trying this:

Fixed - have to use the desktop Alexa  https://alexa.amazon.com/ - unlink Spotify account and re-connect.

Did not work. :-{

Exact same thing happening to me as well. My Spotify account is connected my Alexa account and my daughter would use Spotify Connect to stream to a device from her Spotify account. 

 

Now all the Echo devices are also listed in my Spotify app with "Spotify Connect" under them (this def wasn't the case before) and any time you say "Alexa, Spotify Connect" she responds with searching and starts looking for Bluetooth devices.

 

Must be a bug introduced with the last update or something.

Marked as solution

Found the solution, or at least a temporary workaround! > Try “Alexa connect my Spotify account” https://twitter.com/bradgillespie/status/1132133563560710146 It's clunky, and long and I hope they fix it in the next release. (I'm pointing my finger at Amazon, since they're in control of what Alexa does when it hears the word "connect".)

Apaprently Amazon fixed it - "Spotify connect" once again works as expected.  I don't see any notifications about the change from either company, so I guess it was just a bug which was fixed.

Suggested posts