NODE 2 slows down after version update 3.0.0

Answered

Comments

47 comments

  • Official comment

    Hi Marcus

    I suspect though that when rebooted, your player may been issued a new IP by the router and the old IP is in the router's cache. Try rebooting the router...

    ...if that doesn't work, please send us a log file by selecting Help, Send Support Request so we can help troubleshoot. 

    Comment actions Permalink
  • Avatar
    Marcus Ammer

    Hi Tony, thank you for your advice, however this did not change anything. At the moment I am in contact with Kyle F from your support whom I already sent a log file. They are working on the problem...

    1
    Comment actions Permalink
  • You are in great hands with Kyle... 

    0
    Comment actions Permalink
  • Avatar
    Marcus Ammer

    Got back my player today from service, they found no issue. We tried it out at the dealer - no issue. I come home and nothing has changed for me there. Doesn't work via Wifi, doesn't work via wired LAN connection. The problem is still there. It delivers fast and reliable internet connection via my Apple Time Capsule. All other functions of my router are working flawlessly. I have no idea any more, so doesn't the friendly staff at my dealer's... BIG DISAPPOINTMENT....

    1
    Comment actions Permalink
  • We will be in touch Marcus

    0
    Comment actions Permalink
  • Avatar
    Rrp

    hi Marcus, maybe I know the reason of your problem... a friend of mine has the same problem.

    once BluOS3.0 starts a request over Tidal e.g., it needs a insane and unnecessary  bandwidth of your net connection and if it doesn't get it, it'll stuck. The BluOS2.* needs for a request only above 2 Mbit bandwitdth. 

    so it's a huge bug of the BluOS3.*... nothing to do with the players... the BluOS has to get fixed!!!!

      

     

    0
    Comment actions Permalink
  • Avatar
    Mark Neale

    Wondering if that's similar to the problem I'm having: A month or so ago all my BlueSound devices (3x PN2 and 1xN2) stopped responding. They show on my router, and I can navigate to their web page and run diagnostics, but most functions on their page show : Unable to get current audio settings: Connection refused . This is with a wired connection in all cases and I can reach them via their web page. After various suggestions from the tech support team that did nothing I eventually did a factory restore on all devices and that got them all working again. I accepted a software update 2 days ago (presumably 3.0 or 3.0.2) and they've all stopped again.

    This is very frustrating for the price of the equipment!

    0
    Comment actions Permalink
  • Avatar
    ML

    I’m getting the same problem on two Node 2s also ethernet connected. Although for me the issue started before version3.0.0. Has anyone found a solution? It is very frustrating to have to wait up to 15 seconds for a song to start playing....

    0
    Comment actions Permalink
  • Avatar
    Rrp

    you should read my reply 4 days ago...

    0
    Comment actions Permalink
  • Avatar
    ML

    Is it possible to go back to an older version?

     

    0
    Comment actions Permalink
  • Avatar
    Rrp

    I doubt it, and when possible, the player will want to update to the actual (faulty) firmware again.

    0
    Comment actions Permalink
  • Avatar
    Marcus Ammer

    Hi guys,

    let me tell you how I solved the problem (by myself). I had the Node 2 at the service and they found no issue at all. I then tested the player by myself in the wifi of my dealership and it worked completely normal. Took it home and it showed the same strange behavior as before. So it was clear that my wifi was the problem, which was weird as all other stuff, s.a. Apple TV, worked flawlessly and fast. But as I wanted to upgrade my wifi network anyway as some areas of my home had a poor connection, I decided to get a new router from my internet provider and connect it to a mesh system, consisting of 3 wifi mesh discs that now provide excellent internet download speeds of 40 Mbit in every corner. 1 mesh disc was placed 1 meter close to the Node 2, ensuring excellent wireless connection to the player. But although the Node 2 showed an „excellent“ wifi connection in the help menu, I now had a different issue, although the player would now play songs without any delay: after pairing the iPhone app with the Node 2 it would always loose connection to the player after one or two minutes, so that the player would continue to play a complete playlist without any delay, but leaving me unable to control the player any more via the iPhone app. I then connected the mesh disc via a cable to the Node 2 and this finally led to the solution that the player is now working again as I was used to before upgrading to version 3.0.0. Nevertheless I can still feel that for example loading of album covers takes more time (couple of seconds) than in the genuine Tidal app which is kind of weird as I would expect that those tiny images should load instantly, given the small data sizes compared for example to an HD movie on Apple TV which will start in full resolution within 3 seconds due to my fast internet. To conclude I thinkthat there are compatibility issues with some kind of wireless routers after version 3.0.0. Maybe they changed something with the ports that are allowed to communicate with the player? However it now works for me again, but why exactly remains a mistery for me...

     

    0
    Comment actions Permalink
  • Avatar
    Rrp

    hi Marcus, maybe I know the reason of your problem... a friend of mine has the same problem.

    once BluOS3.0 starts a request over Tidal e.g., it needs a insane and unnecessary  bandwidth of your net connection and if it doesn't get it, it'll stuck. The BluOS2.* needs for a request only above 2 Mbit bandwitdth. 

    so it's a huge bug of the BluOS3.*... nothing to do with the players... the BluOS has to get fixed!!!!

    1
    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    All

    If you are seeing issues, please send us a log file by selecting Help, Send Support Request.

    Also keep in mind that network lag is almost always attributed to the network. When was the last time you rebooted your main router?

     

    0
    Comment actions Permalink
  • Avatar
    Mark Neale

    Rebooting the router made no difference for me, nor did sending in my log files produce anything useful. Only by doing a factory reset to a previous version on all of my devices did I get them back working

    0
    Comment actions Permalink
  • Avatar
    Matteo

    Guys the truth here is that they messed up the software after the 3.0. I was lucky to solve all this just using an old Netgear router instead of the one provided by the broadband company and by the way, BEFORE the update everything was running smoothly. 

    The funny thing is that if use TIDAL on any other device through the native app there aree no issue at all.

    The support team received my log files, then connectd to my device remotely without solving it.

    If you can try another router MAYBE this could solve this, but again it's a software fault...I was considering selling the Bluesound but I'll keep it for the moment.

     

    0
    Comment actions Permalink
  • Avatar
    Rrp

    I don't understand why everyone (Bluesound Support too) is ignoring my advice:

     

    once BluOS3.0 starts a request over Tidal e.g., it needs a insane and unnecessary  bandwidth of your net connection and if it doesn't get it, it'll stuck. The BluOS2.* needs for a request only above 2 Mbit bandwitdth. if you have 50-60 mbit bandwidth, it's ok, but if you have only 10-20mbit, the request from BluOS will stuck. 

     

    now you know the reason, why TIDAL works fine with the own app but not with BluOS.

     

    so it's a huge bug of the BluOS3.*... nothing to do with the players or with your modems... the BluOS has to get fixed!!!!

    1
    Comment actions Permalink
  • Avatar
    ML

    Rrp, I see what you mean with the bandwitdth. But two days ago I upgraded to a 120 mbit network and nothing has changed, I still get the same issue. I did the proper speed test which yielded a 120 mbit tranfer rate. I don't think your solution is applicable to everyone. I still get the delay when connected on ethernet or on wifi and this using Tidal or Tunein.

    I'm also thinking of selling my two Node 2s.

     

     

    0
    Comment actions Permalink
  • Avatar
    Rrp

    @ ML: understand. a friend of mine has the same issue with his node2, me not (Node2(i)). Then he tried his Node2 with my network and viceversa. the result was that my network is working with any Node2 and his not.

    After that he called the tech support of his network provider and the tech support told him, that they can see that the Node2 needs a lot of bandwith only for requests, but not for listening to music etc. Now, my friend swiched to another provider and everything's fine.

    very funny, that your new provider at 120mbit doesn't work... obviously the fault is partly on BluOS, partly on the network provider.

    I have only 50mbit, but I can watch 2-3 football (soccer) games in HD, a movie in HD and listen to Tidal-Hifi simultaneously and I have no troubles at all :) ok, my notebook and my TV get pretty hot, but that's all.

     

    I'm pretty sure, that BluOS has a huge bug inside....

    By the way, sorry for my lousy english, but I don't expect you to read my replies in german :)

     

     

    0
    Comment actions Permalink
  • Avatar
    ML

    Rrp,

    thanks for the information, it makes sense now.

    BTW I'm francophone so I certainly don't mind your english...

    0
    Comment actions Permalink
  • Avatar
    Rrp

    hehe, a beer for everybody :)

    0
    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    Hi All

    If it is in fact a software bug (which we are not seeing here), sending a Support Request from the App will help our QA Team pinpoint an issue by seeing the log file.

    Please select Help Send Support Request.

     

    Thanks

    0
    Comment actions Permalink
  • Avatar
    Rrp

    hi Tony, my friend has sent you his log file, but your advice was like reboot the player, restart the modem etc... always the same advice, like a one string banjo :)  

    fact is, his player (N2 now with BluOS3.0.2) tooks about 15-20s to switch to the next song or the next album with his network, everything's fine with my network. BTW, my player (N2i with BluOS3.0.2) behaviors similar in his or in my network... the tech support of his network provider attest a huge need of bandwidth on every request made by BluOS3.0.2 with a N2(i). his Node(1) needs only 2 mbit on every request and it works fine in every network.

    so Bluesound should know the problem...

    0
    Comment actions Permalink
  • Avatar
    ML

    I did put a request in with log a month ago. An update was promised but nothing yet.

    1
    Comment actions Permalink
  • Avatar
    Paolo Conti

    Hi all,

    i also experienced that problem. It's really frustrating wait for connection from Bluesound. Same problem happens on desktop application. I have a fiber connection with speed test about 70Mb/s

    Please let's know something about fixing that problem.

    Thank's

    Paolo

    0
    Comment actions Permalink
  • Avatar
    Jacob St-Laurent

    Has this improved with the update from two days ago?

    0
    Comment actions Permalink
  • Avatar
    Paolo Conti

    No, no changes with last update. I tried also with amazon music. Same thing. Every tap to a new song or to a new item of menu requires about 20/30 sec

    Paolo

    0
    Comment actions Permalink
  • Avatar
    ML

    Same here no change withe the latest update.

    Stil get the delays.

     

    0
    Comment actions Permalink
  • Avatar
    Rrp

    What facts do we have? since the new FW 3.*.* some units (but not all) don't work properly, the modems are the same as before. the BS-units are the same as before, only the FW is new...

    my friend with the faulty Node2 has a Node1 and this unit works fine with this modem, the Node2 doesn't...

    I wrote the BS-support many times, that the new FW sucks the full bandwidth out of the modem during a request... this is the measurable conclusion of an local internet provider, not my conclusion... 

    I'm afraid that the arrogance and te ignorance of the BS-team is the one to blame...

     

     

    0
    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    We please encourage you to check your network settings and review best practices by reviewing www.bluesound.com/network101 tips and tricks.

    Keep in mind that 70MB throughput to your home form the Internet doesn't necessarily mean that a network bottleneck does not occur inside your home once it has reached your router.

    I would also recommend rebooting your router to clear network cache stored and reset the environment of stored network routes.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.