"TTS/voice messages not sending properly"
• OpenClaw version: 2026.2.19-2 (latest stable)
• OS: macOS 26.3 (arm64), Node 22.22.0
• Channel: Telegram
• Gateway: Local loopback
Issue:
TTS voice messages are generated successfully but sent as text file paths instead of actual voice messages in Telegram.
Expected behavior:
MEDIA:/path/to/voice.opus should be sent as a Telegram voice message.
Actual behavior:
The literal text MEDIA:/var/folders/.../voice-xxxxx.opus appears in the chat instead of a playable voice message.
Evidence:
• TTS files generated correctly (e.g., 49KB opus files with proper permissions)
• File exists at specified path
• marker present in TTS response
• No errors in gateway logs related to TTS or media
• Issue persists after:
• OpenClaw update to latest version
• Telegram client restart
• Multiple TTS attempts
Workaround:
None currently. Reverting to text-only responses.
• OS: macOS 26.3 (arm64), Node 22.22.0
• Channel: Telegram
• Gateway: Local loopback
Issue:
TTS voice messages are generated successfully but sent as text file paths instead of actual voice messages in Telegram.
Expected behavior:
MEDIA:/path/to/voice.opus should be sent as a Telegram voice message.
Actual behavior:
The literal text MEDIA:/var/folders/.../voice-xxxxx.opus appears in the chat instead of a playable voice message.
Evidence:
• TTS files generated correctly (e.g., 49KB opus files with proper permissions)
• File exists at specified path
• marker present in TTS response
• No errors in gateway logs related to TTS or media
• Issue persists after:
• OpenClaw update to latest version
• Telegram client restart
• Multiple TTS attempts
Workaround:
None currently. Reverting to text-only responses.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
