Noticed this morning that my Nova and ND5 SX2 had lost their room assignments in Google Home. Added them back. Fortunately, not a big deal, but definitely a bug. This does not happen with my other Google Home devices.
Hey I have been reading all your replies and i just created this account to tell you i have pretty much the same setup as you and my muso2 also stopped working with Google. i have done all the things you have done too. Im pretty sure its an Naim issue as it stopped working right after the 4.4.0 update. I use google to play music every day but now i cant. it still works on all my nest pucks and google home but i need my Naim sound 
I hope they release a new firmware soon to fix this.
1 Like
I probably should have replied this one instead, anyhow my reply in further down :-/ sorry
I just sent updates to both Google and Naim support.
Let me add that I opened the ticket with Naim three weeks ago, and except for an auto-acknowledgement, I have yet to receive any response.
Google, on the other hand, responds frequently, although I’m not sure how far they are towards a resolution. This seems clearly a Naim issue - my hope with Google is that they can identify the technical nature of the issue Naim will need to fix.
sounds great… I hope it will work again soon, it was pretty much the only feature i used
Update. Today I took the bold and stupid step of attempting to fix this problem. I work in IT and troubleshoot problems for a living, so I do loathe it when I feel I’m being beaten by a tech problem.
I took a pointy thing and reset my Naim Qb 2 and this time it caused a lot less aggravation than the previous occasion. However, it actually made my situation worse. First, the reset did not take back to factory settings but once more to the 4.4.0 firmware. This almost certainly is the reason for why I’m here now and what has broken Chromecast.
The setting up of network connection is at best a clunky and frustrating experience but after a few attempts I connected to my WiFi to discover that now my Google Home app doesn’t display the Naim at all. At least before it was there in some sort of broken way, but now nothing shown whatsoever. Checking my app and the system settings there is the Input section where all the audio connection options are listed. All are turned on and available to turn off if you choose to. All but one, which is the Chromecast option that is off and cannot be turned on.
So, I have dug out one of my Chromecast Audio pucks that are one of the finest things Google ever created and should have never stopped making and connected this to my Naim’s analogue connection. Now I have a working Naim casting speaker that is in my Home app and I can do all sorts of lovely things like play music.
My Google Home is still showing in some places the Naim Chromecast as an option to cast to but Spotify, Audible, BBC Sounds etc see nothing.
For anyone who is not experiencing Chromecast problems is I would say you have not updated the firmware in the Focal & Naim app and I strongly recommend you don’t if you value your Naim casting.
Sorry to hear about your experience.
I agree with you about the ChromeCast Audio pucks. I have three and I dread the day when they stop working. One thing to note - you can connect the ChromeCast’s dual mode output to the Muso’s optical input. But you may not want to go there.
Do you mind if I copy and past some of your experience for the benefit of Google and Naim?
And again this afternoon. Fortunately for me, once I return them to their rooms, I can use voice commands.
You are very welcome to use whatever I write here as I cannot contact them directly being that my Naim is one I purchased second hand and unable to confirm purchase with them.
Thanks for the tip and when this is done we should join forces to persuade Google to bring back Chromecast Audio. The best and cheapest way to take any superb sounding audio device and make it networked.
2 Likes
Done.
By the way, I use my ChromeCast Audio pucks together with the Lyrion Music Server (fka Logitech Music Server) and its ChromeCast plug-in. That gives me access to all the music on my server. Unnecessary with QB2, but great with a simple pair of powered speakers.
Update. I noticed that Google Home did an update today so I started making attempts to see if I can bring my Muso Qb 2 back into my home. Well, I tapped the + symbol and chose the ‘Google Nest or partner device’ and lo and behold my Naim was discovered and added to my home without incident. So far full connectivity and all bells and whistles.
2 Likes
Well, I’m not sure I can take credit, but this is from an e-mail I got from Google yesterday.
“Thank you for your patience. We’ve located the feedback you sent and filed the bug. Our engineering team has received all the information and is investigating and working on a prompt solution. We’ll keep you updated as soon as we have more information.”
Having said that, my Nova still refuses to stay put in my Bedroom and keeps being reclassified simply as a local device (which won’t work with the Google Assistant). I’ve relocated it (again) and will see if the update has an effect.
Undoubtedly you must take a bow as from what I can find online you were the one who brought this to the world’s attention.
Out of interest in your Focal & Naim app in the settings and Input section is Chromecast now displaying ‘On’? This was always ‘Off’ during the past couple of weeks.
At the moment it is possible that they have had a large influx of cases owing to the software update
The software on my ND5XS2 is working well, some have had difficulty
FWIW The NDX2 using the latest firmware works fine with HomeAssistant - using the Google MCast methods.
FWIW the NDX2 using the latest firmware works fine with HomeAssistant - using the Google Cast methods.
Quite handy for automations . though I dont tend to bother with my main hifi system… but the NDX2 is controllable via HomeAutomation screen.
It’s on. I never had a problem with the streaming. My problem was controlling the streaming with the Google Assistant (and my Google Nest Hub tablet).
As of this morning, the Nova remains in its room. My ND5 XS2 has actually stayed put for some time now.
I don’t generally use Google Assistant/Home Automation with my main system (or even my second system). Among other reasons, I see no way I can access the music on my server. But it’s great to be able to call out, “play WFUV on my Muso,” when I’m in the midst of doing three other things.
Is that instructing her to play ‘W F U V’ or ‘WerFuv’? I changed the name of my device as pronouncing Naim was a pain that normally resulted in her not responding or misunderstanding, so as it is placed on a bookshelf my Muso is ‘bookshelf’.
Thanks for the tip about the optical connection that I purchased an applicable cable for the Chromecast Audio and it really does add some oomph to the sound. The Aux connection was fine but when idle the speaker would eminate an annoying hissing sound.
Thanks again for bringing this to the attention of whomever was responsible for this problem and I’m just going to give future Naim updates a wide berth.
Well, now, we get to my other problem, specific to the Muso. I renamed my Muso “Soundbar,” which is one of the functions I use it for. However, Google Assistant didn’t respond properly to that name - it played music on whichever device received the command.
So I changed the name. Except the name reverted to “Soundbar.” Again and again. No matter what name I provided. I spent several hours with Google support on this, and they acknowledged a bug on their side. In the meanwhile, I found a workaround. I can leave the name “Soundbar,” but issue instructions to “Muso Soundbar,” and the Google Assistant understands correctly.
As for your specific question, it’s “W F U V,” a great alt-rock/eclectic station in NYC.
EDIT - alas my Nova slipped out of my bedroom once again and found its way to local devices limbo. So my problem - admittedly at this point little more than an annoyance. - remains unresolved.