upmpdcli Tidal plugin

[GioF_71]

I must have misunderstood you because I thought this new solution was already ready.

It is ready. I use it every day.
What I was saying is that it's not integrated in Moode's GUI.
But you still can play to moode from this media server

Our build and deb packages for upmpdcli and related plugins use the official tagged release from the maintainers Git repo and at least as of this post the latest tagged release is 1.8.16.
https://framagit.org/medoc92/upmpdcli/-/tags

When 1.9.0 is a tagged release we'll build the packages and include the update in moode :-)

@Snoil 

I had only a few moments this morning to follow up on your question.

First, I should have read your post more carefully. My step 1 is still necessary.

In principle, step 2 is not necessary because Tim bumped the version of upmpdcli built into moOde 9.1.0---but read on.

I just tried repeating only step 1 and steps 3-5 on a fresh moOde 9.1.0 install and discovered a couple of missing bits.

1. It turns out there is no /var/cache/upmpdcli directory in moOde as distributed. Conveniently, it gets created the first time a user enables the UPnP renderer (with owner/group upmpdcli:root).

I didn't notice that before because I was already experimenting with the Qobuz plugin so the directory was already present when I took up Tidal.

Solution: just enable the UPnP renderer if the directory doesn't exist yet.

2, Executing step 3 creates a new directory /var/cache/upmpdcli/tidal containing the file pkce.credentials.json, both with owner:group root:root). This ownership causes troubles, such as your UPnP Control Point throwing a "Service login or communication failure error" message when you try to connect to the Tidal service via your moOde player.

I can only assume that I discovered that during my early experiments and promptly forgot. Mea culpa.

Solution: from the command line, change the ownership of the directory and file. I chose to make them the same as their parent /var/cache/upmpdcli directory. Easily done recursively as follows. [ALERT: be sure you're at the correct directory!!!]

Code:

moode: /var/cache/upmpdcli $ sudo chown -R upmpdcli:root tidal

3. At this point, after completing my steps, I seemed to have Tidal available through the moOde UPnP MediaServer which gets started in the process. I can connect, browse, and select a track to play using my Connect Point (mconnectLite on my iPad for this test) BUT it fails to play. There's an internal error thrown in the upmpdcli plugin code. 

Sorry, I don't have time to chase this down until perhaps late today or tomorrow.

Meanwhile, many UPnP Connect Point apps also provide their own direct access to Tidal (and Qobuz). They act as proxy UPnP Media Servers for these services, so you can still play tracks while you wait.

Regards,
Kent

Hey Kent,
Nice work here - I tried running the first command and returned with the error "no such option: --break-system-packages". I am suspecting that the Moode version 8.3.9 needs python3 to be upgraded. Unfortunately, I can't do any further in-place updates to move to Moode 9.x.x. If I were to update my Python, I may break many dependencies.

hello @edwingoh, the --break-system-packages is needed only after a certain release of python (don't know which exactly).
Technically it is possible to create a venv for upmpdcli and avoid the need to use this scary switch, but that would complicate the setup instructions, and at least for now, I'd rather avoid to go deep in that rabbit hole.
But if this is a concern, I can have a look at it and see if I can suggest an easy solution.