Severe issue with my muso

Hi Vesa, 

I have much the same setup as you - iOS9 / El Capitan and Airport extreme base station(s).

I'm double checking airplay works now from various devices and it does. I joined the beta test team very late in the game so the new software was pretty much bug free by the time I joined but I do not recall this being a flagged issue by anyone.

Do you use the Naim App at all - to control radio for example - does that work? If you don't it might be worth downloading to your phone and seeing if that works.

As you say, it does seem a strange coincidence that the fault occurred during an update but you never know. If you try doing the above and it doesn't work then it would confirm there is definitely something wrong with the wireless connectivity on the muso.

Hi and thanks for the reply.

I do use Naim app, which I have reloaded and installed.

Naim app does not see muso, because I can not get muso connected to my wireless networks. Therefore no radio.

Oh, forgot to mention one more thing I tried: sending the wireless info using USB connection. No luck.

Vesa

Unfortunately it sounds like a trip back to the dealer.

im going to my dealer today to return something, I'll run it by him just in case he has any useful suggestions and will let you know.

Hi Vesa

Like Harty01 I'm running El Capitan and IOS 9.0.2, and am on the beta team. I normally have the mu-so "wired" (i.e. connected via an Ethernet cable to a network switch) and did all the beta testing with that configuration. I've just tried moving the mu-so to Wi-Fi and had similar troubles to you. BTW I have the Airport Extremes set to dual band, with the Mac connecting via 802.11ac.

The mu-so is now working properly on Wi-Fi and can be found by the app but it was quite a struggle.

Eventually iRadio started working but I couldn't see the mu-so at all on the network, not even ping it. To get it working properly. I had to power cycle the Airport Express it normally connects to, and also another Airport Express that it skipped onto when I restarted the first.

Have you tried connecting the mu-so via Ethernet?  It might be reassuring to get it working properly that way first. I'd suggest doing a cold start which you can do by turning off at the wall for 30s, or by putting it into deep sleep by holding down the standby button for about a second until the 12 o'clock light flashes once, then pressing standby again to restart it (which should take about 30s). The mu-so LED provides some information about the status of its network connection. White with a tinge of pink is good.

In my case, I think the explanation of not seeing it on Wi-Fi was that it takes a while for the information broadcast by the mu-so to propagate around the network. One approach sometimes recommended is to do a complete cold start. Turn off everything, then first turn on the internet router and wait a minute or so, then any network switches, then Wi-Fi access points (if separate), then the mu-so, and finally your Mac and IOS devices. Doing a clean start gets rid of any cached routing information.

As well as Net Analyzer (which didn't show the mu-so while I was struggling but now does), I found the following useful:

• mu-so web page - either by name http://mu-so-XXX.local/ or browse to mu-so IP address (where XXX is the rest of your muse's name)
• Airport Utility - I used this to see which Airport the mu-so was connected to but you may need to know the mu-so's MAC address to recognise it
• In Terminal, the command dns-sd -L Mu-so-XXX _Naim-Updater which should list the mu-so's Bonjour broadcasts, once they are getting through. You should see one line

Hope this is useful

david

Hi David, and thank you for a list of new tricks.

OK, muso worked over ethernet before and after I installed older version of the muso software. So the problem exists on 2 generations of firmware. I don't have ethernet in my living room, so wireless is a must. And even if I had ethernet, the wireless should work too.

I tried the complete cold start - no luck.

I can not access muso with browser, since it does not exists as a device with IP address.

Thanks anyway. Are we out of tricks? ;-)

br

Vesa

hi vesa

just dropped you an email on this one

Trevor

Be interested to hear how this pans out.

Hah! Problem solved. Muso works like it used to.

I want to thank Naim & its people for first class customer service - you're second to none.

The issues were in my network settings. I am not sure which one created the problem, but here's the solution: in your Apple environment keep the base station name under 16 characters and don't use accented characters in your network name.

Br

Vesa

Glad to hear it is sorted and thanks for sharing the fix.

Yes, thanks for sharing Vesa. Good to know this.