RuView: WiFi Hardware Integration Fixes

Transcript

Good morning. This is RuView for June 2nd, 2026.

Two hardware integration fixes dominated yesterday's activity, both solving fundamental WiFi sensing functionality that simply wasn't working in production deployments.

The more severe issue was complete CSI data capture failure on ESP32-S3 hardware. Pull request 901 reveals that after WiFi station connection, CSI callbacks never fired, yielding zero packets per second even with strong signal strength. The root cause was a configuration error where promiscuous mode filtering was set to management frames only, but CSI extraction actually requires data frames. This meant the CSI feature was essentially non-functional. The fix changes the promiscuous filter from management-only to all frame types, which should restore CSI data flow entirely.

The second issue affected Home Assistant integration scalability. Pull request 899 addresses a device discovery problem where multiple ESP32 nodes were incorrectly sharing a single Home Assistant device identifier instead of creating separate devices per node. This contradicted the documented behavior and would cause sensor data conflicts in multi-node deployments. The fix ensures each node gets its own device registration in Home Assistant's MQTT discovery.

Both issues point to a broader pattern of integration edge cases that only surface in real-world multi-device scenarios rather than single-node testing environments.

Looking ahead, these fixes should restore basic CSI functionality for WiFi sensing applications and enable proper multi-node Home Assistant deployments. Teams running multiple ESP32 nodes should verify their CSI data streams and Home Assistant device registration after these updates.

That's your RuView for today.