Troubleshooting human

[Velociraptor85]

I wanted to give this project a try but somehow its not easy to get into this.

Could you add to your documentation details about what you consider to be a zone?

I wanted to test this with 3 esp32s3 and my laptop I build all and could connect the devices but one improvement I would like to have is a bit more logging output on the server component I was running the rust sensing server and could not figure out if all the esps would connect since it just shows connecting but not which device or what properties like zone/node id/ tdm etc part of those configs I found out by running the aggregator bin which showed me that all the esps connected since different ips where visible but apparantly all the node ids where the same which i fixed but it would be good if the sensing server would also log not only that there was a connection but from which node id/ip

Further more there seems to be a lot of inconsistencies in the documentation and the different versions of the tool. Which make it quite difficult to read and setup properly :)
Exmaple:

• Known Issues & Setup Troubleshooting Guide #301 (comment) states --node-id option
• https://github.com/ruvnet/RuView/blob/main/docs/user-guide.md#hardware-setup under "TDM slot assignment" no node-id option is mentioned

Non the less quite interessting project you have ongoing here and I am really interessted to test this but sadly I was not able to set this up properly yet.

[ruvnet]

Thanks for the detailed feedback — these are all valid pain points.

1. Node ID Collisions

This was a known issue fixed in v0.5.0 — node IDs now persist to NVS. If you flashed firmware before v0.5.0, all nodes default to `node_id: 1`. To fix:

```bash

Re-provision each node with a unique node-id:

python firmware/esp32-csi-node/provision.py --port COM_PORT
--ssid "YourWiFi" --password "secret" --target-ip SERVER_IP
--node-id 1 # Use 1, 2, 3 for your 3 nodes
```

2. Server Logging

You're right — the sensing server only logs "connecting" without identifying which node. This is a good improvement request. In the current code, you can increase log verbosity:

```bash
RUST_LOG=debug ./sensing-server
```

This will show per-frame debug output including node_id:
```
DEBUG ESP32 frame from 192.168.1.42: node=1, subs=64, seq=12345
DEBUG ESP32 frame from 192.168.1.43: node=2, subs=64, seq=678
```

As of PR #326 (per-node state pipeline), the server tracks each node independently in a `HashMap<u8, NodeState>`. You'll see all active nodes listed in the WebSocket `sensing_update` message's `nodes` array.

3. Documentation Inconsistencies

This is tracked in #301 (Known Issues & Troubleshooting Guide). The project has evolved rapidly and some docs reference older CLI flags. Key notes:

• `--node-id` is a `provision.py` argument, not a server argument
• TDM (Time Division Multiplexing) is optional — only needed if you want nodes to take turns on the same channel to avoid interference
• For a basic 3-node setup, you just need unique node IDs and the same `--target-ip`

Quick Setup for 3 ESP32-S3 Nodes

```bash

1. Flash all 3 with v0.5.1: https://github.com/ruvnet/RuView/releases/tag/v0.5.1-esp32

2. Provision each (unique node-id, same target-ip):

python provision.py --port COM3 --ssid "WiFi" --password "pass" --target-ip 192.168.1.100 --node-id 1
python provision.py --port COM4 --ssid "WiFi" --password "pass" --target-ip 192.168.1.100 --node-id 2
python provision.py --port COM5 --ssid "WiFi" --password "pass" --target-ip 192.168.1.100 --node-id 3

3. Start sensing server with debug logging:

cd rust-port/wifi-densepose-rs
RUST_LOG=debug cargo run --release -p wifi-densepose-sensing-server

4. Open the UI at http://localhost:3030

```

Thanks for the interest — happy to help debug further.

[ruvnet]

Answered — setup instructions, debug logging, and provisioning commands provided above. Reopen if you need more help.

[Velociraptor85]

• OK, so I have done all of it with the debug command I also see the frames comming in from different ips and with different node ids. Even cloned and compiled the new 0.5.3 version and falshed that. As well as set the edge=2 and found one ld2410 which I attached the the closes node to me. (wasm output and esp vital frames are coming in)
• Interesstingly enough the health status stil says it just client:2 but mentiones status:ok so not sure how this metric gets generated
• non the less I went onward and recorded datasets as mentioned in https://github.com/ruvnet/RuView/blob/main/docs/user-guide.md#adaptive-classifier included the json content with the train_ as without it it will not use the data for actual trainging which is sadly not mentioned in Known Issues & Setup Troubleshooting Guide #301 (comment) as well as trained the adaptive classifier as mentioned in https://github.com/ruvnet/RuView/blob/main/docs/user-guide.md#training-the-model
  ** now I have a jittery person in the observatory

So next is probably https://github.com/ruvnet/RuView/blob/main/docs/user-guide.md#training-a-model but I am unsure if this is required for a stable presence recognition or if this is requred for the edge comput offloading or if this should be an alternative for the previously trained adaptive classifier

Also whats the reason for the ws interface should this be on port 3001 for the server to work or is this optional or is the port 8765 even hardcoded somewhere :? non the less I did receive an error when i tried the mentioned command in https://github.com/ruvnet/RuView/blob/main/docs/user-guide.md#curl-single-frame altough I verified that the port is open and the sensing-server is listening on the port.

Well I would love to get this thing flying, just wasnt lucky yet. Anyhow interessting idea 👍

[Leeeeeeedw]

After Re-provision 3 ESP32-S3 with a unique node-id, I use the below command on Windows Powershell

cd rust-port/wifi-densepose-rs
set RUST_LOG=debug
cargo run --release -p wifi-densepose-sensing-server

As you see in the picture, I can open the UI with the http://localhost:8080/ui/index.html link, but I can't see or find the log output, could you tell me this?