Control4 Map and Tree View

Watch how to use the Control4 map and tree views for device editing and error management.

Watch video on YouTube

What this video covers

This video shows the Control4 map and tree views, device editing, and error management.

Video points

  • Control4 map view.
  • Control4 tree view.
  • Device editing and error management.

Video chapters

  • 0:00 — Review the generated Control4 map
  • 1:23 — Filter floors and device types
  • 1:50 — Read mapping and feedback errors
  • 2:30 — Place unlocated devices
  • 4:30 — Add a device manually
  • 5:00 — Search and assign Group Addresses
  • 6:00 — Undo and redo changes

Full English transcript

Automatic English captions from the published YouTube video, lightly normalized for product names.

[0:00] after [snorts] the I respond. Please be patient that this could take a couple of minutes. now we have enabled the Control4 menu. and basically we are in the map view the same map view in the room structure. This is very similar to the Control4 structure with floors rooms and the devices. And I'm going to close this at this point. I'm going to explain later. But basically, we can see that we have the building, the different rooms. Basement for example, sorry, ground floor, basement. Inside the basement, we have corridor, guest, bedroom, guest bathroom, garage, machinery room. Inside the corridor, we have basically one dimmer. this dimmer and the group address of this dimmer and also the line. so basically here

[1:00] you can see a lot of important information. also if you notice the lines are different because these are different lines. So we can for example here filter per line. So it's going to only show devices in line 2.1. then we have line 2.2 2 and line 2.3. then we can also filter by floor. So we can see only devices in basement for example. but also we can filter by device types. So suppose we have want to see lights that are type switch. So here very easily you can spot all the important devices in the projects. there is another very interesting feature that we have added. This is the warning that we can see here. when you click here it filters all the device that has some kind of warning. In this

[2:00] case for example we have a light that is a dimmer that definitely is considered dimmer but we are missing the feedback level. you can't export this kind of project without with this kind of error. This is not like mandatory but obviously this point out that something could be wrong. So you can check it. If we enter to it we can see that he has found on off level but not Fal on off in this particular scenario. before getting into all the the devices and so on, I want to show you some very interesting feature. here below the structures menu, we can see unlocated devices that is the same menu what we have here that are devices that were found but like a channel but he

[3:00] couldn't the AI couldn't identify exactly where they belongs. this is why for example here is basement patio and we don't have in the basement any room called patio. So he in this kind of scenarios when he can't locate it with certain kind of precision we create this unknown unlocated devices but you can see that this is very simple because you can select for example in this case all of them are from patio and patio belongs for example to the guest bedroom. So we can select them and we can make a drag and drop. I'm going to do it with only one because I want to show you the two different way to doing this. One is making a drag and drop from this menu to the map view and another way is to make for example from here we are going to do the same. We go to the guest bedroom. We can make a drag and drop from this to here. So

[4:00] this is are these are the two ways to do it. And when you locate it or they unlocate it this menu goes off. So we don't have it anymore. And now we can we can see the devices here. then suppose that we want to add manually a device we can do it very easily. The same about locations as you saw in the before processing with AI. But to add a device you click and add the device. For example, here we can put name test. Here we have the channel that we are supporting currently light and epic gateway and inside light for example switch o in this case we are going to put a dimmer. We can we need to select the line we want it and then level and file level here. The good thing about this is very easy to identify and to find group address. You

[5:00] can search group address by group address or by name or by any combination for example all sorry all like 001. So you can see all the group addresses that has that number or by name for example ceiling sorry ceiling wreck. So basement garage on so this keeps and in this case is indicate that this group address is already been used by a device called ceiling that is in room garage. So you can filter from here and this avoids to show you all the group addresses that are already being used. So only you have the ones who you are not using. So this is a very nice feature because you can select very easily and the

[6:00] group addresses and another very important feature you can commit any error because basically you can put a group address with text or outside the the r the the range of the group

Technical walkthrough summary

The Control4 workspace video shows the generated project after AI processing. The installer can move through map and tree views, inspect devices, open errors, and edit device properties before the package is exported.

This review stage is where many practical mistakes should be found: missing feedback, unclear names, wrong subtypes, unsupported objects or devices placed in the wrong room.

The point of the workspace is to avoid using Composer as the first review tool. Composer should receive a clean .codu package, not a list of unresolved mapping decisions.

Related video pages