Control4 KNX driver build preview
The preview shows the reviewed KNX-derived Control4 structure being handed to the Composer driver, where the build plan is checked before devices are created.
What the driver does in this workflow
The Composer driver consumes the .codu package exported by the AI Assistant. That package carries the reviewed Control4 structure, mapping context and build plan created from the ETS source.
This separates two jobs: the platform handles import, AI parsing and review; the driver handles the final Composer build.
Not just a network connection
A KNX network or routing gateway connects Control4 to the KNX bus. The CoduWorks workflow focuses on the project-building problem around that connection: rooms, devices, names, mappings and duplicate checks.
That distinction matters because connecting to KNX is only one part of the work. Large projects still need a clean Control4 structure.
Supported automatic output
The current automatic build is focused on switch and dimmer lighting, open-close or percentage blinds, scoped thermostats and KNX IP gateway context. Other categories can still exist in the ETS project, but they should not be treated as supported automatic output unless reviewed.
For pricing, counted devices are lights, blinds, thermostats and IP gateways. Keypads, push buttons and sensors do not move the tier by themselves.
Build plan before creation
Before creation, the driver should show what will be created, what already matches and what needs attention. That visible plan is important in existing Composer projects where duplicate rooms or devices are expensive to clean later.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Is this a replacement for Control4 Composer?
No. Composer remains the final environment. The AI Assistant prepares the project and the Composer driver builds the reviewed structure.
What file does the driver use?
The driver imports a .codu file exported by the AI Assistant after the ETS project has been processed and reviewed.
What devices are generated automatically?
The current automatic workflow focuses on lights, dimmers, blinds, scoped thermostats and KNX IP gateways, with unsupported categories left for review or future add-ons.
Use a driver workflow that starts with review
Import ETS, review the generated Control4 structure, export .codu and let the Composer driver build the project.