Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Discord voice channel: bot joins but audio capture pipeline never starts (no PCM/STT/logs) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#71829•Fetched 2026-04-26 05:07:45
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
zcode-appszcode-apps
Participants
zcode-appszcode-apps
Timeline (top)
closed ×1

Error Message

  • Earlier in the same session, discord voice: receive error: The operation was aborted appeared repeatedly, but those stopped after setting daveEncryption: true and decryptionFailureTolerance: 24

Code Example

{
  "channels": {
    "discord": {
      "voice": {
        "enabled": true,
        "daveEncryption": true,
        "decryptionFailureTolerance": 24
      },
      "accounts": {
        "default": {
          "voice": {
            "enabled": true,
            "autoJoin": [{"guildId": "1468536280139698208", "channelId": "1468536280743804951"}]
          }
        }
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Bug Report

Discord voice channel bot joins successfully (confirmed via API: GET /guilds/{guild}/voice-states/@me shows bot in channel with active session), but the audio capture pipeline never starts. No PCM capture, no WAV temp files, no STT transcription, zero voice-related logs despite speaking in the channel.

Environment

  • OpenClaw 2026.4.24 (cbcfdf6)
  • talk-voice plugin loads successfully on startup
  • Discord bot has Connect + Speak permissions
  • channels.discord.voice.enabled: true
  • channels.discord.voice.daveEncryption: true
  • channels.discord.voice.decryptionFailureTolerance: 24
  • channels.discord.accounts.default.voice.autoJoin configured
  • tools.media.audio with gpt-4o-mini-transcribe
  • messages.tts with OpenAI onyx voice
  • Gateway restarts applied between config changes
  • ffmpeg available on host

Config

{
  "channels": {
    "discord": {
      "voice": {
        "enabled": true,
        "daveEncryption": true,
        "decryptionFailureTolerance": 24
      },
      "accounts": {
        "default": {
          "voice": {
            "enabled": true,
            "autoJoin": [{"guildId": "1468536280139698208", "channelId": "1468536280743804951"}]
          }
        }
      }
    }
  }
}

Observed

  • Bot appears in voice channel in Discord UI
  • Discord API confirms bot voice state: channel_id, session_id, mute: false, deaf: false
  • Gateway logs show zero voice/STT/audio/PCM/WAV activity even while user speaks
  • openclaw gateway status shows runtime healthy
  • /vc join returns "not allowlisted for voice commands" (separate issue)

Expected

  • Audio capture should start when bot joins voice channel
  • PCM → WAV → STT pipeline should transcribe speech
  • Bot should respond via TTS in the voice channel

Additional Notes

  • Earlier in the same session, discord voice: receive error: The operation was aborted appeared repeatedly, but those stopped after setting daveEncryption: true and decryptionFailureTolerance: 24
  • The voice.model config key is documented but rejected by the v2026.4.24 schema as "additional properties"
  • autoJoin does not produce any log entries on gateway startup

extent analysis

TL;DR

The most likely fix involves investigating the impact of daveEncryption and decryptionFailureTolerance settings on the audio capture pipeline, as these settings were recently changed and may be related to the issue.

Guidance

  • Verify that the daveEncryption and decryptionFailureTolerance settings are correctly configured and compatible with the Discord API and the bot's permissions.
  • Check the Discord API documentation to ensure that the bot has the necessary permissions to capture audio in the voice channel.
  • Investigate the earlier "operation was aborted" errors and determine if they are related to the current issue, as they may indicate a underlying problem with the audio capture pipeline.
  • Review the OpenClaw logs and configuration to ensure that the talk-voice plugin is properly loaded and configured.

Example

No code snippet is provided as the issue is more related to configuration and settings rather than code.

Notes

The issue may be related to the recent changes made to the daveEncryption and decryptionFailureTolerance settings, and further investigation is needed to determine the root cause. Additionally, the voice.model config key being rejected by the schema may be a separate issue that needs to be addressed.

Recommendation

Apply workaround by temporarily disabling daveEncryption and setting decryptionFailureTolerance to a lower value to see if it resolves the issue, as this may help identify if the problem is related to these settings.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#indexing error#inference speed#output truncation#response parsing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING