KNX Secure preflight preview
The preview shows KNX source context and Control4 device candidates side by side so gateway, feedback and project-readiness assumptions can be reviewed before export.
Why KNX Secure changes the review
A normal KNX mapping review focuses on rooms, devices, group addresses, DPTs, command addresses and feedback. KNX Secure adds another layer: the infrastructure and ETS access model can decide whether the project can be read, validated and connected through the selected gateway path.
That does not mean the Control4 project should ignore Secure context. It means the secure infrastructure should be confirmed before the .codu build package is treated as ready for Composer.
The .knxproj must be processable
The AI Assistant starts from the ETS project file. If the export is protected, incomplete, not the commissioned version or missing usable naming context, the generated Control4 structure will be harder to trust.
For Secure projects, the installer should prepare an export that can be processed without exposing unnecessary secrets to the review layer. Security configuration belongs in ETS and the KNX infrastructure, not in loose notes inside Composer.
- Use the latest commissioned ETS project export.
- Avoid password-protected exports that the platform cannot process.
- Keep secure credentials and infrastructure setup under installer control.
Check the gateway path before blaming mappings
When Secure, routing, tunneling, multicast or filter-table assumptions are wrong, Control4 can look disconnected even if the device mapping is reasonable. The gateway path should be reviewed before devices are recreated.
The review should expose what Control4 needs to build: supported lights, blinds, KNX/IP gateway context, command groups, feedback groups and the assumptions that must be true on the KNX side.
Composer should receive a reviewed package
The .codu file is not a substitute for ETS security configuration. It is the reviewed Control4 build package. A Secure-aware preflight keeps the installer from handing Composer a build plan before source access, gateway routing and feedback visibility are understood.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Does the AI Assistant configure KNX Secure?
No. ETS and the KNX infrastructure remain the place to configure security. The AI Assistant prepares and reviews the Control4 structure from processable project data.
Can I upload a password-protected ETS project?
Password-protected ETS files are not supported in the current workflow. Use a project export that the platform can process safely.
Why mention KNX Secure on a Control4 build workflow?
Because security, gateway routing and project access can affect whether Control4 can communicate reliably after the build. They should be checked before Composer creates devices.
Review Secure context before the Control4 build
Prepare a processable ETS export, review gateway and feedback context, then export a .codu package only when the Control4 structure is clear.