What this video covers
This video shows exporting an AI processed project to Control4 Composer.
Video points
- AI processed project export.
- .codu file for Composer.
- Composer handoff.
Video chapters
- 0:00 — Final project validation
- 0:16 — Export the .codu package
- 0:30 — Review the export summary
- 1:04 — Confirm KNX/IP gateway allocation
Full English transcript
Automatic English captions from the published YouTube video, lightly normalized for product names.
[0:00] Once you have validated all the rooms, names, devices and everything is there at it should to export it and create a Control4 project in with our driver is very simple. You go to export to for C4 and here in this case is the first project. So allows you to use a trial license. We are going to assign to this project. And here before the export you have a summary summary which going to point you out how many buildings floors rooms devices type of tun IP routters we have zero routter and three tunneling this mean that it's going to use the tunnel driver and not the routter driver. how many lines and this unknown is an error is unlocated that the are devices not located in this case we have assign
[1:00] everyone and then here you have like a brief summary of the type of IP gateway I'm using one per line in this project so once it is validate it's very simple you go to export and going to generate a code file this is the one we are going to use in the project. Driver
Technical walkthrough summary
The export video covers the handoff from the AI Assistant to Composer. After review, the platform generates the .codu file that the Control4 driver consumes.
The export should happen only after rooms, supported devices, feedback context, gateway context and obvious errors have been checked.
The .codu file is the closed build package. It carries the reviewed structure and build context so the Composer driver can show a plan and create the project from a controlled source.
