A KNX telegram means nothing without the ETS project. Import it once and every group address arrives named, located and typed.
What a Group Address Is
KNX devices communicate by sending telegrams to group addresses such as 1/2/5. The bus carries the address and a few bytes of data, nothing else. The name of the address, the room it belongs to and how the bytes should be read exist only in the ETS project that the integrator built.
Datapoint Types
ETS assigns each group address a datapoint type (DPT). DPT 1.001 is a switch, DPT 5.001 a percentage and DPT 9.001 a two-byte temperature. Without the DPT, a telegram of two bytes could be a temperature, a light level or a setpoint.
What to Ask the Integrator For
Request the ETS project file or a group address export that includes names, addresses and datapoint types. A list of addresses alone is not enough, and a project without DPTs assigned leaves guesswork. Ask for the building structure as well, so addresses can be placed in rooms and floors.
From Export to Tags
Each group address with a DPT becomes a tag with a name, unit and location. Names follow your hierarchy, so 1/2/5 can become site.tower-a.level-3.room-301.temperature. Keep the ETS name alongside for cross-checking with the integrator.
Keeping It in Sync
When the integrator changes the project, addresses can move or be renamed. Re-import after each commissioning change and compare, rather than editing tags by hand, so the bus and the data model stay in step.
Common Questions
Can IoTServa read KNX without the ETS project?
It can see telegrams and addresses, but not what they mean. Ask the integrator for the project or a group address export with datapoint types.
Does importing the project change the KNX installation?
No. The import only reads the project to name and type the tags. Nothing is written to the bus.