ETS to Control4 conversion preview
The conversion view turns KNX project context into Control4 rooms and devices. The integrator reviews names, mappings and supported device types before creating the export file.
Conversion is not copy and paste
Copying addresses can make a project technically connected, but it does not create a clean Control4 user experience.
The conversion needs to understand which addresses belong together, where the device should live and what the user expects to control.
From buildings and rooms to Control4 navigation
A useful conversion keeps the building logic visible. Floors, rooms and device names should be checked before export because they affect how the project feels inside Control4.
- Building and floor structure for navigation.
- Room assignment for each generated device.
- Device naming that can be reviewed and translated before handover.
Supported device types need explicit rules
Lights, dimmers, blinds and gateways each need different mapping rules. Treating every address family the same creates broken controls or missing feedback.
The review layer should expose unsupported or ambiguous cases instead of hiding them behind an export button.
Before and after comparison
Before conversion, the project is ETS-centric: addresses, ComObjects and topology. After conversion, it should be Control4-centric: buildings, rooms, devices, commands and feedback.
Related tools and documentation
FAQ
What should an ETS to Control4 conversion produce?
It should produce a reviewed Control4 structure, not just a copied list of KNX addresses.
Why is KNX context important?
Context helps group related addresses into real devices and avoid creating incomplete or duplicated Control4 objects.
Can conversion be fully automatic?
Automation can remove a lot of repetitive work, but professional projects still need review before final Composer build.
Convert the project, then review it
Use the AI Assistant to transform ETS context into Control4 structure and keep the final Composer build intentional.