RPi-Jukebox-RFID
RPi-Jukebox-RFID copied to clipboard
π | Spotify does not work anymore
Bug
What I did
My Working Phoniebox stops working since today. Spotify integration does not work. only local playback works
I Changed nothing. Works weeks before like a charm. Spotify Premium is Valid
What happened
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.__main__ Starting Mopidy 3.2.0
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.config Loading config from builtin defaults
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy-local.conf
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy.conf
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.config Loading config from file:///etc/mopidy/mopidy.conf
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.config Loading config from command line options
May 16 19:46:47 phoniebox mopidy[2207]: ERROR [MainThread] mopidy.internal.log Loading logging config '/etc/mopidy/logging.conf' failed. 'formatters'
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.__main__ Enabled extensions: local, spotify, file, mpd, iris, m3u, stream, softwaremixer, http
May 16 19:46:47 phoniebox mopidy[2207]: INFO [MainThread] mopidy.__main__ Disabled extensions: none
May 16 19:46:48 phoniebox mopidy[2207]: INFO [MainThread] mopidy.commands Starting Mopidy mixer: SoftwareMixer
May 16 19:46:48 phoniebox mopidy[2207]: INFO [MainThread] mopidy.commands Mixer volume set to 30
May 16 19:46:48 phoniebox mopidy[2207]: INFO [MainThread] mopidy.commands Starting Mopidy audio
May 16 19:46:48 phoniebox mopidy[2207]: INFO [MainThread] mopidy.commands Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend, SpotifyBackend, LocalBackend
May 16 19:46:49 phoniebox mopidy[2207]: INFO [Audio-2] mopidy.audio.actor Audio output set to "alsasink"
May 16 19:46:49 phoniebox mopidy[2207]: ERROR [SpotifyEventLoop] spotify.session Spotify login error: <ErrorType.USER_NEEDS_PREMIUM: 15>
May 16 19:46:49 phoniebox mopidy[2207]: INFO [SpotifyBackend-6] mopidy_spotify.web Logged into Spotify Web API as XXXXXXXXXX
May 16 19:46:49 phoniebox mopidy[2207]: INFO [MainThread] mopidy.commands Starting Mopidy core
May 16 19:46:49 phoniebox mopidy[2207]: INFO [MainThread] mopidy.commands Starting Mopidy frontends: IrisFrontend, HttpFrontend, MpdFrontend
May 16 19:46:49 phoniebox mopidy[2207]: INFO [IrisFrontend-11] mopidy_iris.core Starting Iris 3.54.2
May 16 19:46:49 phoniebox mopidy[2207]: INFO [HttpFrontend-13] mopidy.http.actor HTTP server running at [0.0.0.0]:6680
May 16 19:46:49 phoniebox mopidy[2207]: INFO [MainThread] mopidy_mpd.actor MPD server running at [0.0.0.0]:6600
May 16 19:46:49 phoniebox mopidy[2207]: INFO [MainThread] mopidy.commands Starting GLib mainloop
May 16 19:49:29 phoniebox mopidy[2207]: INFO [MpdSession-278] mopidy_mpd.session New MPD connection from [127.0.0.1]:34620
May 16 19:49:29 phoniebox mopidy[2207]: INFO [SpotifyBackend-6] mopidy_spotify.lookup Failed to lookup 'spotify:album:0XXX': Session must be logged in and online to load objects: <ConnectionState.LOGGED_O
May 16 19:49:29 phoniebox mopidy[2207]: INFO [MpdSession-279] mopidy_mpd.session New MPD connection from [127.0.0.1]:34622
I think its a problem an is described here -> ? https://github.com/mopidy/mopidy-spotify
"As promised last month, Spotify disabled access to libspotify on 16/05/2022. As of today, seven years after libspotify was deprecated, there is still no official replacement library available."
I think this is a major problem for every Phonebox/Spotify version
Thanks for reporting this.
Looks like this is a real showstopper, we need to look into that.
Holy shite, yes please prioritized this, I think this breaks every other phoniebox out there (including mine :/)
Can confirm. We have 2 Phonieboxes for our children and both stopped playing spotify over night.
Confirmed by 5 boxes and 5 sad children. There will be no quick way around it. We all hoped that day would never come, but it finally has come and there is not much one can do as long as spotify does not reconsider its decision. At least the non-spotify part is still working.
Holy shite, yes please prioritized this, I think this breaks every other phoniebox out there (including mine :/)
Unfortunately I donβt think that there will be quick a solution to this, because Spotify disabled the support of libspotify.
The people from mopidy-spotify (which Phoniebox relies on) are currently working on solutions (see https://github.com/mopidy/mopidy-spotify/issues/110#issuecomment-1129917534), but no idea, when a solution will be available.
@MiczFlor
Is it out of the question to use another API or SDK for Spotify on Phoniebox? It's really depressing to lose that unique selling point. I didn't see it coming, either.
Is it out of the question to use another API or SDK for Spotify on Phoniebox? It's really depressing to lose that unique selling point. I didn't see it coming, either.
See https://github.com/MiczFlor/RPi-Jukebox-RFID/issues/1815#issuecomment-1130384442
Same here spotify is not working anymore. Is there any alternative API or SDK to replace mopidy?
whats about this: https://lib.rs/crates/gst-plugin-spotify (found here https://github.com/mopidy/mopidy-spotify/issues/110#issuecomment-1129917534)
^that might work, see how to install https://qengineering.eu/install-gstreamer-1.18-on-raspberry-pi-4.html ( I hadn't found time to try ;( )
Same here spotify is not working anymore. Is there any alternative API or SDK to replace mopidy?
whats about this: https://lib.rs/crates/gst-plugin-spotify (found here mopidy/mopidy-spotify#110 (comment))
Current implementation relies on mopidy in the Spotify edition (also for non Spotify functions), so from my point of view we should wait for an update of mopidy-spotify. Hopefully this would be only an update of mopidy-spotify.
But if anyone comes up with a different solution and proposes a PR, we could also check if this is the way we want to go.
As we are currently working on a new and shiny version 3 we need to check the implications in https://github.com/MiczFlor/RPi-Jukebox-RFID/tree/future3/spotify as well.
@pabera @ChisSoc @Groovylein @MiczFlor
As we are currently working on a new and shiny version 3 we need to check the implications in https://github.com/MiczFlor/RPi-Jukebox-RFID/tree/future3/spotify as well.
^^I've seen there is already alottah python inside, this might be handsome, I'll try...
https://pypi.org/project/spotify/
As we are currently working on a new and shiny version 3 we need to check the implications in https://github.com/MiczFlor/RPi-Jukebox-RFID/tree/future3/spotify as well.
I've tested the development environment for Spotify yesterday and it works π€ We are using https://github.com/librespot-org/librespot-java, which is using the Spotify Web-API
As we are currently working on a new and shiny version 3 we need to check the implications in https://github.com/MiczFlor/RPi-Jukebox-RFID/tree/future3/spotify as well.
I've tested the development environment for Spotify yesterday and it works π€ We are using https://github.com/librespot-org/librespot-java, which is using the Spotify Web-API
yeah, would be so nice to have a kind of working version, so guys can swtich to future 3 ;)
Hey Guys, that would be so so so awesome if you would be able to find an alternative solution! You would be a star for so many Kids and Dads! :-)
I'm to stupid for active coding contribution. It would be awesome to get an alternative for my son. We both created a huge amount of cards with his favorite audiobooks. Therefore it would be great if you professionals find a way to solve the problem.
As we are currently working on a new and shiny version 3 we need to check the implications in https://github.com/MiczFlor/RPi-Jukebox-RFID/tree/future3/spotify as well.
I've tested the development environment for Spotify yesterday and it works π€ We are using https://github.com/librespot-org/librespot-java, which is using the Spotify Web-API
How mature is the future3/spotify branch? Can it be merged and released yet?
How mature is the future3/spotify branch? Can it be merged and released yet?
Unfortunately it isn't stable at all. The player management and the whole WebApps are not ready for Spotify yet.
Can we get a merge of future3/dev and spotify? Even if not stable and no web-app, i guess you will get a lot of testers :-)
Just came to the discussions to find out, why my daughter's Phoniebox stopped working. And now - oh my, what a catastrophe π₯, our Phoniebox is entirely based on Spotify, I made over 50 cards. Hopefully, it will work again in Future, shame on Spotify to just cut the access.
This was quite shocking news so I thought about alternatives out of desperation: I have an LMS SqueezeboxServer server on another Raspberry Pi (with working Spotify support), so I installed piCorePlayer on my Phoniebox to use it as an LMS Squeezebox Client, and wrote a script to use RFID tags for starting Spotify playlists.
Of course, this is not supposed to be a replacement for Phoniebox, just a quick and dirty fix to get Spotify working again quickly. I hope you find a better solution soon! Until then, if someone is desperate enough to try it out, the script and instructions are here https://github.com/maahn/piCorePhonie
wrote a script to use RFID tags for starting Spotify playlists.
nice!! I'm on a just python script, back to basics, I started yesterday, reading the usb rfid number works, have less time but will be ready hopefully soon
A few words about the future3/spotify branch: This is not just adding Spotify. This branch massively changes (and improves) the way the Jukebox interfaces with the backend players. Previously there has only been one: MPD, and now there need to be multiple. So even future3/develop and future3/spotify are not compatible at the moment and need to be merged, which is a bit of work.
hmm here are some thoughts from my side: Instead of trying to create an Eierlegende Wollmilchsau, maybe be should take a step back and aim for a simple back-to-the-roots version: A codebase that allows playing of spotify based on RFID cards.
oh deer ;) it kind of works, but not really ;) daughter is happy I converted her box to a just Spotiy Connect Client with raspotify she's using her laptop to start an album and closes it after it's playing through the pi -> audio jack -> partybox works flawless since 2 days ;) ... she's old enough to get in touch to the whole spotify world...
for her little brother -> rfid cards kind of work ... see the gist, feel free to do any better ;) I'm not a soo experienced python guy ... https://gist.github.com/sonicdee/bf5f655669ef6900b72c54f0c7696d32 it's using raspotify also, and spotipy to control it, but I'm running in an issue the raspotify device is not active on next day, so it can't be controlled anymore ;( ^^ maybe it can be done all inside librespot better !?
I stuck on this device loosing problem - reboot seems to work ^^ I'm investigating these days, when it works I'll load it to github with better docs...
also haven't figured out how to use py asyncio, but using screen with crontab to start both - works also ;) .. you need to start gpio and Rfspoty side by side also -> sudo is needed for usb rfid, can't find the right stuff to change udev rules...
https://www.heise.de/news/Abgeschaltet-libspotify-Aus-legt-selbstgebastelte-Musikboxen-fuer-Kinder-lahm-7124231.html
After getting an glimpse overview of why Spotify stopped working, I quit my Premium subscription right away (as this was the only reason to have a subscription in the first place). I cannot imagine that they will revive this API β ever. Guess this is expected to happen if you have the monopoly on audio-streaming?!
Has anyone got their box working with providers other than Spotify?
I'll stick with spotify and converted all my stuff to mp3. Slightly more effort but it works even offline.
I switched to MuPiBox and bought touchscreens as adviced... but it only worked one time to play spotify. Now I have a problem.. I hope it will be solved
@oswaldo-be Could you please share more of your migration experiences with MuPiBox ? Given the time frame of a possible fix for Phoniebox I guess it's a viable alternative to many of us, as sad as it is.