ETS import/Updated May 2026

A review-first alternative to the KNX ETS Project Import Wizard

Name: ETS import wizard workflow preview
Uploaded: 2026-05-20
Description: The preview shows the ETS import stage, KNX project view and preparation of a Control4 structure before the Composer driver receives the package.

Searches for the KNX ETS Project Import Wizard usually come from the same pain: the ETS project exists, but recreating its rooms, devices and group addresses in Composer is slow, and some imports show no floors, rooms or usable devices.

Upload the .knxproj file and inspect the KNX project view first.
Let AI generate a Control4 structure that can be edited before export.
Send Composer a .codu package only after the import has been reviewed.

Open AI Assistant View product

ETS import wizard workflow preview

The preview shows the ETS import stage, KNX project view and preparation of a Control4 structure before the Composer driver receives the package.

What installers expect from an ETS import wizard

The intent is not only to upload a file. Installers want the ETS structure to become usable Control4 rooms and devices without manually entering every group address.

A direct wizard can be fast, but it can also hide naming, DPT and duplicate issues until after devices exist in Composer.

When the wizard shows no floors, rooms or devices

A valid ETS project can still produce an empty-looking wizard result when the import path expects Control4-specific ETS records or a project structure that the real KNX installation does not contain.

That does not mean the .knxproj is useless for Control4. It means the project needs parsing from broader KNX context: names, group addresses, ComObjects, DPTs, topology and gateway assumptions.

Use the no-rooms/no-devices flow when the wizard opens the file but finds nothing useful.
Keep standard KNX devices visible instead of requiring Control4-branded records inside ETS.
Review generated rooms and devices before Composer creates anything.

Why review before Composer

A review-first workflow imports ETS into the platform, shows the KNX source, processes it with AI and produces a Control4 view that can still be corrected.

This is useful when the project uses inconsistent names, multiple address families or repeated functions across many rooms.

The .codu handoff

After review, the .codu export becomes the handoff to Composer. The driver reads the package, shows the build plan and creates the final structure.

That keeps Composer from being the first place where import mistakes are discovered.

What to check before export

Before exporting, check room hierarchy, supported devices, feedback addresses, DPT assumptions, gateway context and duplicate risks.

If those items are clear, the Composer build is more predictable.

Official references checked

Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.

FAQ

Can I import a .knxproj into this workflow?

Yes. The platform starts from the ETS .knxproj file, then lets you review the KNX view and generated Control4 structure before export.

Is this the same as a one-click wizard?

No. It intentionally adds a review layer before Composer so mapping and naming issues can be fixed earlier.

Why does the KNX ETS Project Import Wizard show no devices?

Often because the ETS project contains standard KNX devices and naming rather than the Control4-specific records or assumptions the wizard-style import expects.

What does Composer receive?

Composer receives a .codu package through the driver, not loose notes or a spreadsheet of unresolved addresses.