제어 KNX ETS 5/6 ** AI 코딩 조수에서. knx-ets-mcp 연결 MCP-capable 조수 - Claude Code, Codex, 그리고 같은 - 당신의 오픈 ETS에 프로젝트 그래서 그들은 당신이 도움이 될 수 있습니다 ** 새로운 프로젝트를 생성, 기존 하나 유지, 또는 tidy 하나 up: 그것을 검사, 구축 및 편집 (장치, 그룹 주소, 링크, 매개 변수), 검색 제품 카탈로그 및 프로그램 장치 업데이트 - ETS의 자체 엔진을 통해 모두.

** 공식 KNX 제품이 없습니다. ** "KNX"와 "ETS"는 KNX의 상표입니다. 협회. 이것은 독립적 인 실험적 커뮤니티 도구입니다. 당신의 자신의 위험에 사용; 생산 임명에 그것을 점등하지 마십시오 당신은 방해할 것을 감당할 수 없습니다.

무엇 그것

함께 일하는 2개의 부속이 있습니다:

1. Windows에서 ETS 내부를 실행하는 ETS 5/6 AddIn는 안전하고 고정 된 세트를 노출 프로젝트에 대한 작업 - 로컬 ** 이름 파이프 ** (same machine) 이상 도달 가능 옵션 TCP 엔드포인트 (그래서 MCP 서버는 다른 기계에서 실행할 수 있습니다).
2. ** MCP 서버 ** AI 조수가 연결; 그것은 조수를 전달합니다 AddIn에 요청은 파이프 (사임 기계) 또는 TCP (당신의 LAN을 건너)를 명명했습니다.

당신의 조수는 다음 도구가 있습니다:

knx-ets-mcp

Control KNX ETS 5/6 from an AI coding assistant. knx-ets-mcp connects MCP-capable assistants — Claude Code, Codex, and the like — to your open ETS project so they can help you create a new project, maintain an existing one, or tidy one up: inspect it, build and edit it (devices, group addresses, links, parameters), browse and update the product catalog, and program devices — all through ETS’s own engine.

Not an official KNX product. “KNX” and “ETS” are trademarks of the KNX Association. This is an independent, experimental community tool. Use at your own risk; do not point it at a production installation you cannot afford to disturb.

What it does

It has two parts that work together:

1. An ETS 5/6 AddIn that runs inside ETS on Windows and exposes a safe, fixed set of operations on your project — reachable over a local named pipe (same machine) or an optional TCP endpoint (so the MCP server can run on a different machine).
2. An MCP server that your AI assistant connects to; it forwards the assistant’s requests to the AddIn over that named pipe (same machine) or TCP (across your LAN).

Your assistant then has tools to:

• Inspect — devices (with order numbers), group addresses, communication objects (with their function/channel block), topology, building view, catalog, parameters (with labels, units, allowed options, value ranges, and their UI block so the right parameter can be targeted reliably on complex devices), channels/modules, trades, tags, to-dos, project history, and KNX Secure certificates.
• Build — create group addresses, add devices from the catalog, link communication objects to group addresses, set parameters (and reset to defaults).
• Edit — delete/rename group addresses, set descriptions and datapoint types, create and delete group ranges, delete/rename devices, change a device’s individual address, create/delete areas/lines/segments, set communication-object flags (C/R/W/T/U + priority), move GAs/group ranges/lines/building parts between parents.
• Building view — create buildings/floors/rooms/cabinets, assign devices to them, and create building functions linked to group addresses.
• Trades / organization — create/delete trades, assign devices; manage tags, to-do items, and project history entries.
• Bus interface — link/unlink group addresses on couplers (filter table).
• Additional addresses — add/remove additional individual addresses on devices and additional/sending group addresses on lines.
• Catalog — search the online catalog, browse a manufacturer’s products, read product details, pull in online products, or import a manufacturer .knxprod file.
• KNX Secure — list, add, and delete device certificates.
• Project — export (.knxproj), undo/redo, navigate to any object in the ETS UI.
• Bus / online (KNXnet/IP): ping, scan a line for devices, read a device’s