Bluesound BUG with Spotify - no change in 6 months - no audio after 1-3 tracks
AnsweredDevices
Soundbar, sub+, 2x Flexi - home theater group
Software
-
BluOS: latest version (issue started after recent updates)
-
Spotify app: Android 14.0.3
-
Also tested on iPhone (same behavior)
Exact issue description
Spotify Connect playback works normally at first.
When a track ends and the next track starts:
-
audio stops
-
Spotify / BluOS progress bar continues
-
device remains connected
-
restarting the track or skipping back/forward restores audio
Initially this happened occasionally (e.g. every few tracks).
Now it often happens after every track.
Reproduction steps
-
Start playback via Spotify Connect to Bluesound system
-
Let the track finish
-
Next track starts → no audio, timer running
-
Restart track → audio resumes
Reproducible consistently.
What has been ruled out
-
Wired Ethernet only (no Wi-Fi for players)
-
Multiple switches replaced
-
Different router tested
-
IGMP on/off
-
IPv6 disabled
-
DNS changes
-
Different controllers (Android + iOS)
-
Same issue when Spotify is started from within BluOS
Additional observation
-
Similar behavior occurs very rarely with Tidal
-
Strongly suggests a BluOS stream session / track transition issue, not a network problem
Conclusion
This appears to be a BluOS streaming / Spotify Connect track handoff bug.
The issue is reproducible, independent of network configuration, and affects multiroom playback reliability.
-
Official comment
Hi Jiří,
I have escalated your feedback to a support request. A member of our support crew will reach out to you soon. -
I'm facing exectly the same issue.
Unfortunately we cannot get the logs anymore. I would like to figure out if it is a router/network problem or not0 -
Thank you Mark T. I am desperate. I’d like to add an important observation. After a full power cycle of all Bluesound players (e.g. after a power outage or manual unplug), Spotify works flawlessly for about an hour. The issues only start the next day: playback stops after the 2nd or 3rd track (progress bar continues). This strongly feels like some internal state/buffer/cache inside the Bluesound devices getting corrupted over time — not on the phone (app cache is regularly cleared), but on the players themselves. I’ve tried many network-related solutions already and today I’m even installing a new router, but this behavior consistently points to a time-dependent issue inside the Bluesound Spotify Connect implementation.
0 -
Hello Matthias, I'm afraid to hope that the new router will help, but I'm trying to believe it will. I'll keep you posted.
0 -
For me, it works for a few minutes when I log out of Spotify and log back in.
But I only have one Bluesound Node 130, connected to a switch, which is then connected to the router.
I've had this issue since I changed my router a week before Christmas, because the last one was defective.0 -
Hello,
such a problem here since Chistmas on my NAD M10 V2. Spotify support wrote me they have found out now and fix it in an update, but after the last update it still happens.
Is it a Spotify or a BluOS problem?? No one tells the true story!!!
Shall I talk to BluOS support too??
You can look at your watch when it starts: on weekdays at 19:17.
0 -
Since the last update I have the same problem. Does anybody know if there is a solution?
0 -
After extensive testing, I have narrowed the problem down to the following:
-
Playback of full albums on Spotify works perfectly without interruptions.
-
The issue occurs only when playing Spotify playlists.
-
After 2–3 tracks, playback becomes silent while the track timer continues running.
-
The issue appears to happen when the next track is loaded from a different album/source (likely a different server/CDN location).
-
This happens both when using Spotify Connect and when using Spotify directly inside the BluOS app.
-
TIDAL works flawlessly (albums and playlists).
-
Spotify works correctly on all other devices in my network.
-
Network infrastructure has been tested and simplified (single router setup, direct wired connection) with the same result.
It seems the problem may be related to how BluOS handles stream handoff between tracks from different sources, possibly during HTTPS stream reinitialization. The issue appears more sensitive when Spatial Audio content is involved, but it has better sound.
Given that:
-
Albums play without issue
-
TIDAL works without issue
-
Spotify works on other devices
-
The problem occurs only on the Bluesound device
this suggests a potential issue in the BluOS Spotify implementation rather than a general network problem.
Please let me know if you need firmware version details, logs, or any additional diagnostics from my side.
1 -
-
Great work Jiri, thank you. Let’s hope Bluesound will pick this up and fix it. The problem is pretty annoying.
0 -
Hello,
I got your messages now, so I got back to this thread.
For me the problem is over since 2 or 3 weeks.
The BluOS support told me it was a Spotify thing and Spotify told me it was a problem on their side and it should be fixed by an update of them.I got no message that they have fixed it yet, but it works now for me.
It seems that it was something with the syncronisation of the stream.
I'm glad that is over for me now. I think you have to contact the Spotify support chat for getting some help.
Best regards
1
Please sign in to leave a comment.
Comments
10 comments