Roon no longer connecting to 1st generation Naim Mu-so. please advise. thanks

Sorry, again, in my rush to respond I omitted to mention that my NDX2 often disappeared from the Network as well requiring the same workaround. But never mind, everything is now working for me so happy days.
Hopefully the OP will get back working soon :crossed_fingers:t4:

Ok weird, Iā€™m using wired though. Anyways the 1st gen sucks in this regard :slight_smile: (though not quite as much as using Win XP Embedded of all things for the HDX :wink: )

1 Like

I find it ironic that the Bluetooth from my phone has never failed (yes I KNOW that is a totally different technology) but the Roon I am spending money on does not workā€¦ and I will cancel Roon, and just use blooth in other rooms if this continues as is. (my main speakers, Amp, preamp, etc are hard wired). So Roon will be pretty much wasted. And I doubt I could sell the Mu-So for much, especially as is. l will try to talk to Naim on Monday, but I am not optimistic that they will stand by this product.

@moderators while i donā€™t think this is a Roon issue it might be better to move the thread to ā€œsupport.ā€

Thanks

Does the muso appear in the Naim app?
Does the qb appear?

Are they both on WiFi?

1 Like

Must say I am curious too.

I know sometimes that a word can get caught by not very intelligent filtering system for years, I could never write where my cousins in the UK lived Scunthorpe on pink Fish or the Naim forum, always having to say sunny Scunnie.

.sjb

1 Like

You used a word that is in the forum softwareā€™s ā€œstopā€ list of words that automatically cause a post to be referred to the mods. Unfortunate, and purely coincidental, that the firmware lead at Naim happens to share the same surname as the US VP. Politics is a touchy subject apparentlyā€¦

2 Likes

So thereā€™s no hope if I say Naimā€™s Steve Harris really played his trump card with the latest 300 series releases :grinning:.

At least Scunthorpe is a safe bet nowadays.

.sjb

1 Like

yes, the Mu-So appears in the Naim appā€¦which is part of why I thought it was a Roon issue. And they are both on my home WiFi. thanks.

Although I think itā€™s still unclear and we donā€™t have complete information, I have now moved this to Support

I really appreciate all the thought and advice from a number of you. Feels like I am at a dead end. Frustrated with both Roon and Naim. I was considering other Naim productsā€¦but no longer. And whether it is Roonā€™s ā€œfaultā€ or notā€¦it still means I don;t have much use for it. (no need to have Roon streaming elsewhere, as Bluetooth is fine for quality in my other locationsā€¦e.g. bathroom, etc and my living room stereo isn;t an issue). thanks.

and like magic its working againā€¦ whoever suggested to keep trying was rightā€¦ but I had to try that at least 6 or 7 times before it tookā€¦shheshā€¦and who knows how long that will last. thanks again.

2 Likes

It was me, glad to hear youā€™re ā€œback in business.ā€ Itā€™s a real nuisance especially when you know that you will have to go through the process again in the future.

There was issues with the entire range for about a year so @PixelPopper is correct here. Took several firmware iterations to nail it. Happened on my Atom often. Part of the reason I ditched mine was bad firmware. It killed my machine on one update and Steve helped me through on bank holiday to get it working again. It was there network stack causing. Issues with DhCP and it would never get an address.

When, recently?

Screen issues plagued it for a few years after release it didnā€™t seem to affect everyone but then lots had them off. It would often freeze and stop updating, sometimes it would not turn on and not go off when it was set to timeout sometimes just not come on. I had a number of other issues with the Atom where it would lock up for no reason. I had also a previous faulty unit where the sharc DSP had failed so got a replacement but thatā€™s another story.

As for their network stack and its DHCP timing out more recent canā€™t remember when though it will be on their forum still. Although lots was via email and phone.

Right, do think I remember some screen issue complaints, but then that forum is full of complaints about everything. Iā€™m sure it affected people but with a sufficient number of units there will always be issues, so itā€™s hard to tell the difference.

Havenā€™t noticed a DHCP issue and as I am never on the forum anymore havenā€™t read about it. A blessing. Everything would seem perfect for me if I didnā€™t read other peopleā€™s complaints on forums :slight_smile:

Well, I am glad I donā€™t have a Star and its ridiculous ripping issues, but Iā€™m just very happy with the NDX2 and no complaints.

They fixed the issue it only came up when using a switch that has spanning tree enabled as the switch takes time to assign the port active whilst it does its checks and something had changed in their code that made their DHCP timeout so it would not connect to the network after the first reboot of the update and then locked up. We managed to get it back to previous firmware which worked fine and then after attempting to update again several times resulted in same thing we got one try to work. But then when powered off/on it would fail to get assigned DHCP he found in the logs the issue and repeated at Naim. Eventually it was updated after another firmware update before.

Aha, I see.

A fine example of how difficult it can be trying to diagnose problems that only occur sometimes in some configurations!

The op may not be on the latest firmware, and may have an unusual network configurationā€¦ :wink: