A homeowner once told us their previous system worked great — until it didn't. Lights stopped responding. Music cut out mid-dinner party. The thermostat went unresponsive on an August afternoon in Newport Beach. The culprit wasn't a failed processor or a bad driver. It was a neighbor's new mesh Wi-Fi network competing for the same 2.4 GHz band. That's the thing about wireless: it works beautifully in isolation and degrades unpredictably in the real world.
This isn't an argument against wireless technology across the board. Lutron's Clear Connect RF protocol is genuinely impressive — it operates on a dedicated 434 MHz frequency precisely to avoid the congestion that plagues Wi-Fi bands — and Sonos has built a loyal following on the strength of its wireless audio. But when a client is building or renovating a home and has the opportunity to run structured cabling, choosing convenience over conduit is a decision they almost always come to regret.
Bandwidth, Latency, and the Physics You Cannot Negotiate
Wired connections — Cat6A for data, shielded twisted pair for control, fiber for long runs or high-interference environments — deliver consistent bandwidth and near-zero latency. Crestron DM NVX, for instance, routes 4K HDR video across a property over a standard IP network. That works reliably because the network itself is hardwired, managed, and isolated from the noise floor of everyday wireless traffic. Run that same video stream over Wi-Fi and you introduce buffering, dropout, and the kind of HDCP handshake failures that are genuinely difficult to diagnose and explain to a homeowner.
Wireless signals, by contrast, are shared resources. Every smartphone, baby monitor, microwave, and neighboring access point is competing for the same spectrum. In a densely built neighborhood — a hillside community in Laguna Beach, a street of new construction in Newport Coast — a 5 GHz band that tested clean during commissioning may be crowded within a year. You cannot engineer away interference you don't control.
Latency matters as much as bandwidth in a smart home. When a Crestron Home or Savant processor sends a command — dim the lights, lower the shades, switch the input — the response needs to be immediate. A half-second lag on a light switch feels broken to a homeowner, even if the system is technically functioning. Wired control paths don't introduce that variability. A Lutron HomeWorks processor communicating over a dedicated wired backbone, or a Crestron controller issuing commands via RS-232 or Ethernet to a connected device, will respond the same way at midnight on a quiet Tuesday as it will during a crowded holiday gathering with thirty devices on the network.
What Gets Easier When the Infrastructure Is Right
The practical benefits compound over time. A well-run structured cabling system — home runs to a central telecom room, labeled and documented — makes every future upgrade faster and less expensive. Adding a room to the audio system, expanding the Lutron RadioRA 3 network, or deploying additional Ubiquiti access points all become straightforward tasks rather than diagnostic headaches. When a client later wants to add a Triad in-ceiling speaker system to the guest wing or integrate a new Sony 4K projector into the theater room, a technician can complete that work cleanly and quickly rather than spending half a day tracing unknown infrastructure.
Wireless-first systems tend to accumulate workarounds. A range extender here, a powerline adapter there, a mesh node tucked behind a cabinet because the signal wouldn't reach the guest suite. Each addition introduces a new point of failure and makes the overall system harder to support. That complexity also raises the cost of every service call — not because the problem is complicated, but because isolating it takes time.
There is also a security dimension. A wired network, properly segmented with VLANs and managed switching — Ubiquiti's UniFi platform handles this cleanly in residential environments — keeps IoT devices isolated from the primary client network without relying on the homeowner to maintain that separation themselves. Locks, cameras, video doorbells, and intercoms live on their own segment. A compromised smart bulb cannot reach the NAS drive with family photos. That kind of architecture is straightforward to implement when the physical layer supports it, and genuinely difficult to retrofit onto a flat wireless network after the fact.
The Practical Reality
Not every project offers a blank slate. Retrofit work in an existing home sometimes makes wired runs impractical — plaster walls, post-tension slabs, and historic detailing all impose real constraints — and in those cases wireless solutions earn their place. Lutron's RF shading, Sonos in secondary spaces, and carefully placed access points can all perform well when the project constraints demand it. A Sonos system serving a pool house or a guest casita, connected wirelessly back to the main home's network, is a reasonable solution. It becomes a fragile one when the entire home is built that way from the start.
But when a client is early in a new build or a gut renovation — when walls are open and conduit is inexpensive — the conversation is simple: run the wire now, or pay to solve the problem later.
The homes that perform best five and ten years after installation are the ones with solid physical infrastructure underneath. The displays change, the processors get updated, the control platform may evolve — but the Cat6A in the walls stays there, doing its job quietly, the same way it did on day one. Everything else is a layer on top of that foundation.