Tidal Connect Failures

[Umbongo]

Hi.
Tidal connect is now not working at all for me, on V4.006.
For the last few weeks, if I don’t use Tidal for a while it disappears and I have to reboot to get it back but now it just doesn’t play at all.
At first I can browse and select tracks but no output when I try to play them. If I leave it for a while then I can’t browse at all.

[Wheaten]

I expect you made a typo as V4.006 is an old Beta from June 2025.
Please post logs when this behavior happens, so it can be debugged.

[SimonE]

Evening @Wheaten
You probably saw the 2 other current threads reporting something similar (Tidal content disappearing). Both have some logs. Should they be merged or are these different issues?

Tidal issue in volumio native app

Hi Do anyone maybe have same minor issue with tidal in volumio app/ browser That it wont search for tracks or albums I have to logout and login to be able to get artist/album/song up The last two days have been like that Anyone? B regards

and

Problems with TIDAL Integration - stops working when idle

For quite some time now, I have been experiencing strange behavior with all three of my PIs running Volumio. It doesn’t matter whether they are connected via Wi-Fi or LAN. After the PIs have been running for a while, the Tidal integration stops working. I have to restart the respective Pi and then it works again. Until they are idle again. Other integrations or, for example, Radio Paradise run completely normally. Is this behavior known? Thanks in andvance http://logs.volumio.org/volumio/eh…

[Wheaten]

one topic is Native tidal integration, the other is tidal connect. Prefer to keep them separated.

[Umbongo]

Updates have been coming in and definitely had some since June so odd I’m on such an old version. Anyway, downloaded v4.067 and setup from fresh so I’ll see how I get on with that…
Thanks

[Umbongo]

It’s happened again… Start Volumio and everything is fine but if I leave it for maybe 30 minutes then I can no longer browse Tidal.

Logs sent: http://logs.volumio.org/volumio/wuQDseD.html

The drop happened right at the end of the log, sometime between 13:17 and 14:07

[B505]

FYI: Long time later but here’s some ‘journalctl’ output, when attempting and failing to play @Axel 's “When Darkness Takes Flight” selection, via Tidal Connect
[Volumio 4.067 Raspberry Pi4b 2GB 32GB SD]

‘LOW’ res Tidal Connect FAIL log

volumio@node-noire:~$ journalctl -u vtcs -b
Nov 10 20:58:45 node-noire systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 10 20:58:46 node-noire vtcs[1754]: STARTING TidalConnect services, version: 1.5.1-beta1
Nov 10 20:58:46 node-noire vtcs[1754]: STARTED TidalConnect services.
Nov 10 21:00:12 node-noire vtcs[1754]: [2025-11-10 21:00:12.334] [tisoc] [warning] [PlaybackControllerImpl.cpp:520] Illegal state:1
Nov 10 21:00:12 node-noire vtcs[1754]: [2025-11-10 21:00:12.335] [tisoc] [warning] [PlaybackControllerImpl.cpp:213] Ignore play request because play>
Nov 10 21:00:13 node-noire vtcs[1754]: [close:85] Entering
Nov 10 21:00:13 node-noire vtcs[1754]: [close:100] Exiting
Nov 10 21:00:13 node-noire vtcs[1754]: [open:50] Opening with sample rate: 44100, type: 3
Nov 10 21:00:13 node-noire vtcs[1754]: [start:106] Entering
Nov 10 21:00:13 node-noire vtcs[1754]: [start:113] Reopening PCM device…
Nov 10 21:00:13 node-noire vtcs[1754]: [start:115] PCM opened successfully.
Nov 10 21:00:13 node-noire vtcs[1754]: [start:120] Exiting
Nov 10 21:00:13 node-noire vtcs[1754]: [feedThread:223] Entering
Nov 10 21:00:14 node-noire vtcs[1754]: [2025-11-10 21:00:14.129] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_D>
Nov 10 21:00:14 node-noire vtcs[1754]: [2025-11-10 21:00:14.129] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_D>
Nov 10 21:00:14 node-noire vtcs[1754]: [2025-11-10 21:00:14.129] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_D>
Nov 10 21:00:14 node-noire vtcs[1754]: [2025-11-10 21:00:14.130] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_D>
Nov 10 21:00:14 node-noire vtcs[1754]: [2025-11-10 21:00:14.130] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_D>
Nov 10 21:01:53 node-noire vtcs[1754]: [pause:147] Entering
Nov 10 21:01:53 node-noire vtcs[1754]: [feedThread:276] Exiting
Nov 10 21:01:53 node-noire vtcs[1754]: [pause:161] Exiting
Nov 10 21:02:38 node-noire vtcs[1754]: [start:106] Entering
Nov 10 21:02:38 node-noire vtcs[1754]: [start:113] Reopening PCM device…
Nov 10 21:02:38 node-noire vtcs[1754]: [start:115] PCM opened successfully.
Nov 10 21:02:38 node-noire vtcs[1754]: [start:120] Exiting
Nov 10 21:02:38 node-noire vtcs[1754]: [feedThread:223] Entering
Nov 10 21:06:35 node-noire vtcs[1754]: [2025-11-10 21:06:35.598] [tisoc] [error] [ffmpeg_aac_decoder.cpp:31] avcodec major version differ between ru>
Nov 10 21:06:35 node-noire vtcs[1754]: [2025-11-10 21:06:35.598] [tisoc] [error] [ffmpeg_aac_decoder.cpp:34] avformat major version differ between r>
Nov 10 21:06:40 node-noire vtcs[1753]: Segmentation fault
Nov 10 21:06:40 node-noire systemd[1]: vtcs.service: Main process exited, code=exited, status=139/n/a
Nov 10 21:06:40 node-noire systemd[1]: vtcs.service: Failed with result ‘exit-code’.
Nov 10 21:06:40 node-noire systemd[1]: vtcs.service: Consumed 8.821s CPU time.
Nov 10 21:06:40 node-noire systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 1.

[Wheaten]

Problems with TIDAL Integration - stops working when idle

This is an ongoing issue with TIDAL that we are investigating as we speak with them

[GSiguy]

Hi! I am a fairly new user with a Volumio Rivo Plus.

Things weren’t perfect before, but it’s gotten worse after the latest update (3.872) which i installed today. I usually stream from the Tidal App from my windows laptop or android phone, but now it keeps dropping with error messages in the app (“not connected to server” type errors). I had this intermittently in the previous version but this time it happens by the time one track or 2 have played.

Any idea what I should do?

[Wheaten]

Read one post above yours.

[GSiguy]

You mean the part where they’re investigating? Do they normally fix it promptly?

[SimonE]

Problem identified, fix very soon.

Problems with TIDAL Integration - stops working when idle

First of all, huge kudos to @hulver : your assumption was absolutely spot on! Thanks for taking the time to share it; your input helped us quickly identify what was going on (fun fact: neither we nor TIDAL initially thought of this). Here’s what happened: TIDAL recently narrowed the validity window for authentication tokens. Our method for refreshing those tokens was no longer sufficient (that’s on us, our implementation wasn’t fully aligned with how it should have been done). The good news: …

[Wheaten]

Yes Volumio acts very promptly.

[GSiguy]

The other issue i get is that the Tidal Connect app stops autoplaying the next track after a while. I then have to manually advance to the next track for music to carry on playing.

Sometimes, if i change playlists, it will work again.

Is this also a problem some of you encounter?

[pbarata]

Just started to have some error with TIDAL when try to play music. The error message is the following
"Failed to decode http://1271.0.0.1:3245?data=tidal://song/ (…) Quality=HI_RES; got HTTP status 404”

Tried to change the Quality setting, but the error continues. This started when changed the Quality to best available.

Can anyone help?

Thanks!

[Darmur]

a new version with the fix for Tidal and Tidal Connect has been released, please update your devices

[pbarata]

Many thanks. I’ll give feedback after the update.

[B505]

[v4.069 Raspberry Pi4b 2GB 32GB SD]

Some great work has been done on resolving the ‘Tidal Connect’ timeout issue ( @hulver ) and was incorporated in the v4.069 release. For anyone new to the thread, the matter regarding ‘LOW’ res track playback hanging, is still outstanding.

[pbarata]

Just made the update to version v3.874 and everyhting is working fine again!
Thanks