OpenClaw Voice: DIY Hardware for Speech-to-Speech Smart Home Control
A developer repurposed the Home Assistant Voice PE ($59 speaker puck) into a dedicated hardware voice interface for OpenClaw, achieving sub-second speech-to-speech smart home control with voiceprint-based access verification. The entire stack is open-sourced on GitHub.
Key Features
- True speech-to-speech: OpenAI Realtime handles conversations with sub-second latency. You can interrupt it mid-sentence.
- Instant memory recall: The bridge greps
MEMORY.md+ dailies + person-files directly — no agent turn. Ask "What's Grandma's number?" and get an answer in ~1 second. - Self-improving lookups: If grep misses, it escalates to a full OpenClaw turn (scans iMessage, etc.), writes the answer to a person-file. Next time it's sub-second.
- Long-running tasks that announce back: "Research flight prices to London for October" — task handed to OpenClaw, answer spoken back in the room where the request originated. Room-tagged, with details texted. If the turn runs long, you get a "still working on that" notification instead of a timeout.
- Phone call execution: Using a separate openclaw-voice-call-realtime plugin (Twilio + OpenAI Realtime), OpenClaw can place actual phone calls. Example: "Call the pharmacy and ask if my prescription is ready" — call is made, conversation transcribed, result spoken back in the kitchen.
- Voice memory: "Remember that…" with speaker-gated writes. Voiceprints work with guided enrollment, runs natively in C++ on-device.
- Custom wake word: Community trainer; "Hey Leonard" ships as default, with a dropdown to switch.
- False-wake flywheel: Double-tap the button logs a false positive, fed into weekly retraining to improve the model.
- Announce endpoint: Bearer-authed POST — any script or cron job can speak: "Leave in fifteen minutes for the school run."
Integration Contract
The bridge pattern is minimal — one URL, two POST shapes ({'question'} and {'recall'}) plus the announce endpoint. Agent-agnostic but tested against OpenClaw. Docs: agent-integration.md
Design Rule
The Voice PE has no knowledge of its own — all escalations run as OpenClaw turns in the same workspace (MEMORY.md, TOOLS.md, same scripts). Teach OpenClaw once in chat, and the voice path knows it immediately.
Cost
Light household use is tens of cents per day.
📖 Read the full source: r/openclaw
👀 See Also

Codesight CLI reduces AI coding agent token usage by scanning codebases
Codesight is a zero-dependency CLI tool that scans TypeScript, Python, and Go projects to generate compact context files, reducing Claude Code exploration tokens by 12.3× on average according to benchmarks from real production codebases.

Benchmarking Nemotron 3 Super 120B with 1M token context on M1 Ultra
A user tested Nemotron 3 Super 120B with a Q4_K_M quantized model using llama.cpp on an M1 Ultra, achieving a 1 million token context window that consumed approximately 90GB of VRAM. Performance benchmarks show token generation speeds ranging from 255 t/s at 512 prompt processing down to 22.37 t/s at 100,000 token context.

Setting Up OpenClaw as an Always-On AI Assistant
OpenClaw, configured as an always-on AI assistant for a small dev team, is set up on a Railway server with Claude as the backend and integrates with Google Workspace, GitHub, and more.

Exploring LiveDocs: An AI-native Data Analysis Notebook
LiveDocs offers a reactive notebook environment allowing data teams to perform multi-step analyses and maintain analysis end-to-end with the help of an AI agent.