-
Notifications
You must be signed in to change notification settings - Fork 401
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
🐛 | Mopidy dies after receiving wrong Spotify links #1153
Comments
So to clarify: Did I understand that correctly ? |
I noticed that the Spotify link format should be This works until I use a http-link. After reboot, spotify:album:XXX will work again. |
I don't know, if there was an intention to support the http links or if this is possible (I don't use Spotify myself) |
From my point of view someone who is using Spotify edition or has in depth experience could investigate, if using the URLs directly could be implemented. Until know this use case wasn't considered. |
I've experienced the same issue. I think what happens is: However, the bad link is still there. So whenever you swipe that same card, it will crash mopidy again. The solution I found is to delete the card, delete the playlist from the Phoniebox and delete the folder for the playlist from the Phoniebox. Then register the card again with the correct spotify link in the form of spotify:playlist:XXXX. This got the playlist working. Hope it helps! |
This is great, thank you very much! |
Bug
What I did
I installed the raspberry pi with above mentioned buster image and ran the installer script including spotify
What happened
Startup sound is coming, but after sending wrong link to mopidy, no sounds from spotify streams (RFID swipe and web interface) are played
I expected this to happen
play correct links as usual.
Optional: handle wrong formatted links and eventually post some hint for the user or internally convert http link
Further information that might help
I edited my post to be more clear about the situation
Procedure to generate error:
Set new cardID with http link:
https://open.spotify.com/album/0Lya0qWV4qfHVArhaXYSju
Swipe card or play through web interface
In /var/log/syslog there is an mopidy error shown:
After this happening, an additional swipe of some other card or playing through web interface does not produce any sound. Error message in syslog is the same.
e.g.: spotify:album:0Lya0qWV4qfHVArhaXYSju
Raspberry has to be rebooted to be able to play links like
spotify:album:0Lya0qWV4qfHVArhaXYSju
again.
Here I put my first post for reference:
I had a lot of trouble getting the spotify streams running. Same issue as decribed here https://github.com/natumbri/mopidy-youtube/issues/58 or here https://github.com/MiczFlor/RPi-Jukebox-RFID/issues/1067
I got it running by going through this procedure: https://forum-raspberrypi.de/forum/thread/48179-phoniebox-spotify-ich-bekomme-es-nicht-zum-laufen/
I think the main difference from what I did is that I installed the raspian packages for the desktop environment (because I thought that I will not need them on the headles raspberry) However, it seems that there are some drivers hidden which are needed to get Spotify streams running.
EDIT: perhaps it turns out that I somehow got mopidy in troubles.
After going through the mentioned procedure I put in a spotify link (with add new card):
https://open.spotify.com/album/0Lya0qWV4qfHVArhaXYSju
Actually, I still do not know which format a Spotify link must have; it would be most convenient to just copy from spotify web page. However, using this link leads to such error message:
After this happened, all other links to spotify just did not play and produced this error message. Only after reboot, a spotify link such as
spotify:album:0Lya0qWV4qfHVArhaXYSju
did play the musik.
Perhaps it would be possible to convert http links or fetch them from executing.
This is my first bug report so please tell me if I can provide more information.
Software
Base image and version
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Branch / Release
master
Installscript
scripts/installscripts/buster-install-default.sh
Hardware
RaspberryPi version
Raspberry Pi Model B Plus Rev 1.2
RFID Reader
MFRC522
Soundcard
Headphones
Other notable hardware
no GPIO
The text was updated successfully, but these errors were encountered: