RuView: ESP32 CSI Engine Fixes and Live Deployment Features
Three major changes focus on fixing core ESP32 sensor functionality and expanding deployment options. The primary pattern addresses fundamental hardware integration issues that were preventing motion detection from working at all.
Duration: PT2M12S
Transcript
Good morning, it's June 5th, 2026. I'm your host with today's RuView briefing.
The codebase saw critical fixes to ESP32 sensor hardware that was completely non-functional, plus new live deployment capabilities for real-world testing.
The most significant issue was a complete failure of the CSI callback system on ESP32-S3 boards. Pull request 955 reveals that the wifi CSI callback never fired, leaving motion detection completely broken with zero packet yield and all motion readings stuck at zero. This affected both version 0.6.5 and 0.7.0 across multiple hardware configurations. The root cause centers on the ESP32 CSI engine only producing data for received OFDM frames, requiring a fundamental change to how the system triggers CSI collection. This wasn't a minor bug - it was a complete sensor failure that would render deployed devices useless.
Compatibility fixes also landed for ESP-IDF version 6.0, where callback signatures changed and broke builds entirely. The merged pull request 945 addresses this alongside occupancy detection improvements that anchor noise floor calculations to prevent phantom person detection in small sample windows.
On the deployment front, pull request 948 introduces live operational modes with a new ITB wifi landing page featuring real-time WebGL visualization, automatic API detection, and 5-hertz REST polling. The changes include realistic mock data for two-person scenarios and PowerShell deployment scripts, suggesting preparation for field testing or demonstrations.
What's next: The CSI callback fix in 955 needs review and testing to verify it actually resolves the hardware integration on affected ESP32-S3 boards. The live deployment features indicate the system is moving toward real-world validation phases.
That's your RuView briefing for June 5th. Stay updated on the critical hardware fixes.