I’ve always had issues renaming my Muso Qb gen 1. You can change it, it appears with the new name in the app for a while and then reverts to the original name. Not the same as renaming an input I know, but maybe a similar cause?
Interesting. I’ll try this on my Qb2. If mine reverts too, I’ll feed it into the Beta group. Naim are working on sorting out the analogue and digital inputs that won’t turn off, so we could add the renaming to the list.
This was happening on a Mu-so Gen2 of mine, 3-4 times, though I can’t remember if that was 100% pre firmware update or not, was certainly recently…Seems to be stable now however, possibly since the latest iOS App update (I’m not sure if it’s the App or the device itself that broadcasts the name?)…
However, I do have a Qb2 that has definitely once defaulted back to it’s factory name since the firmware update, had never done it previously…Have changed it back to how I want it, and it seems to have stuck thus far, we’ll see…
One more issue I’ve noticed post firmware update, on the Mu-so, is that the Repeat button is no longer persistent…For a long time I’ve always had that on, regardless of source, and it always stuck…but seems to randomly turn off now…
SC
I did that more than three weeks ago. Got a ticket number. Since then - nada.
I have that problem with my Muso 2.
Are you using Google Home? Google has acknowledged a bug. @S.C This problem predated the firmware update.
I would not assume that the Google bug relates to input names as opposed to device names. I don’t see any relation between Google Home and the former.
I did get a ticket for a separate issue (the search/filter bar disappearing on UPnP album/artist searches following the app update) which is more important to me. I don’t want to start another one until that is resolved. It has been reported for about 10 weeks now and not sorted.
As long as you gave them the info they need that should suffice for now. They need;
- The product you are using
- The firmware version by checking the ‘about’ settings
- A description of the issue being experienced
All issues logged with support
Spoke too soon – my Mu-so renamed itself back to default this morning, again.
Qb2 ok still.
SC
Bummer.
As I mentioned above, Google has acknowledged a bug. This was after several hours (over several days) on the phone (or maybe it was chat - this was a while back) with their tech support. Since I have a workaround, I haven’t been pressing for a solution.
Right now, I seem to be acting as intermediary between Google and Naim with respect to Google Home repeatedly banishing my Naim devices from their rooms. No diagnosis (much less a solution) by either party to date.