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+?
