How to stream Tidal and Qobuz on your odio Pi

Tidal and Qobuz streaming are available via upmpdcli. With either plugin enabled, upmpdcli becomes a full music library: you can browse, search, and play directly from any UPnP control point (e.g. BubbleDS Next or BubbleUPnP), in addition to its role as a DLNA renderer.

Both plugins ship with the default odio installation (the installer asks, and defaults to yes). What remains is enabling them in upmpdcli’s config and authenticating with your account, as walked through below for Tidal. The full parameter list is in the official documentation:

• Tidal streaming parameters
• Qobuz streaming parameters

Note

Setup contributed by Antoine L, tested on a Raspberry Pi 2 (2014) running a fresh odio installation. Merci Antoine!

There are two ways to play Tidal on the node: enable upmpdcli’s Tidal plugin, which adds Tidal to the node’s UPnP library for any control point, or use a control point that ships its own Tidal integration, like BubbleUPnP, which needs no configuration on the node at all.

Tidal in the node’s library (upmpdcli plugin)

upmpdcli runs as the odio user and reads its config from odio’s home directory, so every step below starts by switching to that user from your SSH session:

sudo su - odio

1. Enable the Tidal plugin

As the odio user, edit the config (it belongs to odio, so from any other user it appears read-only):

nano ~/.config/upmpdcli/upmpdcli.conf

In the Tidal streaming service parameters section, set:

tidaluser = your@email.example
tidalaudioquality = HI_RES_LOSSLESS
tidaloverridecountrycode = FR

• tidaluser is what activates the plugin. The upmpdcli manual describes it as a bogus variable: it isn’t checked against your Tidal account, which is authenticated in the next step.
• tidalaudioquality sets the maximum stream quality.
• tidaloverridecountrycode overrides the country code; adjust to yours.

2. Authenticate with your Tidal account

Still as the odio user, run the credentials helper shipped with the plugin:

python3 /usr/share/upmpdcli/cdplugins/tidal/get_credentials.py -f ~/.cache/upmpdcli/tidal/oauth2.credentials.json

The script prints a Tidal login URL. Open it in a browser on any device and sign in. The script then writes the OAuth2 token to ~/.cache/upmpdcli/tidal/oauth2.credentials.json (no need to create the directory beforehand) and confirms with:

Displaying credentials file for type [/home/odio/.cache/upmpdcli/tidal/oauth2.credentials.json], json format:
...

3. Restart upmpdcli

Restart upmpdcli.service to pick up the new config, from the embedded UI’s Services panel (one click on the restart icon next to the service), or from the same odio terminal:

systemctl --user restart upmpdcli.service

Tidal then joins the node’s UPnP library alongside the built-in webradio sources, so you can browse, search, and play it from any control point.

Tidal via BubbleUPnP’s own integration

BubbleUPnP on Android also ships its own Tidal integration in its Local and Cloud library, independent of the upmpdcli plugin, so nothing needs to be configured on the node. In the tested setup, BubbleUPnP detected the odio node on its own and asked for a one-time sign-in to Tidal; from there you can browse your Tidal library in the app and direct playback to the node like to any DLNA renderer.

Qobuz

Qobuz is configured in the same file, through its own set of parameters. We don’t have a tested walkthrough yet; if you have set up Qobuz with odio, help us improve this page — open an issue.