The Weakest Link Nobody Wants to Talk About
There's a conversation I keep having with new clients that I didn't expect to be having when I started doing this in 2016. It usually happens about twenty minutes into a walkthrough, after we've talked through display options and seating and acoustic treatment. Then I ask about their network infrastructure, and the room gets quiet.
Not because they don't have Wi-Fi. Everyone has Wi-Fi. They usually have very confident Wi-Fi — a mesh system from Eero or Orbi or Google, maybe upgraded twice in the last four years, definitely fast enough to stream Netflix in every room simultaneously. They know their speed tier from their ISP. They do not know their switch topology. They have never heard of a managed switch. And they are about to spend north of $60,000 on a home theater and automation system that will quietly suffer because of it.
Why This Matters More Than It Did Three Years Ago
The AV world has been moving steadily toward IP for years, but 2023 and 2024 accelerated something. The number of network-dependent devices in a serious install has grown substantially — and more importantly, the sensitivity of those devices to network quality has increased in ways that aren't obvious until something goes wrong.
Consider a mid-tier Bellah install today: a Lumagen Radiance Pro for video processing, a Trinnov Altitude for immersive audio, a Control4 or Josh.ai brain for automation, an Apple TV 4K (or two), a Kaleidescape Strato for disc-quality playback, surveillance cameras, distributed audio endpoints running Ethernet, and a Lutron RadioRA 3 system that still benefits from a clean local network for its app interface. That's not exotic. That's a reasonably appointed house in Westlake or Lakeway. Every one of those devices either lives on the network or depends on it.
Kaleidescape in particular is worth naming here. Their players communicate over the local network with their own server. Latency spikes, packet loss, network congestion from a poorly configured mesh node — all of it shows up. Not always as a dramatic failure. Sometimes as an occasional hiccup during a film that a careful homeowner notices and attributes to something else. I've spent time diagnosing "Kaleidescape problems" that turned out to be network problems the homeowner's ISP-provided router was causing.
Mesh Systems Are Not the Answer
Consumer mesh systems are genuinely good for what they're designed for: getting reliable Wi-Fi coverage across a house without requiring the homeowner to think about it. That's a real problem they solve well. But a whole-home AV and automation install is not the use case they were designed for, and the compromises they make — particularly around how they handle backhaul, how they prioritize traffic, and how they deal with roaming clients — create real friction in demanding environments.
The solution that's become standard practice for serious installs is a properly configured enterprise-grade network: Ubiquiti UniFi or Cisco Meraki on the networking side, with a managed switch infrastructure that allows for VLAN segmentation, QoS policies, and the ability to actually diagnose what's happening when something behaves oddly. Araknis is another name worth knowing — they've built a strong foothold in the custom integration space specifically because their gear is designed to be deployed and managed by integrators, not IT departments.
None of this is glamorous. You cannot show a client a UniFi switch the way you can show them a Sony LSPX-S3 or a Stewart Filmscreen. But it is the difference between a system that works the way it was designed to and one that keeps you guessing.
What This Looks Like in Practice in Austin
Texas Hill Country homes present some specific wrinkles. Properties in Bee Cave, Dripping Springs, or out toward Wimberley are often large, sometimes spread across multiple structures, and frequently dealing with ISP options that are more limited than you'd find inside Austin proper. Starlink has become a real part of this conversation — it's now a legitimate primary connection for some of these properties, and integrating it cleanly into a managed network requires thought.
Multi-structure properties add another layer: getting a clean, low-latency connection from a main house to a pool house or guest casita without relying on Wi-Fi backhaul across long distances. Buried fiber between structures is the answer. It's also the answer nobody budgets for until they've had the experience of their guest house automation falling over because the mesh node on the patio couldn't maintain a stable connection.
The Honest Bottom Line
If you are planning a serious home theater or automation project, the network infrastructure conversation should happen before the equipment conversation. Not after. Not as an afterthought line item at the end of a proposal. Before. Because the ceiling on what your system can actually do — and how reliably it does it — is set by the network underneath it, and that ceiling is invisible right up until it isn't.
If you're building something in Austin or the surrounding Hill Country and want to start that conversation, reach out here. It's worth getting right the first time.