After upgrade to 4.2.6 players disappear randomly
Answered
Hi, 4.2.0 worked perfectly. I have two players (NAD C389 and Alpha IQ speakers). I now have two problems after the 4.2.6 upgrade.
1) When I group the two players, after a few songs or after many songs, it seems random, the NAD drops off the network and I have to power cycle it to get it back in the player list. This also rarely happens when the players are not grouped, but more often when grouped.
2) Streaming audio from a local input (like a record player) on the NAD to the Alpha IQ was working great with 4.2.0, now it constantly stutters.
Is there a way to downgrade to 4.2.0?
Thanks!
Barthold
-
Official comment
Hi Barthold
This sounds like network lag. Please reboot your main network router. Wait 5 minutes, then restart your Players. Wait 5 more minutes then go ahead and play. If problems persist, please select Help, Send Support Request in the App so our Support Crew may review your log file.
-
Hi Tony,
Did that. The network is not the issue. Also, this started as soon as I upgraded to 4.2.6. 4.2.0 was rock solid.
I'll send the support request.
Can you tell me if there's a way to downgrade to 4.2.0?
Thanks!
0 -
None of the changes from 4.2.0 to 4.2.6 would account for this. All of your symptoms suggest network lag. Thanks for the log files, our Support Crew will be in touch.
0 -
Tony, in the above instructions you said, "Please reboot your main network router. Wait 5 minutes, then restart your Players. Wait 5 more minutes then go ahead and play." Now, me and my brain being the way they are, when you say, "restart your players", what do you mean by restart. Should they be unplugged before rebooting the router, then plugged back in (restarting) 5 minutes after the router has been rebooted? I know the players can be "rebooted" from the app, but restarting is throwing me off here.
Thanks in advance,
Tom
0 -
Pulling the power cord of the devices will assure that their addresses in the router get deleted during start up of the router. Afterwards, when reconnected to power, they will get fresh ipaddresses from the router's DHCP server.
Now that all devices are one the same page it would be a good time to make fixed ipaddresses for everything Bluesound on the network.
0 -
“Now that all devices are one the same page it would be a good time to make fixed ipaddresses for everything Bluesound on the network.“
How does one do that?
0 -
The method given by Rays above is meant for professional Bluesound gear.
When you login to your router (192.168.1.1 or such), you should find a menu (under network or wifi )with the summary of all your connected clients. Usually you can edit these addresses setting an option for fixed or reserved addresses. Everything depends on the make of your router, best consult the manual.
0 -
Is it, it is not clear, there is another guide but that has Proffessional on it.
I had a guide before, thought it was that one.
0 -
I agree it's a bit confusing. There is an article in support.bluesoundprofessional.com and a similar one in support.bluos.net. (the one you refer to)
On top there is a comment from Tony: ( from https://support1.bluesound.com/hc/en-us/community/posts/19654761198999-Nad-m33-struggles-to-connect-to-ipad-bluos-app-Sometimes-doesnt-)
##We do not recommend Static IPs. Please use a DHCP reservation. That being be said this will not help if your router is preventing Multicast traffic. Please check your router documentation to allow multicast or prevebt IGMP proxying.
If you are unsure, please email our Support Crew at support@bluesound.com and let them know the make and model of your router.##
Conclusion (for me, personally): I do use static IP but linked to DHCP reservation to assure there are no conflicts on the network and I'm very satisfied with this setup, no more problems.
0 -
All of these suggestions are making a more confusing issue for me. Here's what I know, before V4 I didn't have drop out issues. I've been a happy node 2i and node user since mid 2019. All I want is for my nodes to work like they did before V4. I don't think I should need to delve into router settings, and DHCP reservations and the like. I'm just an end user.
0 -
Very understandable but if your system worked fine before v4.0, it will also work post upgrade.
As far as we, (the users) understand, nothing basic has been changed on the communication part. (Right Tony?)
Your best option remains to execute the network reboot sequence as explained above by Tony. (forget the DHCP stuff for now)
The support team may have some backlog but they will contact you eventually.
0 -
It does not though, 4 has brought various problems. Saying if it worked on 3 it will work on 4 is incorrect. My problem is to do with the 4 interface.
1 -
Thank you, Alain, for your quick reply. I'll give the reboot/restarts a whirl and see where it goes.
Tom
0 -
Thank you Alain for doing your home work - I could not have said it better myself and think you covered it all... (espcially the part that Static IPs are 1) Not necessary if you have proper DHCP reservations 2) Not for the faint of heart and a big reason it is an Easter Egg)
Thomas - If the reboot does not resolve the issue, e-mail us at support@bluesound.com - admittedly we are a little back log but we can arrange for Support Crew Member reach out in the coming days and provide more 1:1 troubelshooting specific to your environment..
0
Please sign in to leave a comment.
Comments
15 comments