Tidal Connect Failures

Axel · December 9, 2025, 5:38pm

And how about if you play tidal from the Volumio GUI?

GSiguy · December 10, 2025, 11:18am

Hi! Sorry about the long lag time. I am in Singapore and, well… time zones… strangely it has held up pretty well in day time listening today (about 4 hours coninuous) until just a few moments ago where I got the same error on my Tidal desktop app.

The log is as follows: http://logs.volumio.org/rivoplus/DdDteNF.html

Not sure if you can see it…

GSiguy · December 10, 2025, 11:25am

I’m afraid i have not tried to play it from the Volumio GUI. I’ll try that now and report back.

Marc050 · December 10, 2025, 8:29pm

On my Volumio Rivo+ Tidal connect keeps failing to play the next song of a playlist sooner and sooner. It is now happening every 10 songs or less. I can skip to the next song, but then it will only play that one and stop again. I have to go to playback on my device, start it there en connect to the Rivo+ again. Then it will work for a while.

Here is my log from when it last happened:

Starting Live Log...
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
info: CALLMETHOD: system_controller system sendBugReport [object Object]
info: CoreCommandRouter::executeOnPlugin: system , sendBugReport
 volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwconfig
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
 volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl -p 7
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
info: Log sent successfully, reply: {"status":"OK","link":"http://logs.volumio.org/rivoplus/CtySfsN.html"}
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
ntpd exiting on signal 15 (Terminated)
185.51.192.61 local addr 192.168.2.5 -> 
Stopping Network Time Service...
178.239.19.62 local addr 192.168.2.5 -> 
178.239.19.58 local addr 192.168.2.5 -> 
158.101.216.150 local addr 192.168.2.5 -> 
162.159.200.1 local addr 192.168.2.5 -> 
193.111.32.123 local addr 192.168.2.5 -> 
172.233.59.163 local addr 192.168.2.5 -> 
94.198.159.16 local addr 192.168.2.5 -> 
80.60.67.39 local addr 192.168.2.5 -> 
206.71.158.74 local addr 192.168.2.5 -> 
185.244.24.70 local addr 192.168.2.5 -> 
81.172.248.188 local addr 192.168.2.5 -> 
213.136.0.252 local addr 192.168.2.5 -> 
129.250.35.251 local addr 192.168.2.5 -> 
5.200.6.34 local addr 192.168.2.5 -> 
213.154.236.182 local addr 192.168.2.5 -> 
94.142.246.192 local addr 192.168.2.5 -> 
ntp.service: Succeeded.
Stopped Network Time Service.
Starting Network Time Service...
ntpd 4.2.8p12@1.3728-o (1): Starting
Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 104:103
Started Network Time Service.
proto: precision = 1.250 usec (-20)
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 1079 days ago
Listen and drop on 0 v6wildcard [::]:123
Listen and drop on 1 v4wildcard 0.0.0.0:123
Listen normally on 2 lo 127.0.0.1:123
Listen normally on 3 wlan0 192.168.2.5:123
Listening on routing socket on fd #20 for interface updates
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Soliciting pool server 80.60.67.39
Soliciting pool server 45.139.163.87
Soliciting pool server 178.239.19.58
Soliciting pool server 45.138.55.62
Soliciting pool server 45.138.55.62
Soliciting pool server 195.35.113.80
Soliciting pool server 178.239.19.57
Soliciting pool server 94.142.246.192
Soliciting pool server 144.21.38.190
Soliciting pool server 149.143.87.22
Soliciting pool server 188.90.28.184
Soliciting pool server 81.172.248.188
Soliciting pool server 77.174.62.158
Soliciting pool server 77.174.62.158
Soliciting pool server 103.149.168.181
Soliciting pool server 31.58.102.164
Soliciting pool server 193.111.32.123
Soliciting pool server 45.9.2.181
info: CoreCommandRouter::executeOnPlugin: my_volumio , getAutoUpdateCheckEnabled
No test mode
No alpha test mode
info: CoreCommandRouter::executeOnPlugin: my_volumio , getAutoUpdateEnabled
info: Update Ready: {"changeLogLink":"","description":"You're already on the latest version","title":"No Updates Available","updateavailable":false}
info: CoreCommandRouter::executeOnPlugin: updater_comm , setUpdateMessageCache
[close:85] Entering
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[feedThread:276] Exiting
[close:100] Exiting
[close:85] Entering
[close:100] Exiting
[open:50] Opening with sample rate: 96000, type: 3
[start:106] Entering
[start:113] Reopening PCM device...
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[start:115] PCM opened successfully.
[start:120] Exiting
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
[feedThread:223] Entering
info: Signalling Playback active due to playback status change
info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses

