10-04-2024 08:39 AM
Naim Audio recently released firmware updates for its streaming products (I have three), and something in the update screwed up its interaction with the Google Assistant. Now, when I say, e.g. "Hey Google, play Abbey Road on my Bedroom Nova," it responds that I have no music playing devices in my home. This is nonsense - not only do I have the three Naim devices, I have Nest and Chromecast Audio devices that are working just fine.
It would appear that the problem stems from the firmware upgrade, but I am asking here if anyone knows what type of problem would trigger that response.
I should note that the problem is specific to voice commands. I can still Googlecast from my iPhone to my Naim devices.
10-07-2024 10:19 AM
Hi jegreenwood,
Thank you for posting in the community. I'm sorry that you're experiencing troubles using Google Assistant voice commands with your Naim Audio devices. I understand how frustrating this must be. I'm here to help.
To check the voice match with your Google Assistance, please do the following:
Ensure all Naim Audio devices are grouped under the same home in the Google Home App.
Let me know how it goes and keep me posted.
Regards,
Byron
10-19-2024 05:49 AM
Good afternoon. I just wish to let you know that you are not alone out there with this problem, which I see you've brought to the notice of the Naim community forum. Last weekend I updated the Focal/Naim app and since making this now I realise stupid decision, it has caused all merry hell with Google Home/Assistant. My Naim Muso Qb now is constantly offline in the Home app. I can no longer verbally ask Google to play any audio to this device. I can no longer select this device as a chosen audio player with any of my Google Nest devices. I can no longer add my Naim to any group of speakers I wish to create. Yes, when trying to cast from third party apps the Naim device is displayed as an option. Also, if I cast to another type of speaker (Bose) I can then add my Naim to this speaker combination. It's a right mess of a situation from an update that I believe is more Naim's creation than Google's but cannot be sure. Just hoping that someone addresses the problem soon.