Group address review preview
The mapping review compares detected KNX objects, device functions and Control4 targets. The integrator checks missing values, ambiguous signals and unsupported combinations before exporting the project.
Group addresses are signals, not final devices
In ETS, a group address represents communication around a value. In Control4, the user expects a device with actions and feedback. Mapping is the process of grouping the right KNX signals into one Control4 object.
That distinction matters because a single light can require switching, brightness and feedback addresses to feel complete in Control4.
Common mapping families
Most projects start with repeatable families: switch lights, dimmers, blinds, scenes and gateway or infrastructure objects.
The mapping layer should recognize those patterns, then let the integrator review exceptions where naming or DPTs are unusual.
- Switch: on/off command plus optional on/off feedback.
- Dimmer: switch, level command, level feedback and optional status.
- Blind: open/close, stop, position percentage and feedback.
Validation before Composer build
The review step should show missing feedback, ambiguous names and unsupported combinations before any .codu file is imported into Composer.
That makes the build report useful: it confirms what will be created instead of revealing mapping mistakes too late.
Tools that help with KNX address work
For standalone checks, a group address generator or mapping estimator can help validate address ranges and estimate the amount of Control4 work before the full project is processed.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Is one KNX group address equal to one Control4 device?
Usually no. A Control4 device often needs multiple KNX addresses grouped together, especially for dimmers and blinds.
What causes most KNX mapping errors?
Missing feedback addresses, inconsistent names, wrong DPT assumptions and duplicated room or device names are common causes.
Should mappings be reviewed before export?
Yes. Review before .codu export keeps Composer cleaner and avoids rebuilding devices after mistakes are found.
Review group address mappings before Composer
Use the AI Assistant to group KNX signals into Control4 devices, inspect exceptions and export a clean .codu file.