CTMatthew

If you don't personally have an enthusiasm for Ubiquiti and are just looking to get a better WiFi experience, your dealer would also be able to provide Access Networks' Ruckus bases APs. Those are fabulous APs and can run without a controller for most deployments. They're "in the family" and would allow you to keep your Araknis gear in place.

Eero appears designed not to work.

I'm very pro-Ubiquiti. It's really the only networking gear I'd use in a residential deployment, but I'm also curious why you'd want to pull apart what's basically a current Araknis system. I agree the APs could probably stand replacement if they've given you some problems, but otherwise you've got a pretty good system in place. Don't get me wrong I think Ubiquiti is easier in the long run, but your costs are sunk at this point!

It's just a janky product. I know that's not technical, but it's a good description of how we'd describe them after years of second, third, and fourth chances. They just have too many problems, and unlike enterprise systems have very little recourse to fix them.

I would not use Eero.

One thing about UniFi switches is they have lower PoE budgets than Araknis so be mindful if you have a lot of PoE needs outside of the UniFi system itself. They're usually adequate for their own APs and some cameras, but it could mean the difference in choosing between the regular switch and the pro version (where there's no 16 port available). The Dream Machine Pro is beyond adequate for home use and if you're at all savvy you'll be able to appreciate the "single pane of glass" view of your network. I'm able to get to the bottom of network issues very quickly because I don't have to log in and out of half a dozen boxes to figure out what's going on.

I agree that I like the way the Halo feels in my hand. Aside from putting the power button in a shed in the backyard it's a very comfortable remote to hold. And at the end of the day it's the new remote for the most stable control system on the market so we're going to like it eventually.

It's how menus are navigated. A simple explanation seems to be that OS3 put things in a grid and OS4 puts things in a list. I guess we'll see when it's deployed on the app and tablets.

My reaction was similar - especially given how great OS3 has been and how fresh it still looks.

I know for a fact it is - what you see on the Halo is essentially the OS4 design language. Personally I think it's a step back from OS3. That interface was so crisp and clean and felt like a great template for all sorts of potential improvements. So far OS4 feels more like a DIY universal remote.

It's been a weird rollout. The OS3 rollout felt fairly coordinated. The OS4 rollout is sort of a secret I guess. The UI design of the Halos is basically a sneak preview of OS4, but since no one is really saying that it just feels like they're not cohesive with the rest of the experience. Should have been an OS4 rollout with new remotes and not vice versa. I also really prefer the form factor of the Neeo and really dislike the power button placement. I think for clients who haven't experienced anything else it's a great remote. Hopefully some of the UI stuff gets sorted out.

I tend to agree. Having had B&O for so long I was sort of shocked that they had a feature that other systems didn't. I don't think most people think of B&O when they think of Sonos/Heos/Bluesound or other multi-room platforms and I assumed that anything they did regarding multiroom functionality was more or less copied from Sonos. Walking through my house and just tapping a button knowing it'll find the music wherever it's playing is so intuitive and makes a pretty sprawling system feel very simple. That being said I've sort of beat this drum for a few years now with both Sonos and Control4 and the response has basically been, " huh."

This sort of conditional logic has always been possible through Room Control, but any of us who sell C4 for a living know that the more back end programming you author on a project the less profitable it becomes and the more support it requires over the years. The ideal scenario is to choose products that already do what you want them to do and leverage the native feature set in the programming. I'll keep beating the drum for C4 & Sonos to figure out how to pull this capability into their drivers as it would make an incredible case for keypad sales on a job where there might not be a lighting control footprint.

Sorry if I missed that. All of B&O's audio products have been part of BeoLink Multiroom for some time. I have some products that go back to 2015 that are compatible. I personally have a mix of stand-alone speakers like the BeoSound 1, BeoSound 2, BeoSound 35, BeoSound Level, and then room kits like the Essence MKII (the older room kit) and the BeoSound Core (the newer room kit). I have my eye on the new A5 They all have AirPlay 2 so you can use them that way as well, but their internal multiroom system is much more stable. I just love the fact that I can touch the top of each speaker or a wall control to join or drop rooms.

LollerAgent - Thanks for posting. That's what I suspected. You're basically programming the logic for joining versus there being a true "join" feature. The double-edged sword for C4 is that a top-flight programmer can often approximate functionality through some conditionals. The Bang & Olufsen system just has this feature and you can link a keypad button or experience button to the Join feature on any given product. This also makes it a little easier should you move devices. Obviously if you're using a matrix to an amp to hard-wired architectural speakers you're not likely to move anything, but B&O is usually a mixture of hard-wired architectural with free-standing speakers. Hopefully I can convince Sonos to push this into their driver somehow! It'll make Sonos users' lives a lot easier!