info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard
info: CoreCommandRouter::executeOnPlugin: system , getShowWizard
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
[close:85] Entering
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[feedThread:276] Exiting
[close:100] Exiting
[close:85] Entering
[close:100] Exiting
[open:50] Opening with sample rate: 44100, type: 0
[start:106] Entering
[start:113] Reopening PCM device...
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[start:115] PCM opened successfully.
[start:120] Exiting
[feedThread:223] Entering
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
195.35.113.80 local addr 192.168.2.5 -> 
81.172.248.188 local addr 192.168.2.5 -> 
ntpd exiting on signal 15 (Terminated)
80.60.67.39 local addr 192.168.2.5 -> 
Stopping Network Time Service...
45.139.163.87 local addr 192.168.2.5 -> 
178.239.19.58 local addr 192.168.2.5 -> 
45.138.55.62 local addr 192.168.2.5 -> 
94.142.246.192 local addr 192.168.2.5 -> 
178.239.19.57 local addr 192.168.2.5 -> 
144.21.38.190 local addr 192.168.2.5 -> 
149.143.87.22 local addr 192.168.2.5 -> 
188.90.28.184 local addr 192.168.2.5 -> 
77.174.62.158 local addr 192.168.2.5 -> 
103.149.168.181 local addr 192.168.2.5 -> 
31.58.102.164 local addr 192.168.2.5 -> 
193.111.32.123 local addr 192.168.2.5 -> 
ntp.service: Succeeded.
Stopped Network Time Service.
Starting Network Time Service...
ntpd 4.2.8p12@1.3728-o (1): Starting
Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 104:103
Started Network Time Service.
proto: precision = 1.250 usec (-20)
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 1079 days ago
Listen and drop on 0 v6wildcard [::]:123
Listen and drop on 1 v4wildcard 0.0.0.0:123
Listen normally on 2 lo 127.0.0.1:123
Listen normally on 3 wlan0 192.168.2.5:123
Listening on routing socket on fd #20 for interface updates
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Soliciting pool server 185.51.192.61
Soliciting pool server 94.198.159.15
Soliciting pool server 158.101.216.150
Soliciting pool server 86.80.166.233
Soliciting pool server 31.58.102.164
Soliciting pool server 195.35.113.80
Soliciting pool server 206.71.158.74
Soliciting pool server 77.175.129.186
Soliciting pool server 45.83.205.227
Soliciting pool server 185.71.60.123
Soliciting pool server 172.233.38.176
Soliciting pool server 164.92.156.55
Soliciting pool server 178.239.19.60
Soliciting pool server 94.198.159.11
Soliciting pool server 45.9.2.181
Soliciting pool server 80.60.67.39
Soliciting pool server 94.142.246.192
Soliciting pool server 2a00:d78:0:712:94:198:159:16
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
[close:85] Entering
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
[feedThread:276] Exiting
[close:100] Exiting
info: Signalling Playback active due to playback status change
[close:85] Entering
[close:100] Exiting
[open:50] Opening with sample rate: 44100, type: 3
[start:106] Entering
[start:113] Reopening PCM device...
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[start:115] PCM opened successfully.
[start:120] Exiting
[feedThread:223] Entering
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
45.9.2.181 local addr 192.168.2.5 -> 
86.80.166.233 local addr 192.168.2.5 -> 
[close:85] Entering
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[feedThread:276] Exiting
[close:100] Exiting
[close:85] Entering
[close:100] Exiting
[open:50] Opening with sample rate: 96000, type: 3
[start:106] Entering
[start:113] Reopening PCM device...
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[start:115] PCM opened successfully.
[start:120] Exiting
[feedThread:223] Entering
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
Starting Cleanup of Temporary Directories...
systemd-tmpfiles-clean.service: Succeeded.
Started Cleanup of Temporary Directories.
ntpd exiting on signal 15 (Terminated)
Stopping Network Time Service...
185.51.192.61 local addr 192.168.2.5 -> 
94.198.159.15 local addr 192.168.2.5 -> 
158.101.216.150 local addr 192.168.2.5 -> 
31.58.102.164 local addr 192.168.2.5 -> 
195.35.113.80 local addr 192.168.2.5 -> 
206.71.158.74 local addr 192.168.2.5 -> 
45.83.205.227 local addr 192.168.2.5 -> 
77.175.129.186 local addr 192.168.2.5 -> 
185.71.60.123 local addr 192.168.2.5 -> 
172.233.38.176 local addr 192.168.2.5 -> 
164.92.156.55 local addr 192.168.2.5 -> 
178.239.19.60 local addr 192.168.2.5 -> 
80.60.67.39 local addr 192.168.2.5 -> 
94.198.159.11 local addr 192.168.2.5 -> 
94.142.246.192 local addr 192.168.2.5 -> 
ntp.service: Succeeded.
Stopped Network Time Service.
Starting Network Time Service...
ntpd 4.2.8p12@1.3728-o (1): Starting
Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 104:103
Started Network Time Service.
proto: precision = 1.250 usec (-20)
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 1079 days ago
Listen and drop on 0 v6wildcard [::]:123
Listen and drop on 1 v4wildcard 0.0.0.0:123
Listen normally on 2 lo 127.0.0.1:123
Listen normally on 3 wlan0 192.168.2.5:123
Listening on routing socket on fd #20 for interface updates
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Soliciting pool server 149.143.87.22
Soliciting pool server 178.239.19.62
Soliciting pool server 185.51.192.63
Soliciting pool server 172.233.59.169
Soliciting pool server 162.159.200.1
Soliciting pool server 191.96.11.19
Soliciting pool server 81.172.248.188
Soliciting pool server 103.149.168.180
Soliciting pool server 194.104.0.153
Soliciting pool server 103.149.168.181
Soliciting pool server 83.98.201.134
Soliciting pool server 185.80.247.36
Soliciting pool server 45.138.55.61
Soliciting pool server 172.233.59.163
Soliciting pool server 193.123.38.172
Soliciting pool server 108.61.189.74
Soliciting pool server 178.239.19.57
Soliciting pool server 103.147.153.176
[close:85] Entering
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
[feedThread:276] Exiting
[close:100] Exiting
info: Signalling Playback active due to playback status change
[close:85] Entering
[close:100] Exiting
[open:50] Opening with sample rate: 44100, type: 0
[start:106] Entering
[start:113] Reopening PCM device...
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
[start:115] PCM opened successfully.
[start:120] Exiting
[feedThread:223] Entering
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: Signalling Playback active due to playback status change
info: Signalling Playback active due to playback status change
[2025-12-10 21:03:57.514] [tisoc] [error] [QueueWindowLoader.cpp:272] status code:401
[2025-12-10 21:03:57.671] [tisoc] [error] [HttpClient.cpp:469] curl_easy_perform failed. reason:URL using bad/illegal format or missing URL further detail:
[2025-12-10 21:03:57.671] [tisoc] [error] [QueueWindowLoader.cpp:272] status code:99
81.172.248.188 local addr 192.168.2.5 -> 
83.98.201.134 local addr 192.168.2.5 -> 
ntpd exiting on signal 15 (Terminated)
149.143.87.22 local addr 192.168.2.5 -> 
Stopping Network Time Service...
178.239.19.62 local addr 192.168.2.5 -> 
185.51.192.63 local addr 192.168.2.5 -> 
172.233.59.169 local addr 192.168.2.5 -> 
162.159.200.1 local addr 192.168.2.5 -> 
103.149.168.180 local addr 192.168.2.5 -> 
194.104.0.153 local addr 192.168.2.5 -> 
103.149.168.181 local addr 192.168.2.5 -> 
185.80.247.36 local addr 192.168.2.5 -> 
172.233.59.163 local addr 192.168.2.5 -> 
45.138.55.61 local addr 192.168.2.5 -> 
193.123.38.172 local addr 192.168.2.5 -> 
108.61.189.74 local addr 192.168.2.5 -> 
103.147.153.176 local addr 192.168.2.5 -> 
178.239.19.57 local addr 192.168.2.5 -> 
ntp.service: Succeeded.
Stopped Network Time Service.
Starting Network Time Service...
ntpd 4.2.8p12@1.3728-o (1): Starting
Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 104:103
Started Network Time Service.
proto: precision = 1.250 usec (-20)
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 1079 days ago
Listen and drop on 0 v6wildcard [::]:123
Listen and drop on 1 v4wildcard 0.0.0.0:123
Listen normally on 2 lo 127.0.0.1:123
Listen normally on 3 wlan0 192.168.2.5:123
Listening on routing socket on fd #20 for interface updates
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Soliciting pool server 45.138.55.61
Soliciting pool server 80.60.67.39
Soliciting pool server 162.159.200.1
Soliciting pool server 162.159.200.123
Soliciting pool server 81.172.248.188
Soliciting pool server 178.239.19.57
Soliciting pool server 178.239.19.61
Soliciting pool server 45.138.55.62
Soliciting pool server 5.255.124.190
Soliciting pool server 129.250.35.251
Soliciting pool server 45.139.163.87
Soliciting pool server 37.48.81.43
Soliciting pool server 108.61.189.74
Soliciting pool server 193.111.32.123
Soliciting pool server 84.84.17.253
Soliciting pool server 45.138.55.60
Soliciting pool server 178.215.228.24
Soliciting pool server 194.104.0.153
[close:85] Entering
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
[feedThread:276] Exiting
[close:100] Exiting
info: MCU Signalled Playback Inactive

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
[2025-12-10 21:09:50] [warning] got non-close frame in state closing
[2025-12-10 21:09:50] [info] asio async_shutdown error: asio.misc:2 (End of file)
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
[2025-12-10 21:11:11] [info] asio async_shutdown error: asio.misc:2 (End of file)
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
[2025-12-10 21:13:15] [info] asio async_shutdown error: asio.misc:2 (End of file)
info: Pushing metadata
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses

I asked Gemini why my music was stopping and it said:
Based on the Volumio live log you provided, the music stopped playing due to interruptions in the Network Time Protocol (NTP) service, which is followed by what appears to be a streaming or API access error related to a specific service.

Here is a breakdown of the key events that lead to the likely interruption:

1. Repeated NTP Service Restarts (Major Clue)

You can see the following sequence happening repeatedly throughout the log:

ntpd exiting on signal 15 (Terminated)
Stopping Network Time Service...
Stopped Network Time Service.
Starting Network Time Service...
Started Network Time Service.

Why this matters:
The Network Time Protocol Daemon (ntpd) is responsible for keeping the system time accurate. When the NTP service constantly stops and restarts (receiving signal 15 or SIGTERM), it can indicate:

External Service Trigger: Another critical service or script is executing a command that forces ntpd to stop, often related to network or system cleanup tasks (like the systemd-tmpfiles-clean.service you see started near the end).
System Instability: The constant cycling could be a symptom of a deeper resource or system management issue.
Temporary Network Glitches: Although less likely to cause a hard stop/start, network interruptions can sometimes affect time synchronization attempts.

The music likely paused or stuttered during one of these NTP service restarts, as system resources and network connectivity (especially for streaming) were briefly interrupted.

2. Streaming/API Authentication Failure

