#Channels

1 messages · Page 1 of 1 (latest)

humble river
#

I've successfully setup discord and whatsapp connections. But none of them are responding. When I type I can see the bot have the "typing" indicator but then it doesnt send anything at all

reef siloBOT
#

Typing with no final message usually means the channel is connected, but the run is failing or being suppressed after handoff. Since it’s happening on both Discord and WhatsApp, I’d check the shared runtime/model first, not re-pair the channels yet.

Please paste these, in order:

openclaw --version
openclaw status --all
openclaw models status
openclaw channels status --probe

Then do this once:

openclaw logs --follow
#

Send one test message, then paste the log lines from that attempt.

A few common gotchas:

  • Discord guild replies: Message Content Intent must be enabled.
  • Discord guild/channel must be allowlisted, and if channels.discord.guilds.<id>.channels exists, only listed channels reply.
  • Discord and WhatsApp groups often require an explicit mention by default.
  • DMs can be blocked by pairing / allowlist policy.

Docs:

Also tell me whether you’re testing in DMs, group chats, or both. That narrows it down fast.

humble river
#

22:09:24+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
22:09:24+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
gateway connect failed: GatewayClientRequestError: pairing required
22:09:24+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"pairing-required","handshake":"failed","durationMs":20,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"76a84f7e-b31a-46a4-a017-03d45da84d52","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":46346,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:46346->127.0.0.1:18789","deviceId":"4765ec4caa38735b0e26815a6c0b940e31b2645f3c4ff58e6842dfedede6803e","requestId":"d7ce7b55-4154-427c-a008-7fd98549b90f","reason":"scope-upgrade"} closed before connect conn=a74e1489-90f6-4072-b466-bbc35ea4dd60 peer=127.0.0.1:46346->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1008 reason=connect failed
22:09:25+00:00 warn gateway {"subsystem":"gateway"} security audit: device access upgrade requested reason=scope-upgrade device=4765ec4caa38735b0e26815a6c0b940e31b2645f3c4ff58e6842dfedede6803e ip=unknown-ip auth=token roleFrom=operator roleTo=operator scopesFrom=operator.read scopesTo=operator.admin,operator.approvals,operator.pairing,operator.read,operator.talk.secrets,operator.write client=cli conn=947c9477-d53d-4ec4-ac23-ffd754a8bc18

version latest, models fine because on tui it works. openclaw pairing list [channel] show nothing but the logs say pairing needed.

reef siloBOT
#

Ah, this log is useful. It’s a different pairing issue than the channel one.

What you pasted is device pairing / scope-upgrade, not discord or whatsapp sender pairing:

  • reason":"scope-upgrade"
  • client=cli
  • scopesFrom=operator.read
  • scopesTo=operator.admin,operator.approvals,operator.pairing,operator.read,operator.talk.secrets,operator.write

So your local CLI/TUI device is only approved for read-ish access, and when it tries to do more, the gateway says pairing required.

That means openclaw pairing list [channel] is kind of a red herring here. The command you want is:

openclaw devices list
openclaw devices approve <requestId>
#

Important: run openclaw devices list right before approving, then use the fresh exact requestId.

Docs:

One more important bit: this log is about the CLI client, so it does not fully explain why Discord/WhatsApp replies are disappearing. It explains why your manual pairing commands are failing.

After approving the device, do this for the actual no-reply bug:

openclaw channels status --probe
openclaw logs --follow

Then send one test message from Discord or WhatsApp and paste the log lines from that attempt. Right now I’d expect the real cause to be one of: