KNX object flag review preview
The preview shows KNX source objects and Control4 candidates side by side so flags, feedback and route assumptions can be reviewed before export.
A group address is not enough
The same group address can be linked to different communication objects, and those objects can have different flags. Control4 may need to write a command, listen for a transmitted status, or send a read request and expect a valid response.
If the wrong object answers, no object answers, or the feedback is only available as a write target, status can look broken even when the address exists in ETS.
Which flags matter during review
The exact behavior depends on the KNX device and application program, but the review should identify whether the object is intended to receive writes, answer reads, transmit changes or update from bus responses.
For Control4, this is especially important for feedback addresses, binary inputs, keypads, scene objects, energy values and HVAC points that may be used for state or triggers.
- Read behavior for status objects that should answer GroupValueRead.
- Transmit behavior for objects that should report changes without polling.
- Write behavior for command objects that Control4 should control.
- Update behavior when an object tracks values from another bus response.
Symptoms that point to flag assumptions
Missing state, one-way devices, stale feedback after restart and unreliable trigger behavior can all point to object flags or sending address behavior rather than a broken Control4 device.
That does not mean CoduWorks changes the ETS file. It means the generated Control4 structure should keep those assumptions visible so the installer knows what to verify in ETS before export.
What the .codu handoff should preserve
The .codu package should carry the reviewed device structure and enough KNX-aware context to show which group address is command, which is feedback and which ETS assumptions must hold on site.
Composer should not be the first place where missing Read or Transmit behavior is discovered.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Does CoduWorks change KNX object flags?
No. Object flags and device parameters are edited in ETS by the installer. CoduWorks makes the relevant context visible before the Control4 build.
Why does Control4 show no status if the group address exists?
The feedback object may not transmit, may not answer reads, may use a different sending address or may not be visible through the KNX/IP route.
Are flags only relevant for read status delay?
No. They also affect triggers, binary inputs, sensors, energy values, HVAC points and any Control4 device that depends on reliable KNX feedback.
Review object flags before Composer
Import ETS, inspect command and feedback context, and export .codu only when object behavior is understood.