observery

[mhmdhz]

My nodes are connected but I can't see the body skeleton live in this part{observery}, but I can receive data in the other part(sensing)

[ruvnet]

A few things to check when sensing data arrives but the observatory skeleton doesn't render:

1. Simulation mode — if the UI is running in simulation mode it will show a static/looping skeleton regardless of live data. Check the observatory panel for a "Simulation" indicator and disable it.

2. UDP data flow — the sensing tab and the observatory consume different data paths. Confirm the aggregator is forwarding packets to the correct host/port that the observatory is listening on (default 0.0.0.0:8765). If you're running Docker with --network host on Linux this is automatic; on Windows/macOS it requires explicit port mapping.

3. Known Issues guide — Known Issues & Setup Troubleshooting Guide #301 collects the most common setup problems including the "UI shows same skeleton" and "No hardware detected" cases with step-by-step fixes.

4. Tutorial — ⭐ Tutorial: ESP32-S3 CSI Pipeline End-to-End Setup (ADR-018) #34 (ESP32-S3 CSI Pipeline End-to-End Setup) walks through the full stack from flash to live observatory view and is the most up-to-date reference.

If none of those resolve it, please share the observatory console output (browser DevTools → Console) and the sensing-server logs — that'll make it much easier to pinpoint the disconnect.

---

Generated by Claude Code

[mhmdhz]

A few things to check when sensing data arrives but the observatory skeleton doesn't render:

1. Simulation mode — if the UI is running in simulation mode it will show a static/looping skeleton regardless of live data. Check the observatory panel for a "Simulation" indicator and disable it.
2. UDP data flow — the sensing tab and the observatory consume different data paths. Confirm the aggregator is forwarding packets to the correct host/port that the observatory is listening on (default 0.0.0.0:8765). If you're running Docker with --network host on Linux this is automatic; on Windows/macOS it requires explicit port mapping.
3. Known Issues guide — Known Issues & Setup Troubleshooting Guide #301 collects the most common setup problems including the "UI shows same skeleton" and "No hardware detected" cases with step-by-step fixes.
4. Tutorial — ⭐ Tutorial: ESP32-S3 CSI Pipeline End-to-End Setup (ADR-018) #34 (ESP32-S3 CSI Pipeline End-to-End Setup) walks through the full stack from flash to live observatory view and is the most up-to-date reference.

If none of those resolve it, please share the observatory console output (browser DevTools → Console) and the sensing-server logs — that'll make it much easier to pinpoint the disconnect.

Generated by Claude Code

i added in the setting the websocket port and the websocket connected to observery but still i have issue with 2 node when i move around the esp32 s3 wroom 1 modules my skelet doesn't move