RIG → Home Assistant · Set up the product's MCP connection
This guide uses LuwuDynamics/xiaolu_mcp_ha, the integration linked by the RIG product tutorial. Its installed name is MCP Server for Xiaolu. Keep that name when searching for it, even when your dashboard language is English.
Connection route: speak to RIG → its agent requests an HA tool → the LuwuDynamics integration executes it in HA → the result returns to the conversation. The integration connects outward to the generated RIG WebSocket access point.
- Prepare your RIG and HA
- Copy the RIG access point
- Install and configure the integration
- Try your first voice command
- Something is not working
1. What you need before starting
Have your RIG online and bound to your international account, a working Home Assistant installation, and HACS installed in HA. First confirm that RIG can have an ordinary conversation and that HA can operate the entity you want to test manually.
HA manages your home devices. HACS installs community integrations. An entity is a named HA capability, such as a lamp's on/off state. Assist is HA's built-in control API selection used by this integration. An MCP access point is the connection supplied by your RIG account for external tools.
If HA or HACS is not installed, complete the official HA installation and HACS setup for your system first. This page covers connecting that installation to RIG, not replacing your robot's firmware.
2. Copy the access point from your RIG account
Open the international RIG dashboard using the account bound to your robot. Find the intended agent's MCP access-point card and copy its full address. Keep the page open to check the connection later.
The value is a WebSocket connection address, normally beginning with wss://. Preserve its full path and any token/query data. Those details are part of the generated connection, not text to replace with your Wi-Fi password. Do not share the address publicly.
Use the address actually provided by your international account. Do not copy a domestic endpoint from an illustration or manually convert its domain. If your international dashboard does not show the card, confirm availability with RIG support; the plugin's configurable address does not by itself verify your account's service access.
Checkpoint: you have an access-point address from the correct account/agent. The separate MCP device-control JSON used by desktop clients is not the value needed here.
3. Install the LuwuDynamics component through HACS
Use the repository's Add to HACS link, or find xiaolu / xiaolu_mcp_ha in HACS. Confirm the repository owner is LuwuDynamics, download the component and restart Home Assistant. These are the installation steps in the project's English instructions.
Wait until your HA dashboard is available again. Downloading a component in HACS and adding an integration instance are separate steps; complete both. If it is missing after restart, check HACS installation status before changing the RIG address.
4. Add the integration and select Assist
In HA, open Settings → Devices & services → Add integration, search for Mcp, and choose MCP Server for Xiaolu. Paste the copied access-point address into its connection field. Select Assist in the API selector, then submit.
| Setting | What it means for this RIG setup |
|---|---|
| Access-point / client endpoint | The full generated RIG WebSocket address. |
| Assist | HA's built-in control API; use this for the first home-device test. |
| Other API choices | Additional APIs already registered in your HA installation. Leave them for later. |
The plugin supports multiple API selections, but at least one is required. A saved configuration confirms that an entry was created; the connection still needs to be checked. You do not configure a generic HA /api/mcp HTTP endpoint or create an HA long-lived token for this plugin's setup form.
5. Choose which HA entities RIG can use
Open Settings → Voice assistants → Expose in HA and make the intended test entity available to Assist. Give it a distinct name, such as Study desk lamp. Check its real state and manual control first.
The integration's available tools depend on HA's exposed entities and APIs. An entity present on a dashboard is not automatically available to the agent. Begin with one ordinary lamp or another simple entity you can observe; keep unrelated controls out of the first experiment.
Return to the RIG access-point page after roughly a minute and use Refresh. Inspect its status and available tools. The official repository recommends checking this page after configuration. If the connection is offline, resolve that before trying a voice command.
6. Ask RIG to perform one clear task
Ensure your robot is using the agent whose access point you configured. Then make one request at a time:
Use Home Assistant to check whether the Study desk lamp is on.
Replace the example name with your actual exposed entity. Inspect the conversation's tool activity and compare the answer with HA. Then try:
Use Home Assistant to turn on the Study desk lamp.
Check the physical lamp and the state in HA. Ask to turn it off and verify again. If your first test is a different entity, choose a supported action for that entity instead of copying a lamp command literally.
Success: RIG requests the intended HA tool, HA changes the correct entity, and the result matches what you observe. A spoken acknowledgment alone is not enough. Keep this evidence while diagnosing later additions.
If a lighting or music request affects the robot instead: inspect the conversation history first. The official integration notes possible conflicts between HA lighting/music tools and built-in screen/music controls. Use an explicit HA request with the entity's distinct name, then check which tool actually ran. Wording can help diagnose selection; it is not a guaranteed fix for a service-side tool conflict.
Something isn't working? Check these in order
| What you see | Next step |
|---|---|
| Component missing in Add integration | Confirm the HACS download completed and HA restarted; search Mcp or Xiaolu. |
| Form cannot be submitted | Check the complete endpoint and select at least one API, starting with Assist. |
| Entry saved but access point offline | Confirm HA is running, outbound network access works, and the address belongs to the intended international agent. |
| Online but expected tools/entities absent | Check Assist selection, entity exposure and HA version; refresh access-point status. |
| RIG uses a different tool | Inspect the conversation history for built-in screen/music conflicts and verify the robot's assigned agent. |
| Correct HA tool called but action fails | Check the entity manually in HA, then enable this integration's debug logging and inspect the execution error. |
| Works, then stops later | Check HA availability, integration logs and whether the copied account/agent access point changed. |
Do not reinstall robot firmware to fix an HA integration form or endpoint mismatch. Record the failing stage: installation, connection, tool exposure, selection or execution.
7. Use AI to help without changing the product flow
I am connecting RIG to Home Assistant with LuwuDynamics/xiaolu_mcp_ha.
The integration is MCP Server for Xiaolu, using my international RIG agent's generated WebSocket access point.
HACS installation and HA restart: [result].
Selected API groups: [names]. Access-point status after refresh: [status].
Test entity name and manual HA result: [details].
Tool actually called in the RIG conversation: [name/result or none].
Error with endpoint tokens removed: [error].
Explain the smallest next check. Do not replace this with the generic HA HTTP MCP setup or invent a server address.
8. Finish the test or disconnect
Return the test device to the desired state. To stop this connection, disable or remove the specific Xiaolu integration entry you added in HA, then refresh the RIG access-point page and confirm its tools are no longer available. Preserve other integrations and entities you already use.
For another external-tool experiment, return to RIG MCP connections. The official browser/calculator bridge follows the same external-tool access-point direction.