hassio-addons/addon-mopidy

Mopidy - Home Assistant Community Add-ons

Home Assistant Community Add-on: Mopidy

Mopidy is an extensible music server.

About

Mopidy plays music from local disk, Youtube, Spotify, SoundCloud, Google Play Music, and more. You edit the playlist from any phone, tablet, or computer using a range of MPD and web clients.

Support

Got questions?

You have several options to get them answered:

• The Home Assistant Community Add-ons Discord chat server for add-on support and feature requests.
• The Home Assistant Discord chat server for general Home Assistant discussions and questions.
• The Home Assistant Community Forum.
• Join the Reddit subreddit in /r/homeassistant

You could also open an issue here GitHub.

Authors & contributors

The original setup of this repository is by Bram Mittendorff, Franck Nijhof and Robbert Müller.

For a full list of all authors and contributors, check the contributor's page.

License

MIT License

Copyright (c) 2019-2022 Bram Mittendorff, Franck Nijhof, Robbert Müller

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

addon-mopidy's Issues

Mopidy-Iris access from external SSL URL

Problem/Motivation

When accessing the mopidy web iris UI from an external secure (SSL) URL the system complains with a CORS access error.

Expected behavior

Access the Iris web module

Actual behavior

Can not connect with Iris when using external URL using mod_proxy.

Steps to reproduce

Accessing the mopidy iris UI with https://external.duckdns.org

Proposed changes

A workaround is manually add the external interface in http/allowed_origins settings

- name: http/allowed_origins
  value: 'external.duckdns.org:443'

A proper fix could be add the external URL in the config on boot

Update version and add snapserver

Problem/Motivation

Hi, I'd like to contribute a bit on this addon. Updating it to the latest iris and also I'd like to add snapserver to this addon.
I think adding snapserver to this addon would be a good addition, but would like to hear opinions.

Add-On not shown in store

Hi guys, I wanted to use/test your add-on. However, I couldn't find it in the official store on my hassio instance. It is also not listed in the official repository, or am I doing something completely wrong?

Thanks for your help and effort!

nginx version problems

Problem/Motivation

Cannot build addon docker

Actual behavior

Apt install fails with these 2 errors:

E: Version '1.14.2-2+deb10u1' for 'libnginx-mod-http-lua' was not found
E: Version '1.14.2-2+deb10u1' for 'nginx' was not found

Steps to reproduce

Either try to install under Supervisor local-addon, or do a docker build anywhere

Proposed changes

I don't know what should be the correct version for these, just tried apt install without version for these 2, and it succeeded.

Mopidy-Spotify extension is not running - you will not be able to play any Spotify tracks

Problem/Motivation

I was able to install modipy in my hassio, but I get the following error while setting up Spotify

Mopidy-Spotify extension is not running - you will not be able to play any Spotify tracks

Expected behavior

I should be able to connect to spotify

Actual behavior

Not connecting

Steps to reproduce

1. Install Modipy
2. configure python plugin Mopidy-Spotify
3. configure API tokens

YAML config example:"

python_packages:
  - Mopidy-Spotify
settings:
  - name: spotify/enabled
    value: "true"
  - name: file/enabled
    value: "true"
  - name: file/media_dirs
    value: /share/mopidy/media
  - name: spotify/client_id
    value: ********************************************
  - name: spotify/client_secret
    value: ********************************************=
system_packages: []

How can we properly configure this integration?

Add more extensions like spotify extension

Problem/Motivation

There are no mopidy addons/ extensions for mopidy available in this addon.

Expected behavior

I would like to play my spotify music via the mopidy addon into my snapcast players.

Actual behavior

I cant play it via spotify because the spotify extension is not running (because it is not available)

Steps to reproduce

Install and try to play spotify songs

white sound on iris browsing.

Want to use mopidy on mpd + alsasink on gentoo current on local browser SMSL AD18 usb FDA power amplifier.

browse iris open white sound on pulseaudio/pipewire. It's lock alsa direct output. So mpd output can't directly play to alsa because of pulseaudio/pipewire sound

