Gateway and generated devices preview
The project view shows generated Control4 rooms, devices and infrastructure context. Gateway-related entries are reviewed before the .codu file is exported for Composer.
The gateway role
The gateway gives the Control4 side access to the KNX bus. In large projects, gateway context matters because devices can belong to different lines, areas or IP interfaces.
Gateway assignment in the reviewed project
A reviewed Control4 structure should make gateway assignment explicit instead of leaving it hidden in manual driver configuration.
That is especially important when multiple IP gateways or secure bridges exist in the same ETS project.
Validation before build
Validation should catch missing gateway references, ambiguous infrastructure names and device groups that cannot be built safely.
Composer handoff
The .codu export gives the Composer driver the reviewed structure. Gateway-related issues should be visible in the report before the final project is created.
Related tools and documentation
FAQ
Does every KNX to Control4 project need a gateway?
Control4 needs a way to communicate with KNX. In practice that normally means a KNX IP interface, gateway or secure bridge configured for the project.
Why track gateway assignment during review?
Because missing or ambiguous gateway references can make a generated Control4 structure difficult to validate after build.
Should gateway objects become user-facing devices?
Usually no. Gateway and infrastructure objects should be handled separately from lights, blinds and other user-facing devices.
Validate KNX gateway context before Composer
Use the AI Assistant to review infrastructure, devices and export readiness before importing the project into Composer.