Spotify Connect is unusable since BluOS 4.0.2 on my Bluesound node 2i
Answered
Spotify Connect has become unusable for me since the latest BluOS update of my Bluesound node 2i.
Basically, any time I try to play a new song, I have to wait 9 seconds before the new song starts.
The issue is always happening 9 seconds into the track, the progress bar resets and then the song starts.
The support basically told me that I needed to contact Spotify, even though the issue clearly is a bug in the new firmware.
Is anyone else facing this issue?
-
Official comment
This sounds like network lag or problems with DNS Cache in your router.
Please reboot your router, wait 5 minutes, then reboot your BluOS Player, wait 5 more minutes then kill and relaunch the Spotify Apps.
If problems persist, then please select Settings, Send Support Request in the BluOS App and our Support Crew will review your log file and help troubleshoot further.
-
Thank you Tony,
That fixed my first issue. However, now I have another issue. Every so often (every 15 seconds or so) the Spotify Connect stream is muted for about half a second.Is there anything I can do about that? It's quite irritating.
Florent
0 -
And my initial problem is back. Am I really going to have to reset my router every 48 hours?
The connection keeps dropping as well.
Is it possible to downgrade back to a firmware pre-4.0? The streamer is really unstable and it takes all the joy out of listening to music.0 -
We are hearing mixed reports that are suggesting this may be a Spotify Connect issue not limited to BluOS Players but other Spotify Connect devices elsewhere. Please also check with Spotify about a possible service disruption at their end.
0 -
I have several other Spotify Connect device around my home and they don't suffer from any issues.
Honestly, it would be nice to own up a bit to the issues that are caused by the 4.0 firmware instead of blaming Spotify for this.0 -
HI Florent
No changes were made to the Spotify SDK in 4.0. May I suggest this article from Spotify Support on how to reset your Spotify Cache they suggest this issue happens often if you have too many incidents of Spotify associated with your account; https://support.spotify.com/us/article/storage-information/
If this does not resolve your issue, please select Settings, Send Support Request so our Support Crew may investigate further.
0 -
I'm also having issues with spotify connect ever since updating to 4.0.2 on my node 2i. I can't even get spotify to connect to the node 2i anymore. I've tried unplugging my router and node, then plugging them back in 5 min apart in case there was a wifi connection issue, but even through the blueOS app when I try to select spotify as a source, it just spins and never connects or opens spotify anymore. When I reboot the node 2i I can see it again in my available devices on spotify, but if I try to select it it tries to connect for a few seconds then fails and then the node 2i is no longer visible as an option. All my other spotify connect devices (google home, google nest mini) have no issue connecting, and I'm able to control spotify on my laptop from my phone, it seems to be an issue with the updated OS version. Is there any way to revert to the old version until this issue is resolved? My player is basically un-usable.
1 -
Hi Connor
No changes were made to the Spotify SDK in 4.0. May I suggest this article from Spotify Support on how to reset your Spotify Cache they suggest this issue happens often if you have too many incidents of Spotify associated with your account; https://support.spotify.com/us/article/storage-information/
If this does not resolve your issue, please select Settings, Send Support Request so our Support Crew may investigate further.
0 -
Tony, the fact that no changes were made to the Spotify SDK in 4.0 doesn't mean that the Spotify Connect experience has stayed the same with 4.0. I'm sure that you changed a lot of other layers within the firmware and those have an impact on the connectivity.
How can I revert to the previous firmware? I've talked to support but they keep telling me to contact Spotify which is starting to be very frustrating. I just want to be able to listen to music.2 -
agreed, there seems to be nothing wrong with the spotify side, I can still connect to my google home speakers without issue, and I had no issues until I updated my node 2i firmware. It seems a very obvious and simple troubleshooting step to allow us to revert to the previous version and see if that resolves the issue, and if it does, then its clearly an issue in version 4.0.2 and you can actually start looking into a patch for the next version instead of blaming spotify.
1 -
Is this issue at all being looked into? I haven't been able to use my node2i for weeks now, as far as I'm concerned its basically bricked. Can we please get a way to roll back for now until the issue is resolved?
0 -
Unfortunately, I don’t think that it’s being looked at. Support basically tells me to contact Spotify because it’s not Bluesound’s problem.
If they don’t acknowledge the issue they’re not gonna do anything about it.
I basically have to use my Node with Bluetooth, it’s sad but it’s the only way to make it work for now.
0 -
I have a pending support ticket, that just got notified that things are taking longer than expected because of "overwhelming excitement over BluOS 4.0" so it sounds like theres a lot of people complaining, but I agree, the lack of acknowledgement that its clearly an issue with the new version is frustrating. Using bluetooth is a good idea for a workaround for now I guess.
0 -
We are continuing to investigate this problem - (@Conner - sorry we haven't gotten to you yet but your log file has been reviewed by QA). In looking at log files from consumers we are having a hard time seeing issues beyond what would be classified as standard networking disconnects from the Spotify server. The amount of customers reporting this issue is not a disproportionate amount reporting similar Spotify issues before the update...
That being said, we are continuing to investigate as we are always looking to make a better experience...
0 -
I just performed a factory reset, and that seemed to resolve the issue (for now anyway) I'll update if it comes back like it did for Florent
0 -
nevermind, it worked for a single listening session, and then when I left home and came back, it wouldn't connect anymore. I did another full factor reset and this time it didn't even work the first time. It connects, and displays the song that I was last listening to, but the play button just gets a white circle going around it over and over, but it never starts playing. This is clearly an issue with the new firmware. I was really hoping that a factory reset would reset it back to its original version, but it updates as soon as it connects to the internet.
0 -
I have the exact same experience. Crazy. And they’re gonna say that it’s Spotify’s fault 😅
Do you use Ethernet or WiFi?-1 -
Wifi, but I tried plugging it into Ethernet and it didn't help.
-1 -
they keep saying this is not widespread, and therefore must be an issue on the spotify side. But they also are saying their support is slow due to so many support requests following the upgrade to 4.0 sooooo sounds like bs to me. There's clearly an issue, and i'm honestly extremely frustrated that my expensive streamer is bricked as far as I'm concerned.
-1 -
There is a new update, did you give it a try?
-1 -
I'm on 4.2.0 and when I click update it shows there's no newer version available
0 -
Thank you for your feedback
We have evaluated and reviewed both case. Both cases confirm this is a service disruption from Spotify and as suspected not part of BluOS 4.x
Please see my post on October 31st here;May I suggest this article from Spotify Support on how to reset your Spotify Cache they suggest this issue happens often if you have too many incidents of Spotify associated with your account; https://support.spotify.com/us/article/storage-information/
0 -
You’ve really got to be joking.
-1 -
they closed my ticket.. wtf
-1 -
going on spotify web, and removing access to all currently connected apps, and logging out of all instances, and then rebooting my node2i and logging back in on my phone, has resolved the issue again, just like it did last time, but will see if it comes back again after a few hours. I'll update again tomorrow
1 -
I’ve done the whole procedure a couple of times, it plays well for about 10 hours and then the next day it’s broken again
0 -
yeah thats my expectation as well. It seems awfully suspicious that a full reset of everything is required, and yet none of my other spotify endpoints have this problem. If it persists again I'm going to try doing the full spotify reset without resetting the node2i since in theory if its just a problem on spotify's side, there's no reason that the node should need a reset too.
0 -
Hi folks, having the same issue here, my node 2i is bricked regarding Spotify Connect. I reverted back to my 30$, >10 yo audio chrome cast that works flawlessly with Spotify Connect. Please look into this Bluesound
0 -
So I got pretty excited when it was still working a day later, but yesterday it stopped working again, and now I'm back to performing another reboot to get it working again. This is ridiculous that I need to reboot my node 2i every other day for it to work properly. I can't believe the abject denial of our issue which collectively started when they sent out an update. None of my other spotify connect devices are having issues.
0 -
This time what I did was remove blueOS app access on the spotify side, and then a reboot of the node2i, and it started working again. Next time I'll try just a restart of the node2i. There's clearly some kind of memory leak or something on the node2i that's causing it to brick after about a day of normal use.
0
Please sign in to leave a comment.
Comments
31 comments