# Tidal Connect Failures

**URL:** <https://community.volumio.com/t/tidal-connect-failures/64980>\
**Category:** Help\
**Tags:** tidalconnect, tidal, myvolumio\
**Created:** [January 21, 2024, 3:56pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980 "2024-01-21T15:56:31Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gareths](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/71c47a/32.png) [@Gareths](https://community.volumio.com/u/Gareths)\
**Post date:** [January 21, 2024, 3:56pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/1 "2024-01-21T15:56:31Z")

</div>

Hi,

First off thanks for this great audio player OS!

I’m running a Raspberry Pi 4 with Allo DigiOne DAC and Volumio 3.569. I have persistent issues with Tidal Connect. Connecting is fine but if I skip tracks backwards/forwards (even within the same album) sooner or later it will stop responding. Also scrubbing within the track will do this.

From this point on attempting to do anything with Volumio (e.g. playing a radio station) will result in the following error:

“Failed to open “alsa” (alsa); Failed to open ALSA device “Volumio”: Device or resource busy”

Only a restart will get things going again.

Any ideas?

---

<div class="post-metadata">

**Author:** ![AweLoi](https://community.volumio.com/letter_avatar_proxy/v4/letter/a/d26b3c/32.png) [@AweLoi](https://community.volumio.com/u/AweLoi)\
**Post date:** [January 23, 2024, 9:02pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/2 "2024-01-23T21:02:36Z")

</div>

I have the exact same problem. When I skip tracks with Tidal Connect Tidal often freeze and restarting Volumio is the only thing that resets it. A solution would be very welcome. I will most likely leave Volumio if there is o fix for this since it makes Tidal almost unusable.

Using Raspberry Pi 3B+

---

<div class="post-metadata">

**Author:** ![volumio](https://community.volumio.com/user_avatar/community.volumio.com/volumio/32/3_2.png) [@volumio](https://community.volumio.com/u/volumio)\
**Post date:** [January 23, 2024, 9:25pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/3 "2024-01-23T21:25:08Z")

</div>

Thanks for the heads up.we are looking into it

---

<div class="post-metadata">

**Author:** ![Gareths](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/71c47a/32.png) [@Gareths](https://community.volumio.com/u/Gareths)\
**Post date:** [January 23, 2024, 9:36pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/4 "2024-01-23T21:36:11Z")

</div>

Thanks. If you need me to test anything or provide logs I can do that. Tidal Connect is one of the main features I use on Volumio so it would be great to see it running well.

---

<div class="post-metadata">

**Author:** ![AweLoi](https://community.volumio.com/letter_avatar_proxy/v4/letter/a/d26b3c/32.png) [@AweLoi](https://community.volumio.com/u/AweLoi)\
**Post date:** [January 24, 2024, 3:23pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/5 "2024-01-24T15:23:15Z")

</div>

There are no problems when playing Tidal from the Volumio app, only trough Connect.

---

<div class="post-metadata">

**Author:** ![volumio](https://community.volumio.com/user_avatar/community.volumio.com/volumio/32/3_2.png) [@volumio](https://community.volumio.com/u/volumio)\
**Post date:** [January 24, 2024, 4:18pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/6 "2024-01-24T16:18:41Z")

</div>

> [@Gareths](#):
>
> Thanks. If you need me to test anything or provide logs I can do that. Tidal Connect is one of the main features I use on Volumio so it would be great to see it running well.

Yes, please provide some logs as soon as the issue occurs. Thanks

---

<div class="post-metadata">

**Author:** ![AweLoi](https://community.volumio.com/letter_avatar_proxy/v4/letter/a/d26b3c/32.png) [@AweLoi](https://community.volumio.com/u/AweLoi)\
**Post date:** [January 24, 2024, 4:55pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/7 "2024-01-24T16:55:00Z")

</div>

I sent you a couple of logs too since I have the same problem. Hope it helps.

---

<div class="post-metadata">

**Author:** ![gkkpch](https://community.volumio.com/user_avatar/community.volumio.com/gkkpch/32/17306_2.png) [@gkkpch](https://community.volumio.com/u/gkkpch)\
**Post date:** [January 24, 2024, 4:57pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/8 "2024-01-24T16:57:07Z")

</div>

when you create a log, you should post the url, which is returned to you, here

---

<div class="post-metadata">

**Author:** ![Gareths](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/71c47a/32.png) [@Gareths](https://community.volumio.com/u/Gareths)\
**Post date:** [February 6, 2024, 4:40pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/9 "2024-02-06T16:40:49Z")

</div>

I have some time now to create debug logs for this issue. But… how do I do that 🙂

Is there an article somewhere on creating debug logs? Do I need to SSH into the device?

Thanks

---

<div class="post-metadata">

**Author:** ![gkkpch](https://community.volumio.com/user_avatar/community.volumio.com/gkkpch/32/17306_2.png) [@gkkpch](https://community.volumio.com/u/gkkpch)\
**Post date:** [February 6, 2024, 11:15pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/10 "2024-02-06T23:15:28Z")

</div>

[How to create a log](https://help.volumio.com/help/how-to-send-a-log-link-for-a-bug-report)

Post the URL here please

---

<div class="post-metadata">

**Author:** ![Gareths](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/71c47a/32.png) [@Gareths](https://community.volumio.com/u/Gareths)\
**Post date:** [February 7, 2024, 6:05pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/11 "2024-02-07T18:05:56Z")

</div>

[http://logs.volumio.org/volumio/gGGiaSL.html](http://logs.volumio.org/volumio/gGGiaSL.html)

Immediately after a forward / backward track skip failure with tidal connect. Only takes about 10 skips to fail usually.

---

<div class="post-metadata">

**Author:** ![Gareths](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/71c47a/32.png) [@Gareths](https://community.volumio.com/u/Gareths)\
**Post date:** [February 7, 2024, 6:16pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/12 "2024-02-07T18:16:38Z")

</div>

and then the log for the ‘failed to open ALSA device’ error that is shown immediately after trying to play any other media. in this case web radio.

[http://logs.volumio.org/volumio/GbGT0b3.html](http://logs.volumio.org/volumio/GbGT0b3.html)

---

<div class="post-metadata">

**Author:** ![G-rig](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/dec6dc/32.png) [@G-rig](https://community.volumio.com/u/G-rig)\
**Post date:** [February 11, 2024, 7:13am UTC](https://community.volumio.com/t/tidal-connect-failures/64980/13 "2024-02-11T07:13:48Z")

</div>

Hey guys something isn’t so great after the last update wish I didn’t do it. Tidal connect seems to bomb out after a while. Didn’t used to happen.

Will try and get a log file sometime.

---

<div class="post-metadata">

**Author:** ![Gareths](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/71c47a/32.png) [@Gareths](https://community.volumio.com/u/Gareths)\
**Post date:** [February 11, 2024, 2:10pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/14 "2024-02-11T14:10:44Z")

</div>

If I change the DAC settings, e.g. disable the Allo Digi One and then enable it again, that seems to get things moving again. Obviously that isn’t a solution but maybe it helps to debug this.

---

<div class="post-metadata">

**Author:** ![adam\_bernatek](https://community.volumio.com/user_avatar/community.volumio.com/adam_bernatek/32/23011_2.png) [@adam\_bernatek](https://community.volumio.com/u/adam_bernatek)\
**Post date:** [February 14, 2024, 3:46pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/15 "2024-02-14T15:46:33Z")

</div>

It seems to appears less often but I still got this issues on my devices when I’m switching songs with Tidal Connect.

---

<div class="post-metadata">

**Author:** ![G-rig](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/dec6dc/32.png) [@G-rig](https://community.volumio.com/u/G-rig)\
**Post date:** [February 17, 2024, 1:53am UTC](https://community.volumio.com/t/tidal-connect-failures/64980/16 "2024-02-17T01:53:10Z")

</div>

> [@adam\_bernatek](#):
>
> ems to appears less often but I still got this issues on my devices when I’m switching songs with Tidal Connect.

Yes that’s a good trick i am using more often.  
I am using an RPi 4 - seems that the cables on the side are very sensitive and if you touch/move them it diconnects and connects all the time so have to be careful not to bump them - could have been the last issue.

ps. just did the update

---

<div class="post-metadata">

**Author:** ![sladflob](https://community.volumio.com/letter_avatar_proxy/v4/letter/s/45deac/32.png) [@sladflob](https://community.volumio.com/u/sladflob)\
**Post date:** [February 18, 2024, 12:31am UTC](https://community.volumio.com/t/tidal-connect-failures/64980/17 "2024-02-18T00:31:00Z")

</div>

Just came here to say “me too”.

I want to switch from using Qobuz to Tidal, partly because I like that I can use the Tidal app with Tidal Connect, but when I tried it a few weeks ago I noticed this problem straight away. The recent update didn’t fix it.

It happens for me using both my HiFiBerry Digi+ and USB output. I’ve been using the workaround someone posted to get things working again but that’s hardly a solution.

I’ve lodged a bug report but from my experience this doesn’t mean much, despite the fact that we are paying customers. Maybe if everyone experiencing the problem does the same it’ll gain some traction.

edit: I just generated another log with the last thing in it being a failure. It happened when I tried to advance track from Tea for the Tillerman. I then did the “trick” of resetting the output device to get it working again. I can’t see anything obviously wrong in there.

[http://logs.volumio.org/volumio/pUGnyxZ.html](http://logs.volumio.org/volumio/pUGnyxZ.html)

---

<div class="post-metadata">

**Author:** ![G-rig](https://community.volumio.com/letter_avatar_proxy/v4/letter/g/dec6dc/32.png) [@G-rig](https://community.volumio.com/u/G-rig)\
**Post date:** [February 18, 2024, 12:05pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/18 "2024-02-18T12:05:39Z")

</div>

Wish I didn’t do the last update, Tidal connect fkd somehow. I can usually switch between the native volumio app and tidal, but sitting in silence again.

Hopefully there is a fix

 ![Screenshot_20240218-220313](https://community.volumio.com/uploads/default/original/3X/b/6/b636a3667d6747a54084919852e0d5bad62704c5.png)

---

<div class="post-metadata">

**Author:** ![sladflob](https://community.volumio.com/letter_avatar_proxy/v4/letter/s/45deac/32.png) [@sladflob](https://community.volumio.com/u/sladflob)\
**Post date:** [February 27, 2024, 12:34pm UTC](https://community.volumio.com/t/tidal-connect-failures/64980/19 "2024-02-27T12:34:13Z")

</div>

I just updated to 3.631 and the problem still occurs. Here’s a new log:

[http://logs.volumio.org/volumio/i7aHACl.html](http://logs.volumio.org/volumio/i7aHACl.html)

---

<div class="post-metadata">

**Author:** ![sladflob](https://community.volumio.com/letter_avatar_proxy/v4/letter/s/45deac/32.png) [@sladflob](https://community.volumio.com/u/sladflob)\
**Post date:** [February 29, 2024, 12:33am UTC](https://community.volumio.com/t/tidal-connect-failures/64980/20 "2024-02-29T00:33:58Z")

</div>

Updated to 3.632 and problem still occurs. It now seems to occur after just one or two advances to the next track, rendering Tidal Connect essentially unusable. New log:

[http://logs.volumio.org/volumio/eTzGqqO.html](http://logs.volumio.org/volumio/eTzGqqO.html)

[Next page](https://community.volumio.com/t/tidal-connect-failures/64980.md?page=2)
