Node 2i network problem after update to 4.8.17
Beantwortet
I have been using Node 2i for over 6 years. Until the last firmware upgrade to version 4.8.17 without any problems. After this upgrade, the streamer is unusable. After a few minutes of operation without any problems, when using any network service (Tidal, internet radio, NAS,...) outages begin. At first for a few seconds, later longer and finally the streamer stops working completely. After a restart, everything repeats. Restarting all network elements does not help either. A few days ago I sent a support request with a diagnostic report attached - no response. I have not tried a factory reset yet because I do not want to lose all settings unnecessarily. Can anyone help?
-
Offizieller Kommentar
Found the cause. I have a TV connected to the Node 2i via an optical cable. I have the Auto Sense option enabled for the optical input. After disabling this option, everything works. It really looks like a BUG in version 4.8.17 that causes the optical input to activate after a while, even if no signal is going into it.
Glad you found the cause. That being said, it is likely not a bug as no changes to auto-sense were included in this revision. Without a log file or knowing what the Optical Port is connected to, it is possible a firmware update on that device (a TV) or a problem with the optical cable could be at fault.
I have asked QA to check anyway but if you would like to troubleshoot further with our Support Crew, they would require a lg file form you by selecting Settings, Send Support Request to fill in those blanks for us. -
After an upgrade it's possible the router is confused abour the ip addresses of the client.
Best do a network reboot: shutdown players and router, restart router and wait a few minutes, restart the Node(s) and controller(s).
You could also make ip address reservations in your router for player(s), controller(s) and NAS.
This can make your network more stable and avoid the issue you experienced.
Factory reset will not be helpful in this case.
0 -
Thanks Alan for your response. I've already done everything you wrote except assigning static IP addresses. I have a lot of devices on my network and I haven't had any problems with DHCP so far. I'll try that, but I don't think it will solve the problem.
0 -
I couldn't find a way to set up a static IP address for my Node 2i. Support recommends: "We do not recommend using Static IPs. Instead, we recommend setting up DHCP reservations to achieve the same outcome." I did that, but it didn't help. Any other recommendations? Are there any Node 2i owners who still have everything working after upgrading to version 4.8.17?
0 -
Factory reset will reset the wifi configuration on the Node and thus likely be counterproductive.
Like Alain suggests, set a DHCP reservation for the Node. It is good networking practice to do this for every device that has a permanent presence / dedicated function in the network, like (file, email etc) servers, printers et cetera.
Have a Node 2i for 4 years and not encountered the issues you mention, not on 4.8.17 either.
0 -
Found the cause. I have a TV connected to the Node 2i via an optical cable. I have the Auto Sense option enabled for the optical input. After disabling this option, everything works. It really looks like a BUG in version 4.8.17 that causes the optical input to activate after a while, even if no signal is going into it. I hope this bug will be fixed in the next version. Automatic activation of the optical input is a very useful feature. I'm just not sure if anyone responsible for the bugs is reading this here... Thank you all for your help.
0 -
Tony, thanks for your response. There hasn't been a firmware update on my TV recently. The optical cable is still the same and works without a problem. I'm using the Node 2i as the DAC for the TV and everything still works as it did with the previous version, except for the issue with the Auto Sense option. I've already submitted a support request, including the diagnostic file. I don't see the ticket, although I received an email confirming its creation: "You can view this ticket's progress online by clicking the link below:
Thank you
Sincerely,
The Bluesound Support Crew"1 -
Request number links are secure and not public so can only be seen by the account that submitted them (or a Support Crew Member). I noticed you had two e-mail addresses with us. I took the liberty of merging the accounts. If that is an issue mention that with the Support Crew member you speak with via e-mail.
0 -
I have the exact same problem as described above with my Node2 after the 4.8.17 firmware update.
I also have a device (Google Chromecast Audio) attached to the optical input. Disabling "Auto Sense" resolved the issue for me as well. Please fix this bug in the next firmware release.
1 -
hi all,
I too had the issue with music fading out from my Node2i, restarted it and it would work for 3-5 minutes. During this time my Pulse Flex continued to work. Rebooted my router anf no improvement.
Thank you @gbundes, changing the optical input settings resolved the issue. My TV (Sony Android) has not had a recent update.
it still worked after re-enabling auto detect - but I didn't do extensive testing to confirm that the issue had gone away.
0 -
Tony W. Anything new regarding request 453494?
0 -
The issue was not resolved with the latest firmware release 4.8.21
I tried switching auto-sense back on again and after a few minutes I started getting drop-outs and eventually the whole Node 2 became unresponsive. Disabling auto-sense was the workaround that made it play again.
0 -
Same issue due to a chromecast audio plug on the optical input. I confirm the latest release does not solve the issue.
What a waste of time looking for the root cause !!! I was looking at the node icon, not sure anymore...0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
13 Kommentare