CoduWorks
Contact
KNX → Control4OverviewFor integratorsServicesFree ToolsBlogAboutContact
Free generator

KNX group address generator

Configure floors, rooms, and categories to generate a consistent, exportable KNX group address structure for ETS planning and later integration review.

Parameters

Generated rows
128
First address
1/0/0
Last address
1/0/127
Group addressNameCategory
1/0/0F01-R01-LIGHTS-1lights
1/0/1F01-R01-LIGHTS-2lights
1/0/2F01-R01-LIGHTS-3lights
1/0/3F01-R01-LIGHTS-4lights
1/0/4F01-R01-BLINDS-1blinds
1/0/5F01-R01-BLINDS-2blinds
1/0/6F01-R01-SCENES-1scenes
1/0/7F01-R01-SCENES-2scenes
1/0/8F01-R02-LIGHTS-1lights
1/0/9F01-R02-LIGHTS-2lights
1/0/10F01-R02-LIGHTS-3lights
1/0/11F01-R02-LIGHTS-4lights
1/0/12F01-R02-BLINDS-1blinds
1/0/13F01-R02-BLINDS-2blinds
1/0/14F01-R02-SCENES-1scenes
1/0/15F01-R02-SCENES-2scenes
1/0/16F01-R03-LIGHTS-1lights
1/0/17F01-R03-LIGHTS-2lights
1/0/18F01-R03-LIGHTS-3lights
1/0/19F01-R03-LIGHTS-4lights
1/0/20F01-R03-BLINDS-1blinds
1/0/21F01-R03-BLINDS-2blinds
1/0/22F01-R03-SCENES-1scenes
1/0/23F01-R03-SCENES-2scenes
1/0/24F01-R04-LIGHTS-1lights
1/0/25F01-R04-LIGHTS-2lights
1/0/26F01-R04-LIGHTS-3lights
1/0/27F01-R04-LIGHTS-4lights
1/0/28F01-R04-BLINDS-1blinds
1/0/29F01-R04-BLINDS-2blinds
1/0/30F01-R04-SCENES-1scenes
1/0/31F01-R04-SCENES-2scenes
1/0/32F01-R05-LIGHTS-1lights
1/0/33F01-R05-LIGHTS-2lights
1/0/34F01-R05-LIGHTS-3lights
1/0/35F01-R05-LIGHTS-4lights
1/0/36F01-R05-BLINDS-1blinds
1/0/37F01-R05-BLINDS-2blinds
1/0/38F01-R05-SCENES-1scenes
1/0/39F01-R05-SCENES-2scenes
1/0/40F01-R06-LIGHTS-1lights
1/0/41F01-R06-LIGHTS-2lights
1/0/42F01-R06-LIGHTS-3lights
1/0/43F01-R06-LIGHTS-4lights
1/0/44F01-R06-BLINDS-1blinds
1/0/45F01-R06-BLINDS-2blinds
1/0/46F01-R06-SCENES-1scenes
1/0/47F01-R06-SCENES-2scenes
1/0/48F01-R07-LIGHTS-1lights
1/0/49F01-R07-LIGHTS-2lights
1/0/50F01-R07-LIGHTS-3lights
1/0/51F01-R07-LIGHTS-4lights
1/0/52F01-R07-BLINDS-1blinds
1/0/53F01-R07-BLINDS-2blinds
1/0/54F01-R07-SCENES-1scenes
1/0/55F01-R07-SCENES-2scenes
1/0/56F01-R08-LIGHTS-1lights
1/0/57F01-R08-LIGHTS-2lights
1/0/58F01-R08-LIGHTS-3lights
1/0/59F01-R08-LIGHTS-4lights
KNX planning

How to structure KNX group addresses before ETS work

A generator is useful only when the KNX group address naming convention remains readable after commissioning. The goal is not to fill addresses quickly; it is to create groups that an installer can understand months later.

Use a repeatable 3-level structure

A common approach is main group for function family, middle group for floor or area, and subgroup for the concrete channel. This keeps lighting, blinds, HVAC and scenes separated while still making room context visible.

Reserve predictable address sets

For dimmers, blinds and HVAC, reserve related addresses next to each other. Switch, feedback, dimming, value and value feedback should be easy to recognize as one functional set.

Do not treat CSV as the final project source

CSV is useful for planning and QA, but the final ETS project should keep devices, ComObjects, DPTs and topology together. For KNX to Control4 work, the .knxproj remains the richer source.

Examples

Group address structure examples

These examples are starting points. Adapt the main and middle group strategy to your company standard before importing anything into ETS.

PatternUseNote
1/0/0 - F01-R01-LIGHTS-1Lighting commandKeep feedback or dimmer value nearby.
1/0/1 - F01-R01-LIGHTS-1-FBLighting feedbackUse a clear suffix for status objects.
2/0/0 - F01-R01-BLINDS-1-UPDOWNBlind commandReserve stop and position addresses in the same block.
4/0/0 - F01-R01-SCENE-1Scene objectDocument payload expectations before Composer programming.
FAQ

Frequently asked questions

What is a KNX group address generator for?

It creates a repeatable group address plan that can be reviewed before ETS work. It helps avoid duplicate addresses and weak naming patterns.

Can I import the CSV directly into ETS?

Use the CSV as a planning or QA artifact. Before final integration, verify the structure in ETS and keep the .knxproj as the source for rich project context.

What structure works best for Control4 mapping later?

Keep command and feedback addresses close, use stable names for room and function, and keep DPT intent clear so the later Control4 review can group signals into devices.