Mu-So Qb keeps renaming itself!

Streaming Audio
1

Hello all,
I have a rather strange issue with a first Gen Qb which keeps renaming itself to a previous name. It was originally situated in the conservatory, and this was its name.

After a year or so I then relocated it to the study, and renamed it “study” in the Naim app. It retains this name for 1, two or even 3 days, but then mysteriously renames itself to the original name of conservatory.

I’ve tried renaming it a dozen or more times, the result it always the same.

It’s not a big deal, the Qb otherwise performs faultlessly. It’s more for general interest sake that I am posting here. Utterly baffling to me.

Paul

2

Perhaps it’s just trying to tell you that it misses its old location !

3 Likes
3
4

I had that problem with a Muso 2. My assumption had been that Google Home (also in use) was changing the name - they are linked - but I don’t believe Series 1 supported ChromeCast/Google Home. Perhaps I had the wrong culprit.

And it was something of a problem for me. I had named it Soundbar - a function it occasionally fulfilled. But with that name, every time I told the Google Assistant to play music from the Soundbar, it would also turn on the (ChromeCast-ready) TV and switch the Muso input to HDMI.

All I can say is it finally stopped doing that - I couldn’t tell you why.

Edit - maybe the same problem exists in the relationship between Apple Home and Muso 1.

5

Thanks for posting. This jogged the memory, I too added the Qb to Apple Home a few years ago, although i never found Apple home very useful and hardly ever used it. I’ve now deleted it from Apple home and renamed it in the naim app. Let’s see.

As I mentioned, this is more of a curiosity than a problem - I find most of this home networking stuff incomprehensible.

Paul

1 Like
6

One of my Qb mk2 developed this issue about six months back. Both Qbs are hard wired to the same switch and both work flawlessly. The only thing is one started renaming itself with the the default name “Qb 2160”.

No other operational issues at all. Just the name. It’s sibling in the next room is fine.

Having ruled out network differences I suspect they simply have a bug somewhere. Seems to be cosmetic though.

7

If you make sure you are on the latest firmware and then do a factory reset (the pin in the little hole on the back) it should then stop renaming itself. The number isn’t anything to do with its MAC address or any serial number, but something to do with Chromecast. The reset will fix it.

8

Thanks HH, everything seems stable for the time being, if it plays up again then I’ll invoke the reset……..

9

But the OP had a 1st generation QB. I didn’t think that had ChromeCast. That’s why I suggested the same problem might exist with Apple Home.

Or is my memory incorrect.

10

You are correct, the 1st gen Musos were the first ever Naim products to support Airplay, but Chromecast didn’t arrive until 2nd gen.

11

Really strange behaviour. I don’t use Chromecast, and a couple of days ago I deleted all the MuSos from Apple Home. The Qb retained its new name for a couple of days, then reverted to its previous name.

Additionally, another MuSo which was renamed about 4 years ago has now also decided to rename itself to an earlier name, after being removed from Apple Home.

What sorcery is this !?

Device reset seems the only option…. Will report back for those who may be interested….

12

I don’t use Chromecast or any smart home connectivity at all. And mine is a gen 2. I have mapped back the first occurance of this to the last firmware update when radio switched over from vTuner to NaimTuner.

But in my field I see 90% of problems blamed on something in an upgrade and 99% of the time it’s not the upgrade. It’s just coincidence or that the upgrade was the last time someone paid close attention. So I’m not sure. It didn’t affect the other one.

I’m not inclined to reset. I don’t want to go through initial setup again just for a cosmetic issue. For sure there is a bug somewhere but why sweat the little stuff?

13

I had so many other problems with ChromeCast (definitely ChromeCast) and Google Home/Assistant I assumed this was ChromeCast as well. Guess not.

IIRC, I had a long conversation with Google support about this, and they seemed to think it was a Google issue. And in my case, the rename (to Soundbar) was accompanied by turning on my ChromeCast TV and switching the Muso input to HDMI.

14

Well you know I’d not put it past Google devices to autonomously decide to just do stuff. I have both two Google Pixel phones and a Google Assistant Sony TV. On all devices this is disabled.

But who knows what “disabled” really means.

15

I’ve got a Qb2 that has this problem. It is linked to Google Home, but I don’t know if that’s relevant. A factory reset doesn’t fix it.

16

I had this very same issue a number of years ago. I asked a very helpful gentleman @ Naim who asked if i was using the Apple Home “thingy” (my words not his!!) and he advised that this was causing the problem. I turned all Apple “Home” stuff off and deleted Muso Gen1, from within that App and the problem disappeared.
I don’t know why..but it did solve my problem.

18

Sorry - I tried to delete my last post, as I noted I already posted in this thread, but I guess I did it wrong.

Edit - I guess I did it right.

19

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.