Help Ruvnet! Detection Window showing the same thing regardless of position and people in room.

[munozluis1015]

I just created a mesh of ESP32 S3s and when I go to the detection window, it always shows the same thing regardless of position or amount of people in the room. To make a mesh do I have to follow this?, https://github.com/ruvnet/RuView/issues/34
I didn't follow that and simply flashed all the different ESP32's with a different COM and connected them to my WIFI.

https://imgur.com/a/doggYlx

[HSIEEN]

Seems we encounter a same problem. I tried traning but not worked.

[ruvnet]

What training process are you using?

[munozluis1015]

What training process are you using?
I haven’t done any training yet. This is straight after flashing the ESP32s. It should still work roughly without any training no?

[ruvnet]

The detection window currently runs a simulation mode when no real-time CSI data is connected via WebSocket. The poses you see are synthetic — they don't change based on actual room conditions.

To get real detection from your ESP32 mesh:

1. Start the aggregator server — this collects CSI frames from your ESP32 nodes via UDP and exposes a WebSocket endpoint
2. Connect the UI — in the detection/observatory page, enter your WebSocket URL (e.g. ws://localhost:3030/ws/csi) and click Connect
3. Verify CSI data is flowing — check the serial monitor on each ESP32 to confirm frames are being sent

Without the WebSocket connection, the UI has no way to receive your ESP32 data and falls back to the built-in simulation.

Training is not required for basic detection — the pre-trained model should respond to CSI signal changes. But you do need the data pipeline (ESP32 → UDP → aggregator → WebSocket → browser) connected end-to-end.

If you're unsure whether your ESP32s are sending data correctly, check that:

• Each node has a unique node_id (set via provision.py)
• They're sending UDP packets to the aggregator's IP/port
• The aggregator logs show incoming frames

[munozluis1015]

The detection window currently runs a simulation mode when no real-time CSI data is connected via WebSocket. The poses you see are synthetic — they don't change based on actual room conditions.

To get real detection from your ESP32 mesh:

1. Start the aggregator server — this collects CSI frames from your ESP32 nodes via UDP and exposes a WebSocket endpoint
2. Connect the UI — in the detection/observatory page, enter your WebSocket URL (e.g. ws://localhost:3030/ws/csi) and click Connect
3. Verify CSI data is flowing — check the serial monitor on each ESP32 to confirm frames are being sent

Without the WebSocket connection, the UI has no way to receive your ESP32 data and falls back to the built-in simulation.

Training is not required for basic detection — the pre-trained model should respond to CSI signal changes. But you do need the data pipeline (ESP32 → UDP → aggregator → WebSocket → browser) connected end-to-end.

If you're unsure whether your ESP32s are sending data correctly, check that:

• Each node has a unique node_id (set via provision.py)
• They're sending UDP packets to the aggregator's IP/port
• The aggregator logs show incoming frames

I see, so therefor I must follow your "Tutorial: ESP32-S3 CSI Pipeline End-to-End Setup (ADR-018) #34" to correctly set up the mesh? You must use the Rust Toolchain to set up the mesh?

[agale]

Hello,

I'm having the same problem. I'm running 4 esp32s3 devices, flashed with the latest 0.4.1 firmware and set unique node_id's on each (1, 2, 3, 4). I've verified unique node_id's using ESPConnect and verified websocket connections are active and receiving/sending on the aggregator via chrome and command line:

1. opened dev tools in chrome and verified data is flowing on the websocket 'ws://192.168.1.124:3000/ws/sensing' matching what i get when running curl below
2. ran 'curl -s http://localhost:3000/api/v1/sensing/latest | python -m json.tool" on the aggregator and received:
   { "classification": { "confidence": 0.4064675830596627, "motion_level": "present_still", "presence": true }, "estimated_persons": 2, "features": { "breathing_band_power": 32.903202180900834, "change_points": 6, "dominant_freq_hz": 0.35000000000000003, "mean_rssi": 7.0, "motion_band_power": 26.898831904185837, "spectral_power": 147.34375, "variance": 29.901017042543337 }, "nodes": [ { "amplitude": [ 0.0, ... 9.848857801796104 ], "node_id": 1, "position": [ 2.0, 0.0, 1.5 ], "rssi_dbm": 7.0, "subcarrier_count": 64 } ], "persons": [ { "bbox": { "height": 244.44112053494786, "width": 108.91373585095698, "x": 229.2044958356782, "y": 133.86768695611755 }, "confidence": 0.4064675830596627, "id": 1, "keypoints": [ { "confidence": 0.4009922522320911, "name": "nose", "x": 284.0976328491051, "y": 152.63260829060602, "z": -0.3348 }, ... { "confidence": 0.3113914631030022, "name": "right_ankle", "x": 314.4675575965034, "y": 336.0162143867997, "z": -0.3348 } ], "zone": "zone_1" }, { "bbox": { "height": 227.97920383638683, "width": 136.63566973109215, "x": 308.9224067347468, "y": 134.05118632224293 }, "confidence": 0.34549744560071327, "id": 2, "keypoints": [ { "confidence": 0.2742083599763702, "name": "nose", "x": 382.70591564243404, "y": 151.80354714016647, "z": -0.3348 }, ... { "confidence": 0.3411495031717004, "name": "right_ankle", "x": 405.6662439185215, "y": 352.03039015862976, "z": -0.3348 } ], "zone": "zone_2" } ], "signal_field": { "grid_size": [ 20, 1, 20 ], "values": [ 0.04290034941372243, 0.04658961106558277, ... 0.04658961106558598, 0.04290034941372246 ] }, "source": "esp32", "tick": 388570, "timestamp": 1773370675.291, "type": "sensing_update", "vital_signs": { "breathing_confidence": 0.29132659601572725, "breathing_rate_bpm": 8.063217145564051, "heart_rate_bpm": 94.62516966236737, "heartbeat_confidence": 0.43073135233705634, "signal_quality": 0.5 } }

One odd thing is the json response only shows 1 node ("node_id": 1) under the "nodes" object no matter how many esp32s3's I connect. In my setup shouldn't there be 4 "nodes" objects?

Cheers

[munozluis1015]

2. 96104 ], "node_id": 1,

Hello, just wondering, did you follow the 'Tutorial: ESP32-S3 CSI Pipeline End-to-End Setup (ADR-018) #34" to create the mesh of ESP32's?

[agale]

Hi, no I just read your response and hadn't followed that step. Will report back.
Note, this is the guide I initially followed RuView Setup Guide
Thank you.

[agale]

Update, followed #34 and am getting the expected outcome in terms of info:
[node:1 seq:697793] sc=192 rssi=-56 amp=34.1
[404 bytes from 192.168.1.218:59999]
[node:1 seq:1609] sc=192 rssi=-66 amp=25.3
[404 bytes from 192.168.1.113:63616]
[node:1 seq:731436] sc=192 rssi=-58 amp=32.7
[148 bytes from 192.168.1.138:64452]
[node:1 seq:731440] sc=64 rssi=-53 amp=10.5
[404 bytes from 192.168.1.144:64417]
[node:1 seq:763269] sc=192 rssi=-50 amp=33.2
[148 bytes from 192.168.1.218:59999]
[node:1 seq:1611] sc=64 rssi=-74 amp=9.6
[148 bytes from 192.168.1.218:59999]
...
However, node number doesn't change as stated above. Double checked NVS Inspector in ESPConnect and verified unique node_id values.

Thanks

[munozluis1015]

Update, followed #34 and am getting the expected outcome in terms of info: [node:1 seq:697793] sc=192 rssi=-56 amp=34.1 [404 bytes from 192.168.1.218:59999] [node:1 seq:1609] sc=192 rssi=-66 amp=25.3 [404 bytes from 192.168.1.113:63616] [node:1 seq:731436] sc=192 rssi=-58 amp=32.7 [148 bytes from 192.168.1.138:64452] [node:1 seq:731440] sc=64 rssi=-53 amp=10.5 [404 bytes from 192.168.1.144:64417] [node:1 seq:763269] sc=192 rssi=-50 amp=33.2 [148 bytes from 192.168.1.218:59999] [node:1 seq:1611] sc=64 rssi=-74 amp=9.6 [148 bytes from 192.168.1.218:59999] ... However, node number doesn't change as stated above. Double checked NVS Inspector in ESPConnect and verified unique node_id values.

Thanks

I will try myself in the morning and report back too!

[agale]

Every ~10-20 packets on each node I get:
parse error: Invalid magic: expected 0xc5110001, got 0xc5110002
[148 bytes from 192.168.1.113:51571]

[JAGUARAVI]

In rust-port/wifi-densepose-rs/crates/wifi-densepose-sensing-server/src/main.rs (ESP32 source mode), the server always returns only a single NodeInfo in the nodes array of every SensingUpdate, regardless of how many ESP32s are actually streaming.

Even though the ESP32 firmware is correctly tagging packets with different node_id values, the Rust server overwrites the node cache on every packet and only keeps the last one received.

[ruvnet]

Likely Cause: Channel Mismatch or Missing MAC Filter

When the detection window shows identical output regardless of position, the most common cause is the ESP32 collecting CSI on the wrong channel or from the wrong AP.

v0.4.2-esp32 (release) fixes this with:

1. Auto-channel detection — firmware now detects the AP's channel after WiFi connect (no more hardcoded channel)
2. MAC filter — isolate CSI from a specific AP to eliminate noise from neighboring networks

Try this:

# Flash new firmware
python -m esptool --chip esp32s3 --port COMX --baud 460800 write_flash \
  0x0 bootloader.bin 0x8000 partition-table.bin 0x20000 esp32-csi-node.bin

# Provision with your AP's MAC address (find it on your router admin page)
python provision.py --port COMX --ssid "YourSSID" --password "YourPass" \
  --target-ip YOUR_PC_IP --filter-mac AA:BB:CC:DD:EE:FF

The --filter-mac ensures you're only getting CSI from your specific AP, not from neighbors. This should give you varying detection signals as people move.

Also verify your aggregator PC is receiving UDP packets on port 5005 (netstat -an | grep 5005).

[agale]

Hi,

I flashed 0.4.2 and provisioned with the new provision.py (latest in repo) but after some testing got the following errors:

1. with --channel other than 6 (on router and esp32s3):
   [632 bytes from 192.168.1.138:52541]
   parse error: Invalid subcarrier count: 306 (max 256)

2. specifying --filter-mac regardless of channel:
   [node:1 seq:0] sc=192 rssi=-54 amp=13.2
   [404 bytes from 192.168.1.138:49369]

$ netstat -an | grep 5005
udp 0 0 0.0.0.0:5005 0.0.0.0:*

Thanks

[munozluis1015]

Hi,

I flashed 0.4.2 and provisioned with the new provision.py (latest in repo) but after some testing got the following errors:

1. with --channel other than 6 (on router and esp32s3):
   [632 bytes from 192.168.1.138:52541]
   parse error: Invalid subcarrier count: 306 (max 256)
2. specifying --filter-mac regardless of channel:
   [node:1 seq:0] sc=192 rssi=-54 amp=13.2
   [404 bytes from 192.168.1.138:49369]

$ netstat -an | grep 5005 udp 0 0 0.0.0.0:5005 0.0.0.0:*

Thanks

Do you know to pull up the observatory page so I can enter my WebSocket URL? I'm having trouble finding where to put it.