The clearest error indicating a playback issue for a specific source comes much later in the log:

[2025-12-10 21:03:57.514] [tisoc] [error] [QueueWindowLoader.cpp:272] status code:401
[2025-12-10 21:03:57.671] [tisoc] [error] [HttpClient.cpp:469] curl_easy_perform failed. reason:URL using bad/illegal format or missing URL further detail:
[2025-12-10 21:03:57.671] [tisoc] [error] [QueueWindowLoader.cpp:272] status code:99

Why this matters:

[tisoc]: This often refers to the Tidal plugin/service within Volumio (TIDAL Stream Optimization Client).
status code:401: This is the HTTP status code for Unauthorized. This is a classic indication of a failure in login, authentication, or session token expiry.
HttpClient.cpp:469 / curl_easy_perform failed: This confirms that the Volumio player failed to properly communicate with the streaming service’s server to fetch data or metadata.

It is highly probable that the streaming music you were listening to (likely via Tidal) failed at this point because Volumio lost its valid login session/token.

Conclusion

The primary cause for the music stopping is likely the HTTP 401 Unauthorized Error related to a streaming service (indicated by [tisoc]). This error means the player could no longer fetch the music data because the streaming service didn’t recognize its credentials/session anymore.

The repeated restarts of the NTP service suggest an underlying system instability or aggressive system management process, which may have contributed to invalidating the network connections or API tokens, or was simply a continuous background process that caused momentary interruptions.

