Live WeCom topology …
Message path (not just connectivity). FIRST hop from WeCom is always Grok Bot box listeners (Bot Secret Connect WS). Hub & online app are never first. Owner: Grok Bot / Sever (box sockets + hub ops). wecom_ws_on_site: false.
Box listeners
Edges
Live JSON GET /api/gateway/topology · refresh ~4s
Loading…
Primary hub
https://wecom.candas.cn/ (aliases /hub · /gateway)
Hard rule
Site is HTTPS/JSON/SSE gateway only. WeCom long-connection WS is owned by Grok Bot box listeners. Online app & AIs are clients of this gateway — never a second Bot Connect WS on Plesk.
Quick links
Gateway snapshot
…
Bot status (inventory)
Authorities / scopes / blockers
From bots-inventory + connection flags. connection_owner is flag-based, not a live WS probe.
| Bot | botid | Scopes | Saved | Blocker | Owner | Listener |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Monitor live events
SSE /api/events — ingest/relay stream, not Bot Secret Connect.
Daily chat / group reports
Loading stub…
| Group | chatid | Status | Summary |
|---|
Highlights
None yet (pending_wecom_export).
Admin smart-issues checklist
Manual WeCom Admin paths + inventory blockers. Site never rotates Secret / never switches 长连接→回调.
Inventory blockers
Useful Admin paths
- WeCom Admin → 安全与管理 → 管理工具 → 智能机器人 (per-bot scopes / multi-user / 长连接)
- Do not: Secret rotate · 长连接→URL callback · 开放的机器人 · delete bots
- Docs: WECOM-GATEWAY-HUB.md · WECOM-MGMT-API.md · SMART-SUMMARY-SETUP-CHINA-EGYPT.md