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
Having something similar I think. When it happens, Sources says Tidal is logged in ok, but no Tidal content is available. I fix it by logging out and back in to Tidal. Then it works fine again for two or three days.
Edit: I’m running Volumio 4.016 on a wired Pi5.
Sounds like the same.
I’m rebooting. Works faster than logout and Login.
My daily cronjob at night for rebooting all volumios does Not Help.
And I thought I was the only one with this problem. I have exactly the same error pattern with Tidal.
Asus Tinkerboard (4.4.71+ armv7l) with volumio System version 3.832
I have same problem using Volumio Motivo that auto updates to latest software version. I disconnect from Tidal then reconnect/relogin to Tidal through Volumio Sources drop-down to restore access to my music. I tried factory reset and problem persists.
It seems to take a couple hours of idle for the problem to appear. Reboot solves the problem but it’s faster to sign out and back in to Tidal.
I’ve had the same thing for a few days, I confirm.
I am also having this issue with Volumio running on a minidsp SHD. Have to disconnect Tidal and log in again multiple times in a day. I am running v3.608
I have this issue to, very annoying. Volumio 3.832 on rpi 3b+ and rpi5.
Same here. Both Tidal integration and Tidal connect disconnects. It is a very annoying problem, making volumio2 useless for me.
Same here. Started maybe a week ago. Volumio 3.832
However, it seems to be irrelevant which version is used.
I have 1x 3.866 and 2x 4.064.
Up - the problem still exists.
It is irrelevant of the Volumio version, it seems. I have Volumio 3.832 and the issue persists.
The first time I encountered the error I was playing music from Tidal via the native Volumio UI. Music stopped all of a sudden, and the Tidal source dissapeared from my menu, even if I was properly logged in and with Tidal Connect enabled.
After a couple of resets, I figured I’d try to log out of Tidal on Volumio and log back in. This seemed to fix it for a bit. Until I encountered the error again. To recap:
Through Volumio, I randomly can’t access my saved albums, artists, or playlists; and search for music doesn’t work (no results come through). When they do, I can’t play results - nothing happens. In this state, although separate, Tidal Connect from a phone or desktop app also do not work - they see the Volumio player, but can’t play anything through it (nothing happens on hitting “play”).
A log out / log in seems to fix things for a bit, until they break again.
Hi,
We are aware of this issue and we are working on it! thanks for the collaboration.
Best regards,
Marco Volumio Support
Hello everyone! I am a new Rivo+ owner, just purchased. I also have the strange issue when using Tidal with Volumio app. The problem is that after exactly 1 hour appear the error “Failed to decode ……got HTTP status 404” and TIDAL doesn’t work furthermore. The only solution to resolve this is to restart the Rivo+, then TIDAL works another 1 hour and so on. It’s very frustrating to restart the device after every hour to play TIDAL. I mention that the connection with router is wired and there is no problem with Ethernet. I didn’t try TIDAL Connect to see if the same problem persists, as I don’t like sound quality on this connection. I had other devices (Blue Node, Eversolo) which have no problems with connection to TIDAL by their own app. Is this a serious issue of Volumio app which can not be fixed? Is there any chance that the problem will be solved?
See the 1st post above your reply. Identified and being worked on,
Hi.
Raspberry Pi 4, SD, v4.067
Logs sent: http://logs.volumio.org/volumio/wuQDseD.html
New image loaded to SD card and booted
Setup Volumio and everything working
Left inactive for approximately 25 minutes
Tidal no longer working. Unable to browse and previously played tracks in play queue do not play.
Works again after reboot
The drop happened right at the end of the log, sometime between 13:17 and 14:07
Thanks
This is an ongoing issue with TIDAL that we are investigating as we speak with them
On my Rivo+ using the Tidal app my playlist regularly just stops playing. I can go to the next song by tapping next, but it will stop after playing that one song again. I have to start playing on my phone and then reconnect to the Rivo+ for the playlist to get going again. I don’t know whether this is a related issue or not.
Hello everyone,
I have been a satisfied user of VOLUMIO streamers for three years now and have had the RIVO Plus since this year but this is the first time I have encountered this problem.
Normally, via UPNP Rendering, I use the RIVO Plus (over a wired LAN not a Wireless one) as the AUDIRVANA Studio End-Point, which allows me to apply both room correction filters and advanced upsampling.
But in this situation, when streaming with TIDAL is managed by AUDIRVANA and not by VOLUMIO, I have no problems whatsoever and music streaming works well without any interruptions, thus ruling out any network or connectivity issues.
However, when I listen to TIDAL streaming via VOLUMIO integrated into the RIVO streamer, after normally playing a few songs, everything crashes irreparably with an error message, forcing me to restart the streamer.
This morning, with the update to the newly released system version 3.872, I was hoping for a resolution to the problem but unfortunately nothing changed.
Adding the observation that streaming also works wonderfully well with the proprietary TIDAL Connect App, it therefore seems quite clear and evident that the problem is attributable to the way in which VOLUMIO manages streaming access permissions with TIDAL, which may have changed some rules.
