Subject: [Open source] Design-time ETS review + Home Assistant export via an MCP/AI assistant — beta, testers wanted
Hi all,
I've built an open-source design-time assistant for KNX and I'd value this community's critical eye. It's an MCP server that an AI client (Claude) drives, but the important part is what it does to a project file, not the AI:
- Reads a
.knxprojread-only — no bus access at all (no KNX/IP or networking libraries in the dependency tree; it physically cannot reach an installation). - Checks naming, DPT consistency, and missing status objects, pairing command↔status primarily from ETS Function roles.
- Generates a Home Assistant KNX package and ETS-importable GA exports (XML / CSV), plus a Markdown report to review before import.
I've hardened it against public ETS 4.2 / 5.0 / 5.5 / 6 test projects (it found and I fixed several real bugs, each now covered by a regression test), and there's a full 239-GA demo project + dashboard so you can see input → output.
It is beta and I'd genuinely like it tested against real projects. It's read-only and never connects to a bus, so trying it is safe.
Repo: GitHub - NickoScope/nickol-knx-mcp: Design-time KNX/ETS6 assistant as an MCP server: parse .knxproj, validate naming/DPT/status, generate Home Assistant YAML + ETS XML/CSV. No live bus access. · GitHub · Demo/screenshots: nickol-knx-mcp — design-time KNX/ETS6 assistant (MCP server) · MIT.
Honest, technical feedback (including "this is wrong because…") is exactly what I'm after. Thanks!
Not affiliated with the KNX Association; KNX/ETS are trademarks of the KNX Association cc.