Naim app misbehaving with NC system

I normally control my NC based system via the Naim-Focal app. I can select source (Phono, TV, Streamer, Server ) and can control volume and mute sources via the app, either on the iPad or iPhone. But now, mysteriously, the volume is no longer controllable via the app, although it will still mute.

Any suggestions? The pre-amp is the NAC332 and the streamer is the NSS333. Any help gratefully received!

Also, the 332 isn’t displaying any volume settings on its display. Time for a power down of everything?

I’ve had no issue with my NSC222. Are you running the latest version of the app which was released on the 21st June 2026.

Yes, v8.1.1 of the Naim app is running.

I find if I use the remote to adjust the volume too rapidly it loses pairing for some reason. A power down sorts it.

G

I’ll try that, although a hard shut down (power off at the dedicated consumer unit) has thus far failed to resume normal service. :slightly_frowning_face:

2 Likes

Further update: seems to work as expected when controlling my QB2. App can control volume, change sources, mute etc. So the problem would seem to be with the 332/333. Previously when I put the system into standby via the app, both the 333 and the 333 shut down as did their associated NPX 300 power supplies. They no longer do this. Problem with System Automation?

I’d turn it all off, turn it on again and set up the system automation anew.

2 Likes

I pretty much get the same thing as you @Homeworks and a full power down seems to fix it. I’ve contemplating getting a mini to mini toslink to join the 333 and 332 to see if that helps. Otherwise I just put this down to an occasional glitch :man_shrugging:

Power down, then delete the app. Power up and reconnect the app. Connect to existing devices.

G

Yes, I have seen the same thing. I turned off system automation. A volume control setting becomes visible in the app for the 333. Change the control from ā€œhybridā€ to ā€˜fixed’. Then, you need the 332 remote to control volume for a while before changing anything else. The volume control setting change brought the 333 back from mute.

About an hour later I checked back in the app to find that system automation had come back automagically, but it was all working again. I can’t be sure this will work for you, because it was all a bit hit and miss.

I’ve never had to go that far, just off at mains and reboot both 333 and 332 and it all starts working properly again.

But @Homeworks notes that hasn’t sorted the issue. Deleting a reconnecting to the app is no hardship and has sorted occasional glitches I’ve had.

G

1 Like

Understood @GraemeH and it maybe needed. Something else must be at play I don’t think I have ever had to delete the app. I need to ā€˜swipe’ up to clear quite often, but rarely anything more.

1 Like

Thanks for all the suggestions so far. I’ve undertaken the following steps:

  1. Powered down whole system by turning off power at dedicated consumer unit. Left for 10 minutes before re-instating power.
  2. Whilst powered down, followed @GraemeH ’s suggestion and deleted Naim-Focal app from my iPhone and re-installed v8.1.1 from the App Store.
  3. Re-set the 332 back to factory settings by depressing the brightness button on its rear panel.
  4. Re-paired the 332 remote
  5. Set up System automation again (via the Naim app)

All to no success.

Via the app on the iPhone I can control the source selection, can move from one track to the next and the mute function works ( ie it mutes if I touch the loudspeaker icon on the iPhone screen).

What doesn’t work at present:

Tapping the + and - buttons has no effect on volume.

No volume level appears on the NSS333 screen.

When i go into ā€˜Standby’ by using the app, the 333 and its associated NPX300 power supply dutifully goes into ā€˜Standby mode’, the 332 obstinately does not.

I’m pretty much out of ideas at this point. Any other thoughts, or is it call Salisbury time?

It sounds like system automation is not working because none of the functions on the 332 are responding. I would contact Salisbury for help.

1 Like

I thought that the important part here would be pairing the remote to the 333 and that would more or less take care of modern system automation. This may of course be incorrect I am only running 332 with Classic s streamer. But if so I would re pare the remote with the 333 not 332.

1 Like

Rather than setting up the system automation/synchronisation between the 333 and 332 using the app have you tried pressing any button (except stand by) on the 333 then same on the 332?

1 Like

I have similar setup to you, but don’t use the 332 remote. I connected the 333 to 332 wirelessly/Zigbee following the instructions and use the 333 remote or app only. I didn’t want two remotes! There is an app setting to switch between off/wired/wireless.

Have you definitely got the Zigbee connection working?

Incidentally switched my system on just now from standby and it failed to come out of mute. Off at the wall for 332 and 332 instantly fixed it.

1 Like

Like you, I don’t tend to use the Naim remotes, as I normally control the system via an iPad, or if I’m feeling super-lazy and don’t want to be prised off the sofa, my iPhone.

When it is all working properly, I can rouse the system out of standby, control which source - streamer, phono or TV are the three inputs presently employed - set the volume and mute and switch between local or internet streaming (Tidal or NAS) and put the system into standby mode all via the Naim app. Now, the volume control is not available and the standby only seems to work for the 333 and its NPX300, the 332 and its NPX300 remain active.

I think that the remotes are paired correctly as I can change volume, switch track etc which I presumably wouldn’t be able to do if they weren’t paired?

There’s probably something simple that I’ve omitted, or I’ve made an inappropriate selection in set-up, but I can’t obviously see what it might be. Frustrating, particularly as it was working fine previously.