Grok Gadgets: Home Assistant

On this page

This guide uses ASD-STE100-inspired writing. It does not claim formal compliance. See the project writing guide.

Use the diagnostic probe to inspect MCP discovery. Use the setup guide to prepare an existing Home Assistant installation for Grok. This project uses Home Assistant's own MCP server.

Experimental alpha. Tests cover discovery fixtures and local client transports. We have not verified an actual Home Assistant installation, native Grok calls, mobile clients, or physical home devices. The probe lists capabilities. It does not call tools, read resources, or control your home.

Hand-authored MCP fixture to Read-only diagnostic probe; Read-only diagnostic probe to Redacted capability summary; Existing Grok Bot to Home Assistant upstream MCP server (pending); Home Assistant upstream MCP server to Selected exposed home entities (pending). Intended paths; verification gates apply.

The solid lines show the software-only first step. The dotted lines show the proposed connection to a real home. That connection needs an authorized installation, compatible authentication, and a reachable endpoint. Home Assistant can connect directly to the Bot. It does not need the Grok Gadgets gateway or another home-control server.

Run the fixture first

Clone adidshaft/grok-gadgets-home-assistant and enter its root directory.

You need Python 3.11, uv, and internet access for the first dependency installation. You do not need another repository, Home Assistant, a Grok account, a token, or a device. Tests used macOS arm64. Windows, Intel Mac, and real-home installation remain unverified.

uv sync --frozen --python 3.11
uv run ha-probe --fixture fixtures/assist.json
uv run python -m unittest discover -s tests -v

Expected fixture summary:

{
  "evidence": "fixture tested",
  "tool_count": 2,
  "resource_count": 1,
  "prompt_count": 1,
  "tool_calls_performed": 0,
  "resource_reads_performed": 0,
  "grok_verified": false,
  "hardware_verified": false
}

The command also reports the fixture's MCP protocol version and context-capability flags. The fixture contains manually written discovery data. It does not contain results from a Home Assistant release. The recorded test run passed 13 tests. Tests cover discovery validation, pagination limits, authentication failures, URL checks, and private-data removal. They use mocks and temporary loopback fixture transports.

Next step	Guide
Prepare a separately authorized real endpoint	Setup recipe
Understand upstream reuse and remaining Grok requirements	Feasibility record
Review the tested environments and limits	Verification
Improve fixtures, diagnostics or documentation	Contributing
Diagnose installation or discovery errors	Support

Where this project fits

The gateway serves the separate gadget simulator, USB devices and SDK applications. The Linux SDK and ESP32 SDK help build new gadgets. This repository reuses Home Assistant's own MCP integration and entity exposure. This repository provides discovery diagnostics and a setup guide. It does not provide an adapter or guarantee general compatibility.

A cloud Grok Bot cannot launch a path on your computer. Check authentication, transport, network access, and call results on the actual client. The local probe does not prove OAuth compatibility, equal desktop/mobile behavior, automatic event delivery, or physical effects. The historical feasibility review records sources, dates, and pending experiments. It does not verify the current platform.

Use the issue chooser. Keep tokens and household names private; vulnerabilities use Security. General discussion is at r/GrokGadgets under the hub's Code of Conduct.

Original code is Apache-2.0, with attribution in NOTICE. The package uses the official MCP SDK pinned by uv.lock; package and dependency license metadata are described in verification. This independent project is unaffiliated with xAI and Home Assistant. Package releases remain pending; use the source installation above.

History note

Pre-publication commit dates were reconstructed across 29 September–5 October 2026 at the owner’s request. Verification records retain their actual execution dates. See the history and privacy record.