Upgrade Mopidy to version 3 #803
Comments
|
PR #804 has been merged. Please try Mopidy 3 by using |
|
This issue should be closed, when mopidy3 script is merged into default script |
|
I've just tried the installation and mentioned the following error: Currently, I'm not able to test sound, Spotify, ... since this is an RPi for testing. |
|
Yes, you're right that should be fixed. |
|
We need to add pip upgrade commands, in case the user already has an older version installed, see #759 (comment) |
|
I'd prefer requirements.txt files to pin versions and install those we know
exactly to work.
|
|
Good idea. GitHub would also create automatic pull requests, if any security issues appear for package versions used in requirements.txt. Should we just put all possible packages in one requirements.txt or differentiate between classic, Spotify and maybe other components and e.g. Gmusic? |
|
I'd use multiple specific ones, during install they can be all added to one
install command. `pip -f req-base.txt -f req-spotify.txt` etc
s-martin <[email protected]> schrieb am Sa., 29. Feb. 2020, 11:37:
… Good idea.
GitHub would also create automatic pull requests, if any security issues
appear for package versions used in requirements.txt.
Should we just put all possible packages in one requirements.txt or
differentiate between classic, Spotify and maybe other components and e.g.
Gmusic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#803?email_source=notifications&email_token=AAI7W6RFPMYRMMIJZ67MWZ3RFDSNJA5CNFSM4KZRGIOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENLWRHY#issuecomment-592930975>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI7W6XZCIUJTMS3RFKNKCLRFDSNJANCNFSM4KZRGIOA>
.
|
|
Hi @s-martin, |
|
Yes, but some local changes were accidentally mixed in. I'll make a new one. |
|
So to solve #607 I just have to do this at my Phoniebox currently used, right? |
|
this would re-install the whole stuff on your phoniebox and erase all media in the process. We would be glad if you could test it with a different sd-card abd a fresh buster installation. (just to be sure you can easily go back to your "working" setup afterwards) |
|
Yes, testing this would really help. Attention: please make Backups as this could delete your settings, RFID cards and music! |
|
Ok so fresh buster install via the automatic script and then run the above command, correct? Could try this in a few days. |
|
@Hamsert the above line IS the spotify installer script but with mopidy3 instead of mopidy2 |
Okay, so I install buster and then run above script and I should be good? |
|
Yes |
|
When I try it I get this result: |
Sorry, we merged the mopidy script last night into the regular installer script. Please use: |
|
I am going to test the script - I really want the phoniebox to run :) |
|
When I open Spotify from the Phoniebox website, I get the following errormessage: |
Can you provide a screenshot or logs? |
|
Sure, the log output is massive: pi@raspberrypi:~ $ journalctl -u mopidy Mar 08 12:47:29 raspberrypi systemd[1]: Starting Mopidy music server... Mar 08 12:47:29 raspberrypi systemd[1]: Starting Mopidy music server... |
|
Could you try again with so the output doesn’t get truncated at the end of the lines? |
|
pi@raspberrypi:~ $ journalctl -f -u mopidy |
|
I installed buster I tried Youtube Download and it's working so offline files working confirmed as well. |
|
Sweet, it works, thx! The webinterface feels way faster and also the connection to iris feels way better than the stretch version/mopidy&python 2. |
|
fixed in #847 |
|
So if I would like to install it again to a new sd card, how would the full fixed command look like? |
|
just merged those two PRs. |
|
Even after reinstalling everything (Dev. Script) I recieve the same Error Message. |
|
that may be the case, yes. Don't know why that might be, but its definitely a possibility. |
I upgraded to Mopidy 3 recently with the same client ID and secret and didn't have any issues. |
|
Hi, i've tested the phoniebox on my pi zero with mopidy and got the spotify connect problem. First everything went fine. Fast start, Local Playlist plays sound, spotify plays sound, NICE!. Afterwards i rebooted, in hope everything would start fine again, but now i have the following problem with starting of mpd, and of this nothing is working So two things are not ok:
not sure what todo
EDIT: Starting manualy brings up following error in /var/log/mpd/mpd.log Startupsound is fine ... so sound is working ... so what is the problem Any ideas? Best regards Marcus |
As Python 2 is dropped by more and more parts it makes sense to upgrade Mopidy for Spotify integration to version 3.
Mopidy provides an extensive
FAQ how to upgrade.
Important things to consider:
mopidy-iris has a bug jaedb/Iris#474 in the last version for python 2, see #759. So Python 3 and Mopidy 3 would work around this.
mopidy-gmusic Integration will also only work with python 3, see #741.
@ZyanKLee providee already a install script for Mopidy 3 https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/develop/scripts/installscripts/buster-install-mopidy3.sh but mostly untested.
I would work on this issue, but I don’t have a Spotify account, so other people would need to test this.
The text was updated successfully, but these errors were encountered: