Document the KNX tools for AI conversation agents - #47656
Open
martinhoefling wants to merge 3 commits into
Open
Conversation
Covers the new KNX LLM API: how to select it on a conversation agent or the Model Context Protocol Server, what the 22 tools can do and what each group needs, who can reach them once an administrator has attached the API, and the pagination and raw-KNX-data limits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
home-assistant
Bot
added
has-parent
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
21 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation to the KNX integration page for the new KNX LLM API (“KNX”) intended for use by AI conversation agents and via the Model Context Protocol Server, including what the tools do, how to enable them, and key limitations.
Changes:
- Added a new section describing how to enable and use the KNX tools for AI conversation agents and MCP clients.
- Documented the tool groups and prerequisites (telegram history, ETS project, DPT lookup, live bus access).
- Added KNX-tool-specific limitations to the Known limitations section.
Suppressed comments (1)
source/_integrations/knx.markdown:496
- "Select it on the integration" reads awkwardly in American English. "Select it in the integration" is clearer.
The KNX API is not used by default. Select it on the {% term integration %} that provides your conversation agent, such as [Anthropic](/integrations/anthropic/), [Google Generative AI](/integrations/google_generative_ai_conversation/), [OpenAI](/integrations/openai_conversation/), or [Ollama](/integrations/ollama/):
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
`/api/mcp/knx` requires an administrator token, so the "everyone who can talk to that agent" model only applies to conversation agents and to the base `/api/mcp` endpoint. Match the Model Context Protocol Server documentation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Documents the KNX LLM API added in home-assistant/core#178029.
The KNX integration registers an LLM API named KNX that gives a conversation agent, and through the Model Context Protocol Server also an external MCP client, tools to inspect a KNX installation and interact with the bus. The new section covers how to select the API, what the 22 tools do and what each group requires (telegram history, ETS project, data point types, live bus access), who can reach them once an administrator has attached the API, and the pagination and raw-KNX-data limits.
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.