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:
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.
OK. My most recent communication from Google states:
"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. "
However, as you insist your solution must come from Naim, I’ll be sure not to pass anything further from Google on to you.
Edit: It is also possible that Naim has called upon a ChromeCast function in a manner permitted under Google’s SDK guidelines, but in a context Google didn’t anticipate. Then the fault lies with Google.
I got a feedback from Naim support : “reboot your phone and router” which did not change anything.
I saw that one issue is that the QB 2 might not always find your network. Have you tried connecting with an ethernet cable at least for troubleshooting purposes? Then see if Google Home finds it (even if its only listed as a local device).
It’s a very good point.
It is now cabled and everything works and I could add the speaker to Google Home.
Thank you.
I will keep it cabled until the problem is solved, if ever.
Thank you
I completely forgot that option…
It always found the network, the issue is that the app was sometimes looking, in Access Point mode (Durect Access), for a device name that was not the one published by the device. So the app expects a name and the system publishes another one. That I think is a bug. It happened time to time after a reset.
Ahhh - my home network doesn’t have separately identified access points. It’s a Mesh network with one satellite, but everything connects to the router.
The direct access point is not published by the router, it is set and published by an iot and enables any client to connect to that IOT limited wifi.
Nevertheless you helped a lot.
I also did 2 things
I noticed that in my router the Qb2 was named “salon”. I don’t know why but this might be in conflict with the room named “salon” in google home. So I deleted Salon in Google Home and decided to l call the Qb2 everywhere including in the app “salon”. I also read rhat someone else faced the same issue in above previous messages.
more importantly, in my multiple changes to get this working, I switched to 2.4Ghz wifi only, and kept resetting. I now enabled the 2.4Ghz and 5Ghz
RESULTS:
Both have corrected the situation and .
.I can now Chromecast to “Salon” (my Qb2) and it is available in Google Home…
I had/have a naming problem as well. I named my Muso “soundbar,” (which is one function it serves), but the Google must have had issues with that, and it always played music on the device that received the verbal command.
So I changed the name - but Google kept changing it back. I tried at least half a dozen names. That was actually when I opened my Google ticket. This all preceded the firmware update, but it continues.
Luckily I discovered that even though Google Home (and the Naim app) list the name as “Soundbar,” when I ask Google to play music on “Muso Soundbar” it correctly identifies the Muso.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