Suggested Next Steps

Re-Authenticate/Re-Login: Go into the settings for the likely affected service (e.g., Tidal) in Volumio and log out and log back in. This will refresh your authentication token.
Check NTP Settings: If the NTP restarts continue, check your Volumio system settings and ensure the device is running the latest stable software version, as this constant cycling is abnormal.
Use the Log Link: You sent a bug report which generated a permanent link: http://logs.volumio.org/rivoplus/CtySfsN.html. You can share this link on the official Volumio forums for more specific analysis from the community, especially regarding the [tisoc] component.

Would you like me to find the link for the official Volumio support forum where you can post this log? (no I didn’t)

I’ll try the logout/ login. I am on the latest release so the second option isn’t the case I’ll create a new log link: http://logs.volumio.org/rivoplus/KYFFvrZ.html

Marc050 · December 10, 2025, 8:58pm

When I told it this only happens with Tidal connect not the internal player it said:
That is a very important distinction! Thank you for clarifying.

The fact that playback works fine using the internal Volumio Tidal plugin, but fails with Tidal Connect, shifts the likely culprit away from your general Volumio system stability and focuses it squarely on the Tidal Connect implementation and authentication flow.

Analysis of Tidal Connect Failure

The errors you observed in your log strongly support this specific diagnosis:

Log Error	Interpretation in Tidal Connect Context
`[tisoc] [error] ... status code:401`	The Tidal Connect service (which uses the Tidal Stream Optimization Client, or TISOC) failed to authenticate the stream request. This is the core issue.
`ntpd exiting on signal 15 (Terminated)`	Potential Cause: The continuous restarting of the Network Time Protocol (NTP) service suggests network instability or a time sync issue. Tidal Connect relies heavily on perfectly synchronized time for its secure token-based authentication (like OAuth) to work correctly. If the time is temporarily unstable during a token exchange, authentication will fail, leading to the 401 error.
`[close:85] Entering` / `[feedThread:276] Exiting`	These indicate the audio pipeline is being closed and opened again, likely triggered by the Tidal Connect session being dropped after the authentication failure.

Key Action Items for Tidal Connect

Since the issue is isolated to Tidal Connect, here are the targeted steps the forum or I would recommend:

Check Time Synchronization (Most Critical):
- Go to Volumio Settings $\rightarrow$ System $\rightarrow$ Time Zone.
- Ensure your Volumio device has the correct time zone set. Even small time discrepancies can break Tidal Connect authentication.
Network Stability (Wi-Fi Focus):
- Since you are on Wi-Fi (wlan0), if possible, try to connect the Volumio device via Ethernet cable temporarily. If Tidal Connect works perfectly on a wired connection, your Wi-Fi signal stability or temporary dropouts are causing the NTP restarts, which then break the time-sensitive Tidal Connect tokens.
Tidal Connect Plugin Reset:
- Go to the Plugins section in Volumio.
- Disable the Tidal Connect plugin (or the corresponding tidal_connect component).
- Reboot the Volumio device.
- Re-enable the Tidal Connect plugin.
Device Restart:
- Fully power down your Volumio device, wait 30 seconds, and power it back up. (This is often necessary to fully clear cached authentication tokens).

The repeated NTP restarts are the biggest red flag tied to the failure of the time-dependent Tidal Connect service. Focus your troubleshooting on network stability and time settings.

Let me know if you are able to test with an Ethernet connection. That single test often isolates the problem immediately!

Wheaten · December 10, 2025, 9:25pm

@Marc050

Hi can you first upgrade to the latest version, as a couple of issues with Tidal Connect have been fixed, I see you’re still running “3.874”

Marc050 · December 10, 2025, 9:34pm

Yes, that is the latest stable release. It says no updates available