alsasink direct output on mopidy + iris + local browser.
default pipewire/pulseaudio output need to be the same as alsasink.
don't do on home page, but pw access is visible on pw-top with clicking on "browse"

Remove browser pulseaudio/pw access on iris (problem doesn't not exist on other web extensions) or remove white sound playing.

Installing This addon on Raspberry PI 4B

It appears that this addon is not supported on raspi or any other arm based systems. It appears greayed out in the addon menu and there is no way i can find install it.

Is it possible, as i understand this is written in python, to change a config file in order to allow this addons install on pis or any other arm machine as they are very popular for running HA.

Mopidy "not compatible with the processor of your device or the operating system you have installed on your device"

Mopidy will not install on Core 2021-12-8 / Supervisor 2021.12.2

Error message is "This add-on is not compatible with the processor of your device or the operating system you have installed on your device."

Have added edge repository, and am trying to install. Cannot get any further than holding page, install is greyed out.

System log entry is
22-01-09 21:13:20 ERROR (MainThread) [supervisor.addons] Add-on 40817795_mopidy not supported on this platform

mopidy addon ingrees returns: 502: Bad Gateway

Problem/Motivation

is not working after update

Expected behavior

HA mopidy addon web shall be accessible via HA ingress

Actual behavior

Is not working, frame returns 502: Bad Gateway

I think issue could be here:

[cont-init.d] nginx.sh: executing... 
2021/01/25 21:26:27 invalid character '/' looking for beginning of value

 You are running the latest version of this add-on.
 System: Debian GNU/Linux 10 (buster)  (amd64 / intel-nuc)
 Home Assistant Core: 2021.1.5
 Home Assistant Supervisor: 2021.01.7
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] folders.sh: executing... 
[cont-init.d] folders.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
2021/01/25 21:26:27 invalid character '/' looking for beginning of value
[cont-init.d] nginx.sh: exited 1.
[cont-init.d] packages.sh: executing... 
[cont-init.d] packages.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[21:26:27] INFO: Starting Mopidy...
[21:26:27] INFO: Setting audio/output to audioresample ! audio/x-raw,rate=44000,channels=2,format=S16LE ! audioconvert ! wavenc ! filesink location=/share/snapcast/mopidy

Spotify addon not running

Problem/Motivation

