Cannot set device password

[cantsetdevicepass]

I can't set a device password. Whenever I try, it instantly says "There was a problem setting your password." No helpful error message or steps to take are provided other than this. Also, after trying once, the link to this page disappeared from my account settings. It is accessible by going directly to the URL:

https://www.spotify.com/us/account/set-device-password/add/

but it does not work. Since I was logged out of all devices (for some reason) a few days ago, my (custom-written) speaker system is no longer working until I can reset this device password.

[Joan]

Hi there @cantsetdevicepass,

Thanks for reaching out. 

We weren't able to reproduce this issue consistently. Can you try this in an incognito window, on different devices and different networks? If the issue persists, please send us some screenshots of the error so we can look into this further.

Let us know how it goes.

[dieinafire]

I have the exact same problem as the OP.

From here: https://www.spotify.com/uk/account/set-device-password/add/

The page is pre-populated with my device username as I'm already logged in, so I redacted the device username in the screenshot. I cannot reset the password. Same error every time and even the option to create a device password has vanished from my account page.

I did the network voodoo recommended by Joan, different networks, private browsing logins over multiple browser types, same outcome.

[Joan]

Hi @dieinafire,

Thanks for the reply.

Could you let us know what model speaker you're using? Consider trying to log in on that device using your regular Spotify account password instead. If necessary, you can reset that here, this should work. 

Let us know how it goes.

[Pierric82]

Hi,

I received an email saying my password was reset and I needed to set it again. Out of caution I initially avoided clicking the link and went directly to Spotify. It wasn't clear to me if it was my main password (since I logged in with FB and thus didn't use the main password) or my device password.

I started by resetting my device password by going to "establish a device password". There, the user id was the same as before, but it allowed me to set a password, so I did. However, setting that new password on my device resulted in "bad credentials".

I then also changed my main account's password, to be safe. I then tried using my main credentials from the device instead of the device credentials, just in case. No luck.

Then I realised, the "establish a device password" option is now gone from my account's menu! Going directly to https://www.spotify.com/account/set-device-password/ gives me an error when I try to set a password - the developer tools show me it's because there's already a password (interestingly, it seems that password can't be reset by the user??). But the credentials I had set up still don't work

I don't know what else to try anymore. Things were working fine, now they're not.

The device in question is a raspberry Pi running Raspotify (based on librespot) under Debian. This is how I listen to Spotify ~90% of the time. If it stops working, I'm giving up my subscription for sure.

Hope someone can help. And by the way, is there no more direct support channel? for a paid service???

Thanks

P.

[akn69fr]

Hi Pierric82,

I'm having exactly the same issue, and my use of Spotify is 100% identical to yours (RPI + Raspotify).

I really encourage Spotify developers to resolve this issue very quickly, otherwise I will move my Family Premium account to Qobuz.

Thanks

[Pierric82]

Thanks for chiming in @akn69fr! At least I know I'm not crazy, and probably not doing something very stupid out of oversight.

I finally found the support email address which is as simple as **bleep** but is nowhere to be found on the website (at least the spanish version, as I think I found it on the US site in the end). Or it's just very well hidden. In any case, I've been having a very long chat with them since yesterday, and so far I feel like I'm speaking with chatGPT (probably an older version too 🤣). Zero progress has been made and I don't think the people answering me understand the questions I ask.

Spotify seems to be checking all the boxes of "startup gone corporation in a bad way": customer-averse product decisions, hidden support, de-skilling of support teams... it's all too common unfortunately. I don't feel like migrating to a new platform, but I feel like I will have to investigate options as well since at this rate, I will have cancelled Spotify by next week.

Do you know good raspberry options for other platforms like qobuz, by the way?

[Pierric82]

From the conversation in issue 1293 of the Spotifyd project on github (no linking allowed), it seems we are not alone and it is indeed a Spotify decision to discontinue password-based authentication.

[akn69fr]

Hi Pierric82,

I didn't try Qobuz on Raspberry Pi yet, but someone mentioned bubbleupnp server.

[RandomCustomer]

Not only that but it looks like they are ignoring devices they don't like that would have used it (raspotify, spotifyd, librespot)
They are no longer "Discoverable" as you can see my my attachments, they are there to any device on the same network, but Spotify is only showing "Partner" devices like the LG TV.

[dieinafire]

Like @Pierric82, I had a pretty miserable experience with Spotify's online chat support, which just repeatedly sent me to two different 9 year threads in this forum that no longer apply. 

Similar story with the spotify support email address. I couldn't seem to convince them that there was a difference betw...

Like most of the previous posters I'm using a pretty current build of raspotify which is of course just mostly a wrapper for librespot, on some Bookworm based Pis. I've had them all running using a device password for about 8 years.

I had been using a device password for the whole time until like most of the other posters, it stopped working suddenly a few days ago along with an annoying password reset email. I totally agree with some of the other conclusions here, I think Spotify silently sunsetted the device password feature.

I have kind of a workaround.

It turns out that librespot moved a long, long time ago to a zeroconf infrastructure, so you don't actually need local credentials on the Pi. This blurb kinda explains it, not directly, but a bit: **bleep**, I can't link to github! github? Really! 

In the Raspotify github Basic-Setup-Guide:

<URL this formum objects to>/dtcooper/raspotify/wiki/Basic-Setup-Guide

Spotify credentials
Unless you have disabled zeroconf (mDNS) discovery, librespot does not need your Spotify credentials, zeroconf will take care of authentication.

However if you have disabled discovery for whatever reason and you provided your credentials you will also want to enable credential caching so that librespot will cache the auth token and not have to login every time you connect. Unless you like nag emails ofc?

To enable credential caching change this in /etc/raspotify/conf:

# Disable caching of credentials.
# Caching of credentials is not necessary so long as
# LIBRESPOT_DISABLE_DISCOVERY is not set.
LIBRESPOT_DISABLE_CREDENTIAL_CACHE=
To this:

# Disable caching of credentials.
# Caching of credentials is not necessary so long as
# LIBRESPOT_DISABLE_DISCOVERY is not set.
# LIBRESPOT_DISABLE_CREDENTIAL_CACHE=

I just commented out the old spotify LIBRESPOT_PASSWORD and LIBRESPOT_USERNAME entries in /etc/raspotify/conf, restarted the daemon, and my standard Spotify clients (like the provided by vanilla spotify client on a laptop) just started discovering the Raspotify speakers again using mDNS discovery. The downsides of this way of doing things of course is that you've gotta have an authenticated spotify client on the same broadcast domain as the raspotify speakers for the speakers to authenticate, so I can't randomly start blaring music in my house from off my network. Also, if you, like me, have gotten a little funky with vlans, using zeroconf will be tricky. 

Hopefully this helps.

[RandomCustomer]

My guess is the window to use that has closed, it seems that unless you already have a credential file via discovery (that has a lifespan I bet) you can't use the discovery work around now, I know I can't. Every machine on my network can see my raspotify and Spotifyd devices, the Spotify apps are just ignoring them now.