Help with migration from Clawdbot to OpenClaw (v2026.1.29) - WhatsApp & ElevenLabs issues
Hey! I’ve been running Clawdbot for a while, and I’ve spent the last 4 hours trying to migrate to the new OpenClaw (v2026.1.29). I need some advice on the safest way to "fresh start" my config without losing my bot's personality.
Current Situation:
System: Ubuntu, recently updated from clawdbot to openclaw@latest via the official install script.
Service: Migrated legacy clawdbot-gateway to the new openclaw-gateway.service.
The Issue: I’m getting ENOENT errors when trying /tts. It seems like the ElevenLabs API key and voice settings didn't migrate cleanly into the new ~/.openclaw/openclaw.json.
The Error: Media failed: ENOENT: no such file or directory, open '/tmp/tts-xxx/voice-xxx.mp3'.
My Question:
I want to run openclaw onboard --install-daemon to re-enter my API keys (Gemini, ElevenLabs) and properly link WhatsApp again.
Is it 100% safe to run onboard without losing my soul.md, identity.md, and memory.md files in ~/.openclaw/workspace/?
I'm terrified of wiping the bot's "soul" and memory. Should I just manually edit the JSON, or is onboard the "OpenClaw Standard" way to repair a broken config during this migration?
What I've tried:
Cleaned up legacy systemd units.
Verified openclaw doctor (shows ElevenLabs as unconfigured).
or just normal re-configure fix it? Since right now the bot WhatsApp is sending unplayable audio file for every I sent, even /new session nothing! Even /compact command on WhatsApp it sends unplayable audio
Current Situation:
System: Ubuntu, recently updated from clawdbot to openclaw@latest via the official install script.
Service: Migrated legacy clawdbot-gateway to the new openclaw-gateway.service.
The Issue: I’m getting ENOENT errors when trying /tts. It seems like the ElevenLabs API key and voice settings didn't migrate cleanly into the new ~/.openclaw/openclaw.json.
The Error: Media failed: ENOENT: no such file or directory, open '/tmp/tts-xxx/voice-xxx.mp3'.
My Question:
I want to run openclaw onboard --install-daemon to re-enter my API keys (Gemini, ElevenLabs) and properly link WhatsApp again.
Is it 100% safe to run onboard without losing my soul.md, identity.md, and memory.md files in ~/.openclaw/workspace/?
I'm terrified of wiping the bot's "soul" and memory. Should I just manually edit the JSON, or is onboard the "OpenClaw Standard" way to repair a broken config during this migration?
What I've tried:
Cleaned up legacy systemd units.
Verified openclaw doctor (shows ElevenLabs as unconfigured).
or just normal re-configure fix it? Since right now the bot WhatsApp is sending unplayable audio file for every I sent, even /new session nothing! Even /compact command on WhatsApp it sends unplayable audio
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
86,471Members
Resources
Similar Threads
Was this page helpful?