WARNING 2022-11-17 10:24:07,201 [388:MainThread] mopidy.__main__ Found soundcloud configuration errors. The extension has been automatically disabled: WARNING 2022-11-17 10:24:07,201 [388:MainThread] mopidy.__main__ soundcloud/auth_token must be set. WARNING 2022-11-17 10:24:07,202 [388:MainThread] mopidy.__main__ Please fix the extension configuration errors or disable the extensions to silence these messages. ERROR 2022-11-17 10:24:07,214 [388: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/local/lib/python3.7/dist-packages/mopidy/__main__.py", line 129, in main extension.setup(registry) File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/__init__.py", line 49, in setup from mopidy_spotify.backend import SpotifyBackend File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/backend.py", line 8, in <module> import spotify File "/usr/local/lib/python3.7/dist-packages/spotify/__init__.py", line 95, in <module> from spotify.album import * # noqa File "/usr/local/lib/python3.7/dist-packages/spotify/album.py", line 380, in <module> @serialized SystemError: ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time) ERROR 2022-11-17 10:24:07,274 [388:MainThread] mopidy.__main__ Extension youtube failed during setup. This might have left the registry in a bad state. Traceback (most recent call last): File "/usr/local/lib/python3.7/dist-packages/mopidy/__main__.py", line 129, in main extension.setup(registry) File "/usr/local/lib/python3.7/dist-packages/mopidy_youtube/__init__.py", line 39, in setup from .backend import YouTubeBackend, YouTubeCoreListener File "/usr/local/lib/python3.7/dist-packages/mopidy_youtube/backend.py", line 10, in <module> from mopidy_youtube.apis import youtube_api, youtube_japi, youtube_music File "/usr/local/lib/python3.7/dist-packages/mopidy_youtube/apis/youtube_music.py", line 7, in <module> from ytmusicapi import YTMusic ModuleNotFoundError: No module named 'ytmusicapi'

Expected behavior

- name: spotify/enabled
  value: "true"
- name: spotify/username
  value: **********
- name: spotify/password
  value: ********
- name: spotify/client_id
  value: *************
- name: spotify/client_secret
  value: **********
- name: spotify/bitrate
  value: "320"

Actual behavior

Fail to start

latest addon version is not available at dockerhub hassioaddons/mopidy-amd64

Problem/Motivation

Can't ugrade Hassio addon to the latest one (based on mopidy 3.50.0). Tried also reinstall but only older version of addon (based on Mopidy 3.49.0) is available for install via Hassio addon store on amd64 arch

Expected behavior

Updated addon version (based on Mopidy 3.50.0) is available for install at Hassio addon store

Actual behavior

Latest addon update is not available via Hassio addon store

Steps to reproduce

Try to update Mopidy Hassio addon via addon store

Proposed solution

please rebuild amd64 docker container based on latest addon github code

20-07-15 11:24:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
20-07-15 11:24:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
20-07-15 11:24:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/synesthesiam/hassio-addons repository
20-07-15 11:24:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/raph2i/hassio-addons repository
20-07-15 11:24:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository-edge repository
20-07-15 11:24:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/agileek/hassio-addons repository
20-07-15 11:24:38 INFO (MainThread) [supervisor.store] Load add-ons from store: 122 all - 0 new - 0 remove
20-07-15 11:25:21 INFO (SyncWorker_22) [supervisor.docker.interface] Stop addon_40817795_mopidy application
20-07-15 11:25:23 INFO (SyncWorker_22) [supervisor.docker.interface] Clean addon_40817795_mopidy application
20-07-15 11:25:23 INFO (SyncWorker_22) [supervisor.docker.interface] Remove image hassioaddons/mopidy-amd64 with latest and 06fcfd1
20-07-15 11:25:24 INFO (MainThread) [supervisor.addons.addon] Remove add-on data folder /data/addons/data/40817795_mopidy
20-07-15 11:25:24 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for 40817795_mopidy
20-07-15 11:25:24 INFO (MainThread) [supervisor.addons] Add-on '40817795_mopidy' successfully removed
20-07-15 11:25:37 INFO (MainThread) [supervisor.addons] Create Home Assistant add-on data folder /data/addons/data/40817795_mopidy
20-07-15 11:25:37 INFO (SyncWorker_26) [supervisor.docker.interface] Pull image hassioaddons/mopidy-amd64 tag 06fcfd1.
20-07-15 11:26:08 INFO (MainThread) [supervisor.addons] Add-on '40817795_mopidy' successfully installed
20-07-15 11:26:24 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for 40817795_mopidy

GitHub

hassio-addons/repository

Home Assistant Community Add-ons. Contribute to hassio-addons/repository development by creating an account on GitHub.

GitHub

home-assistant/hassio-addons

➕ Docker add-ons for Home Assistant - home-assistant/hassio-addons

GitHub

synesthesiam/hassio-addons

My Hass.IO add-ons. Contribute to synesthesiam/hassio-addons development by creating an account on GitHub.

GitHub

raph2i/hassio-addons

some Hass.IO Addons. Contribute to raph2i/hassio-addons development by creating an account on GitHub.

GitHub

hassio-addons/repository-edge

EDGE - Home Assistant Community Add-ons. Contribute to hassio-addons/repository-edge development by creating an account on GitHub.

GitHub

agileek/hassio-addons

Contribute to agileek/hassio-addons development by creating an account on GitHub.

Addon not listed in Hassio?

Problem/Motivation

I found this addon via a google search, but in Hassio I cannot see the it under the community addons

Expected behavior

Mopidy listed under addons

Actual behavior

Not listed

Steps to reproduce

Open Hassio, go to addons and "add-on store". Check Community Hass.io Add-ons for Mopidy

Issue with Sound

Problem/Motivation

Trying to play mp3 audio file on HA. Not working as expected

Expected behavior

Clear Sound

Actual behavior

Sound is very distorted, chopping and non ending (continuous)

Steps to reproduce

HA installed on Win10 with VBox and vdi image

Proposed changes

Not sure. Any suggestions/changes appreciated to resolve this. This feature is very important to me for many different scenarios.
Thanks in advance.

Mopidy-Spotify extension is not running

Problem

Spotify extension seems to not be installed

Expected behavior

Spotify extension should get started with

- name: spotify/enabled
    value: 'true'

setting enabled.

Actual behavior

Getting Mopidy-Spotify extension is not running - you will not be able to play any Spotify tracks message in Settings->Spotify

Mopidy API on 6680 port

Problem/Motivation

Hi Frenck ! Thanks for this great addon, which works fine on my Intel NUC running HassOS.
I'm able to integrate it as media_player with the MPD integration (port 6600, as default), but I'm not able to reach the Mopidy API on the 6680 port.
I'd like the ability to reach the Mopidy API on the 6680 port in order to use this custom integration https://community.home-assistant.io/t/media-player-platform-for-mopidy/265836 which basically allows to browse the Mopidy library and display artworks in its media_player.

Expected behavior

I talked about it with the maker of the custom integration, who said that the Mopidy API port is needed, not the MPD one.

Actual behavior

Only the Mopidy MPD port is configurable in the HA Mopidy add-on configuration tab :

Steps to reproduce

Integration this https://github.com/bushvin/hass-integrations through HACS, and then not being able to integrate it :

Proposed changes

Being able to set a Mopidy API port in the HA Mopidy add-on configuration tab, which will allow the use of the custom integration.
Here are the latest messages about it on the dedicated custom integration thread : https://community.home-assistant.io/t/media-player-platform-for-mopidy/265836/161

Hope you'll consider it. :) anyway, thanks for reading !

HA integration: websocket/mpd?

This is not an issue, more a request to enable a form of integration of this mopidy-addon as an entity in home-assistant, either via mpd extension (which as far as I know is not included in this docker-image) or via websocket-api.
If I overlooked other possibilities, I am sorry to open this.

Situation:
Snapserver + Snapcast are installed as Addons from here and are setup to be seen in HA as mediaplayer entities.
Mopidy is installed from this repo and works like a charm.

I would like to issue mpd commands(or direct API queries) from my node-red flow to mopidy to start to play a certain URI at a certain time(Radio Alarm).
So having either the mpd extension added or the http port forwarded to the host system would make this a lot easier.

Right now my solution is to mute the speaker and leave Mopidy streaming the radio in silence through the night until the my node-red flow unmutes the speaker.

Again apologies if I overlooked a solution that is already available.

libffi error for spotify?

Problem/Motivation

Extension spotify failed during setup. This might have left the registry in a bad state.

Expected behavior

spotify module should load

Actual behavior

spotify module fails with error:
SystemError: ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time)

Steps to reproduce

Fresh install of HASSIO plugin mopidy

Proposed changes

Looks like libffi-dev is removed in dockerfile while still required?

Support for armv7

Hi,

I was using HA in a venv until now, with mopidy installed through regular debian packages. I just migrated to hassio but this addon does not seem to have anything but amd64 enabled, any reason for that or is it just that you don't have anything to test arm ?

I tried cloning the repo and adding the arch myself, but the build is failing with no explanation :

20-04-08 20:26:19 INFO (SyncWorker_4) [supervisor.docker.addon] Start build local/armv7-addon-mopidy:dev
20-04-08 20:26:28 ERROR (SyncWorker_4) [supervisor.docker.addon] Can't build local/armv7-addon-mopidy:dev: The command '/bin/bash -o pipefail -c apt-get update         && apt-get install -y --no-install-recommends         dirmngr=2.2.12-1+deb10u1         gpg-agent=2.2.12-1+deb10u1         gpg=2.2.12-1+deb10u1         libnginx-mod-http-lua=1.14.2-2+deb10u1         luarocks=2.4.2+dfsg-1         nginx=1.14.2-2+deb10u1         git=1:2.20.1-2+deb10u1         && curl -L https://apt.mopidy.com/mopidy.gpg | apt-key add -     && curl -L https://apt.mopidy.com/mopidy.list -o /etc/apt/sources.list.d/mopidy.list         && apt-get update         && apt-get install -y --no-install-recommends         libffi-dev=3.2.1-9         libxml2-dev=2.9.4+dfsg1-7+b3         libxslt1-dev=1.1.32-2.2~deb10u1         libasound2-dev=1.1.8-1         libspotify12=12.1.51-1         libspotify-dev=12.1.51-1         zlib1g-dev=1:1.2.11.dfsg-1         build-essential=12.6         python3-dev=3.7.3-1         python3-gi=3.30.4-1         python3-gst-1.0=1.14.4-1+b1         gstreamer1.0-alsa=1.14.4-2         gstreamer1.0-plugins-bad=1.14.4-1+b1         gstreamer1.0-plugins-good=1.14.4-1         gstreamer1.0-plugins-ugly=1.14.4-1         gstreamer1.0-pulseaudio=1.14.4-1         && luarocks install lua-resty-http 0.15-0         && curl https://bootstrap.pypa.io/get-pip.py | python3     && pip3 install --no-cache-dir -r /tmp/requirements.txt         && find /usr/local/lib/python3.7/ -type d -name tests -depth -exec rm -rf {} \;     && find /usr/local/lib/python3.7/ -type d -name test -depth -exec rm -rf {} \;     && find /usr/local/lib/python3.7/ -name __pycache__ -depth -exec rm -rf {} \;     && find /usr/local/lib/python3.7/ -name "*.pyc" -depth -exec rm -f {} \;         && apt-get purge -y --auto-remove         dirmngr         gpg-agent         gpg         git         libffi-dev         libxml2-dev         libxslt1-dev         zlib1g-dev         build-essential         gcc         python-dev         dpkg-dev         gcc-7         luarocks     && rm -fr         /var/{cache,log}/*         /var/lib/apt/lists/*         /root/.cache     && find /tmp/ -mindepth 1  -delete' returned a non-zero code: 127

I'll look into this tomorrow but any tips (like how to get the actual output from the command instead of just that error code) would be appreciated as I've never used hassio or docker before, thanks !

No Connection from Mopidy to Snapcast when using Hassio with SSL

I'm running my Hassio Instance with SSL. The Mopidy Addon works great so far but it was not possible to establish a connection to the snapcast server. Neither to the snapcast server on the same hassio instane or antoher instance in my LAN.

My other Instance (Debian Server) running without SSL, so i give it a try an disabled SSL for the hassio. After that, mopidy directly connected to the hassio snapcast server and the other snapcast server on my debian machine.

I'm not sure if it is just a Problem from the AddOn or a mopidy problem.
In a normal mopidy instance your not able to switch to ssl connection because iris is using the http extension where are no options to enabeld ssl.

So my question now: Is there a way to establish a connection between mopidy an snapcast with activated ssl for hassio?
Maybe with the ip from the docker snapcast container? Does anybody got that two Addons running in this way?

General Infos:
Mopidy Addon from this repo
Snapcast Server from this repo: https://github.com/raph2i/hassio-addons
HassOS 4.12 in a VM

Unable to connect to external Mopidy Instance with this plugin

Problem/Motivation

Setup:
HomeAssistant (with this plugin) is running on a vm in the basement (the local instance), and a raspberry with deconz and mopidy running in my living room (the remote instance).
I want to use this HA plugin to connect to the Mopidy instance on the Raspberry.

When entering host and port of the remote instance, the web socket connection opened by the plugin uses the wrong URL to connect to the external mopidy instance. Thus the plugin is unable to connect to remote mopidy instance.

Expected behavior

Websocket opened to ws://<host>:<port>/mopidy/ws/

Actual behavior

Websocket opened to ws://<host>:<port>/api/hassio_ingress/<hash>/mopidy/ws/

Steps to reproduce

