Feedback cross-check preview
The preview shows linked KNX source and Control4 devices so command, feedback and DPT context can be reviewed before export.
Command address is not enough
A switch, dimmer or blind usually needs a command path and a status path. The command tells KNX what to do; the feedback confirms what actually happened.
If the build only knows the command address, Control4 can show stale state, scenes can branch from the wrong value and troubleshooting becomes slower.
Status sync for lights and blinds
Lights need reliable on/off and level feedback. Blinds need position, movement or stop context where available. The review step should keep these related addresses visible as one device candidate.
- Switch/dimmer command and feedback should be checked together.
- Blind position, open-close and stop objects should not be reviewed in isolation.
- Unsupported or unclear combinations should stay visible for installer review.
DPT and function context
Feedback can be wrong even when the group address looks right. The DPT and function matter: binary status, percentage value, relative dimming and position feedback should not be treated as interchangeable.
Gateway, router and filter table visibility
If relevant group addresses are not visible through the KNX/IP path used by Control4, the generated device can look broken. Routing and filter-table context should be reviewed before changing the Control4 build.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Why do feedback addresses matter in Control4 KNX projects?
They keep the Control4 state aligned with the KNX actuator state, which affects UI status, scenes and troubleshooting.
Can command and feedback use the same address?
It depends on the KNX device and object design. The safer workflow is to review object intent and DPT instead of assuming that one address is valid for both.
When should feedback problems be found?
Before .codu export when possible, so Composer creates the project from a reviewed mapping rather than a partial address list.
Review feedback before Composer
Use the AI Assistant to cross-check KNX source data and Control4 devices before exporting the build package.