Having started this thread, I should now report that all my streamers are now working with the Google Assistant. Other than a reset, which resulted in a partial resolution, I’m not sure how this happened. And I still have one issue for which I have a viable workaround.
But I’m a happy camper.
(Now to focus on the sound quality . . .) 
My muso still doesn’t work with Google. I can rename it and google assistant see the new name, but i still cant ask google to play music on it. This latest firmware sucks
I tried reset the muso and many other things 
When you open Google Home is your Muso listed at the bottom as a Local device? Like my Nova in the screenshot.
Fortunately, that no longer happens for me.
yes and when i add it to a room its just offline. I can chromecast to it just fine, but asking google to play on it doesnt work. I feel like i just have a huge bricked speaker now and i havent used it for weeks. When i have time i will give it 1 last try to fix it, otherwise i will buy another product that works. All my nest, home speakers also works fine.
Hi @itmanuk,
Sorry, I don’t really get your point as I’m not native speaker.
I having a chromecast problem with my second-hand bought Muso 2. It’s not discoverable by any means. I reseted it many time and the firmware still 4.4.0 (6575).
I have the same issue (turn on Chromecast built-in but it will turn off shortly, Mu-so 2 Chromecast is not discoverable) Could you please share with me how to solve it?
On the other hand, you also said that Google Chromecast device works for you. Which generation of GG Chromecast do you use? I have a GG Chromecast 2nd genration (HD one), but it doesn’t work. No sound comes out via the HDMI port.
Hello there
My Muso QB 2 Google Cast firmware is 1.56.310669
I would make sure your Google Home app is the latest version.
I was successful in adding my device by tapping on the + and selecting ‘Google Nest or Partner device’
If you are unable to turn on Chromecast input in the Naim & Focal app settings then you won’t get very far.
I wish I could tell you what I did to fix it, but the fact is I don’t know. After a while the problem just went away, first for my ND5 XS2 and a week or so later for my Nova. (I have a different, ongoing problem with my Muso, for which I have found a workaround,) This could be the result of a fix by Google. They claimed their tech support was working on the problem, but I never received a communication from them that it was fixed. I got nothing from Naim and they closed my ticket.
A few thoughts:
Try these steps:
You could also delete and reinstall the Google Home app. Or at least be sure you’re running the latest version.
Especially the removal from the Muso in Google Home is essential. Whenever I had problems with Chromecast, that’s what my first action always was.
For some reason the handshake doesn’t always work after an update (from either side, Naim or Google).
After removal try adding a new device, and hopefully then it will see the Muso again.
So follow the steps that @jegreenwood stated.
Alas the fix has now failed - perhaps tied into the most recent version of iOS (18.2). My Nova has started falling out of it’s Google Home “Room” into “Local devices” purgatory, where it no longer responds to the Google Assistant. What’s worse is that after the most recent updates to iOS, I have no straightforward way of moving it back. There is no gear icon; nor is there a button that says Move to a Room. For the moment, I have an older iPhone, which I have not updated. That one still has a button.
This has got to be some bizarre interaction between the Google Home app, iOS and the Naim firmware.
Note - at the moment this only affects my Nova. It does not affect my ND5XS2, nor my Muso 2. Nor does it affect my Chrome-enabled non-Naim devices.
Has anyone got to the bottom of this? I am in the same position of having the Muso show as local device in Google Home and it I add it to a room it goes offline. Google assistant refuses to recognise the device. Like others in the chat I can Chromecast to the Muso.
Naim support suggestion was to connect the Muso via ethernet cable. Only had tiny patch cable available so I have ordered a new cable and will check it out…however I do not hold out much hope.
Very annoying that it doesn’t work. I end up streaming music to a crappy speaker in my kitchen because it works with Hey Google, and my Muso2 just sits unused most of the time.
If anyone figures it out…please share.
I have been advised by both Naim and Google that they acknowledge the bug and are working on it. I’m hoping for a fix in the next update.
As for Ethernet - my Nova is connected to a mesh satellite via Ethernet, so I doubt very much that that is the issue.
Among the very weird aspects of this problem are these:
It only affects my Nova. My other Naim streamers including one on wi-fi stay put in their rooms.
For a while, Google Home on some of my iDevices had an “assign to room” button. But then they disappeared. However, I had an old iPad around that I hadn’t been using. It still has the button. I keep it powered off, only using it to return my Nova to a room as needed.
Edit - I see I am mostly repeating myself.
I see a few people have managed to move their Naim streamer (mine is a Muso QB) from Local Devices to a room. When I go to it in Google Home, there is no settings button from which to do that or anything else. That also means I can’t remove it to try again.
I’ve also got a Uniti Nova. It doesn’t show up at all.
My Uniti Atom HE goes in and out of the room every ?night? 
… initially it disappeared all together, with the lasted firmware now I can see it, but it doesn’t stay in its allocated room…I move it into a room, but at a point in time it “comes out” to the generic HOME… really annoying…
Most of my iDevices have lost the option (via the gear icon or a button) to move my Nova to a room. I am left with one old iPad that still has a button. As mentioned, I keep it powered off so it cannot download whatever update is screwing things up.
Just pray that the option to return it to the appropriate Room doesn’t vanish.
I have a solution, or at least one that works for me.
Recap: My Muso QB decided to become a Local Device in Google Home, with no gear icon to move it to a room or remove it. Every time I did a factory reset, it appeared there again. Neither was it visible to Nest devices in rooms to become the default audio for that room.
Solution: Reset the Muso and go through the setup process in the Naim app. When you get to Chromecast screen, click Skip, NOT Continue. Complete the rest of setup as normal. It will not now appear as a Local Device in Google. In the Google Home app Devices screen, click + to setup a device, select Google Nest or partner device. The Muso will be found and you can add it to a room. It can now be used as the default audio for that room, and will have a gear icon to access its settings.
Smart thinking!
Although if the Naim device falls out of its Room on average once a day (as was the case for me), a bit of a kludge.
Curious as to whether anyone using an Android based smartphone has the same problem.
I have that problem with an Android phone.
Below is the latest response I received from support.
—INSERT—
Thank you for the update. However, we can confirm that our firmware, software, and systems have no known faults related to these areas with Chromecast and its integration with Google Home. From our testing, such issues are typically related to smartphone setup configurations, local network environments, or other similar factors.
To narrow down the issue, we suggest performing a factory reset on the unit. Additionally, we recommend returning the device to your contractual partner where it was purchased for further testing in their demo room. Most fully approved Naim retailers, outside of John Lewis, are equipped to carry out these tests.
If the issue persists in-store—on your unit and not their demo unit—this may indicate a hardware fault related to the Google authentication token and license required for such products. In rare cases, these license keys can become faulty.
—END INSERT—
So not an issue with their software, but most likely a phone/network issue.
My nearest store is 1.5 hours away, so not terribly convenient.
Hope others live closer and can get it fixed
Thank you so much Nick. This actually worked. Brilliant