• Install and activate this plugin in HomeAssistant
• Go to Settings / Server in the mopidy Dashboard
• Open the browser developer console (Network)
• Add a new server in the Server Settings (arbitrary third host/port)
• Click 'Switch to this server'
• Now check the outgoing webservice connection to ws://<host>:<port>/api/hassio_ingress/<hash>/mopidy/ws/
• Note: No second mopidy instance is required to check the correctness of the request url

Proposed changes

As far as I see:

• the request URL is rewritten by the internal nginx server somehow here [0,1]
• See below two excerpts from the Mopidy JS
• This seems necessary to use HomeAssistant Ingress feature to access the local instance.
• It should be either possible disable this rewriting for a specific host, or make sure, that the rewriting only happens when connecting to the local mopidy instance.

[0] https://github.com/hassio-addons/addon-mopidy/blob/main/mopidy/rootfs/etc/nginx/templates/ingress.gtpl#L14
[1] https://github.com/hassio-addons/addon-mopidy/blob/main/mopidy/rootfs/etc/nginx/templates/ingress.gtpl#L15

Except form JS in HASSIO Mopidy:
return e.webSocketUrl=e.webSocketUrl||t+n+"/api/hassio_ingress/<hash>/mopidy/ws"

the same excerpt from a standalone instance:
return e.webSocketUrl=e.webSocketUrl||t+n+"/mopidy/ws"

Finally, if this is not the HomeAssistant way, to Integrate an external mopidy instance, I would be happy about a hint on how to do this properly.

Kind regards,
Tom

Snapcast integration Disconnected

Problem/Motivation

Mopidy-Iris has integration with Snapcast, however from Settings I see the Snapserver is in a disconnected state

Expected behavior

When you provide the Snapcast server host and port (1780) Mopidy-Iris should connect.

Actual behavior

With a Snapcast docker container loaded in the Home Assistant host (using Portainer for example), the Snapcast server is accessible, however Mopidy-Iris is unable to discover the Snapcast server.

Steps to reproduce

In Portainer create a new stack with the following docker-compose config:

snapserver:
    image: "docker-registry/snapserver"
    ports:
        - "1704:1704"
        - "1705:1705"
        - "1780:1780"
    volumes:
        - fifo:/tmp/snapcast/

Snapserver container can be pulled from https://hub.docker.com/r/ivdata/snapserver or build your own from https://github.com/IVData/dockerfiles/tree/master/snapserver

access to Mopidy HTTP API

Problem/Motivation

While Mopidy/Iris could be managed by external (for example mobile) app via MPD interface, this is not optimal due to incomplete Mopidy MPD implementation. Therefore it would be great to have possibility to use Mopidy HTTP API control interface as well. (for example by Mopidy Mobile Android app). I tried to use Network configuration for Mopidy addon to map "Web interface" but I think it is IRIS interface, not Mopidy HTTP API.

Expected behavior

Be able to use Mopidy HTTP API interface which should be available/mapped to HA available IP.

Actual behavior

Could not use Mopidy HTTP API

Steps to reproduce

Try to control Mopidy via Android Mopidy Mobile app.

Proposed changes

• allow to configure port mapping from container to HA for Mopidy HTTP API
• allow to configure user/passwd for Mopidy HTTP API (from other than localhost IPs)

Not in Hass.io repo?

Hi,

Would like to install, but the repository https://github.com/hassio-addons/repository doesn't seem to provide mopidy?

How to install and integrate?

How to install and integrate in home assistent?

Mopidy Addon not available in the community repo

Problem/Motivation

This addon is not available in the community addon.

Expected behavior

Should be available.

Proposed changes

Please add a new instruction on how to install this addon. I can't find out how to install it.

installation

Problem/Motivation

Since the add-on is not available yet, how can it be installed shoudl someone want to try now before it is deemed to be stable ?

Also, is there a date when it is expected to be available ?

Exception Occurs Retreiving Tracks, Albums, etc. for Spotify within Mopidy (Iris).

Problem/Motivation

INFO     2020-11-26 02:25:24,568 [422:SpotifyBackend-7] mopidy_spotify.lookup
  Failed to lookup 'spotify:directory': Could not parse 'spotify:directory' as a Spotify URI
ERROR    2020-11-26 02:25:24,596 [422:Core-14] mopidy.core.library
  SpotifyBackend backend caused an exception.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/mopidy/core/library.py", line 17, in _backend_error_handling
    yield
  File "/usr/local/lib/python3.7/dist-packages/mopidy/core/library.py", line 181, in get_images
    if future.get() is None:
  File "/usr/local/lib/python3.7/dist-packages/pykka/_threading.py", line 45, in get
    _compat.reraise(*self._data['exc_info'])
  File "/usr/local/lib/python3.7/dist-packages/pykka/_compat/__init__.py", line 29, in reraise
    raise value
  File "/usr/local/lib/python3.7/dist-packages/pykka/_actor.py", line 193, in _actor_loop
    response = self._handle_receive(envelope.message)
  File "/usr/local/lib/python3.7/dist-packages/pykka/_actor.py", line 299, in _handle_receive
    return callee(*message.args, **message.kwargs)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/library.py", line 35, in get_images
    return images.get_images(self._backend._web_client, uris)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 23, in get_images
    uris = sorted((_parse_uri(u) for u in uris), key=uri_type_getter)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 23, in <genexpr>
    uris = sorted((_parse_uri(u) for u in uris), key=uri_type_getter)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 45, in _parse_uri
    uri_type, uri_id = parsed_uri.path.split(":")[:2]
ValueError: not enough values to unpack (expected 2, got 1)
INFO     2020-11-26 02:25:27,370 [422:SpotifyBackend-7] mopidy_spotify.lookup
  Failed to lookup 'spotify:your': Could not parse 'spotify:your' as a Spotify URI
ERROR    2020-11-26 02:25:27,405 [422:Core-14] mopidy.core.library
  SpotifyBackend backend caused an exception.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/mopidy/core/library.py", line 17, in _backend_error_handling
    yield
  File "/usr/local/lib/python3.7/dist-packages/mopidy/core/library.py", line 181, in get_images
    if future.get() is None:
  File "/usr/local/lib/python3.7/dist-packages/pykka/_threading.py", line 45, in get
    _compat.reraise(*self._data['exc_info'])
  File "/usr/local/lib/python3.7/dist-packages/pykka/_compat/__init__.py", line 29, in reraise
    raise value
  File "/usr/local/lib/python3.7/dist-packages/pykka/_actor.py", line 193, in _actor_loop
    response = self._handle_receive(envelope.message)
  File "/usr/local/lib/python3.7/dist-packages/pykka/_actor.py", line 299, in _handle_receive
    return callee(*message.args, **message.kwargs)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/library.py", line 35, in get_images
    return images.get_images(self._backend._web_client, uris)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 23, in get_images
    uris = sorted((_parse_uri(u) for u in uris), key=uri_type_getter)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 23, in <genexpr>
    uris = sorted((_parse_uri(u) for u in uris), key=uri_type_getter)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 59, in _parse_uri
    raise ValueError(f"Could not parse {repr(uri)} as a Spotify URI")
ValueError: Could not parse 'spotify:your:tracks' as a Spotify URI
INFO     2020-11-26 02:25:28,720 [422:SpotifyBackend-7] mopidy_spotify.lookup
  Failed to lookup 'spotify:your:tracks': Could not parse 'spotify:your:tracks' as a Spotify URI
