Building a Voice Assistant with OpenClaw, Alexa, and Local LLM

A developer shared their implementation of a voice-first assistant that uses OpenClaw as the AI agent backbone, integrated with Alexa for voice interaction and a local LLM for cost-effective query handling.
How It Works
The system is triggered by saying "Alexa, open Lucy" to a custom Alexa skill. Queries are processed through a four-tier routing system:
- Fast path (0ms): Handles time, date, and hardcoded responses
- Ollama local LLM (<1s): Uses Qwen 2.5 3B for general knowledge queries, running on a Mac Mini with Apple Silicon
- Claude agent (5-12s): Handles personal context, memory, and complex reasoning
- Deferred + tools (up to 2min): Manages email, web search, and database queries via Home Assistant TTS
Responses return to the same Alexa device that initiated the query, auto-detected via Home Assistant's last_called feature. The system uses Piper TTS on Home Assistant for neural Spanish voice output on Sonos speakers and can deliver morning briefings with market data, calendar information, and business metrics.
Technical Stack
- OpenClaw: AI agent backbone supporting Telegram, Alexa, and voice interfaces
- Alexa Custom Skill: Node.js proxy with PIN authentication and session chaining
- Ollama + Qwen 2.5 3B: Local LLM providing ~0.5s responses
- Home Assistant: Integrates Alexa Media Player, Piper TTS, and device routing
- Piper TTS: Neural Spanish voice for Sonos speakers
Key Implementation Details
The developer found that using a local LLM saves approximately 80% of API costs for simple questions that don't require Claude. However, they noted that local models "hallucinate freely" and added a bypass filter for business and financial queries.
Alexa speech recognition was identified as the bottleneck, with AMAZON.SearchQuery and multiple sample utterances helping improve accuracy. Authentication uses userId rather than sessionId since Alexa generates new sessions for each invocation. The developer persists authentication to file because in-memory Maps don't survive proxy restarts.
The proxy code is available as open source: openclaw-alexa-voice. Future plans include wake word detection ("Hey Lucy"), smart home control, and presence-based speaker routing.
📖 Read the full source: r/openclaw
👀 See Also

Developer Switches Business OpenClaw to RunLobster After Security Incident, Keeps Personal Instance Self-Hosted
A developer moved their business OpenClaw agent to RunLobster at $49/month after discovering their self-hosted instance had been exposed on 0.0.0.0 for 3 months following the February CVE. They kept personal OpenClaw self-hosted on a Mac Mini for non-critical workloads.

Recursive AI Agent System Builds and Improves Its Own Website
A developer built a website using Claude Code that generates its own newsletter content, then uses that content to identify gaps and create an improvement backlog. The system runs on a weekly pipeline deployed on Vercel.

User Deploys AI Assistant 'Elvis' on VPS for Project Management Tasks
A developer spent three days setting up an AI assistant called 'Elvis' on a Linux VPS, integrating it with Microsoft Teams, JIRA, Asana, and email systems. The assistant successfully handled project management tasks including reading emails, extracting requirements, updating change requests, and coordinating with team members.

Real-time Conflict Monitor Built with Claude API Analyzes News Impact
A developer used Claude's API to build an automated pipeline that reads conflict news from 100+ sources, classifies by topic/country/severity, generates impact scores (1-100), and produces 3-line smart summaries.