ETS import setup preview
The preview shows an ETS project being imported, inspected and prepared before AI processing. The installer checks KNX context before exporting a Composer-ready package.
Start with the official setup path
If you are using Control4 tools directly, start from the official Control4 KNX documentation and dealer resources for the exact import setup requirements, product drivers and supported hardware. That is the source of truth for the native workflow.
CoduWorks does not replace that documentation. It adds a review-first path for the ETS project when the installer needs to inspect KNX source context, supported devices and mapping assumptions before Composer creates anything.
- Use official Control4 documentation for product-specific setup.
- Use the ETS project as the source for topology, rooms, addresses and DPT context.
- Use a review layer when the native import result is empty or incomplete.
Preflight before importing the ETS project
Before the import, check whether the .knxproj is processable, whether building and room structure exists, and whether group addresses carry enough naming and datapoint context to infer real devices.
A project can be valid in ETS and still be weak for an automatic Control4 build if functions are unnamed, feedback is missing, or the project uses only loose group address naming.
- Confirm the file is a usable .knxproj, not a partial export or protected archive.
- Check buildings, floors and rooms before relying on the wizard output.
- Check lights, blinds and gateway objects against supported build scope.
When the wizard shows no floors, rooms or devices
Forum cases around the KNX ETS Project Import Wizard often describe the same symptom: the file opens, but the next steps show no floors, rooms or useful devices.
That does not always mean the KNX project is useless. It can mean the native import expects a different ETS structure or Control4-specific modelling. In that case, inspect the ETS source directly and build a reviewed structure before exporting to Composer.
- No floors usually points to missing or incompatible building structure.
- No rooms can mean the ETS layout does not match what the wizard expects.
- No devices can happen when the ETS project has generic KNX devices, not Control4 devices.
Review-first alternative
The CoduWorks flow imports the .knxproj, shows KNX context, processes the project with AI, then lets the installer review the proposed Control4 structure before export.
The goal is not to bypass professional setup. The goal is to avoid discovering missing rooms, wrong device grouping or duplicate-prone names after Composer has already created a large project.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Where should I find the official Control4 KNX ETS Import Setup Guide?
Use official Control4 or dealer documentation for the native setup guide, product drivers and supported hardware. CoduWorks is a review workflow that prepares ETS context before Composer build.
Why does the Control4 ETS import wizard show no rooms?
The ETS file may not contain the building or room structure expected by the wizard, or the project may not be modelled around Control4 devices. The source project should be reviewed before rebuilding manually.
Can a generic KNX ETS project still be used for Control4?
Yes, but it needs interpretation. The AI Assistant can process the .knxproj, group supported lights, blinds, thermostats and gateways, and export a reviewed .codu package for the Composer driver.
Turn the ETS setup check into a reviewed build plan
Import the .knxproj, inspect floors, rooms, group addresses and supported devices, then export .codu only after the Control4 structure is clear.