Waymark / Routes / iot Process a natural-language command with Home Assistant's Conversation API
domain: iot · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps POST a JSON body like {"text": "turn on the lights in the living room", "language": "en"} to /api/conversation/process with your auth token Or send {"type": "conversation/process", "text": "...", "language": "en"} over the authenticated WebSocket API Optionally set agent_id to target a non-default conversation agent (defaults to the home_assistant agent) Read response.response_type in the reply (action_done, query_answer, or error) to see what happened Pass the returned conversation_id back on the next request to continue a multi-turn conversation Check continue_conversation in the response to know if HA expects a follow-up utterance Known gotchas Error replies carry data.code (no_intent_match, no_valid_targets, failed_to_handle, unknown) plus a human-readable speech.plain.speech message action_done responses list targets ordered general-to-specific (area, domain, device_class, device, entity, custom) plus separate success/failed lists — don't assume one target Speech can be plain text or SSML; check which of speech.plain / speech.ssml is populated
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp