Looking for some help: OpenClaw maintainers so they can look directly at your logs + schema | Friends of the Crustacean 🦞🤝 | Page 1

autumn bronze Mar 5, 2026, 4:58 PM

#

IS this the correct place: Telegram: ON · OK · accounts 1/1
Bot: @Myopenclawminibot
DM /start + ping → no reply
Accounts panel: "Unsupported schema node. Use Raw mode."
Changing channels.telegram.dmPolicy from "pairing" to "open" → GatewayRequestError: invalid config
Config (raw) has no accounts/access block; version 2026.3.2 on macOS (node 22.22.0)

halcyon thornBOT Mar 5, 2026, 4:58 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

rough ruinBOT Mar 5, 2026, 5:01 PM

#

Yep — this thread in #help is the right place for this kind of “Telegram is connected but silent” debugging.

A few concrete points from the docs that line up with what you’re seeing:

Dashboard “Unsupported schema node. Use Raw mode.”

That’s just the Dashboard form renderer not being able to represent some config shapes (maps like groups: { "*": ... }, etc).
It’s not inherently a Telegram failure; it just means “edit this in Raw mode / config file / CLI”.

Why dmPolicy: "open" throws GatewayRequestError: invalid config

open is only valid if you also set allowFrom to include "*".

Minimal valid example:

{
  channels: {
    telegram: {
      enabled: true,

#

        dmPolicy: "open",
        allowFrom: ["*"],
      },
    },
  }

If you want “only me can DM the bot”, use:

{
  channels: {
    telegram: {
      dmPolicy: "allowlist",
      allowFrom: ["tg:123456789"], // your numeric Telegram user id
    },
  },

#

Why /start + ping can still look like “no reply” on dmPolicy: "pairing"

/start does not generate a pairing code by itself (FAQ calls this out).
The fastest check is:
```
openclaw pairing list telegram
```
If you see a pending code after you DM the bot, approve it:
```
openclaw pairing approve telegram <CODE>
```

If it’s truly receiving nothing, run the standard ladder (and paste the Telegram-related log lines):

#

openclaw gateway status
openclaw channels status --probe
openclaw logs --follow

Then DM the bot while logs --follow is running — we should at least see inbound updates (or a clear Telegram API error).

Docs to anchor this:

autumn bronze Mar 5, 2026, 5:16 PM

#

We fixed it with the Paring approved. Thank you very much for the help

#Looking for some help: OpenClaw maintainers so they can look directly at your logs + schema