Same issue, I performed a hard reset, it asks me for the wifi, name, chromecast, etc.
Then when I go to the settings, I see Chromecast disabled and the buttom does not allow to enable it…
I’ll do it again.
Another interesting thing is that sometimes afyer a reset the wifi name published as AP by the Qb2 is not what the app is looking at…hence it does not find it…
Name published as AP:
Name looked for by the app:
I’ll do another reset. I always push for > 10 sec
I did another 2 resets, does not work.
I need a beer.
The beer did not solve the issue, I created a ticket.
In the meantime I can no longer use this system as I was used to stream Deezer or Tunein through Google Assistant commands.
2 Likes
After the reset in Google Home is the Muso QB2 listed as a local device without a room association? Scroll down to the bottom of the devices page in the app. If so, what happens after you assign it to a room.
Also worth noting, the name of the Muso in Google Home is linked to the name of the Muso in the Focal/Naim app. Change it in one place and sooner or later it will change in the other.
Also Apple or Android phone? And what software version?
This from a thread I started:
It took @itmanuk several resets before one worked. But in a later post he said a reset solved the problem. Based on his comments, be sure you have the newest version of Google Home.
Thank you, that’s too late as I removed the Qb2 (with former fw) in GH to be sure Google Home would look at the new one (as one possible solution)
Currently, Google Home does not see my Qb2 (it’s not discovered) so nothing I can do there.
I have latest versions of everything, GH, Android.
I think the problem lies with the firmware and until solved nothing GH will be able to do.
I see you’ve created a ticket with Naim support which is what I’d have suggested.
I think the Chromecast licence operates differently to other services such as Airplay 2 and can become uncoupled from a particular device - not the best experience but hopefully Naim can put it right for you.
Thank you.
This time I uninstalled/reinstalled the app and did a factory reset. Still unable to enable Chromecast.
I think I did more than 10 resets today.
The 3 Naim systems I have (Nova, Qb2 and mu-so2) have been working without any issues for the last 3-4 years but this is testing my long relationship.
I won’t upgrade the 2 other systems…
I assume you’re using Chromecast from an Android device? Perhaps not, but do you have any other playback options such as Airplay (even if unofficial)?
Out of interest I’ve not used Chromecast for some years, primarily because despite allowing better quality then Airplay it never did gapless playback properly without using various utilities/workaround I never managed to get to work for me.
Yes, Android.
No, I am alone here, in middle of nowhere in mountains and only Android phone.
It’s not that I care about Android, Chromecast or whatever else, it’s more that I like using Google Home and asking music to play without opening a phone or a computer. I would probably also enjoy Alexa but started 10+ years ago with GH.
Now fortunately I also have a Kef LS60 here that works fine 
2 Likes
Wow, those KEFs look nice!
KEF has a terrible app, but the speakers are really good and nice indeed.
1 Like
Latest firmware borked Chromecast functionality on both my Qb2 and Nova. Factory reset ressurected it on the Qb2, however no such luck with the Nova.
Same issue on my side. Since the latest FW-updates, Chromecast doesn’t work on my Mu-so 2 and Qb 2 any more (however, it works on my NDX 2). Factory reset and the like didn’t help.
I can switch on Chromecast in the App but it automatically switches off again after a short while and the devices are not visible for Chromecast. Diagnostics show that the Google Cast ToS are set to „not accepted“ (while they are shown as „accepted“ for my my NDX 2).
I opened a ticket at customer service and was referred to an upcoming App update that didn’t come so far.
2 Likes
Did you open the ticket with Naim or Google? I have tickets opened with both, and your diagnostics contain information I have not sent to Google. With your permission, I would like to forward the information to them as well. I don’t believe they can solve the problem, but they may have an advantage in diagnosing it as they created the API.
p.s. Where did you get the diagnostic information. I would like to do the same.
To be clear, please look at this screenshot . At the bottom please note that my Nova is listed as a local device but not assigned to a room. From my experience, I have concluded that:
- The Google Assistant cannot issue commands to that device until I assign it to a room; and
- “Add device” won’t work because the device has already been added - it’s just misplaced.
It’s easy to move a local device to a room. Just select it, choose the gear icon, select device information and then placement. Choose the appropriate room and save.
My current problem is that my Nova keeps disappearing from my bedroom and migrating to Local Devices. At this time, my ND5 XS2 and Muso are staying put in their respective rooms. (My problems were much worse before I did factory resets.)
I don’t know about the input enabling failure. Right now, I have 2 devices working properly and the input is enabled. It occurs to me that if one had no Naim devices capable of accepting ChromeCast instructions, the input would automatically be disabled. But that’s just a guess.
Just a remark, this happened after the upgrade and the vendor is Naim, not Google, hence I opened a ticket with Naim only. The inability to enable Chromecast is in the Naim app.
And so far the only question I have received from Naim about my ticket is, “What have you learned from Google.”
I’m not sure that, “You break it, you fix it - alone,” is the most efficient path to a solution. Google wrote the ChromeCast API. I’m pretty sure they did more testing than Naim could ever do, and they may recognize the symptom and be better able to link it to a cause. They can’t provide a firmware fix, but they can provide guidance.
Your view, my view is that I bought it from Naim. I am not qualified neither do I have the time or the appetite to identify the root cause and the party that should fix it. I would add zero added-value and just create additional noise. I just know that I had a system that worked perfectly well before the upgrade that was made available by Naim.