UnitiQute 1 found but not controlled by App

Posted by: NickBiden on 14 November 2018

Apologies if this has already been asked but sometimes simply getting the right search terms is a challenge!

The situation is this. I have both a Unitiqute 1 and a MuSo Qb on the same network. (i've switched off the wireless extender to eliminate that aspect). The UnitiQute is on an ethernet connection whilst the Qb is on a wireless connection.

The App on my Xperia XZ2 compact can find both devices and will control the Qb. It finds the Qute but won't connect for the purposes of control and returns to the 'Find Rooms' screen when the attempt to connect times out. However, the app will allow multi-room control of the Qute from the Qb.

Baffled! Suggestions or ideas welcome.

Thanks

Posted on: 14 November 2018 by David Hendon

There was another stream recently rather similar to this where a very old streamer (a Uniti in his case) wouldn’t play with the current app. The answer in that instance turned out to be that the owner had to update the streamer firmware as he was running very old firmware.

What is your UQ1 firmware status? You can check that using the remote and the wrench or spanner key and then navigate from there. The current version firmware is 4.6 and if it’s 3.xx then you probably need to update it.

best

David

Posted on: 15 November 2018 by NickBiden

Thanks David,

My firmware is current on both the Qute and the Qb. So that, hopefully, rules out anything relating to out of date app/firmware.

I've made a few changes to the setup since yesterday which I am now evaluating. (Wifi extender is still off) I have switched off DHCP on both devices and set up static IPs. The router was set to give them static IPs based on MAC address but when using DHCP the DNS settings on the streamers differed from that on the router. Now I'm not an expert so I don't really know whether this could or would have an affect but I thought it was worth a check.

Currently I do have control of both devices through the App on my phone.

I'll post an update when I think I have resolved the issue.

Nick

 

Posted on: 15 November 2018 by David Hendon

Your words “I am not an expert...” is usually a real steer that you should use DHCP on both streamers and let the router do it’s stuff! Setting fixed IPs is always slightly fraught unless you know exactly what you are doing and why you are doing it. On a simple home network you gain nothing by doing it either.

And if the DNS numbers were different on the streamers than on the router that shows at least that something isn’t right. So it shouldn’t cause a problem in itself, but it’s a sign that something is wrong.

Anyway good luck with your further tests!

Best

David

Posted on: 15 November 2018 by Bart
NickBiden posted:

The router was set to give them static IPs based on MAC address but when using DHCP the DNS settings on the streamers differed from that on the router. Now I'm not an expert so I don't really know whether this could or would have an affect but I thought it was worth a check. 

Well (a) that was your problem and (b) you're likely to keep having problems if you fuss around with these settings and don't really know what you're doing.  The good news is that you won't break anything, but the next time you reboot something, you may well lose connectivity again.

In the normal home environment there (typically) is no need for static IP addresses, and even less regard for MAC addresses of any of your networked devices, or any of this other stuff.

 

Posted on: 15 November 2018 by NickBiden

Thank you for the feedback.

Bart & David, you both comment about simple home networks. Out of curiosity at what point does a network cease to become simple? And is that a function of how you use the network or the number and nature of the connected devices? Whilst 'not an expert' and happy to acknowledge that others will be more knowledgeable I would also not consider myself to be completely naive.

Always happy to learn.

Posted on: 15 November 2018 by Guinnless

Multiple subnets takes it out of "simple". VLANs, commercial traffic, high security firewalls etc

Posted on: 15 November 2018 by David Hendon

Yes as Guinnless says. A single router with lots of things (audio and otherwise) connecting via WiFi and/or Ethernet, with one or more switches and additional wireless access points that extend the main WiFi network to multiple servers, stores and streamers still counts as simple.

best

David

Posted on: 15 November 2018 by Bart
David Hendon posted:

Yes as Guinnless says. A single router with lots of things (audio and otherwise) connecting via WiFi and/or Ethernet, with one or more switches and additional wireless access points that extend the main WiFi network to multiple servers, stores and streamers still counts as simple.

best

David

Agreed.  We have laptops....phones...ipads...2 nas boxes...ND555, UnitiQute2...Roon Core...2 tv's...2 apple tv's...2 Nest thermostats...one fridge...Ring doorbell...certain security devices...who knows what else on our network.  It's still what I refer to as a "simple" network.  Zero fixed ip addresses. Zero attention to MAC addresses.  It's been running flawlessly for years . . . 

Posted on: 15 November 2018 by David Hendon

A fridge! I thought that was an internet myth!

bedt

David

Posted on: 15 November 2018 by Simon-in-Suffolk
Bart posted:
David Hendon posted:

Yes as Guinnless says. A single router with lots of things (audio and otherwise) connecting via WiFi and/or Ethernet, with one or more switches and additional wireless access points that extend the main WiFi network to multiple servers, stores and streamers still counts as simple.

best

David

Agreed.  We have laptops....phones...ipads...2 nas boxes...ND555, UnitiQute2...Roon Core...2 tv's...2 apple tv's...2 Nest thermostats...one fridge...Ring doorbell...certain security devices...who knows what else on our network.  It's still what I refer to as a "simple" network.  Zero fixed ip addresses. Zero attention to MAC addresses.  It's been running flawlessly for years . . . 

Seriously, a consideration with larger populations of hosts on a subnet... is that there is more network processing each host needs to do .. which includes the streamer... therefore in the limit the streamer  network card interface processing and resultant electrical and RF noise will be higher for a streamer on a subnet with many hosts  compared to a subnet with a small number of hosts... yes we are only talking minute differences here.. but some forum members appear to have very golden ears.

The solution would be to create a dedicated audio streamer subnet with a tiny number of hosts on it, possibly just your streamer and route to it and use broadcast helpers and a multicast routing protocol such as PIM between your small streamer subnet and your larger home subnet. This is the proper meaning of data network isolation.

One shouldn’t confuse network topology with complexity of data network applications running over the network.