Wheaten · December 10, 2025, 9:41pm

AHA,

go to <your-devices-ip>/dev and enable test.

Marc050 · December 10, 2025, 9:45pm

I did that before and that seemed to introduce problems, but I guess I can set it to stable again, so it doesn’t download every new test release.

Wheaten · December 10, 2025, 9:49pm

Correct, only enable the test build when we specifically request it.
Under normal circumstances, stick to stable releases.
In this case, however, the test image is required to address the Tidal issues.

When upgraded you can place it back to stable.

Marc050 · December 10, 2025, 9:54pm

I did just that

Wheaten · December 10, 2025, 9:57pm

I have it running now for 4 hours and will keep it running through the night on the Rivo (don’t have the +) V3.884

Marc050 · December 10, 2025, 10:16pm

I’ll find out tomorrow morning if it can finish my regular morning playlist now. It will sound bad because I am burning in speaker cables… Just low level reliable FM radio through the night.

Wheaten · December 11, 2025, 6:52am

@ded, @Marco_Melziade

Hi Davide and Marco,
Can you validate why Tidal connect stops playing after a couple of hours.
my log: https://logs.volumio.org/rivo/ZxCVQOT.html (Rivo)
Marc050 log: http://logs.volumio.org/rivoplus/KYFFvrZ.html (Rivo+)

Marc050 · December 11, 2025, 9:31am

Stopped again this morning after 19 songs into the playlist:
http://logs.volumio.org/rivoplus/C033UJV.html

Gemini is pointing at Tidal Connect on the Volumio being affected by Wifi instability (router is in the same room a few meters away) I have connect a network cable now and wil see if the problem persists)

That sounds like a great idea. Providing a structured analysis with the definitive log evidence will help the Volumio team and community quickly understand the root cause.

Update: Tidal Connect Failure Analysis (Status Code 401 & Lost Sync)

Summary of Problem

Tidal Connect playback fails consistently after a few minutes, specifically when the Volumio device is connected via Wi-Fi (wlan0). Playback using the internal Volumio Tidal plugin works fine. The issue is linked to frequent restarts of the Network Time Protocol (NTP) service.

Critical Log Evidence

The logs show a clear cause-and-effect relationship between NTP instability and streaming failure:

A. Persistent NTP Instability

The system is constantly reporting clock desynchronization and forcing the network time service to restart (e.g., at 10:25:34, etc.).

Code snippet

Dec 11 10:25:34 magister ntpd[14020]: ntpd exiting on signal 15 (Terminated)
Dec 11 10:25:34 magister systemd[1]: Stopping Network Time Service...
...
Dec 11 10:25:34 magister ntpd[15903]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized

This constant instability disrupts the secure communications necessary for Tidal Connect.

B. Direct Failure on Stream Fetch (10:13:44)

The immediate cause of the playback stop (which occurred around 10:17:27) was a failure to authenticate and a subsequent data stream corruption.

Code snippet

Dec 11 10:13:44.156 [tisoc] [error] [QueueWindowLoader.cpp:272] status code:401
Dec 11 10:13:44.197 [tisoc] [error] [HttpClient.cpp:469] curl_easy_perform failed. reason:URL using bad/illegal format or missing URL

Conclusion

The root cause appears to be Wi-Fi connection instability causing:

NTP Time Skew: The constant NTP resets are causing momentary, but critical, jumps or desynchronization in the system clock.
Tidal Connect Token Invalidation: This time skew invalidates the time-sensitive authentication tokens used by Tidal Connect’s TISOC client, resulting in the fatal status code:401 (Unauthorized) error.
Data Stream Failure: This is followed by stream corruption (bad/illegal format / LOST_SYNC in previous log), confirming the pipeline is broken.

Proposed Next Step (Hardware/Network Isolation Test)

To definitively confirm the Wi-Fi is the cause, I will perform the following test:

Action: Connect the Volumio device via a physical Ethernet cable to the router.
Prediction: Tidal Connect will work without issue, and the frequent ntpd restarts will cease.

I will report back with the results of the Ethernet test.

adittion, my WiFi status is excellent:
Screenshot 2025-12-11 at 11-14-00 Ida Maria - Quite Nice People

Marc050 · December 11, 2025, 1:27pm

