What this video covers
This video shows the automatic project build inside Control4 Composer.
Video points
- .codu import in the Control4 driver.
- Automatic project build.
- Composer build flow.
Video chapters
- 0:00 — Open the Composer driver
- 0:31 — Upload the .codu package
- 1:02 — Refresh and inspect the build plan
- 1:36 — Existing-project and duplicate checks
- 2:02 — Run the automated build
- 3:00 — Re-run to create missing items only
Full English transcript
Automatic English captions from the published YouTube video, lightly normalized for product names.
[0:00] Once we have exported the code file from the platform this is very simple. You go to the project you you install our driver in any room. you can create like a dummy floor and room and obviously identify the controller and so so on the bas basic stuff in order to add the driver. when you enter to the driver we have a builder tab that where is where it ask you about the code file you can make a drag and drop or you can select it select the file from here for example let's go to download and select the demo it's going to study the the file and it will tell you okay this is a build project report he's going to to create one building four floor, 23 rooms, 76 devices. And this is very important. When this finish you
[1:00] should do a refresh project. It's not refresh navigator. Then refresh navigator is been made automatically by the driver. But you should go here and click refresh because depending of the size of the controller and so on you could see a weird behavior of the order of the devices in the drivers if you don't pull all information from the controller. So here are some important things. This driver is intelligent enough to understand the current behavior of the current status of the buildings, floors and rooms of the project. If in the platform you match the same names of buildings, floors or rooms, he's going only to focus in the things that are missing like for example drivers. even though if he can also detect drivers there. so let's build this.
[2:00] Let go to a start and you're going to see how this is going to start to creating first the locations and then the devices. Well, now it's finished. We are going to make a refresh. Perfect. Now if we go device by device we are we can see that he has already make the configuration and also every device is going to be tied in this case to the proper IP gateway because we have more than one depending of the line it's going to be connected in the one two or three if we go back to the driver we are going to see now this statistics he creates one building four floor 23 rooms 76 divid is in 114 seconds. suppose that we want to load
[3:00] the file again. This is to show you how this behaves. If we look at the driver again, he's going to study and he's going to say that in this scenario all rooms and devices are ready in the project because he identified what is there. If we delet for example one floor one room with devices or one floor with devices he is going to tell you that is going to create those missing locations and devices.
Technical walkthrough summary
The Composer driver video shows the final build step. The installer imports the .codu file inside Composer, reviews the action summary, and runs the automated project build.
This part is intentionally create-focused. The driver should show what it is about to create and give the installer a pause before anything is written into the Composer project.
The build flow is designed for reviewed projects. The platform prepares the structure; the driver executes it in Composer while avoiding unnecessary manual device creation.
