Tidal Connect Failures

Hi @GSiguy . I’m running Tidal Connect right now, no issues so far.

Here’s a selection from your log:

Dec 30 17:06:11 rivoplus volumio[3393]: info: CoreCommandRouter::executeOnPlugin: tidalconnect , onGetConfig
Dec 30 17:06:11 rivoplus vtcs[19580]: STARTING TidalConnect services, version: 1.5.2.56
Dec 30 17:06:11 rivoplus vtcs[19580]: STARTED TidalConnect services.
Dec 30 17:06:11 rivoplus volumio[3393]: info: Executing endpoint tc_connect
Dec 30 17:06:11 rivoplus volumio[3393]: info: CoreCommandRouter::executeOnPlugin: tidalconnect , onConnect
Dec 30 17:06:11 rivoplus volumio[3393]: info: Connecting to TidalConnect
Dec 30 17:06:11 rivoplus volumio[3393]: info: CoreCommandRouter::servicePushState
Dec 30 17:06:11 rivoplus volumio[3393]: info: CorePlayQueue::getTrack 9
Dec 30 17:06:11 rivoplus volumio[3393]: info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current spop Received tidalconnect
Dec 30 17:06:11 rivoplus volumio[3393]: info: CoreCommandRouter::servicePushState
Dec 30 17:06:11 rivoplus volumio[3393]: info: CorePlayQueue::getTrack 9
Dec 30 17:06:11 rivoplus volumio[3393]: info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current spop Received tidalconnect
Dec 30 17:06:11 rivoplus volumio[3393]: info: TidalConnect service started!
Dec 30 17:06:11 rivoplus volumio[3393]: info: TidalConnect service started!
Dec 30 17:06:11 rivoplus volumio[3393]: info: TidalConnect service started!
Dec 30 17:06:11 rivoplus volumio[3393]: info: TidalConnect service stoped!
Dec 30 17:06:11 rivoplus volumio[3393]: info: TidalConnect service stoped!
Dec 30 17:06:11 rivoplus volumio[3393]: info: Updating tc_getconfig REST Endpoint for plugin: music_service/tidalconnect
Dec 30 17:06:11 rivoplus volumio[3393]: info: Updating tc_connect REST Endpoint for plugin: music_service/tidalconnect
Dec 30 17:06:11 rivoplus volumio[3393]: info: TidalConnect service started!
Dec 30 17:06:11 rivoplus sudo[19626]:  volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start vtcs.service
Dec 30 17:06:11 rivoplus sudo[19626]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 30 17:06:11 rivoplus sudo[19626]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus volumio[3393]: info: TidalConnect service started!
Dec 30 17:06:12 rivoplus mpd[19579]: Dec 30 17:06 : decoder: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Dec 30 17:06:12 rivoplus systemd[1]: Started Music Player Daemon.
Dec 30 17:06:12 rivoplus sudo[19500]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus sudo[19417]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus sudo[19547]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus sudo[19323]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus sudo[19471]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus sudo[19524]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus sudo[19225]: pam_unix(sudo:session): session closed for user root
Dec 30 17:06:12 rivoplus volumio[3393]: error: MPD error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: MPD error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: MPD error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: MPD error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: MPD error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: MPD error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: The expression evaluated to a falsy value:
Dec 30 17:06:12 rivoplus volumio[3393]:   assert.ok(self.idling)
Dec 30 17:06:12 rivoplus volumio[3393]: error: updateQueue error: null
Dec 30 17:06:12 rivoplus volumio[3393]: info: TidalConnect service stoped!
Dec 30 17:06:12 rivoplus volumio[3393]: info: TidalConnect service stoped!
Dec 30 17:06:12 rivoplus volumio[3393]: info: Updating tc_getconfig REST Endpoint for plugin: music_service/tidalconnect
Dec 30 17:06:12 rivoplus volumio[3393]: info: Updating tc_connect REST Endpoint for plugin: music_service/tidalconnect

From that section, it looks like you start a TC instance, then:

Dec 30 17:06:11 rivoplus volumio[3393]: info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current spop Received tidalconnect

After that, you get a bunch of notifications of Tidal Connect stopping. It looks like you or the system tries again, then get this recurring Timidity error (which surprises me, because I don’t know what Timidity is used for here):

Dec 30 17:06:12 rivoplus mpd[19579]: Dec 30 17:06 : decoder: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg

And then subsequent MPD errors until Tidal Connect stops once more.

A few seconds later, this happens:

