Updated my Qb2 and now Chromecast disabled

Good morning,

I have 2 Mu-So and one Naim.

I had the perfectly bad idea to upgrade the Qb2 firmware yesterday.

Since then I can no longer Chromecast to it.

In the app, it does not allow me to enable Chromecast…and of course in other audio apps the Qb2 is not seen as a Chromecast audio system. I can no longer add it in the Google Home app (not discovered)

This is very frustrating, I can only play internet radios available in the app.

Any views?

Thank you,
Francis

Below is a picture of the app page where it’s no longer possible to enable Chromecast…

Try a hard reset.

1 Like

You are not the first to post on problems with ChromeCast after updating firmware.

@itmanuk may have had the same problem as you. It appears his problem was solved by a factory reset (but only after some additional issues). My problem was different but possibly related. In my case the reset didn’t fix everything, but what remains is an annoyance, not a showstopper.

I have opened tickets with both Naim and Google.

1 Like

Thank you both.
Need to figure out how to perform a hard reset…:slight_smile:

Rear panel, theres a little hole to the right of the 3.5mm socket, stick in a pin for 10 seconds.

2 Likes

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 :slightly_smiling_face:

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