When it happens, and it has happened frequently during my testing, I delete the shaded one and add the “Local Devices” one to the appropriate room.
Looking at google home the reason why I stopped all interest in this way of controlling my Naim device is the limitation I need to use spotify or apple music.
Indeed, I already did that once a few days ago and still ended up with what you see today. So I re-did the steps and will follow up. I’ll try restarting router/phone/Naim etc just to be on the safe side when I get the chance.
Not that I really use Google Home though, but of course we should follow up until things work as they are supposed to.
Actually Google Home/Assistant works with both Spotify and now (to my surprise) Apple Music.
That is, when it works. 
Something else I just noticed. When I have the Google Home app open, I can see that when I tell the Google Assistant to play music on my Nova, the Nova icon flips to offline for a moment while it reports no devices that can play music. Then it flips back.
I have the same problem, since I have update my Muso 2, the Google Assistant has stopped working. I delete Muso 2 in google assistant but impossible to find it now.
1 Like
Interestingly, my Muso 2 started working with the Google Assistant again. But my Nova and ND5 XS2 still cannot.
So this morning I had some time on my hands so I I tried again to do a hard reset on my ND5 XS2. Lo and behold, the Google Assistant was back.
I then tried the same thing on my Nova. Now I’m getting a 2-4-10 error message.
First - am I doing the hard reset correctly.
I unplug the unit and hold in the top and bottom buttons while I replug it in until the screen lights up.
After maybe 15 seconds the screen displays an abstract pattern. I can see a progress meter running across the bottom. When do I release the buttons.
Then after maybe another 30 seconds the screen with input selections comes on, but the standby button is now flashing 2-4-10. And I can’t do anything else.
If I’m doing the reset correctly, what does the error signal mean?
EDIT - Apparently, those are not the buttons I needed. I tried the middle two buttons, and after two more attempts, the Nova booted. And I have the Google Assistant back.
I should note that my original choice of buttons was based on a post I found in this forum.
Good afternoon. I just wish to let you know that you are not alone out there with this problem, which I see you’ve brought to the notice of the Naim community forum. Last weekend I updated the Focal/Naim app and since making this now I realise stupid decision, it has caused all merry hell with Google Home/Assistant. My Naim Muso Qb now is constantly offline in the Home app. I can no longer verbally ask Google to play any audio to this device. I can no longer select this device as a chosen audio player with any of my Google Nest devices. I can no longer add my Naim to any group of speakers I wish to create. Yes, when trying to cast from third party Android apps* the Naim device is displayed as an option. Also, if I cast to another type of speaker (Bose) I can then add my Naim to this speaker combination. It’s a right mess of a situation from an update that I believe is more Naim’s creation than Google’s but cannot be sure. Just hoping that someone addresses the problem soon.
- Casting directly to Audible Android app does not work. Only works in a roundabout way by casting to secondary device and then adding Naim speaker. In truth the whole process is a dog’s dinner of a process that involves playing on the Google Home app and then Audible app.
Did you try a factory reset on the QB2. I had to try twice, but that solved the problem for me. (I may have had one offline incident after that, but basically things are working.)
If not please let me know. Google support is analyzing the offline issue. If you can do screenshots of your Google Home app when it occurs, I can send them on.
Thanks for the reply. I did try a factory reset, or thought I was following the instructions I believed were applicable to the Qb 2, but I had a very frustrating and even dreadfully anxious 30 mins or so when the device didn’t respond whatsoever and looked like I had bricked it.
If you could confirm to me the exact procedure of how to factory reset this particular Naim I would be very grateful and will hold my breath and try again. Do I take it that the device is displayed in the Naim app with firmware that is not 4.4.0?
Currently, I don’t have a QB2. I have a MuSo 2, and for that I stick the tip of a paperclip into a pinhole and hold it there .
Oh, I’ve stuck it in a number of times and for my efforts I even found myself thinking that I had lost one of the most expensive items in my house. No, I will leave this for someone to put right and correct what has obviously been an untested updated when it comes to the Chromecast functionality. I can count on two fingers the times I have seen an update with this device in the time I have had it, and to release such a botched firmware update should be viewed as an embarrassment to whomever let it out into the wild.
Thanks for your time in responding.
MuSo 2 here. After the firmware upgrade I could not see the MuSo device working in Google Home App.
I removed it and it was discovered once again, placed in “Local Devices” and I can cash audio from phone and change volume via the app… But Home does not properly recognize it and it cannot be used to cast music via voice commands nor be placed on a Room (the settings icon in device does not show at all, just the three dots).
I’m not resetting it as I do not use this feature but definitely you are not alone.
If you select it in local devices then go to settings, you can assign it to a room. This was something that happened frequently before my resets on both my Nova and my ND5 XS2 fixed my Google Assistant issue. It happened once since then, although this may have been some sort of carryover from before the problem was resolved. In any event, for me, the situation has changed from a total failure to a potential minor hiccup, by no means the only one I have with my computer/networked products.
FWIW - I have had an active exchange with Google on these issues (as well as an older, unrelated issue regarding my Muso). They really seem to be interested in resolving the Local Devices issue. But as noted, it’s no longer happening for me.
My reference number is 1-6173000037041 if you want to chime in with them.
Agreed, but for mine the settings icon is not appearing in Home app. I’m not using the feature hence not doing a reset, too annoying.
Many people use chromecast regularly so no general fault here.
Agreed and confirmed, Chromecast works just as usually was doing.
As I stated in my original post, ChromeCast is not the problem - the problem is (and fortunately in my case “was”) with the Google Assistant properly responding to commands regarding Naim products.