KNX / ETS XML import – cannot choose target Group Address structure (imports always to root)

Avatar

Area: cc/devices/knx → Import data from ETS

Problem description

In large KNX projects I regularly import only parts of the ETS Group Address structure (XML export), not the whole project.
This is intentional — importing the full ETS project every time is heavy, slow and requires a lot of re-verification.

Typical workflow:

  • In ETS I export only a fragment of Group Addresses, e.g. branch 3/2/...

  • XML contains correct GroupAddress info with full GA (e.g. 3/2/0)

Example ETS XML export:

<GroupRange Name="SENSORS" RangeStart="6656" RangeEnd="6911">
    <GroupAddress Name="SENSOR1" Address="3/2/0" />
</GroupRange>

Actual behavior in ComfortClick

After import:

  • All Group Addresses are placed in devices/knx root

  • They are not imported into their logical GA structure (3/2/...)

  • There is no option to select target GroupRange / folder

  • There is no bulk move option afterwards → everything must be moved one-by-one

This is very time-consuming and error-prone in large projects.

Expected behavior

Expected Reason
Import into correct GA structure (3-level based on GA) Structure is already known from ETS
or allow selecting target GroupRange Partial imports are common
or provide bulk move after import Basic project hygiene

Current workaround (undesirable)

I have to manually edit the ETS-generated XML and wrap the exported fragment into a higher-level GroupRange, copied from a full ETS export:

<GroupRange Name="FLOOR" RangeStart="6144" RangeEnd="8191">
    <GroupRange Name="SENSORS" RangeStart="6656" RangeEnd="6911">
        <GroupAddress Name="SENSOR1" Address="3/2/0" />
    </GroupRange>
</GroupRange>

This works, but:

  • requires manual XML editing

  • is error-prone

  • is extremely annoying in large / iterative projects

Question / request

Is there:

  • a setting to define import target location, or

  • a planned improvement to make ETS partial imports respect GA structure, or

  • a bulk move feature for imported KNX objects?

This would significantly improve workflows for large KNX projects.

Thanks in advance.