The webgui extension is visible nowhere within the default mopidy gui or by going to the musicbox_webclient/ url extention directly.
CONTEXT:
I have just installed the musicbox on ubuntu 19.10 Server (on a raspberry pi 4 device)… sudo python3 -m pip install Mopidy-MusicBox-Webclient
I have made sure that the following… [musicbox_webclient] enabled = true musicbox = false websocket_host = websocket_port = on_track_click = PLAY_ALL
… is in the conf files
the one under ~/.config/mopidy
and the one under /etc/mopidy
I can successfully run mopidy and view it on any device in my local network /usr/lib/python2.7/dist-packages/mopidy/ext.py:202: PkgResourcesDeprecationWarning: Parameters to load are deprecated. Call .resolve and .require separately. extension_class = entry_point.load(require=False) INFO Starting Mopidy 2.2.3 INFO Loading config from builtin defaults INFO Loading config from /home/ubuntu/.config/mopidy/mopidy.conf INFO Loading config from command line options INFO Enabled extensions: mpd, http, stream, m3u, softwaremixer, file, local, soundcloud INFO Disabled extensions: none INFO Starting Mopidy mixer: SoftwareMixer INFO Starting Mopidy audio INFO Starting Mopidy backends: StreamBackend, M3UBackend, FileBackend, LocalBackend, SoundCloudBackend INFO Audio output set to “autoaudiosink” INFO Loaded 5865 local tracks using json INFO Logged in to SoundCloud as “Emo No Rio” INFO Starting Mopidy core INFO Starting Mopidy frontends: MpdFrontend, HttpFrontend INFO MPD server running at [::]:6600 INFO HTTP server running at [::]:6680 INFO Starting GLib mainloop
However, the webgui extension is visible nowhere within the default mopidy gui or by going to the musicbox_webclient/ url extention directly (as seen below).
Install the latest 3.x version of Mopidy from apt.mopidy.com by following the instructions in our document at https://docs.mopidy.com/en/latest/installation/debian/. That version is a Python 3 compatible release and will work with the Python 3 version of Mopidy-Musicbox-webclient you have installed.
You are currently running Mopidy v2.2.3, that’s an old Python 2 version, perhaps installed from the Ubuntu software repositories? That version only works with Python 2 versions of extensions. None of the Python 2 versions will see any updates. You probably don’t want that.
I have gotten around to installing a mopidy once again with a fresh ubuntu 18.04.4 on raspberry pi 4 following the exact instructions indicated, as you listed above.
I then installed musicbox and soundcloud as indicated in their respective pages.
Any mopidy command, however, brings up the following: ERROR: Mopidy requires Python 2.7, but found 3.6.9.
I have tried what was indicated in these pages, but to no avail
Any idea at all what can be done here? Any advice would be much appreciated. Thanks!
I am back at ground zero (ubuntu 19.10)
However, following the standard instructions outlined here installs v2.3.2 by default. I haven’t found a way to install 3.0.2…
Might it have to do with what version of python is being detected? I have 2 and 3 installed:
ubuntu@ubuntu:~/.config/mopidy$ ls -la /usr/bin/python
lrwxrwxrwx 1 root root 7 Oct 10 11:32 /usr/bin/python -> python2
ls -la /usr/bin/python2
lrwxrwxrwx 1 root root 9 Oct 10 11:32 /usr/bin/python2 -> python2.7
ls -la /usr/bin/python3
lrwxrwxrwx 1 root root 9 Oct 2 2019 /usr/bin/python3 -> python3.7
Nope, python 2 and 3 installed is normal, it’s fine. The instructions are definitely correct. You need to make sure you are using apt.mopidy.com. Installing that old versions is exactly what happens if you do not use apt.mopidy.com
Hi there and thanks for the quick response(s).
Excuse me if I am missing something completely obvious here, but I am still unable to figure this out. Please excuse my computational noobness
This is what I’m doing, as instructed in the instructions you cited:
ubuntu@ubuntu:~$ wget -q -O - https://apt.mopidy.com/mopidy.gpg | sudo apt-key add -
OK
ubuntu@ubuntu:~$ sudo wget -q -O /etc/apt/sources.list.d/mopidy.list https://apt.mopidy.com/buster.list
ubuntu@ubuntu:~$ sudo apt update
Hit:1 https://apt.mopidy.com buster InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports eoan InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports eoan-updates InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports eoan-backports InRelease
Hit:5 http://ports.ubuntu.com/ubuntu-ports eoan-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'contrib/binary-arm64/Packages' as repository 'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'non-free/binary-arm64/Packages' as repository 'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'
There seems to be something going wrong here : 'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'
Does this have to do with this being a raspberry pi? Anyway, it’s clearly impacting the install i.e. the version that gets installed is still 2.3.2…
Ohhh. I am sorry. I lost the details of what you were doing along the way and forgot this was all on a raspberry pi. Even though you said it in a couple of your posts. We don’t provide 64bit arm binaries it seems. Not sure what it would take for us to do that.
You’ll have to go down the installing from source route in the docs, and that should work! Again, apologies for missing that.
