Sonos creates it's own mesh network, called SonosNet. I have a sub and soundbar wired and two wireless Sonos One's but the Controller shows all the devices as wired because they link up through SonosNet and feed back into the main network via the wired connections.Sonos kit is a bit weird at times
*** Official Ubiquiti Discussion Thread ***
- Thread starter RoyMi6
- Start date
Soldato
- Joined
- 24 Sep 2015
- Posts
- 3,976
Yep, it's a pain. If you're not up to speed with your STP/RTSP settings then you can have all sorts of fun and games with ports getting blocked if you have some Sonos kit hard wired and some on wireless. That's always fun when it's a trunked uplink port that RTSP has decided to down.
If I could hardware *ALL* my Sonos stuff then I would, but there's a few that I can't (including a Move, which does have an ethernet port) so I've found it much easier just to leave them all using wireless.
I thought Sonos always advised leaving one device wired, or was that just for the initial setup? I always favour wired over wireless. The only reason the two One's I have aren't wired is because they move around quite a bit.
On a related note, my controller doesn't show IP addresses for ANY hard wired device but it does show an address for everything that is wireless. Controller version 6.0.28. A bit of Google searching suggests this is just one of the many bugs (oh, and my network map has disappeared. I might try a reboot to try and fix that one).
The first 6 (maybe 4) hardware versions of the ES- and US-XG-16 had a fault on the main board so there were issues with the 4 RJ45 ports not being able to hold 10GbE connections. And the first few (maybe board revision 4) had incompatibility issues with some DACs and SFP+ modules. All that is now resolved (since about December 2017 I think) and these are very solid units now.
Soldato
- Joined
- 24 Sep 2015
- Posts
- 3,976
I think (it's been a while since I did it) that the older devices needed to be connected by an ethernet cable to perform the initial setup but no requirement to keep any devices hard wired once the initial setup has been done. Never devices use bluetooth for the initial setup so no need to use an cable.
Ideally I'd have all of my Sonos stuff hard wired but for 2 of the One's that's not possible until we renovate the upstairs of the house. And the Move doesn't have an ethernet port so little chance of getting that one hard wired
Soldato
- Joined
- 24 Sep 2015
- Posts
- 3,976
Not something I remember with 6.0.28, or any version actually. Do the wired clients show up at all?
Topology has been hilariously unrelable for me in the past but since v6 of the controller it's generally been spot on.
They're all there, just no IP address shown against them.
My Controller is running on a Pi, along with Pi-Hole. Thought I'd run a 'quick' update (not the controller, just the Pi) - an hour later and it's still slowly working through the update
. I'm guessing the fact that all internet connected devices now route through this so even when usage is only light, updates are very slow.I'll have to wait until the family are out (which is rare these days) before I attempt to update the controller before I get yet more complaints that the internet isn't working.
My Controller is running on a Pi, along with Pi-Hole. Thought I'd run a 'quick' update (not the controller, just the Pi) - an hour later and it's still slowly working through the update
shouldnt take that long, might take a while if you're several kernel updates behind maybe. pihole is only serving dns traffic so throughput should be very light.
It's still going - 90 mins later! It's only 1 month out of date. Last month when I did this, it was about 2 years out of date and it didn't take anywhere near this long. The only thing that has changed in that time is that we now have a Unifi network up and running with the controller being on this Pi.
Soldato
- Joined
- 24 Sep 2015
- Posts
- 3,976
The UniFi controller can chew through the RAM. Is the the UniFi update that's taking so long or an 'apt upgrade' that's doing it?
The controller doesn't need to be running all the time so you could free up resources on the Pi but shutting down the controller whislt updating the Pi.
The controller doesn't need to be running all the time so you could free up resources on the Pi but shutting down the controller whislt updating the Pi.
I think it was that - it was only an apt upgrade which I would have expected to take 5-10 mins max. 2 hours later and it has finally finished.
So if I restart the controller (or upgrade it) then it won't cut the internet off for the family? Might try that later.
Soldato
- Joined
- 24 Sep 2015
- Posts
- 3,976
I routinely update my controller and underlying OS whilst my other half and I are working - zero interruptions. It will cause all your devices to reprovision though when they connect back to the controller. Some people say that a provision will cause interruption but it's not something I've seen here.
It might be worth doing the upgrade when you won't get assassinated for an interruption but keeping a continual ping running to something on the internet and see if you get any drops.
Good plan. Whatever did we do before unlimited internet connections that are in use 24/7?! The OS upgrade did cause a massive slowdown in resolving DNS (due to Pi-Hole on the same device, at a guess) and the controller did stop and start a couple of times but all is good now.
Out of interest, how often do you update them both? I'm new to Unifi and I'm always nervous updating the controller due to the number of people that seem to have issues with updates.
Soldato
- Joined
- 24 Sep 2015
- Posts
- 3,976
For the price of a Pi it'd be worth having a second unit running Pi-Hole so you can do updates without taking down internet access or slowing it down too much. Make your current Pi the secondary.
I check for OS updates on my controller (an Ubuntu 18.04LTS VPS) usually once a week and I update the controller often - I'm on the beta channel so once a new beta controller comes out I'll update to it. If that causes problems I can just push back a snapshot of the VM and it's back up and running on the previous version. I wouldn't recommend beta controller releases in your instance though, rolling back isn't trivial with a physical controller.
I check for OS updates on my controller (an Ubuntu 18.04LTS VPS) usually once a week and I update the controller often - I'm on the beta channel so once a new beta controller comes out I'll update to it. If that causes problems I can just push back a snapshot of the VM and it's back up and running on the previous version. I wouldn't recommend beta controller releases in your instance though, rolling back isn't trivial with a physical controller.
That's what I was thinking during the two hour update today - a second Pi (which I think I already have lying around somewhere) will be a better option for the controller.
Both Controller and Pi-Hole updated in around 10 mins without issue. Now version 6.0.41. I won't be going anywhere near the beta channel though! My topology map is now back too
Soldato
- Joined
- 24 Sep 2015
- Posts
- 3,976
It'd be less work to leave UniFi where it is and setup the other Pi with Pi-Hole. Moving a controller isn't all that tricky but it can be a bit of a faff.
good to know thanks
Sky Q does something similar if I recall. Planning on cabling my house in the new year, SkyQ and Sonos both in use and already set RSTP on my core switch
Wonder when the likes of the NanoHD will be upgraded to a new Wi-Fi6 version. Got a cabling project once Tier4 ends to start. Thought about purchasing two NanoHD units and selling the Lite, Pro and FlexHD. However it'd be better to prob wait for the updated Wi-Fi6 versions..
Might have a look on ebay and MM for used items.
Might have a look on ebay and MM for used items.