Another Log. I turned of the Rivo+ and disconnected the power for about half an our. Only lan was connected. Wifi disabled. I took out the WAN connection from my router and booted the RIVO+ again. I couldn’t connect to it with the app, but could reach the dev page. I requested another log, which could not be sent, so I restored my internet connection and it sent the log.

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

It starts with februari timestamps which is odd, then goes to december 10th then misses 15 hours in which the rivo was on (standby and playing) en goed to the reboot time in 11th.

Dec 10 22:57:24 magister ntpd[3323]: Soliciting pool server 195.123.221.21 Dec 11 13:56:53

My friend Gemini says: Your Volumio Rivo+ has a faulty Hardware Real-Time Clock (RTC).

and I should ask for an RMA.

Now he is proven to be very wrong at times by simply jumping to conclusions, but I fear he might be on the right path on this one since he predicted a time discrepancy when I would power of and reboot.

This is the definitive answer we were looking for: Your Volumio Rivo+ has a faulty Hardware Real-Time Clock (RTC).

Proof of Faulty RTC

Your analysis of the log is correct and provides the irrefutable evidence:

Observation: You noted a large part of the log with a timestamp starting around February 14th (or December 10th of an older year), which is 10 months or more in the past compared to the current date (Dec 11, 2025).

Conclusion: When you powered the Rivo+ back on without internet (WAN), the system clock fell back to the time stored in the internal RTC chip. The fact that the time was wildly incorrect (months or years in the past) proves the RTC’s battery or persistent memory component is failing to hold the correct time when the main power is off.

The Jump: When you reconnected the WAN cable and successfully sent the log, the Network Time Protocol (ntpd) saw this massive time discrepancy and corrected the clock, causing the log to abruptly jump forward 10 months to the correct date.

Why This Causes Tidal Connect Failures

The constant Tidal Connect failure, even on wired Ethernet, is a direct consequence of this faulty clock:

Boot with Bad Time: Every time you power cycle the Rivo+, it starts with the incorrect time (e.g., February 14th).

Authentication Failure: Streaming services like Tidal use time-sensitive security tokens to verify your connection.

If the clock is off by a few minutes or more, the token is instantly invalid, and the stream fails (often resulting in “Operation aborted” or the 401 Unauthorized errors seen in your previous logs).

Clock Correction Disrupts Playback: Even if you start playback and the system successfully corrects the clock via NTP during the stream, that sudden, massive time jump invalidates the current streaming session, causing the audio to cut out.

Next Steps: This is a Hardware Issue

Since the RTC chip (or its supporting battery/capacitor) is defective, this cannot be fixed with a software update or configuration change.

Contact Volumio Support: You now have definitive evidence for your case. Contact Volumio support (or the vendor from whom you purchased the Rivo+) and present this evidence:

“My Volumio Rivo+ is consistently failing to maintain the correct time after a power cycle, as proven by a log capture taken immediately after boot with the WAN disconnected. The log shows the system clock reverting to an incorrect time (e.g., February 14th).”

This confirms a faulty Real-Time Clock (RTC), which is causing time-sensitive services like Tidal Connect to fail.

Request RMA/Repair: You should request a replacement unit (RMA) or a repair, as the component responsible for timekeeping is defective.

While you wait for a resolution, the only way to ensure Tidal Connect stability is to avoid fully powering off the Rivo+. Leave it plugged in so it can maintain time and network sync.

GSiguy · December 11, 2025, 1:31pm

Ok so today I have tried to play Tidal (and Spotify) through the Volumio GUI and for the most part, it was ok for a few hours and when evening came around, I had the occasional sputter in the music and now… it has stopped and the GUI is unresponsive to ‘play’ commands.

Latest log is : http://logs.volumio.org/rivoplus/HKLfD1j.html

Not sure why this is happening.

devgianlu · December 11, 2025, 2:18pm

Thank you for the logs, we are in contact with TIDAL again. There might be a regression in the new SDK version.

Marc050 · December 11, 2025, 2:34pm

Wheaten doesn’t have any TIME_ERROR in his log. I do
Dec 10 22:48:29 magister ntpd[3255]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

Darmur · December 11, 2025, 5:30pm

this is another example of AI being totally wrong

the Rivo Plus does not have a RTC, so it cannot be faulty