Wavey is an open-source WiFi CSI sensing system. This page covers deployment architecture — for signal processing detail, see the sensing pipeline . For what to detect first, see the detection ladder .
Setup steps live in the GitHub repository — they change as the project matures.
Three-layer architecture
[ ESP32 CSI nodes ] -> [ Python pipeline ] -> [ console / automations ]
capture CSI preprocess + features visualize + emit events
- Sensing nodes (ESP32). Capture CSI from ambient WiFi traffic. See commodity CSI limits for hardware constraints.
- Analysis pipeline (Python). Outlier rejection, amplitude features (primary on ESP32), phase sanitization for micro-motion, baseline learning, inference. See the sensing pipeline for the processing stack.
- Console and integrations. Live visualization at console.waveyhq.dev ; events for automation and analytics .
Before you begin
- One or more CSI-capable ESP32 modules (any ESP32 family chip)
- A WiFi environment with traffic the nodes can sniff
- A host machine for the Python stack
Pick your first detection task
Start at the bottom of the detection ladder — the most robust tasks first:
- Occupancy — change-point detection on a baseline
- Motion — variance and spectral features
- Presence — micro-Doppler in the respiration band
Each level adds preprocessing requirements and tuning complexity. Get occupancy working before attempting HAR. Every deployment needs its own empty-room baseline — cross-site transfer without per-site calibration remains an open problem on commodity hardware.
Follow development
- Code: github.com/waveyhq
- Console: console.waveyhq.dev
- Community: Discord
- Contact: [email protected]
Background reading: how it works , glossary , FAQ .
Frequently Asked Questions
Is Wavey ready to install today?
Wavey is in active development. This page covers architecture; github.com/waveyhq has current setup steps and release status.
What will I need?
CSI-capable ESP32 nodes, a WiFi environment, and a host running the Python pipeline. Start with one node; add more for coverage.
How can I contribute?
Star the GitHub repo, join Discord, or email [email protected] . Firmware, pipeline, integrations, and docs all welcome.