Most smart home problems aren't device problems. They're network problems. Wire your backbone — access points, camera NVR, smart home hub — and let the endpoints stay wireless. New construction gets ethernet during rough-in for $50–$100 per drop. Retrofit runs $200–$400 per drop. MoCA over existing coax fills the gap where neither works.
- Wire the backbone: APs, NVR, hub, switch, NAS
- Leave wireless: Switches, thermostats, sensors, bulbs
- New construction: Cat6A, $50–$100 per drop
- Retrofit: Cat6, $200–$400 per drop
- No cable path: MoCA over existing coax
- Typical 2,500 sq ft home: 16–24 drops
Most smart home problems aren't device problems. They're network problems.
The quick answer
If your smart home devices drop off randomly, respond slowly, or stop working after you add a few more gadgets, the devices probably aren't the issue. The network is. And nine times out of ten, the fix isn't a better router — it's wired ethernet in the right places.
This isn't about wiring every light switch and sensor. Smart switches, thermostats, and door sensors run wirelessly just fine. The problem is when people try to run the backbone of their smart home over WiFi too — access points, camera systems, hubs, media servers. That's where things fall apart.
The right approach: wire the backbone, leave the endpoints wireless. Below is what that looks like in practice, and what to do whether you're building new or working with an existing home.
What actually causes smart home dropouts
WiFi is a shared medium. Every device on your network competes for airtime on the same radio channel. Five devices is fine. Thirty is not. Devices wait in line to transmit and that's when you get slow response times, automations that miss their triggers, and cameras that buffer before showing live video.
On top of congestion, most homes have coverage gaps that only show up once you're relying on WiFi for 20+ devices instead of just your phone and laptop. A signal strong enough to browse the web isn't necessarily strong enough for a camera streaming 4K continuously, or a smart lock that needs to respond in under a second.
The third issue is mesh backhaul. Consumer mesh systems (Eero, Orbi, Google Nest WiFi) work fine for general browsing, but most use wireless backhaul — the nodes talk to each other over WiFi. That means every device on a satellite node is going through two WiFi hops to reach the internet, which cuts effective bandwidth roughly in half and adds latency. In a smart home with continuous-stream devices, that tradeoff matters.
What to wire, what to leave wireless
The goal isn't to wire everything. It's to wire the infrastructure and let the endpoints stay wireless. Here's how that breaks down across the categories of devices in a typical smart home.
Access points are the biggest one. A wired AP with a dedicated ethernet run back to your switch performs completely differently than a mesh node relying on wireless backhaul. The devices connected to it get the full bandwidth of that cable, and the radios are used entirely for client devices — not wasted on backhaul traffic. This is why enterprise WiFi (UniFi, Meraki, Ruckus) always runs wired, and why consumer mesh is still a compromise.
The camera problem
Security cameras are the fastest way to expose network problems. A single 4K camera streaming continuously uses 8–25 Mbps. Run four of those over WiFi and you've consumed a significant chunk of your available bandwidth, added latency on the network, and introduced a new failure point every time the camera has to reassociate with an access point.
A wired camera doesn't have any of those problems. Cat6 to each camera location, back to a PoE switch — the cameras get power and data over the same cable with no WiFi involvement at all. The NVR records locally, your phone pulls a clean stream, and the only time a camera goes offline is if the power goes out.
For new construction this is easy — we run Cat6 to planned camera locations during the rough-in phase and the cable disappears inside the walls permanently. For existing homes it takes more work, but retrofit installs are done regularly and produce the same end result.
Cameras keep buffering or going offline?
That's almost always a network issue, not a camera issue. We diagnose it and fix it — usually with a wired backhaul.
Wired access points vs. consumer mesh
This is where we see the biggest performance gap between a well-designed smart home network and one that just uses whatever mesh kit was on sale at Costco.
Consumer mesh (Eero Pro, Orbi, Google Nest WiFi) is fine for its intended purpose — simple whole-home coverage without running cable. But most use wireless backhaul between nodes. When a device connects to a satellite, traffic travels wirelessly from device to node, then wirelessly again from node to router. That second wireless hop eats bandwidth and adds latency.
Wired access points work differently. Each AP has a dedicated ethernet run back to a central switch. The AP uses its radios entirely for client devices — no backhaul tax. Coverage is consistent, capacity is higher, and the system is more stable because there's no wireless link in the chain that can degrade.
UniFi (Ubiquiti) is what we typically deploy for smart home clients who want serious performance. The access points are excellent, the management software is solid, and the system scales cleanly as you add devices. It costs more than a consumer mesh kit, but for a home with 30+ smart devices and cameras, it's the right tool.
How many ethernet drops does a smart home need?
More than most people expect. Here's a baseline for a typical 2,500–3,000 sq ft home in southeast Wisconsin or anywhere comparable.
| Location | Drops | Purpose |
|---|---|---|
| Network closet / utility room | 1 home run | Switch, router, patch panel |
| Each bedroom | 2 | Desk, TV or access point |
| Living / family room | 2–4 | TV, AP, media device |
| Home office | 2–4 | Workstation, monitor, VoIP |
| Access point locations | 1 per AP | WiFi coverage throughout |
| Camera locations (exterior) | 1 per camera | PoE, no WiFi involved |
| Smart home hub location | 1 | Home Assistant, SmartThings |
| Garage | 1–2 | Camera, AP, workshop |
| Typical total | 16–24 | Well-designed smart home |
During new construction, each drop adds $50–$100 in material and labor. The same drop run after drywall is up costs $200–$400. The math on pre-wiring is pretty clear.
Cat6 vs Cat6A: which one?
For new construction, run Cat6A. It handles 10-gigabit speeds at full 100-meter distance, has better shielding against interference, and the price difference over Cat6 is small relative to total project cost. You'll be living with this cable for 20+ years — future-proofing it at install time costs almost nothing.
For retrofit work in existing homes, Cat6 is usually the right call. It handles gigabit without issue, is easier to fish through tight spaces, and the performance difference between Cat6 and Cat6A doesn't matter for the speeds most home networks actually use. The cable standard won't be the bottleneck.
Zigbee and Z-Wave: the other wireless protocols
Not everything in a smart home should run on WiFi anyway. Smart switches, door sensors, motion detectors, and smart bulbs often run on Zigbee or Z-Wave — lower-power mesh protocols designed specifically for smart home devices. They operate on different frequency bands than WiFi (2.4GHz for Zigbee, sub-GHz for Z-Wave) and don't compete with your phone and laptop for airtime.
A Zigbee or Z-Wave network of 20 switches and sensors adds essentially zero load to your WiFi. Each device also acts as a repeater, extending the mesh to the next device. This is why a house with 40 Zigbee devices can still have rock-solid WiFi — they're not on the same network.
The hub that coordinates Zigbee and Z-Wave devices (Home Assistant, SmartThings, Hubitat) should be wired to ethernet. The hub itself doesn't move, doesn't need to be wireless, and is the single most important device in your smart home to keep on a stable connection.
What this looks like in practice
A typical BadgerLayer smart home network build looks something like this.
- Central network closet — patch panel, managed switch, router, and UPS for clean power. Everything terminates here.
- 2–3 wired UniFi access points — one per floor or zone, each with a dedicated Cat6 run back to the switch. Full coverage, no wireless backhaul.
- PoE switch port for each camera — cameras get power and data over the same Cat6 run. NVR is also wired directly to the switch.
- Home Assistant on wired ethernet — the hub that coordinates automations runs on a stable connection. Automations don't miss triggers because the hub's WiFi dropped for two seconds.
- Smart switches, sensors, locks on Zigbee / Z-Wave — running on their own mesh protocol, separate from WiFi entirely, which keeps WiFi congestion down.
- WiFi reserved for what actually needs it — phones, laptops, tablets, video doorbells. Fast and reliable because it's only handling what WiFi should handle.
The result is a network where smart home devices respond instantly, cameras stream without buffering, and automations run when they're supposed to. The infrastructure that needs to be always-on and always-responsive is wired. Everything else stays out of WiFi's way.
Building or doing a major renovation?
Get structured wiring run before drywall goes up. A fraction of retrofit cost, decades of payoff.
New, retrofit, or no-cable-path: the decision framework
Three scenarios, three honest answers. Which one you're in determines what to do next.
Whichever scenario you're in, the principle is the same: wire the backbone, leave the endpoints wireless. The specific path to get there is just a matter of what your house allows.
Want a network that actually supports your smart home?
New construction wiring, retrofit installs, and network upgrades for existing setups. Designed right the first time.