FWIW, when Tidal Connect would run into more frequent connection hiccups before, I managed to reproduce the error on another brand’s streaming system + UI that runs on an AVR. And the solution with that system was… to clear my queue, turn it off, then restart it and attempt playback again.
That’s what led me to think the issue had more to do with Tidal Connect itself than with Volumio - at least for that particular issue.
Yes it’s definitely a tidal connect issues not hardware.
Is Qobuz connect up and running yet (not that I’m interested)?
No it’s still in beta by Qobuz themselves.
Well I ended up getting a new phone. I don’t want to jinx it too early but had a good responsive session for an hour or so yesterday with tidal connect. 
Tried logging in and out. Tidal connect is stubbornly refusing to show volumio as a device. Haven’t seen it for many weeks now. Super disappointed. Has anyone else got any bright ideas??
I don’t understand but after trying literally nothing different it’s worked tonight!! So flakey but don’t want to jinx it so just going along for the ride…
Glad it’s working now. Let us know how it goes from here on.
Hi, this is the log for whenever Tidal Connect fails and blocks ALSA.
As reported before, the behavior is that there’s suddenly no audio from a loaded Tidal track, although the track seems to be playing from the Volumio UI (but not from the Tidal app, where there’s no playback indicators). Upon stopping Tidal Connect and selecting a local track, this error is registered in the system log:
Sep 27 18:54 : exception: Failed to open "alsa" (alsa); Failed to open ALSA device "volumio": Device or resource busy
Sep 27 18:54 : player: problems opening audio device while playing "INTERNAL/Blackfield - II/01 Blackfield - Once.flac"
Sep 27 18:57 : player: played "INTERNAL/Blackfield - II/01 Blackfield - Once.flac"
ALSA lib /home/pi/volumio-alsa-plugin/src/pcm_volumioswitch.c:143:(_snd_pcm_volumioswitch_open_target_pcm) PCM Volumio ALSA Switch Plugin failed to open the switcher target pcm volumioLocalPlayback`
Upon further inspection, I’ve found this line when the error was triggered:
nomad vtcs[22334]: [2024-09-27 18:38:01.738] [tisoc] [warning] [flac_decoder.cpp:282] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
I tested it again, skipping tracks randomly from a playlist, and got these errors all within a minute, when Tidal Connect failed again and blocked ALSA:
vtcs[27745]: [tisoc] [warning] [PlaybackControllerImpl.cpp:510] Illegal state:1
vtcs[27745]: [2024-09-27 19:15:02.772] [tisoc] [warning] [PlaybackControllerImpl.cpp:214] Ignore play request because playback state is not STARTED. state_=2, playstate_=1, player_state_=0`
vtcs[27745]: [tisoc] [warning] [flac_decoder.cpp:282] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
vtcs[27745]: [tisoc] [warning] [flac_decoder.cpp:282] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_BAD_HEADER
vtcs[27745]: [2024-09-27 19:15:03.903] [tisoc] [warning] [flac_decoder.cpp:282] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC`
vtcs[27745]: ALSA lib /home/pi/volumio-alsa-plugin/src/pcm_volumioswitch.c:912:(_snd_pcm_volumioswitch_advance) PCM volumioMultiRoomServer cannot write to target PCM volumioOutput as it has failed its update check.
vtcs[27745]: [tisoc] [warning] [PlaybackControllerImpl.cpp:214] Ignore play request because playback state is not STARTED. state_=2, playstate_=1, player_state_=0`
vtcs[27745]: [tisoc] [warning] [PlaybackControllerImpl.cpp:214] Ignore play request because playback state is not STARTED. state_=2, playstate_=1, player_state_=0`
[tisoc] [warning] [TidalEvents.cpp:446] Continue event sending result: 502
Hope it helps.
Also, why does the Spotify Plugin constantly receive Volume updates? When not in use, like when playing a local file, Tidal Connect, or Tidal file; every time a track changes a line like this appears:
volumio[981]: SPOTIFY: RECEIVED VOLUMIO VOLUME 22