Unexpected keyword argument 'uri' - Moped web interface not doing anything

General
1

Hey guys!

I’m running Raspbian stable on a Raspberry Pi 3. I’m tracking the Mopidy apt repo so we got a bump to 3.x now.

Edit: there was a stray Mopidy 2.0.1 Python install so I’ll report back once I have confirmation that wasn’t interfering.

I have reinstalled and reconfigured as per the installation instructions, but we’re not getting any sound. I’m seeing this error every time we try playing a stream through Moped:

2020-04-24 16:10:00,406 INFO [500:Core-7] pykka: Exception returned from Core (urn:uuid:959ecdd4-5d54-4622-a8de-bb4ab4a4957f) to caller:                      
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pykka/_actor.py", line 193, in _actor_loop                                                                             
    response = self._handle_receive(envelope.message)
  File "/usr/lib/python3/dist-packages/pykka/_actor.py", line 299, in _handle_receive                                                                         
    return callee(*message.args, **message.kwargs)
TypeError: add() got an unexpected keyword argument 'uri'
2020-04-24 16:10:06,883 INFO [500:Core-7] pykka: Exception returned from Core (urn:uuid:959ecdd4-5d54-4622-a8de-bb4ab4a4957f) to caller:                      
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pykka/_actor.py", line 193, in _actor_loop                                                                             
    response = self._handle_receive(envelope.message)
  File "/usr/lib/python3/dist-packages/pykka/_actor.py", line 299, in _handle_receive                                                                         
    return callee(*message.args, **message.kwargs)
TypeError: add() got an unexpected keyword argument 'uri'

Mopidy config:

[core]
cache_dir = /var/cache/mopidy
config_dir = /etc/mopidy
data_dir = /var/lib/mopidy

[audio]
output = alsasink

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

[http]
enabled = true
hostname = 10.0.0.60
port = 6680
zeroconf = Mopidy Bureau

[mpd]
hostname = 10.0.0.60

Package versions:

# apt policy mopidy
mopidy:
  Installed: 3.0.2-1
  Candidate: 3.0.2-1
  Version table:
 *** 3.0.2-1 500
        500 http://apt.mopidy.com buster/main armhf Packages
        100 /var/lib/dpkg/status
     2.2.2-1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages


# pip3 list
Package       Version  
------------- ---------
asn1crypto    0.24.0   
certifi       2018.8.24
chardet       3.0.4    
cryptography  2.6.1    
entrypoints   0.3      
idna          2.6      
keyring       17.1.1   
keyrings.alt  3.1.1
Mopidy-Moped  0.7.1    
Mopidy-TuneIn 1.0.0    
pip           18.1     
pycrypto      2.6.1    
PyGObject     3.30.4   
Pykka         2.0.2    
python-apt    1.8.4.1  
pyxdg         0.25     
requests      2.21.0   
SecretStorage 2.3.1    
setuptools    40.8.0   
six           1.12.0   
ssh-import-id 5.7      
tornado       6.0.3    
urllib3       1.24.1   
wheel         0.32.3
2

Moped hasn’t seen an update for a long time, it doesn’t look compatible with the Mopidy v3 API.

3

Thanks, I was afraid so… I’ve seen people wagering it wouldn’t play too nice with Python 3 either. Is there a good web interface alternative?

4

There’s a list of those we know are compatible at https://mopidy.com/ext/

1 Like
5

Thanks a lot! Will have a look at those!