Lighting editor tools preview
The editor tools help review device names, lines, rooms and mapping values. The integrator can adjust lighting entries in bulk before exporting them to Control4.
Switch lights
A basic light needs an on/off command and often a feedback address. If feedback is missing, the Control4 interface can show state incorrectly after external changes.
Dimmers and brightness values
Dimmers need brightness command and feedback values in addition to switching. The DPT and object name help identify which address controls level and which one reports state.
Bulk cleanup before Composer
Names imported from ETS often contain installation shorthand. Bulk edit and search/replace make it easier to produce clean Control4 names without editing every device in Composer.
Validation checklist
Before export, confirm each light has the expected room, type, command address and feedback behavior.
- Switch has command and optional status.
- Dimmer has level command and level feedback.
- Room and display name are readable for the final Control4 project.
Related tools and documentation
FAQ
What KNX addresses does a Control4 dimmer need?
Usually switch command, brightness command and brightness feedback. Some projects also include separate on/off feedback.
Can light names be cleaned before Composer?
Yes. Bulk editing and search/replace are best done before the .codu export so Composer receives clean names.
Why does feedback matter?
Feedback keeps Control4 state aligned when a light changes from KNX keypads, sensors or other automation logic.
Review KNX lighting before it reaches Composer
Use the project editor to clean names, check feedback and export Control4 lights with the right mapping.