Bring Smart Home
to CrewAI

Composio provides access to 1000+ smart home tool integrations including Sensibo (climate control), Philips Hue (lighting), SmartThings (hub), and many more device ecosystems. Use list_composio_tools to discover all available tools, or search_composio_tools to find tools for specific apps or categories.

With arguments (execute_composio_tool): You provide a JSON object matching the tool's exact schema. This gives you precise control over every parameter. With text (execute_composio_tool_with_text): You provide natural language instructions like "turn on the AC to 72 degrees" and Composio's AI parses and maps it to the correct parameters. Use arguments for precision, text for convenience.

Visit https://app.composio.dev/ and sign up for a Composio account. Navigate to your API settings or developer dashboard to generate an API key (starts with ak_). The key gives you access to all available smart home tool integrations.

No! Composio handles authentication to individual smart home services internally. You only need your Composio API key. However, you may need to connect your accounts to specific services through Composio's connection management first. Use the connected_account_id parameter when executing tools if you have multiple accounts connected.

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.