By Christopher Wolff — Founder, Edge Orbital

Most people hear “WiFi sensing” and think it sounds like science fiction. It is not. It is channel-state information, phase shifts, and signal changes you can measure with hardware that already exists.

The important point is this: the network does not just connect devices. It can also perceive motion, occupancy, and disruption without a camera pointed at someone’s face.

That matters because cameras create friction. People tolerate them when they have to, but they do not love them. WiFi CSI gives you another path. You can detect that someone entered a room, moved through a hallway, stopped moving, or changed the RF environment without building a surveillance stack around image collection.

If you are reading this because you saw the phrase WiFi sensing through walls, this is the more practical follow-on question: what hardware actually supports it, and why does CSI matter?

What WiFi CSI actually is

CSI stands for channel state information. In plain English, it is a more detailed read of how a wireless signal changed between transmitter and receiver. RSSI gives you a rough power number. CSI gives you a much richer fingerprint of the path the signal took.

That is why CSI-based sensing can detect subtle environmental changes that a normal WiFi connection ignores. A person walking across a room, breathing behind drywall, opening a door, or blocking a corridor changes multipath behavior. CSI lets you model those changes.

That is the real reason WiFi sensing matters. It is not a novelty. It is the first credible path to device-free sensing using infrastructure people already understand.

What hardware is actually required

Not every router exposes CSI in a usable way. That is where a lot of bad blog posts go soft. They imply any consumer WiFi box can become a spatial sensor overnight. That is weak. The answer is more specific.

You need hardware and drivers that expose channel state information at the PHY layer, plus a capture pipeline that can export and process that data. The exact path depends on whether you are running a lab experiment, a prototype, or a production system.

If the question is, “What CSI-capable hardware is required?”, the honest answer is: start with hardware that gives you direct CSI access, then move toward controlled edge nodes once you care about repeatability, latency, and packaging.

Why WiFi CSI beats camera-first sensing in more places than people admit

Cameras are still useful. I am not pretending otherwise. But they drag privacy, storage, lighting, placement, and consent problems behind them. WiFi CSI is different.

• No line of sight required. You are measuring signal disturbance, not pixels.
• Works in darkness, smoke, and visual clutter.
• Lower social friction. A router is normal infrastructure. A camera is an explicit watcher.
• Useful for awareness, not just recording.

That last point matters most. A lot of security systems are built for evidence after the fact. CSI-based sensing is valuable because it can support earlier awareness before someone ever reviews footage.

Where WiFi sensing still breaks

This is also where people oversell it. CSI is not magic. Environments change. Furniture moves. RF noise shifts. Walls and materials matter. Calibration matters. False positives are real if your modeling is weak.

So the right frame is not “replace every camera.” The right frame is: add a privacy-preserving sensing layer where camera-first systems are brittle, intrusive, or unnecessary.

That is why the strongest designs are hybrid. Use CSI where presence, motion, anomaly detection, or occupancy shifts matter. Use other sensing layers only when you truly need a visual confirmation path.

Why this matters for Edge Orbital

I care about this category because it fits the same thesis behind everything else we are building: the infrastructure should not just move data. It should understand what is happening around it.

That is true for wireless networks, for personal safety, and for the broader spatial intelligence stack. A good sensing architecture gives you earlier awareness without forcing people to live inside a camera grid.

That is also why I think WiFi CSI is strategically important. It turns ordinary network equipment into a sensing surface. Once that happens, the network stops being plumbing. It becomes context.

What I would build first

If I were advising a team evaluating WiFi sensing today, I would not start by chasing a giant product vision deck. I would start with three hard questions:

1. What event are you trying to detect? Presence, fall, intrusion, occupancy change, breathing, corridor movement, or something else.
2. What latency and confidence do you need? Research demo and operational system are not the same thing.
3. What is the acceptable privacy tradeoff? That answer should drive the stack, not marketing language.

Then I would prototype with CSI-capable hardware, validate detection on a narrow problem, and only after that worry about packaging. Most teams do the opposite. They go wide before they go true. That is why they burn time.

The real opportunity

The real opportunity is not a gimmick article about routers seeing through walls. The real opportunity is a new category of infrastructure-native sensing, where the network itself becomes part of the awareness layer.

That is a bigger story than smart homes. It reaches into facilities, worker safety, private campuses, and any environment where you want earlier awareness without defaulting to cameras everywhere.

If you want the broader category case, start with WiFi Sensing Through Walls. If you want the system layer underneath it, the architecture lives in our technology overview.

Related reading: why routers are becoming spatial sensors, device-free WiFi detection, and Tripwire Recon live on iPhone.