New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect my spotify account #152
Comments
|
Recently Spotify disabled the skill's API key so the skill can currently not be used. I'm trying to get through to Spotify to get this up and running again I'm also working on a workaround where users can supply their own key to the skill. got a POC on that but it'll require some more work to get it user friendly. |
|
Ok, thanks! I am looking forward to it! |
|
same The observationRecently noticed: I confirmed my user/pass is correct in the config, so then retried the "Connect" button in the account skills it punts me to something like: browser shows: INVALID_CLIENT: Failed to get client @forslund - per discussion; System Versions
|
|
What is a bit bonkers to me is:
|
|
Found:
|
|
This sucks |
|
@fermulator any Updates from Spotify? |
|
Nothing yet;
@forslund indicated to me offline he contacted them as well (not sure by which method) The other way I know of is:
But obviously this already went through that process? (@forslund can confirm) - but the application/request is so basic, I'm not sure how Spotify intends to approve or denote applications that REQUEST for written consent to have their application control Spotify via voice... |
|
Yes but same here with Deezer. Wrote them approximately 5 Emails and they sayed to me write them on twitter but no answer yet. |
|
I started the "HW partner application" process, I also reached out through their Developer support (which I think is new) asking if there were some other channel to go through for this. They confirmed that it was the HW partner form that was needed. So it's the waiting game right now... |
|
@forslund ok thank you for your engagement ;) |
|
I fear only hardware partners with some kind of deal will be admitted. It is always a money game. Sad. |
|
Yes that's my fear as well. There is a branch which can use user supplied auth info, but I still need to write some docs on how to use it and make it smoother in case Spotify declines again. |
|
i cant figure out how to use my own key. is there a guide anywhere? |
|
EDIT: this method has been added for now into the skill and instructions are available in the readme.md. I leave the old temporary instructions below for completeness but they should not be used anymore. I quick (and quite dirty) but working way to run spotify with local auth Set up a developer account and make sure to whitelist go to the mycroft-spotify skill directory and checkout the branch feature/local-api-key
then in the mycroft-core dir run this should result in a hidden file called now before starting Mycroft you need to put the client key and client secret in the environment variables Then start Mycroft. Sorry that I haven't had time to clean this procedure up... |
|
Thanks for the guide. Unfortunately that branch doesn't work for me: This is very odd, since the spotipy docs do show a So presumably a versioning issue? I wish I could help, but Python's dependency management has always baffled me. |
|
Also, there's a step missing - you also need to whitelist |
|
Ah humm, yes I think I've updated the spotipy dependency... try running Will add the whitelist step to the description. Thanks for flagging |
|
Works, awesome! Would be a real shame if every user had to fiddle about with a developer account, but at least the option's there for now. |
It shouldn't be too bad once you can put your credentials in via Mycroft/Selene. Just a list of instructions to create the app appropriately and some copy-pasting would be needed. |
|
I was able to get it mostly working, I can get it to play and stop on other devices but not on the mycroft itself. Almost like it wasn't registered as a device at all. |
|
The skill is not a player in itself, it requires a local player to be installed. Such as librespot or spotifyd (the player needs to be logged in and can't be in discovery mode) |
|
Oh thank you, I miss understood |
I couldn't see this on the README. May be worth mentioning if not already to prevent future tickets? |
|
I have a PR I've forgotten to merge, sorry. It would be helpful if you could read through PR #145 and see if anything should be added |
|
I've left you some feedback on that PR! |
|
I'm in the same position as @Djinnxie and just receive the EDIT: It might be that spotipy doesn't support headless. EDIT2: If you install links ( |
|
Yeah it doesn't do headless it tries to launch a webbrowser. You can run it on a desktop and transfer the files to the target machine. Thank's for the links tip as well! |
|
Thanks @forslund !! All working now, appreciate the help My bad for missing this crucial bit for spauth.py:
Cheers |
|
Any pointers? I actually does seem to work for me now. After playing some stuff from my phone on other devices, mycroft can see the ones I have used, but not the others. Strange, but it seems I am set now atleast. |
|
It can only see logged in devices. so if the devices are set to be in discovery mode. After connecting to them using your phone they will be logged in. What devices are you trying with? |
I have some chromecast devices. It works well enough for me with the current mode of operation, I was just surprised that nothing was showing up first :) |
|
I have been able to successfully connect to Spotify and can use Mycroft to remotely play Spotify songs on my phone but I have been unable to set my Picroft as a device. When Spotify is not open on my phone and I say "What Spotify devices are available?", Mycroft replies with "There are no Spotify devices available". I have added my Username and Password to 'Play Spotify' section of my skills, however when I click on the 'Connect' button, it opens a page that simply says 'INVALID_CLIENT: Failed to get client' at the following url: Can anyone shed any light on where I am going wrong. Thanks. |
Hi, I don't think a spotify player is integrated in this skill. If you wish to play music on your raspberry pi you can do what I did and install raspotify on there: https://github.com/dtcooper/raspotify |
Thank you @mickenordin, that was it. The Pi is now showing up as a device and it does try to play the tracks, however there is no sound output to my speakers. I am using a USB DAC with external speakers so I think some tweaking of the output device is required. |
|
Hello, everyone, |
|
Hi @Frederic94220 Above in a comment made the 30th Oct I've provided some instructions. I'm going to try to get a bit more streamlined approach into the skill during next week. (Most is done, just trying to document things). It won't be perfect but a bit better than following instructions in an issue on github. |
|
I've now merged the change to allow local api keys, with a basic helper script and instructions in the readme. Still work to do before it's completely user friendly however. |
|
Do you mean the readme of the spotify skill? Cause I can't see a change there... |
|
Yes, the steps I've written are here: https://github.com/forslund/spotify-skill#creating-access-token I'd be happy to get feedback if there are things that are unclear, to improve it :) |
Alright, you want feedback @forslund, I hope you don't regret this ;D
I managed to run And it actually does look like the file |
|
Thanks, I must add a note that this hasn't been released to the mainline (there will currently be some conflicts with the Mark-1 install until the next release of core). Currently you need to ask Mycroft to install the beta version of the skill (or use the |
|
hello, good morning, sorry, when I try to configure my spotify account in mycroft, a page appears saying INVALID_CLIENT: Failed to get client, how can I fix it? |
|
Hi @JesusCendejas, sorry for the delay in answering. Currently you need to install the beta version of the skill, you should be able to say "Hey mycroft, install the beta version of the spotify skill". Then you need to follow the instructions from the readme here: https://github.com/forslund/spotify-skill#authorization Let me know if you get stuck some where and we'll try to improve the instructions |
|
Hey @forslund, after downloading the beta version of the skill and following the guide in README.md, I still get an error. After I put my username and password into the corresponding fields at account.mycroft.ai/skills, I get the following message: |
|
Where do you get that, is it the skill log or is it when running the auth script? Another thing that may be of interest, what platform is this on? |
|
auth.py finishes successfully, after that (according to README.md) one has to add the account into the skill settings at https://account.mycroft.ai/skills. This is the step where the setup fails. After saving the configuration and pressing the "Connect" button, I have my mycroft running in docker. |
|
Ok, something is off, after the update there should be no Connect button on the skills page. Can you verify that the skill starts successfully by either using the Also if you have several installs there may be tabs on the skill page with multiple versions of the spotify skill |
|
@forslund Thank you very much. The truth is that I was able to register the spotify account, however when I ask What Spotify devices are available? mycroft returns There are no Spotify devices available, just like when I say some command like Play Hello Nasty on Spotify it prints I'm not sure how to play Play Hello Nasty on Spotify, how can I fix it? good evening |
|
The problem may be that there is no spotify-connect enabled player set up? The skill is not a player on it's own, instead it uses the spotify-connect api to start playback on detected devices (they need to be logged in with user / password...see readme). It was developed with librespot and the Spotify desktop-client as reference devices. |
|
Hello @forslund I would be really greatful for any help |
|
Hi @Maxibraeu, the instructions here are a bit dated. please checkout the default branch (21.02) and follow the instructions in the readme.md here. Since you've switched branches back and forth the incorrect version of spotipy may be installed. So you might need to run something like Let me know how you get along with that and I'll try to help you further if you get stuck. |
|
Hi @forslund its me again,first thanks for your quick response. I tried to do the new installation but failed on following error while installing raspotify. but if I search for example libc6 there is no version 2.31 Thanks for help |
|
@Maxibraeu sorry for the late response. I've been away for a couple of days. Can you tell me what system you're running on? Assuming that it's the picroft you're using: It could be that Raspotify has switch to the latest Debian Bullseye as target for their build and the picroft is still based on the old Debian Buster. I shall test this and see if I can do a custom build and provide a repo for the picroft. |
|
@forslund you are completely right. I am using Picroft and it would be really nice if you could make a custom build and provide a repo. Thank you very much. |
|
@Maxibraeu sorry for the long response time. I haven't gotten around to creating a debian repo of my own but I checked my version and you can download the deb from this github tag: https://github.com/dtcooper/raspotify/releases/tag/0.31.3 My guess is that all 0.31.x releases will work. |
|
Hi @forslund thanks for you anwer, I installed your version of Raspotify and then found all files from your description , but when I was going on and then finaly tried to use the Skill there was an Error again wich looked like this: And when I do What he says I get the same Error. But I got an Email from Spotify that a new device has logged into my account Thaks for your Help. |
|
@forslund Its me again I saw that I used the wrong username and now its working thanks for all you help during the last weeks |

When I want to configure your Skill with my Spotify credentials I get an error page with the error: INVALID_CLIENT: Failed to get client. Am I doing something wrong?
The text was updated successfully, but these errors were encountered: