KNX to Control4: facts, scope, and limits.

1. ImportUpload a processable ETS .knxproj.
2. InterpretThe platform reads topology, locations, devices, ComObjects, GAs, and DPTs.
3. ReviewConfirm rooms, names, types, mappings, gateways, and warnings.
4. ExportGenerate the reviewed .codu package.
5. BuildThe driver shows the plan and creates the supported structure in Composer.

Buildings, floors, rooms, and areas are project structure and never consume the allowance. Devices or combinations outside this matrix remain context or exceptions until validated; they are not promised as automatic creation.

ETS

Processable ETS5 and ETS6 .knxproj projects. Encrypted files require their password. CSV, ESF, or OPC can be references but are not equivalent inputs.

Control4

CoduWorks Composer driver. The current Composer/Control4 OS version and dealer environment must be validated before production use.

Output format

Reviewed .codu package for the driver; it is neither a native ETS export nor a third-party driver package.

Maximum upload

200 MB

• The platform processes account/security data, uploaded project files, mappings, and outputs to provide the service.
• AI features may send relevant project inputs to AI providers; a professional must review their responses.
• Access uses accounts, sessions, and project-scoped authorization. The public website does not expose project data.
• When a project is deleted, heavy KNX relational data is removed. KNX metadata and the Control4 structure are retained in a deleted state for audit/history.
• Unreferenced temporary extraction directories are pruned after 168 hours. Agent conversation and audit retention is configured to 90 days.
• For access, correction, erasure, or other privacy requests: info@coduworks.com.

No transmission or storage method eliminates all risk. This description reflects the implementation reviewed on 18 August 2026 and does not replace a contract or DPA.

One-time project license. Only lights, blinds, thermostats, and IP gateways count. Taxes are applied as legally required. Unlimited types are included under the current launch offer and may change in a future offer.

The driver updates through the product, so you do not need to find files or check technical release data. If an update requires action, the product will guide you through it.

Updates

Managed automatically through the product.

Support

info@coduworks.com · Tell us about your project and what you need help reviewing.

These resources show the workflow on a real project, the scope the product can generate, and the checks that remain the installer’s responsibility. Official sources place CoduWorks within the ETS and Control4 ecosystem without presenting third-party products as CoduWorks features.

Direct answers about Control4 KNX integration, ETS6 compatibility, project editing, and supported devices.

How does a Control4 KNX integration work with CoduWorks?

The platform imports the ETS project, keeps topology and group addresses available for review, prepares the Control4 structure, and exports a .codu package. The driver shows the plan and creates only the supported, installer-reviewed structure and devices in Composer.

Does CoduWorks support ETS6 projects?

Yes. It supports processable ETS5 and ETS6 .knxproj files. Encrypted projects need their password, and topology, DPTs, mappings, and feedback must still be validated before commissioning.

Does the product include a Control4 driver editor?

Yes. It combines a cloud editor with KNX and Control4 context, .codu export, and a CoduWorks Composer driver. It is not a native ETS export and does not replace Composer.

Which KNX devices can the Control4 driver create?

The public matrix includes lights, blinds, thermostats, and KNX/IP gateways, plus contacts, relays, motion sensors, and keypad buttons under the visible launch-offer conditions. Each variant requires command, feedback, DPT, and semantic review.