iOS apps keep not finding rooms

Posted by: Red Ticker on 06 August 2017

I have 4 UnitiQute2s wired into my home network controlled using the iOS app running on iPods which connect to the network over WiFi. Since the update to the latest app version 5.7.3 I frequently get "Finding Rooms" and then "No rooms found". Previously they just used to connect straight to the last UnitQute2 they were connected too. When I check on my router, or with Fing, the UnitiQute2s are visible on the network and entering the IP address into my web browser connects straight to the UnitiQute2.

This is what I get when I connect:

Device Name:Study
Current Profile Name:Profile1
Mac Address:00:11:F6:A9:A2:FA
Current IBSS State:false
Current SSID:not available
Current Encryption State:not available
Current IP Address:192.168.0.25
Current Netmask:255.255.255.0
Current Default Gateway:192.168.0.1
Current DNS1:192.168.0.1
Current DNS2:0.0.0.0
Current DHCP State:Got IP address from a DHCP server
Current Proxy Server State:off
Current Proxy Server: 
Current Proxy Server Port:0

 

and

Connection Status:connected, BSS
Signal Strength:not available
Wireless Channel:not available
Firmware Date:2015-09-15
Firmware Version:2.0.68.13731

 

I have turned off and reset the router, network switches, and the iPods as well as quitting and restarting the apps, but the problem persists.

Any ideas?

Martin 

Posted on: 06 August 2017 by Red Ticker

Forgot to add that the UnitiQute2s use reserved IP addresses, so its always the same from the router.

Posted on: 06 August 2017 by David Hendon

Naim believe that in 5.7.3 they have fixed this problem they inadvertently introduced with 5.7 and I suggest that you call Naim support and discuss it with them. The only advice I would have given is to restart the router and to force-quit and restart the app and you have tried those already. I hope they can suggest something else.

best

David

Posted on: 06 August 2017 by Red Ticker

Thanks for the suggestion David. It just seems strange that these problems have started since the recent app updates. I'll try and call Naim.

Best

M

Posted on: 06 August 2017 by Mike-B

I've had my far share of finding rooms followed by the #*!@$  "No rooms found" during beta testing; but in defence of 5.7.3 it has pretty well fixed it other than an occasional Finding Rooms flash & an even shorter NDX image flash before going into the Home Screen.  

To go back & expand on one of David's suggestions:  I'm suspicious of reinstalling over an existing app might leave a 'problem' link in place & to prevent this I normally delete the app, then force an  iPad restart - press & hold both the Sleep/Wake & Home buttons until you see the Apple logo (about 10 secs)  -  then re-install & set-up your settings preferences.   The restart clears the RAM rubbish that might be causing the problem.  It might not fix your No Rooms Found problem,  but worth a try,  ya never know.

I see  'Got IP address from a DHCP server'  so thats good.     I would also run a systematic power cycle of the system & network - Broadband hub first & let it finish its start process,  then each component,  one at a time.   

Posted on: 06 August 2017 by Cbr600

I have the same problem with not finding my muso, Qb and atom, using the iPad.

all I do at the moment is shutdown and reboot the iPad and then when I start the Naim app it finds everything again. Until the next time !!

Posted on: 06 August 2017 by Mike-B

Yea but,   you have real "Rooms" with Muso, Qb & Atom & a mix of old & new platform to boot,  I've just got one NDX.  The question I keep asking is why my app with its Multi-Room setting 'Off' needs to go finding "Rooms".    The beta test team at HQ have it noted & (I hope) is WIP & will be fixed some time for a future revision release.

Posted on: 06 August 2017 by DrMark

As I have said here before, on the Android app it almost never finds my "room" (I only have the one) - and I have to use the Naim remote to "wake up" the 272, which then tells me on first press "No Network" then on second press "Please Wait" and searches. At this point it is best to close the app while the 272 sorts itself out (about 30 seconds) and when the 272 has found things, then start the app.

I consider this an annoyance, and really something that ought not be, but I only get raging pissed off when I cannot use the system because of drop outs (see other thread, and the things that can be done) or on the rare occasions where I have to reboot almost everything to get it going...where I think "I have a $15K audio system and I cannot listen to a bloody thing!"