DPT review/Updated May 2026

DPT3 relative dimming needs review before Control4 build

Name: DPT and dimmer cross-check preview
Uploaded: 2026-05-20
Description: The preview shows KNX source context linked to Control4 devices so DPT assumptions can be reviewed before export.

DPT3 relative dimming is a common source of confusion because it represents step-style dimming commands, not a simple absolute level. In this workflow, DPT3 assumptions should be made visible and reviewed instead of being converted blindly into Control4 dimmers.

Treat DPT3 as a review signal, not an automatic supported dimmer output.
Use DPT-5 level and feedback level when creating supported dimmer devices.
Keep relative dimming, switch and feedback addresses visible during cross-check.

Open AI Assistant View product

DPT and dimmer cross-check preview

The preview shows KNX source context linked to Control4 devices so DPT assumptions can be reviewed before export.

What DPT3 means in practice

DPT3 is used for relative control such as dim up, dim down or stop-like step behavior. It is different from an absolute brightness value where a device receives a clear level percentage.

That distinction matters when generating Control4 devices, because a driver build needs predictable command and feedback points.

Supported dimmer output uses level context

The current automatic output focuses on dimmer mappings with level and feedback level context, typically DPT-5 style values. DPT3 relative dimming is not treated as an automatic supported output for generated dimmer devices.

If a project includes DPT3 objects, they should appear in review so the installer can decide whether the project has the required level addresses for a clean Control4 dimmer.

What to cross-check

For lights, check switch command, level command, level feedback and any relative dimming object together. A single DPT label is not enough to prove that a Control4 dimmer can be built safely.

On/off command and feedback.
Absolute level command and feedback.
Relative dimming objects that may be present but not used for automatic generation.

Avoid hidden assumptions in Composer

When DPT3 is hidden until Composer, the installer may only discover the mismatch after devices are already created. The better workflow exposes DPT assumptions before export and keeps unsupported combinations out of the automatic build.

Official references checked

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

FAQ

Is DPT3 relative dimming automatically supported?

No. The current automatic generation focuses on supported level-based dimmer mappings. DPT3 should be reviewed before export.

Why is DPT3 different from DPT-5?

DPT3 carries relative dimming commands, while DPT-5 style level values can represent an absolute brightness percentage.

What should I do if my ETS project uses DPT3?

Review the related switch, level and feedback addresses. If the needed absolute level context is missing, do not force automatic Control4 dimmer generation.