What does the AI Assistant do?

The AI Assistant imports an ETS project, generates a reviewable Control4 structure, and exports a .codu file. The Composer driver uses that .codu file to build the project inside Composer.

What can I edit before export?

You can review rooms, devices, subtypes, lines, group addresses, mapping errors, names, translations, reorganization, and bulk changes before export.

Does it replace Composer Pro?

No. The AI Assistant prepares and validates the project before export. Composer remains the environment where the Composer driver runs the build and the final integration is validated.

What devices are supported now?

Current core support includes switch/dimmer lights, open-close and percentage blinds, KNX IP gateways, and scoped thermostat devices. RGB, sensors, keypads, generic relays, and wider HVAC stay as review context or separate scope, not automatic core generation.

Convert KNX projects into Control4, ready for Composer.

Process your KNX project file with AI, export the project, and upload it to the Control4 driver to create the supported devices automatically.

Open AI Assistant Book a meeting

From ETS to Composer in one reviewable workflow.

AI Assistant screenshot showing the project Control4 structure

01Import ETSCreate the project, upload the .knxproj file, and review the KNX view before processing.02Process with AIThe AI Assistant generates rooms, Control4 structure, and supported devices with KNX context.03Edit your wayUse tools Composer does not give you: AI translation, search and replace, bulk edit, PDF, and rollback.04Export and buildGenerate the .codu, import it into the Composer driver, and review the build report before creating.

Import your ETS project

Upload the .knxproj and let the AI Assistant turn it into a reviewable Control4 structure with KNX context.

View detail

Search and replace made easy

Find devices, rooms, lines, or naming patterns and replace them in one controlled pass before export.

View detail

KNX to Control4 Data Cross-Check

Verify KNX channels and linked Control4 devices in one view for a fast, easy project review.

View detail

Translate the full project with AI

Choose a target language and translate project names, rooms, lines, and devices in one pass, with review and rollback before export.

View detail

Bulk edit without repetitive Composer work

Update names, subtypes, rooms, and lines across many devices at once, review the changes, and keep the .codu export clean.

View detail

Video documentation

Real videos from the KNX-Control4 workflow

Open the current documentation videos for ETS import, AI processing, Control4 review, mapping, and Composer build.

View all videos

Import ETS and review the KNX viewUpload the .knxproj file and inspect the KNX project view before AI processing.View video

AI processing workflowGenerate rooms and Control4 structure from the KNX project data.View video

Control4 map, tree and errorsEdit generated devices and review mapping issues in the Control4 workspace.View video

ComObjects and Group Address mappingSee how KNX ComObjects and Group Addresses correlate with Control4 devices.View video

Search, replace and KNX GA lookupSearch devices, replace values and look up KNX Group Addresses from the Control4 view.View video

Automatic build in ComposerImport the .codu file, review the action summary and run the automatic Composer build.View video

KNX-Control4 guides

Key guides to review

ETS import, mapping, troubleshooting, safe builds, and pricing without turning this section into a full index.

Control4 KNX driverHow the reviewed .codu package reaches the driver and creates lights, blinds, thermostats, and IP gateways in Composer.ETS Import Setup GuideCheck .knxproj, floors, rooms, DPTs, and empty wizard results before Composer.KNX DPT mapping for Control4DPT-1, DPT-5, ComObjects, feedbacks, and assumptions to review before export.Control4 KNX troubleshootingCheck gateway IP, routing, feedback, and mapping context before changing Composer.Duplicate-safe buildWhat the driver should check in Composer before it creates the new structure.Control4 KNX pricingLicense tiers by counted lights, blinds, thermostats, and KNX IP gateways.

Pricing

Each project is licensed by the number of lights, blinds, thermostats, and IP gateways prepared and built. Coming soon.

Lights, blinds, thermostats, and IP gatewaysEven if the project has hundreds of keypads, push buttons, or sensors, they do not move the license tier. For pricing, lights, blinds, thermostats, and IP gateways count as devices, keeping the cost more accessible.

License 01

0-75counted devices

Small projects

For compact installations with up to 75 lights, blinds, thermostats, and IP gateways inside the project.

Coming soon

License 02

75-300counted devices

Medium projects

For large homes or professional projects with more lights, blinds, thermostats, and IP gateways to generate.

Coming soon

License 03

+300counted devices

Large projects

For high-volume integrations with more than 300 lights, blinds, thermostats, and IP gateways.

Coming soon

Review your KNX-Control4 case with us.

If you want to check whether the workflow fits a real project, book a short session and we will review the context before you start.

Schedule on Calendly

Useful for questions about ETS, supported devices, .codu export, or the Composer build.

Upload ETS and review what the AI Assistant prepares for Composer.

Start in the platform or contact us if you want to review a project.

Open AI Assistant Contact us