Dec 30 17:06:22 rivoplus volumio[3393]: info: Spotify Stop
Dec 30 17:06:22 rivoplus volumio[3393]: SPOTIFY: SPOTIFY STOP
Dec 30 17:06:22 rivoplus volumio[3393]: SPOTIFY: {"status":"pause","position":9,"title":"Natsu no Omoide","artist":"Yoshinao Nakada","album":"yours;Gift","albumart":"https://i.scdn.co/image/ab67616d0000b273bfbad9c9afa9baa6437427b5","uri":"spotify:track:5IvShdg6eOKt3AzztEhqcx","trackType":"spotify","codec":"ogg","seek":0,"duration":249,"samplerate":"320 kbps","bitdepth":"16 bit","random":null,"repeat":null,"repeatSingle":false,"consume":false,"volume":100,"dbVolume":null,"disableVolumeControl":false,"mute":false,"stream":"spotify","volatile":false,"service":"spop"}
Dec 30 17:06:22 rivoplus volumio[3393]: info: Sending Spotify command to local API: /player/pause
Dec 30 17:06:22 rivoplus volumio[3393]: info: TidalConnect Active
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreCommandRouter::volumioGetState
Dec 30 17:06:22 rivoplus volumio[3393]: info: CorePlayQueue::getTrack 9
Dec 30 17:06:22 rivoplus volumio[3393]: info: Currently active: spop
Dec 30 17:06:22 rivoplus volumio[3393]: info: Setting Volatile state to tidalconnect
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreStateMachine::setConsumeUpdateService undefined
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreCommandRouter::servicePushState
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreStateMachine::pushState
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreCommandRouter::volumioPushState
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreCommandRouter::servicePushState
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreStateMachine::pushState
Dec 30 17:06:22 rivoplus volumio[3393]: info: CoreCommandRouter::volumioPushState
Dec 30 17:06:22 rivoplus volumio[3393]: info: Signalling Playback active due to playback status change
Dec 30 17:06:22 rivoplus volumio[3393]: info: Signalling Playback active due to playback status change
Dec 30 17:06:22 rivoplus volumio[3393]: info: Signalling Playback active due to playback status change
Dec 30 17:06:22 rivoplus volumio[3393]: info: Signalling Playback active due to playback status change
Dec 30 17:06:22 rivoplus volumio[3393]: SPOTIFY: RECEIVED VOLUMIO VOLUME 100
Dec 30 17:06:22 rivoplus volumio[3393]: SPOTIFY: RECEIVED VOLUMIO VOLUME 100
Dec 30 17:06:22 rivoplus volumio[3393]: SPOTIFY: RECEIVED VOLUMIO VOLUME 100
Dec 30 17:06:22 rivoplus volumio[3393]: info: MCU Signalled Playback Active
Dec 30 17:06:22 rivoplus volumio[3393]: info: MCU Signalled Playback Inactive
Dec 30 17:06:22 rivoplus volumio[3393]: info: MCU Signalled Playback Active
Dec 30 17:06:25 rivoplus vtcs[19580]: [2025-12-30 17:06:25.991] [tisoc] [warning] [PlaybackControllerImpl.cpp:520] Illegal state:1
Dec 30 17:06:25 rivoplus vtcs[19580]: [2025-12-30 17:06:25.992] [tisoc] [warning] [PlaybackControllerImpl.cpp:213] Ignore play request because playback state is not STARTED. state_=2, playstate_=1, player_state_=0
Dec 30 17:06:25 rivoplus volumio[3393]: info: Pushing metadata

That same track on Spotify appears in your previous logs - do you fall back to it? is it stuck in a cache? Did you attempt to play back from Spotify then in between using Tidal Connect, or not?

@Darmur @devgianlu Please help - any ideas as to what could be happening on this Rivo+?

Ok. For a long time, the Rivo Plus had not appeared on my phone’s (android) Tidal app. But it did appear yesterday (when I had the server error issues) so I tried it to make sure it worked. Once it did, i tried to go back to using the Tidal app on my laptop and that was when the issues started.

As for same track issue, it is one of my ‘favorited’ tracks but i wasn’t playing it yesterday as far as i can remember…

BTW i am only into ownership of the Rivo+ for about 2 months. Is this something I should be looking as a constant issue as a user of this streamer?

Hi @GSiguy, Have you contacted support regarding your specific issues? Also, are you running anything through a VPN or firewall?

When you say “a long time”, how long? The typical Tidal App behavior on Android on iOS is that when you tap on the speaker you first see your device’s native outputs, then only when you close and tap again do the rest of the available network devices appear. Is this what you mean?

When you say “contact support” may I know specifically who you are referring to?

Definitely no VPN on.

As for firewall, I am not entirely sure as my setup is in a rented office and I use the landlord’s wifi. ShieldsUp! test shows as follows:-

Like i said, I am not IT savvy so i really can’t say if :point_up: is of any help… All i know that it is likely that it has been this way even when the Rivo+ was running smooth.

