-
Notifications
You must be signed in to change notification settings - Fork 111
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
New Playlists not Discovered #127
Comments
I have the same problem only I just reinstalled mopidy and mopify-spotify so nothing shows up for me. |
I was gonna try uninstalling and reinstalling, but now that you've said that... Really hope this gets addressed soon. |
I have the same Issue with the Discover Weekly playlist. I've noticed that the user referenced in the spotify uri changed from
Other playlists by the same |
People have been reporting this on other playlists too, including their own. It's looking like Spotify have changed/broken something at their end. If you enable a more verbose log level (-vvvv) you should see one or more "ChannelError(4, 1, playlist)" type messages. There is not much we can do to address this while we continue to use libspotify/pyspotify for our playlist information. This is another reason why we need to move over more things to use the Spotify WebAPI instead. |
Hey all, not sure what happened, but when I checked on my playlists this morning, all the new ones I created last week are now appearing. Looks like they're all loaded properly, but I didn't notice any big changes to my system. The most recent changes to my system was an update to I do notice that Discover Weekly still isn't showing up in my playlists, but that's been an issue for a while now. Can anyone else confirm? |
Nice, the playlists I got a timeout on is now working again for me too. My guess is that there was a problem with the libspotify servers that has now been fixed.
This hasn't changed for me either. I have the discover weekly playlist on one of my machines, but with the wrong tracks, and I don't have it on another of my machines. |
Hi, same problem for me since january -> Playlist "discover weekly" not ok. Any solution with that user issue (Failed to lookup "spotify:user:spotify:playlist:) ? I liked very much the spotify's playlist "discover weekly" :-( |
"Discover Weekly", "Release Radar" and any other special playlists owned by the Spotify user no longer work with Spotify's libspotify library as discussed in #122. This is their doing and unfortunately they show absolutely no interest in fixing it (see #110). But we will be able to work around the problem as part of #130. I'm closing this since whatever was wrong with regular user playlists was a temporary issue with the Spotify servers. |
@kingosticks is there any progress on merging mopidy-spotify-web? Tried again today (after 1y off) and still don't see |
@ikcalB He has indeed been working on his fork on the following branch: https://github.com/kingosticks/mopidy-spotify/tree/fix/web-api-playlists-v2 Haven't tried it yet, but looks like it works from the commit messages :) Edit: Just tried, you can't browse the songs inside the playlists yet, but you can load the entire thing into the mpd playlist! Works like a charm. Thanks, @kingosticks |
@kenogo am trying that branch right now: At least in GMPC seemingly nothing changed. Still can only see Which client do you use? EDIT: Can see them in category 'Playlists' though. Is that intended? I'd rather like to see the playlists in the spotify treeview too (as I do have lots of old m3u playlists) |
For the last few weeks, I noticed that the Discover Weekly playlist was missing from my list of playlists in ncmpcpp. This was annoying but I figured there might have been a change to how Discover Weekly presents itself, and I lived with it.
Last night, I created a few new playlists, and noticed that they are not showing up in my list of available playlists.
I am currently running mopidy v2.1.0 and mopidy-spotify v3.0.0
Here is my current config, located in
/etc/mopidy/mopidy.conf
:The text was updated successfully, but these errors were encountered: