Tidal Connect Failures

Help and Support Help
, ,
327

Hi @GSiguy . I’m really sorry to hear this.

I’m not a Rivo+ owner so I can’t comment on that experience specifically. My systems are RPi 4B’s running Volumio Premium (both on V3 and V4) connected to external DACs, and the intermittence in connectivity currently applies only to the Authentication Token issue we detected early December.

I’m testing Tidal Connect in these systems as I type and, so far, I haven’t run into any issues.

I have a couple of questions:

a) Could you please provide your most recent log to review?
b) Have you tried using Tidal through the native Volumio UI - that is, through your Rivo+'s network address (devicename.local) or Volumio app? If so, do you run any into any connectivity issues there?

This way, the Volumio team and other community members can chime in and help.

328

To answer your questions:-

  1. This was the last log i sent to Support http://logs.volumio.org/rivoplus/q4zWFjU.html

  2. I have not tried Tidal through the Volumio UI in a while. I don’t really like using it as the UI is not as good as that of the Tidal app. When I used it perhaps a month ago, Tidal ran fine under the Volumio UI.

BTW, for my use case (windows laptop & android phone), i find the Volumio UI slow and it keeps reloading.

329

Since I was not getting any joy playing music through Tidal Connect, I took the opportunity to change to the a new power conditioner that i recently bought and the VR+ was disconnected from power for a while.

Unfortunately, the power re-cycle did not help at all.
http://logs.volumio.org/rivoplus/0aFWctm.html

Apart from Support is there anyone else i can reach out to? Tidal?

330

Hi @GSiguy

Your first log shows plenty of networking or server handshake/contact errors for Tidal Connect, like these:

Jan 21 20:39:31 rivoplus vtcs[6885]: [2026-01-21 20:39:31] [error] handle_transport_init received error: TLS handshake timed out
Jan 21 20:39:31 rivoplus vtcs[6885]: [2026-01-21 20:39:31] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
Jan 21 20:39:31 rivoplus vtcs[6885]: [2026-01-21 20:39:31.553] [tisoc] [error] [WebsocketServerTls.cpp:104] Connection failed. Session State: 3, Error Code: 5, Message: TLS handshake timed out
Jan 21 20:39:32 rivoplus vtcs[6885]: [2026-01-21 20:39:32] [error] handle_transport_init received error: TLS handshake timed out
Jan 21 20:39:32 rivoplus vtcs[6885]: [2026-01-21 20:39:32] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
Jan 21 20:39:32 rivoplus vtcs[6885]: [2026-01-21 20:39:32.012] [tisoc] [error] [WebsocketServerTls.cpp:104] Connection failed. Session State: 3, Error Code: 5, Message: TLS handshake timed out
Jan 21 20:39:32 rivoplus vtcs[6885]: [2026-01-21 20:39:32] [error] handle_transport_init received error: TLS handshake timed out
Jan 21 20:39:32 rivoplus vtcs[6885]: [2026-01-21 20:39:32] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
Jan 21 20:39:32 rivoplus vtcs[6885]: [2026-01-21 20:39:32.451] [tisoc] [error] [WebsocketServerTls.cpp:104] Connection failed. Session State: 3, Error Code: 5, Message: TLS handshake timed out
Jan 21 20:39:35 rivoplus volumio[3200]: info: CoreCommandRouter::volumioGetState
Jan 21 20:39:39 rivoplus vtcs[6885]: [2026-01-21 20:39:39] [error] handle_transport_init received error: TLS handshake timed out
Jan 21 20:39:39 rivoplus vtcs[6885]: [2026-01-21 20:39:39] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
Jan 21 20:39:39 rivoplus vtcs[6885]: [2026-01-21 20:39:39.236] [tisoc] [error] [WebsocketServerTls.cpp:104] Connection failed. Session State: 3, Error Code: 5, Message: TLS handshake timed out
Jan 21 20:39:45 rivoplus vtcs[6885]: [2026-01-21 20:39:45] [error] handle_read_frame error: asio.system:125 (Operation aborted.)

But your second log has something new (to me):

There are plenty of kernel errors like these:

Jan 22 00:03:57 rivoplus kernel: CFG80211-ERROR) wl_escan_handler : escan is not ready ndev ffffffc04de3a000 drv_status 0x0 e_type 69 e_states 8
Jan 22 00:03:57 rivoplus kernel: CFG80211-ERROR) wl_escan_handler : escan is not ready ndev ffffffc04de3a000 drv_status 0x0 e_type 69 e_states 8

More connectivity errors like these:

Jan 22 00:08:25 rivoplus volumio[3389]: error: Failed to parse state for serial connection: TypeError: Cannot read property 'toUpperCase' of undefined

And lots of “Volumio Onboarding” errors that weren’t present in any of your previous logs, like these:

Jan 22 00:09:07 rivoplus volumio5-onboarding[4704]: time=2026-01-22T00:09:07.526+08:00 level=WARN msg="pending write acknowledgment timed out, retrying" component=conn/ble addr=2
Jan 22 00:09:07 rivoplus volumio5-onboarding[4704]: time=2026-01-22T00:09:07.526+08:00 level=ERROR msg="pending write exceeded maximum retries, dropping" component=conn/ble addr=2 chunks=1 index=0
Jan 22 00:09:07 rivoplus volumio5-onboarding[4704]: time=2026-01-22T00:09:07.526+08:00 level=ERROR msg="failed to send event" component=server dst="00:00:00:00:00:00%02 @ 0x2cf91a0" event=SERVER_EVENT_TYPE_PLAYER_METADATA_CHANGED error="peer is gone"

What has changed between both operations?

Also, regarding this:

BTW, for my use case (windows laptop & android phone), i find the Volumio UI slow and it keeps reloading.

I’m also sorry to hear. I’ve tested the Volumio UI in multiple operating systems through browsers and native apps and have found it very responsive with minimum reloading. Maybe your systems have a memory issue, or in the case of your Android device, a power saving issue that makes the app lag when not in use after some time (for example, while listening to a couple of songs)? Do you find the system lags through browsers on both your windows laptop & phone as well?

@Darmur @devgianlu @volumio please help!

331

I am very sorry if i am of little help as i really do not know what the networking or server handshake/contact errors, kernel errors, connectivity errors and volumio onboarding errors actually mean.

Yesterday, there was a time that i was trying to load the Volumio UI on my laptop using the IP address which it is connected to, but with little to no success.

I then suspected that the Rivo+ may have switched over to a different IP address so I tried to use my Android phone to check the ‘Network’ to determine if the IP address had changed. My phone’s Volumio Rivo+ app kept prompting me to pick wired or wireless connection (by this time i had pulled out the ethernet connection). I tried to connect it via wifi and it refused to connect via wireless.

I eventually plugged the ethernet cable into the Rivo+ and, only then did the wireless connection get recognised and connected.

Not sure if that info helps…

332

Today I am using Tidal Connect exclusively through the laptop’s Tidal app and I still keep getting errors.
http://logs.volumio.org/rivoplus/Srt0Dpw.html

333

Have you received any recent replies from support?

@volumio @Marco_Melziade

334

All they have said is that Tidal is on it. This was on Wednesday.

I spent quite a bit of time today (with the help of Gemini) trying to trouble shoot. Switched Fusiondsp off, Spotify connect off, used only ethernet connection (as Gemini read the logs and suspected a conflict between wired and wireless) and several other things… But to no avail. The disconnecting and server errors keep happening.

335

It is very frustrating that it keeps happening although I try my darnest to troubleshoot the issue. Support can be unresponsive (like right now)
I am this close to getting rid of the Rivo+ and going to something far more reliable like Eversolo, Bluesound, Matrix Audio, etc. Considering the price of the Rivo+ (plus linear power supply) is more or less equivalent to an Eversolo T8, the Rivo+ is a completely untenable proposition to me.
image

http://logs.volumio.org/rivoplus/lDlAjPz.html

336

Hi @GSiguy , any news from the support team regarding your case?

This last error you posted again points to network issues in your particular setup. And there seems to be an error in the log as well, as it doesn’t show much beyond plugin setup.

I would point to a factory-reset and configuration from scratch with your device, but again, you’re entitled to premium support and their handling of your issues. @Marco_Melziade @volumio

For what it’s worth, I can’t replicate this behavior on any of my Pi setups. Once again, I hope the team chimes in soon.

337

UPDATE:
First of all, this issue (from what we know) should affect all devices integrating TIDAL Connect, it’s not Volumio specific but due to some changes done on TIDAL side.

The good news is that we just received an update from TIDAL which seems to work fine. We are in the process of testing and performing QA on the update that will fix it. For what we see now, it will be a matter of days for us to release an update that will fix this.

1 Like
338

Hi, thanks for the update on this!

I also hope the Volumio team & support look at @GSiguy 's specific case either by opened tickets or his reported logs on this thread. It looks like it could be something particular in addition to the token authentication issue on Tidal’s end that’s affecting all of us. Hope this all helps!

339

@TubularBells I am afraid that the Support Team has not responded to my emails, to date. This is almost a week now since I have heard last from them.

I took a break from the frustrations of the frequent dropouts yesterday and just listened via the Volumio UI to Radio Paradise. Today, the situation has started giving me issues again.
http://logs.volumio.org/rivoplus/TdH4ShC.html

I have done the factory reset at least once since the end of last week but it has not helped much. I have cleared the Tidal desktop app’s cache and that seemed to have done some good but it did not make the issues go entirely away, as can be seen from the behaviour today.

340

@TubularBells Thank you for trying to help.

341

Hello everyone and thank you for your patience. Version 3.905 has been released to the test channel with a potential fix for TIDAL Connect. Please let us know if it solves the playback issues.

342

@devgianlu I do not see any update available.

BTW i am still awaiting Support’s response to my issues. The last i heard from you guys was Wed 21 Jan 26.

It is awful trying to listen to anything right now via the Tidal desktop app.

http://logs.volumio.org/rivoplus/uMiFdyX.html

343

@GSiguy The version is in the beta channel while we assert that the issue has been resolved by TIDAL. You can try it by switching to the test channel: How to switch Update Channel (Stable/Test)

344

I’ve done the switch. The Rivo+ restarted but it still won’t work. http://logs.volumio.org/rivoplus/WRvniFf.html

345

I see, thank you for the prompt response. We did not experience this error during internal testing, I have reported this immediately to the TIDAL team.

346

Hi Adrian,
thanks for your patience, it’s taking longer than expected unfortunately, because the resolution depends on TIDAL feedback and fixes.
We’ve already reviewed the logs you shared and escalated the issue directly to them, as the behavior you’re experiencing is linked to changes on their end.

We understand how frustrating this is, especially when listening becomes unreliable, and we really appreciate your patience while we work with TIDAL to get this fully resolved for everyone.
We’ll keep you posted as soon as we have concrete news.
Best regards,
Marco
Volumio Team