Map KNX DPTs and ComObjects into Control4 devices

DPTs tell the workflow how a KNX value should be interpreted. Without that context, a group address is just a number and the generated Control4 device may miss command, feedback or position behavior.

  • Use DPT and ComObject context to group KNX addresses into real Control4 devices.
  • Check command and feedback pairs before exporting to Composer.
  • Keep unsupported combinations visible instead of creating unreliable devices.
Open AI AssistantView product

KNX DPT and Control4 cross-check preview

The preview shows linked KNX data and Control4 devices so the installer can check channels, DPT assumptions and mappings before export.

Why DPT context matters

A group address alone does not explain whether it is an on/off command, a level feedback value, a stop command or a position percentage. DPT context helps determine how Control4 should use the value.

The AI Assistant uses this context together with names and ComObjects to build a device candidate that can be reviewed.

Lights and dimmers

Switch lighting is normally driven by on/off values, while dimmers need level values and feedback. The workflow should separate simple switches from dimmers and avoid assuming that every lighting address behaves the same.

DPT3 relative dimming is not part of the current automatic dimmer support, so it should be surfaced for review rather than silently treated as a complete dimmer.

Blinds and shades

Blinds often need movement commands, stop values, percentage positions and feedback. A Control4 blind can look correct but behave poorly if stop or feedback addresses are missing or inverted.

Review DPT assumptions before export

The goal is not to hide uncertainty. If DPTs, ComObjects or address names are incomplete, the review step should make that visible before the .codu export reaches Composer.

Official references checked

Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.

Related tools and documentation

FAQ

Is DPT enough to create a Control4 device?

No. DPT is important, but the workflow also needs names, ComObjects, group address families and room context.

Which DPTs matter most for supported devices?

The current workflow focuses on DPT-1 style on/off and stop values, DPT-5 style level or percentage values, and matching feedback where available.

What happens with unsupported DPT combinations?

They should be reviewed instead of being converted blindly into Control4 devices.

Next step

Check KNX DPT mappings before Composer

Use the AI Assistant to group ComObjects, DPTs and group addresses into Control4 devices you can review before export.