CoduWorks
Contact
/
KNX → Control4OverviewFor integratorsServicesBlogAboutContact

Your complete guide from KNX to Control4.

Follow clear steps, avoid common mistakes, and learn with short videos for each phase.

Back to product pageNeed help? Contact

Guides

Easy-to-follow documentation, from start to finish.

Follow the sidebar from top to bottom to complete the full workflow clearly.

Scope / Limitations

Scope and Limitations

Platform scope, current limitations, supported device categories, and driver behavior in existing Control4 projects.

Scope and limitations

The KNX to Control4 AI Assistant is designed to take a finished ETS project and convert it into a deployable Control4 structure (locations + compatible virtual devices) that can be built automatically by our Control4 driver.

Ideal workflow

  1. Start with a completed ETS project. Your ETS project should be final (devices, group addresses, naming, and programming already done).
  2. Upload the ETS project to the platform. Import your .knxproj file and let the platform generate the Control4 structure and supported devices.
  3. Review and refine in the platform. Tweak the generated Control4 structure as needed: rename rooms, adjust mappings, and use bulk-edit tools to finalize everything. When ready, export the .codu file.
  4. Add the driver in Control4 Composer. You dont need to manually build the entire room structure first. Create a single dummy room, add the Control4 processor + our driver, and then let the driver build the rest.
  5. Review the build report and run the builder. When you upload the .codu file, the driver shows a report before building, so you can confirm exactly what will be created.

Current platform limitations

  • You cant re-upload an ETS file to the same project (for now).
  • Password-protected ETS files are not supported.
  • If your project is password-protected and you are not using KNX Secure, remove the password and upload the file again.

Using the driver with existing Control4 projects

The driver is designed to be safe in existing projects.

  • The driver never deletes anything.
  • If Building / Floor / Room names match exactly between the platform and your Control4 project, the driver will not create duplicates.
  • The driver also checks devices inside each room by device type, linked group addresses, and key datapoints. If they match, the driver wont duplicate devices.

Tip: Read the build report first

Before building, the driver shows a summary of how many buildings, floors, rooms, and devices will be created.

If it shows 0 Buildings / 0 Floors / 0 Rooms, your locations already match.

Always back up first

Even though the driver is safe, always create a Control4 project backup before running the builder.

Supported devices (virtual devices) and group addresses

  • Lighting - Switch: On/Off DPT-1, Feedback On/Off DPT-1.
  • Lighting - Dimmer: Level DPT-5, Feedback Level DPT-5.
  • Not supported for dimmer: DPT3 relative dimming.
  • Blinds - Percentage blinds: Level DPT-5, Feedback Level DPT-5, Stop DPT-1, and optional Open/Close DPT-1.
  • Blinds - Open/Close blinds: Open/Close DPT-1 and Stop DPT-1.
  • KNX IP Gateways - Tunneling: IP address optional (recommended).
  • KNX IP Gateways - Router: default multicast address (editable).

Not currently supported (yet)

These device categories are supported at the moment:

They are planned for future updates. No ETA.

  • HVAC
  • RGB / color lighting
  • Sensors
  • Relays
  • Keypads Buttons

AI light load omissions (by design)

The AI can intentionally omit some categories to keep the generated project clean and focused, such as:

  • Color lighting (RGB, separated channels or combined).
  • Fans / extractor fans / exhaust fans*
  • Pumps, gate openers, and similar loads*
  • * You can still add these manually (for example as a switch), but we dont auto-generate them by default.

Need help?

If you have any questions or edge cases, contact us and well help you choose the best workflow.