You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How to use aggregator with observatory and server #383
Note: --udp-port 5006 (not 5005) — the sensing server listens on the aggregator's forwarding port.
Step 3: Verify the chain
# Check aggregator is receiving from nodes# (look for "Received frame from node X" in aggregator logs with --verbose)# Check sensing server has nodes
curl http://localhost:3000/api/v1/sensing/latest
# Open UI# http://localhost:3000/ui/index.html
Pointing the sensing server to 5005 instead of 5006
Expecting the aggregator to provide visualization
Not verifying that the sensing server is actually receiving data
Correct Setup (clean sequence)
Step 1 — Start Aggregator
cargo run -p wifi-densepose-hardware --bin aggregator --
--bind 0.0.0.0:5005
--forward 127.0.0.1:5006
--verbose
You should see logs like:
Received frame from node 1
Received frame from node 2
Step 2 — Start Sensing Server (CRITICAL PART)
sensing-server
--source esp32
--udp-port 5006
--http-port 3000
--ws-port 3001
This is where most setups fail:
It must listen on 5006, not 5005
Step 3 — Verify Data Reaches Server
JSON with node data
timestamps
possibly motion / CSI values
If empty:
Aggregator is not forwarding correctly
Or server not bound to correct port
Step 4 — Open UI http://localhost:3000/ui/index.html
Debugging Checklist (if it still doesn’t work)
Confirm aggregator forwarding
Run:
netstat -anu | grep 5006
Or add debug logs:
Look for outgoing packets
2. Confirm server is listening
netstat -anu | grep 5006
3. Bypass aggregator (isolate problem)
The sensing server connects directly to ESP32 nodes over UDP by default. To use your aggregator as the data source instead of talking to nodes individually, you need to point the sensing server at the aggregator's output endpoint.
Check sensing-server --help for the available --source and aggregator connection flags in your release version — the exact flags vary by version. The aggregator re-emits all node data on a single endpoint that the sensing server can consume, which is how multi-node setups are intended to work at scale.
The Known Issues & Setup Troubleshooting Guide (#301) covers the aggregator → server → observatory/UI flow. If your aggregator is receiving data from the nodes, the next step is to ensure the sensing server is running and pointed at the aggregator, then load the UI (observatory) from the server's HTTP endpoint. The guide has the step-by-step for common Docker and native setups.
Activity
ruvnet commentedon Apr 16, 2026
The data flow from aggregator to visualization is:
Step 1: Start the aggregator (it receives from ESP32 nodes on 5005, re-emits on 5006):
Step 2: Start the sensing server pointed at the aggregator's output port:
Note:
--udp-port 5006(not 5005) — the sensing server listens on the aggregator's forwarding port.Step 3: Verify the chain
See also the setup troubleshooting guide at #301.
Generated by Claude Code
Muitamax commentedon Apr 20, 2026
Most Common Mistake (you’re likely here)
You’re probably doing one of these:
Pointing the sensing server to 5005 instead of 5006
Expecting the aggregator to provide visualization
Not verifying that the sensing server is actually receiving data
Correct Setup (clean sequence)
Step 1 — Start Aggregator
cargo run -p wifi-densepose-hardware --bin aggregator --
--bind 0.0.0.0:5005
--forward 127.0.0.1:5006
--verbose
You should see logs like:
Received frame from node 1
Received frame from node 2
Step 2 — Start Sensing Server (CRITICAL PART)
sensing-server
--source esp32
--udp-port 5006
--http-port 3000
--ws-port 3001
This is where most setups fail:
It must listen on 5006, not 5005
Step 3 — Verify Data Reaches Server
Run:
curl http://localhost:3000/api/v1/sensing/latest
Expected:
JSON with node data
timestamps
possibly motion / CSI values
If empty:
Aggregator is not forwarding correctly
Or server not bound to correct port
Step 4 — Open UI
http://localhost:3000/ui/index.html
Debugging Checklist (if it still doesn’t work)
Run:
netstat -anu | grep 5006
Or add debug logs:
Look for outgoing packets
2. Confirm server is listening
netstat -anu | grep 5006
3. Bypass aggregator (isolate problem)
Run sensing server directly on node port:
sensing-server --source esp32 --udp-port 5005
If this works:
Aggregator is the problem
UDP ports:
5005
5006
must be open
ESP32 nodes must send to:
<aggregator_ip>:5005
NOT:
<server_ip>:5006
ruvnet commentedon Apr 28, 2026
The sensing server connects directly to ESP32 nodes over UDP by default. To use your aggregator as the data source instead of talking to nodes individually, you need to point the sensing server at the aggregator's output endpoint.
Check
sensing-server --helpfor the available--sourceand aggregator connection flags in your release version — the exact flags vary by version. The aggregator re-emits all node data on a single endpoint that the sensing server can consume, which is how multi-node setups are intended to work at scale.Generated by Claude Code
ruvnet commentedon May 11, 2026
The Known Issues & Setup Troubleshooting Guide (#301) covers the aggregator → server → observatory/UI flow. If your aggregator is receiving data from the nodes, the next step is to ensure the sensing server is running and pointed at the aggregator, then load the UI (observatory) from the server's HTTP endpoint. The guide has the step-by-step for common Docker and native setups.
Generated by Claude Code