Live Human Pose Detection websocket connection failed

[fox007ggr]

你好，我用了3个esp32s3 分别设置了
python provision.py --port COM3 --ssid "xiaomi_24" --password "---" --target-ip 192.168.28.147 --node-id 0 --tdm-slot 0 --tdm-total 3
python provision.py --port COM3 --ssid "xiaomi_24" --password "---" --target-ip 192.168.28.147 --node-id 1 --tdm-slot 1 --tdm-total 3
python provision.py --port COM3 --ssid "xiaomi_24" --password "---" --target-ip 192.168.28.147 --node-id 2 --tdm-slot 2 --tdm-total 3

Live Human Pose Detection

没有检测到人像运动

服务端运行在 ubuntu 22.04 上，UDP端口是 5005

请问，我改怎么设置才能正确的运行起来

[fox007ggr]

[ruvnet]

The screenshot alone isn't enough to diagnose — could you share a few pieces of text so we can pinpoint where the connection is failing?

1. Browser DevTools → Network tab
Filter by WS, click the failing connection, copy the Request URL and the status code (e.g. 101 Switching Protocols, 404, 502, connection refused). Also copy any error string from the Console tab — for example:

• WebSocket connection to 'ws://...' failed: Error during WebSocket handshake: Unexpected response code: 404
• WebSocket is closed before the connection is established.
• Mixed Content: The page at 'https://...' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://...'
• net::ERR_CONNECTION_REFUSED

2. Server side

docker logs wifi-densepose --tail 50
curl -s http://<server>:3000/health | jq .

Look for lines like WebSocket server listening on 0.0.0.0:3001 or WebSocket client connected (sensing). The sensing-server actually serves WS on port 3001, not 3000 — a common cause of "connection failed" is that the UI was opened from an older api.config.js that still points WS at port 3000.

3. Page URL
The exact URL you have open in the address bar (host + port). And which UI you're using — the bundled /ui/ from sensing-server, or the dashboard from the v1 Python stack.

For reference, #386 and #499 both had similar-looking "websocket failed" symptoms; both turned out to be config-pinning issues in the cached UI. The fix in #272 patches app/ui/config/api.config.js to derive the WS URL from window.location rather than hardcoding localhost:3000. If your image is from a Docker deployment of wifi-densepose, you may need to copy the patched api.config.js into the container as droidblastnz did in #499 — happy to walk through that once we know which UI you're hitting.

---

Generated by Claude Code

[95P10Aa4Ob]

Fix: WebSocket connects to wrong port

The UI's sensing.service.js builds the WebSocket URL using
window.location.host which returns the HTTP port (3000), but the
server runs /ws/sensing on the WebSocket port (3001).

Fix — patch sensing.service.js:

sed -i 's|const _wsHost.*window.location.host.localhost:3000.|const _wsHost = (typeof window !== "undefined" && window.location.host) ? window.location.host.split(":")[0] + ":3001" : "localhost:3001";|' ui/services/sensing.service.js

Then restart Docker mounting the patched ui folder:

docker stop $(docker ps -q)
docker run -p 3000:3000 -p 3001:3001 -p 5005:5005/udp
-e CSI_SOURCE=esp32
-v ~/RuView/ui:/app/ui
ruvnet/wifi-densepose:latest

Root cause: The HTTP server (port 3000) and WebSocket server
(port 3001) are two separate Axum listeners. The UI assumes both
are on the same port. Tested on Raspberry Pi 4 + ESP32-S3-DevKitC-1.

[fox007ggr]

你好：

我强制修改文件 websocket.service.js 82行
url = 'ws://192.168.28.147:3001/ws/sensing';

sensing.service.js 16行
const _wsHost ='192.168.28.147:3001';

websocet 链接成功，但是页面一直报错

[fox007ggr]

websocket.service.js:162 Uncaught TypeError: Cannot set properties of undefined (setting 'lastActivity')
at ws.onmessage (websocket.service.js:162:31)
ws.onmessage @ websocket.service.js:162

[fox007ggr]

还是没有人像

[fox007ggr]

run DEMO 正常显示

[fox007ggr]

成功的显示出来了 ，但是很慢