ERROR    2020-11-26 02:25:31,266 [422:Core-14] mopidy.core.library
  SpotifyBackend backend caused an exception.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/mopidy/core/library.py", line 17, in _backend_error_handling
    yield
  File "/usr/local/lib/python3.7/dist-packages/mopidy/core/library.py", line 181, in get_images
    if future.get() is None:
  File "/usr/local/lib/python3.7/dist-packages/pykka/_threading.py", line 45, in get
    _compat.reraise(*self._data['exc_info'])
  File "/usr/local/lib/python3.7/dist-packages/pykka/_compat/__init__.py", line 29, in reraise
    raise value
  File "/usr/local/lib/python3.7/dist-packages/pykka/_actor.py", line 193, in _actor_loop
    response = self._handle_receive(envelope.message)
  File "/usr/local/lib/python3.7/dist-packages/pykka/_actor.py", line 299, in _handle_receive
    return callee(*message.args, **message.kwargs)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/library.py", line 35, in get_images
    return images.get_images(self._backend._web_client, uris)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 23, in get_images
    uris = sorted((_parse_uri(u) for u in uris), key=uri_type_getter)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 23, in <genexpr>
    uris = sorted((_parse_uri(u) for u in uris), key=uri_type_getter)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_spotify/images.py", line 45, in _parse_uri
    uri_type, uri_id = parsed_uri.path.split(":")[:2]
ValueError: not enough values to unpack (expected 2, got 1)

Expected behavior

Sqlite database/table may not exist. Empty records possibly?
Try/except handling in the event of an invalid data.

Actual behavior

Exception causes the webUI to not provide any usable data. Addon is useless.

Steps to reproduce

Valid Spotify account to test.

Proposed changes

See expected behavior. Would this need to be possibly pushed back as an issue against the Mopidy or Iris repos?

Any timeline for arm support?

Problem/Motivation

Most people run Hassio on Raspberry Pi's?

Expected behavior

I was hoping this would work as an addon in Hassio on a Raspberry Pi.

Actual behavior

It does not work on arm processors.

Steps to reproduce

It can not be installed on any arm based architecture cpu's.

Proposed changes

Please make it work on Raspberry Pi's
Many people would like this?

I saw that you closed the same issue almost a year ago.
Has anything gotten better?

Update edge repository

Problem/Motivation

Using edge repository, media folder is not mounted in instance. I checked the code and #198 is already merged fixing the issue

Expected behavior

lastest changes available to test

Actual behavior

latest version available is from March

Steps to reproduce

Configure /media as local media folder

After restart - playlist lost

Problem/Motivation

After restart mopidy addon, mopidy lost all playlists

Expected behavior

Persistence volume for playlists?

Actual behavior

No more playlists

Steps to reproduce

Install, start, add some URL to playlist and restart :)

Proposed changes

More details:
Mopidy Current version: 3c1b37e
core-2021.2.3
supervisor-2021.02.9
Home Assistant OS 5.11

Add Icecast2 port mapping

Problem/Motivation

When switching on the Icecast2 feature the url is not accessible due to the port not being exposed by the docker container.

Expected behavior

Expect the port to be configurable on supervisor.

Actual behavior

No port can be configured for Icecast when setting up the addon

Steps to reproduce

Navigate to Mopidy Iris UI, select settings. Select Icecast click enable the navigate to the specified URL

Proposed changes

Adding the mappable port in the Mopidy Configuration page. I would like to contribute more to the community, so it would be great to know where I can start after cloning the repo.

Can't start Mopidy (No such image: hassioaddons/mopidy-armv7:latest)

Problem/Motivation

I tried to use Mopidy, it seems like the install go thru but when I want to start it doesn't actually start. The Start button doesn't go away and the logs don't get filled at the bottom, even with a refresh.

Expected behavior

I excpected Mopidy to start and become available on the Ingress.

Actual behavior

Mopidy didn't start and when I looked in the logs of Mopidy there was nothing. And in the Hass.io > System I saw this line:
19-06-09 19:42:40 ERROR (SyncWorker_15) [hassio.docker] Can't create container from addon_40817795_mopidy: 404 Client Error: Not Found ("No such image: hassioaddons/mopidy-armv7:latest")

Steps to reproduce

I added the repository for the edge addons and used the interface as normal to install; not changed any settings and this happens.

Proposed changes

It seems like a image file is not available from the addons store. maybe due to the hassioaddons/mopidy not being hassio-addons. But I am not sure about that.

Specs:

Hostname | hassio
System | HassOS 2.12
Deployment | production
Version | 166
Latest version | 166
Raspberry Pi 3B(+) I believe.