Can't connect wifes iPhone to muso qb

Posted by: pixies on 17 April 2016

For the first time my wife has asked to use her iPhone to play music on our Muso qb via the Naim app. (She has previously just used blutooth for simplicity!).

I have set everything up but when clicking on the musoqb image nothing happens and a message says 'to check if you have the latest firmware visit naims website. The Naim app is newly installed on her phone and current musoqb version says 1.4.0. I can connect to my NDX on her phone no problem and can connect to both via my iPad so anyone know what's going on?

I think she's been put off using it altogether!

Posted on: 17 April 2016 by noname

Might it be that you are still connected to the Qb from the Naim app on your iPad?

 

Posted on: 17 April 2016 by hungryhalibut

You need to click on the picture of the Qb on the left. If you click on the right it's too close to the three dots at the top, which makes it go funny. See if I'm not right!

Posted on: 17 April 2016 by pixies

Guilty of doing both Doh! All sorted now. Thanks for your help yet again.

Posted on: 17 April 2016 by hungryhalibut

You're welcome. I only know this because I kept doing the same. The Muso helpline people couldn't help, so I used contacts at Naim via the beta group. Have you tried the multiroom yet - it's very clever. 

Posted on: 17 April 2016 by pixies

Hi HH. I have tried multi room but I must admit that my first few months of the Muso Qb have been a bit frustrating. Love the form and sound but have experienced many connection issues with the above being the latest.    

I have struggled to keep everything on the same wifi connection due to the distance between my NDX and muso and have to use a spare BT hub as a wifi extender for the muso in the kitchen. Multi room only seems to work if all streamers are on the same wifi (or should this not be the case?). When I hard wire the Muso via BT home plug I lose the ability to play any radio..bizzare! Muso helpline have been helpful as has the forum. Ho hum!

Posted on: 18 April 2016 by robgr

I too hit this issue with the Android app version so I don't believe it's confined just to the iOS version

Issue likely more likely found on a mobile device but I hit on the solution by chance (fat fingers!)