ETS source file/Updated May 2026

Use the .knxproj file as the source for Control4 review

Name: .knxproj import preview
Uploaded: 2026-05-20
Description: The preview shows an ETS project being imported so the KNX source can be reviewed before AI processing and Control4 export.

A .knxproj file is the project archive produced by ETS. For a KNX to Control4 workflow, it is valuable because it can carry topology, devices, communication objects, group addresses, DPTs and names in one project source.

Start from the project source instead of a loose list of addresses.
Keep topology, rooms, devices and datapoints together during review.
Export .codu only after the KNX context has been processed and checked.

Open AI Assistant View product

.knxproj import preview

The preview shows an ETS project being imported so the KNX source can be reviewed before AI processing and Control4 export.

What the .knxproj file contributes

The exact available data depends on how the ETS project was built, but the project archive can provide richer context than a flat spreadsheet. Names, devices, communication objects and datapoints help explain what each group address is meant to do.

That context is what allows the AI Assistant to propose rooms, devices and mappings for review before Composer receives the build package.

Why partial exports are not the same

Exports such as OPC or CSV can be useful for lists and checks, but they can lose part of the project context. A Control4 build workflow benefits from the project source whenever it is available.

The goal is not just to know that address 1/2/3 exists. The goal is to understand which room, device, ComObject, DPT and function it belongs to.

Before uploading the ETS project

The best results come from a finished ETS project with clear naming, room structure and group address organization. Password-protected files or incomplete naming can reduce what the review layer can infer.

Finish ETS programming and naming before import.
Check that supported lights, blinds, thermostats and gateways have clear group address context.
Keep a backup of the ETS project before sharing or processing it.

From .knxproj to .codu

The .knxproj file is the KNX source. The AI Assistant processes and reviews that source. The exported .codu is the closed build package handed to the Control4 Composer driver.

Official references checked

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

FAQ

Is .knxproj the same as a group address CSV?

No. A CSV can list addresses, but a .knxproj project archive can include broader topology, device and ComObject context depending on the project.

Can I use a password-protected ETS project?

Password-protected ETS files are not supported in the current workflow. Use a project export that the platform can process.

Does the .knxproj go directly into Composer?

No. The platform imports and reviews the .knxproj, then exports a .codu package for the Composer driver.