As to what I meant a “long time”, let me explain by giving some context. The Rivo+ is a setup in my office. So I have been controlling it almost exclusively using the Tidal app from my windows laptop. I hardly use or even look at the Tidal App on my android phone. That is until maybe a week or so ago when I noticed that it does not detect the Rivo+ on my phone Tidal App. Yes, for android, the way I can check is the same as on iOS, i.e. tap on speaker icon, see device’s native outputs available, choose it. Until a few days ago, there was no Rivo+ showing up on my device’s native outputs. It has shown up recently until now. In contrast, Rivo+ DOES show up on the Spotify Connect app on my phone during that period when it does not show up on my phone’s Tidal app.

Hi @GSiguy , and Happy New Year!

There is a Contact Support option from within your Rivo+ menu, and you can also use the following support link:

https://volumio.atlassian.net/servicedesk/customer/portal/1/group/1/create/1

You can even reference your posts and logs as extra evidence on the ticket as well. I hope this helps.

A Happy New Year to @TubularBells and your Family too!

Thanks for showing me where to turn for help!

Support is entirely quiet. I had sent an email on Friday or Saturday and followed up on their standard response with 2 more emails but I have yet to hear from Support.

Frustrating…

Hi Adrian,
I apologize for the late response, but we have been out of the office for the holidays.
I have shared your logs with the team for investigation. I will get back to you as soon as I have an update via email.
Best regards,
Marco Volumio

@GSiguy As of 29 December I can see that you are still affected by the 401 bug. We are still waiting for a proper fix from TIDAL.

Everyone is coming back from vacation now, so I think there will a bit of backlog.

The disconnection is happening a lot today. Not sure if it’s a factor but I noticed that it coincides with an update to the Tidal app.
http://logs.volumio.org/rivoplus/tNNrD8c.html

Tidal Connect disconnecting has continued and makes the app almost unusable right now. Support is also not reverting to my last couple of emails.
http://logs.volumio.org/rivoplus/eGcpvdc.html

I am going to get rid of my Volumio Rivo Plus if this nonsense keeps happening. Unacceptable dropouts, zero response from Support, totally unenjoyable experience.

Hi @GSiguy please note that our support will reply from 8 to 17 Monday to Friday.

I had a look at your log and I mostly see playback trough Spotify.

I would suggest to

  • disable fusion DSP ( depending on your playback device it might create problems on frequency/bit depth switching)
  • restart your device

If that persist, there might be a conflict with Spotify (maybe some other device in your network is pinging the Spotify service, causing tidal connect to stop ) so I would try disabling Spotify as well.

Let us know

Hi,

Our development team is currently reviewing your issue today.

Thank you for your cooperation and patience
Best regards

Marco Volumio

Hello everyone, I am deeply sorry about the TIDAL Connect situation.

I am continuously trying to get a hold of the TIDAL team to get this issue resolved, but they keep ignoring me. I’d like to mention that this is not a Volumio OS issue, it’s a bug in their own provided TIDAL Connect SDK which we cannot modify or correct ourselves.

Hi,

I was playing through Spotify earlier as Tidal Connect was not working properly.

I have deleted Fusion DSP for now.

Tidal Connect seems more stable today but there seems to be a long wait between tracks. Also the continuous play seems to be stopping around 19 songs in.

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

I spoke too soon. It Tidal Connect disconnected again…
http://logs.volumio.org/rivoplus/87Gm6CY.html

Hi Guys,
an update and recent summary of this issue.

WHAT THE ISSUE IS
TIDAL Connect stops playback about once every 4 hours. It means that if you’re playing trough TIDAL Connect, the streaming will stop on its own, and to restart it you just have to press pause and then play from TIDAL app.

WHY THIS HAPPENS
This happens because of recent changes on TIDAL’s own infrastructure. This change reduced the lifetime of authentication token, and therefore it can cause an authenticated session to expire without properly refreshing.

WHAT ARE WE DOING
Unfortunately there’s not much we can do, as TIDAL Connect is built upon a library that we receive from TIDAL themselves. We already communicated with TIDAL about this and they confirmed that they are working on a fix. Rest assured, that as soon as this is fixed on their end, and we will receive the update, we will update and release it promptly.

WHAT CAN YOU DO IF YOU HAVE THIS ISSUE
It’s annoying, however if your TIDAL Connect playback stops, simply reselect the track you were playing. From what we have observed this should happen not more than 1 time every 4 hours.
We want you to know that we are as frustrated as you are and would like to see it resolved ASAP.

Hi. Thank you and the team for the update. Please let us know how this moves forward.

On the plus side, there seem to be no issues with playback from within the native Volumio UI or integration.

Tidal Collect has become virtually unplayable again. It disconnects me in less than 1 song right now. I have informed support and given my logs.

What I really want to know is if this is what I should expect for the entire duration of owning and using a Volumio Rivo+? I hope someone can give me a candid answer.