This post is for anyone suffering connectivity issues that insome way involves Google services (for me this is chromecast) I have had two MuSo 2’s. The first one I had to return under warrenty as it repeatedly lost connectivity via the App, Internet Radio and Youtube music via chromecast. After a few weeks, the new MuSo 2 started experiencing the same inability to connect. I had tried all reccomended actions and had help from Naim support. It was the support team that had reccomended that I replace the unit under warrrenty after exhausting all other options. I was initially using wifi but swapped to wired in the hope that it would solve the issue (it didn’t)
Anyways, once the new MuSo 2 started doing the same thing, and having gone through all the usual reset/restart/reinstall/turn everthing off and go for a long walk etc… I wondered if it was a software handshake issue. Perhaps the Naim app or MuSo was not releasing the connection cleanly on power off (or standby) So when restarting one side thinks it’s still conncted and the other is trying to establish a connection, and so the connection fails. Having gone through several avenues I went into my Android phone apps and found “Google play services” and did a “force stop” and launched the Naim app, at which point it instantly connected. Since performing this action, it has only failed to connect once in the past 3 months, and when it did fail, I simply repeated the force stop, and the app and MuSo 2 perform perfectly.
Sorry for the long post, hopefully this helps some of you that have the same connection issue.
Cheers
Tony
Interesting. I have reported on my share of problems with Naim and ChromeCast on this forum. One that I hadn’t previously mentioned was Google Home (on my iDevices) reporting from time to time that my Muso 2 or QB 2 was “offline,” which it wasn’t - I could play music on them with the Focal/Naim app. I actually have this issue more frequently with my Sony TV.
I don’t know if this is the same as the problem you describe. And as far as I know there is no “Google play services” in the iOSphere. But so far the unplug/replug or the reset pinhole have brought things back to normal.
Actually, I updated my thread today on the topic with some good news - not a complete solution, but a major step forward.
It’s a long and winding thread, though, and I had a range of issues to deal with.
The first question to ask is whether your QB 2 is in a Google Home “room.” For this you need the Google Home app. (The Google Assistant relies on the Google Home app for this function to work.) Open the app, select “Devices” and see if your QB 2 is in a room. If not, scroll to the bottom and see if the QB 2 is listed as a “local device.” If so, select it. You may see an “Add to a Room” button. Click the button and select the room to which you add it. (Note - these are completely virtual rooms - they need have no connection to where the unit actually sits.) If instead of a button, you see a gear icon, click on that and do the same. (If you see neither, curse fate and try a reset of the QB 2 - but see my post from today.) Note the name given to the QB 2. You can then try a command. Start with something simple like “Play music on [Name of Room] [Name of Device].”
If you don’t see your QB 2 at all, this means Google Home is unaware of your QB 2. In that case you need to click the Add button in Devices. Google Home will then try to find the QB 2. If you’re lucky it will. Then follow the instructions to get the QB 2 fully linked. If it doesn’t find it, go into the Focal/Naim app, choose Settings/Services and Accounts, and make sure Google Cast is turned on.
Actually, I haven’t had that much difficulty with my MuSo. It’s my Nova that’s been driving me crazy. Also, I’m in the iOSphere. Things may be different if you’re using an Android setup. Also, please note, that the Google Assistant has some significant limitations. It can’t play music from your home library. And, the last time I checked, it could only access certain streaming services, which do not include Tidal or Qobuz.