What this video covers
This video shows the relationship between KNX ComObjects, Group Addresses, and Control4 mapping.
Video points
- KNX ComObjects.
- KNX Group Addresses.
- Correlation with Control4 mapping.
Video chapters
- 0:00 — Cross-check KNX and Control4
- 0:17 — Inspect actuator correlations
- 1:34 — Review unsupported channels
- 2:34 — Create a mapping manually
- 3:00 — Verify dimmer mappings
Full English transcript
Automatic English captions from the published YouTube video, lightly normalized for product names.
[0:00] a feature that I really love. now we are in Control4 side. But if we go to the KNX side of the project, we come back to this these menus that we saw previously. suppose that we go to an switching actuator. We can see that this switching actuator has two channels with group addresses. And now that we have the Control4 enabled, we can see that in the group address we have the Control4 simol and this indicates the amount of Control4 devices that are using this group address. And for for every device we have the summary of how many logical devices in Control4 are using this group address. So in actuator that using two definitely two channels we have two devices. This is a crystal clear indication that we
[1:00] have all the devices that we need in this actuator is in Control4 side. The same if for example if you go to the Deli gateway we can see here for example we have the channel 17 we have a device that's called demo house basement gas bedroom ceiling and we can see the group addresses that are being used in that as you can see here we have the regulation DP3 that currently we are not supporting it here basically Basically, we can see that we have two channels, two devices. So, here it's very very easy to spot if all the actuators have the right amount of of Control4 devices. suppose that we have a device that is not there because Control4 couldn't
[2:00] the II couldn't found it. it's not the cases because this project is very accurate and I found everything but we have a very nice feature suppose that this device is not present and you want to add it manually in Control4. You basically select the group address that you want. That is for example the brick brightness value and feedback brightness value. This one you go to right click or plus this is repeated because it's the same group address. You go right click add Control4 device or you click in this plus button and instantly you have a new popup with a device that here for example we call it ceiling ceiling we can select a room kitchen
[3:00] the type is dimmer and the line is automatically picked from the device individual address so it's in is like suggested you can change if you want. And here even though that you can search like always we have added a new feature that you can basically you make a drag and drop. So as you have select these two group addresses you have an ability to make a drag and drop. So this very easily you add a new Control4 device and but of course this is repeated and we can see that we have two ceiling lights in the kitchen. this is something that we don't want but here you can see how this work. I really think that this is very cool feature, something that I miss it a lot because when I was a programmer, I I had to do it device by device and make a a checklist. So this is very easy to cross information between the two platforms.
Technical walkthrough summary
This mapping video focuses on the relationship between KNX ComObjects, Group Addresses, DPTs and the generated Control4 devices. It shows why a Control4 device usually needs more than one KNX address.
The installer can compare the KNX source with the Control4 view to confirm command addresses, feedback addresses and datapoint intent before export.
This is useful when diagnosing status problems. A command may be correct while feedback is missing or mapped with the wrong function, so the cross-check keeps both sides visible.
