Please help. No matter what I do i cannot get mopidy to see an extension :(

pallebone · January 12, 2020, 10:17pm

I have installed the extension using “sudo pip install Mopidy-Iris” 100% so its not only installed for my user acocunt, but when mopidy is run as a service, it does not find the extension. I have removed, reinstalled, retried everything i can think and followed multiple guided on this. I am so sad I cant seem to work out what has gone wrong no matter what I check.

Here is my system:
Ubuntu 20.04
Current Method of install on this attempt: Added apt source sudo wget -q -O /etc/apt/sources.list.d/mopidy.list https://apt.mopidy.com/buster.list
Then installed Mopidy via apt-get
Then sudo pip install Mopidy-Iris

This is the config file found in sudo nano /etc/mopidy/mopidy.conf
[http]
enabled = true
hostname = 192.168.3.21
port = 6680
zeroconf = Mopidy HTTP server on $hostname
allowed_origins =
csrf_protection = true
default_app = mopidy

[iris]
enabled = true

[spotify]
enabled = true
username = CORRECT USERNAME
password = CORRECT PASS
client_id = CORRECT ID
client_secret = CORRECT SECRET

[local]
data_dir = /var/lib/mopidy/local
media_dir = /var/lib/mopidy/media

[logging]
config_file = /etc/mopidy/logging.conf
debug_file = /var/log/mopidy/mopidy-debug.log

here is the output of
journalctl -u mopidy (name of server is Shinobi)

Jan 12 17:03:07 Shinobi mopidy[228852]: INFO Jan 12 17:03:07 Shinobi mopidy[228852]: INFO Jan 12 17:03:07 Shinobi systemd[1]: Jan 12 17:03:07 Shinobi mopidy[228852]: INFO Jan 12 17:03:07 Shinobi mopidy[228852]: INFO Jan 12 17:03:07 Shinobi mopidy[228852]: INFO Jan 12 17:03:07 Shinobi mopidy[228852]: INFO Jan 12 17:03:08 Shinobi systemd[1]: Jan 12 17:03:08 Shinobi systemd[1]: Jan 12 17:03:08 Shinobi systemd[1]: Jan 12 17:03:08 Shinobi systemd[1]: Jan 12 17:03:09 Shinobi mopidy[229482]: INFO Jan 12 17:03:09 Shinobi mopidy[229482]: INFO Jan 12 17:03:09 Shinobi mopidy[229482]: INFO Jan 12 17:03:09 Shinobi mopidy[229482]: INFO Jan 12 17:03:09 Shinobi mopidy[229482]: INFO Jan 12 17:03:09 Shinobi mopidy[229482]: ERROR Jan 12 17:03:09 Shinobi mopidy[229482]: INFO Jan 12 17:03:09 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: ERROR Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:10 Shinobi mopidy[229482]: INFO Jan 12 17:03:11 Shinobi mopidy[229482]: INFO [MainThread] mopidy.commands GLib mainloop got SIGTERM. Exiting…
[MainThread] mopidy.commands Stopping Mopidy frontends
Stopping Mopidy music server…
[MainThread] mopidy.commands Stopping Mopidy core
[MainThread] mopidy.commands Stopping Mopidy backends
[MainThread] mopidy.commands Stopping Mopidy audio
[MainThread] mopidy.commands Stopping Mopidy mixer
mopidy.service: Succeeded.
Stopped Mopidy music server.
Starting Mopidy music server…
Started Mopidy music server.
[MainThread] mopidy.main Starting Mopidy 3.0.1
[MainThread] mopidy.config Loading config from builtin defaults
[MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy.conf
[MainThread] mopidy.config Loading config from file:///etc/mopidy/mopidy.conf
[MainThread] mopidy.config Loading config from command line options
[MainThread] mopidy.internal.log Loading logging config ‘/etc/mopidy/logging.conf’ failed. ‘formatters’
[MainThread] mopidy.main Enabled extensions: softwaremixer, stream, http, m3u, file, mpd, spotify
[MainThread] mopidy.main Disabled extensions: none
[MainThread] mopidy.main Extension spotify failed during setup. This might have left the registry in a bad state.
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/mopidy/main.py”, line 129, in main
extension.setup(registry)
File “/usr/lib/python3/dist-packages/mopidy_spotify/init.py”, line 49, in setup
from mopidy_spotify.backend import SpotifyBackend
File “/usr/lib/python3/dist-packages/mopidy_spotify/backend.py”, line 9, in
from mopidy_spotify import Extension, library, playback, playlists, web
File “/usr/lib/python3/dist-packages/mopidy_spotify/library.py”, line 5, in
from mopidy_spotify import browse, distinct, images, lookup, search
File “/usr/lib/python3/dist-packages/mopidy_spotify/browse.py”, line 38, in
“albums”: spotify.ToplistType.ALBUMS,
AttributeError: module ‘spotify’ has no attribute ‘ToplistType’
[MainThread] mopidy.commands Starting Mopidy mixer: SoftwareMixer
[MainThread] mopidy.commands Starting Mopidy audio
[MainThread] mopidy.commands Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend
[MainThread] mopidy.commands Starting Mopidy core
[MainThread] mopidy.commands Starting Mopidy frontends: HttpFrontend, MpdFrontend
[HttpFrontend-8] mopidy.http.actor HTTP server running at [::ffff:192.168.3.21]:6680
[MainThread] mopidy_mpd.actor MPD server running at [::ffff:127.0.0.1]:6600
[MainThread] mopidy.commands Starting GLib mainloop
[Audio-2] mopidy.audio.actor Audio output set to “autoaudiosink”

Here is the service status:
sudo systemctl status mopidy
● mopidy.service - Mopidy music server
Loaded: loaded (/lib/systemd/system/mopidy.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-01-12 17:03:08 EST; 12min ago
Process: 229469 ExecStartPre=/bin/mkdir -p /var/cache/mopidy (code=exited, status=0/SUCCESS)
Process: 229471 ExecStartPre=/bin/chown mopidy:audio /var/cache/mopidy (code=exited, status=0/SUCCESS)
Main PID: 229482 (mopidy)
Tasks: 11 (limit: 6900)
Memory: 47.0M
CGroup: /system.slice/mopidy.service
└─229482 /usr/bin/python3 /usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf

Jan 12 17:03:10 Shinobi mopidy[229482]: AttributeError: module ‘spotify’ has no attribute ‘ToplistType’
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [MainThread] mopidy.commands Starting Mopidy mixer: SoftwareMixer
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [MainThread] mopidy.commands Starting Mopidy audio
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [MainThread] mopidy.commands Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [MainThread] mopidy.commands Starting Mopidy core
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [MainThread] mopidy.commands Starting Mopidy frontends: HttpFrontend, MpdFrontend
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [HttpFrontend-8] mopidy.http.actor HTTP server running at [::ffff:192.168.3.21]:6680
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [MainThread] mopidy_mpd.actor MPD server running at [::ffff:127.0.0.1]:6600
Jan 12 17:03:10 Shinobi mopidy[229482]: INFO [MainThread] mopidy.commands Starting GLib mainloop
Jan 12 17:03:11 Shinobi mopidy[229482]: INFO [Audio-2] mopidy.audio.actor Audio output set to “autoaudiosink”

What did I do wrong??? I am at such a loss Sorry and thanks in advance for any assistance at all.

Pete

(relevant section if you missed it):
Jan 12 17:03:09 Shinobi mopidy[229482]: INFO [MainThread] mopidy. main Enabled extensions: softwaremixer, stream, http, m3u, file, mpd, spotify

Note: Iris is missing.

kingosticks · January 12, 2020, 10:50pm

You’ve done everything right except that Mopidy-Iris is not yet compatible with Python 3 and thus can’t be used with Mopidy v3.x.

Use https://mopidy.com/ext/ for an overview of which extensions are Python 3 compatible.

pallebone · January 13, 2020, 1:06pm

@kingosticks

Many thanks for your prompt reply. This is very helpful information, thank you. I will go and try find out if there is any work in progress on this so I can at least help test if there is any release if nothing else. Thank you for your time, it was appreciated
Pete

kingosticks · January 13, 2020, 2:10pm

There is a Python 3 branch and an issue at https://github.com/jaedb/Iris/issues/356. Some of the work is done, I think jaedb might just be a little busy right now.