Reimport a KNX project in Boss’nX: merges and address conflicts

When the ETS project changes, reimport its .knxproj file into Boss’nX: the Structure step matches the detected items with the existing components, offers to add the new datapoints to them and lets you choose which address to keep in case of conflict. You update the existing components instead of creating new ones.

Intended for administrators and installers with Manage topology and Manage components. For a first creation of components, follow the structure review, whose filters and selection this guide reuses.

Before you start

• You work on a computer, at the Structure step of Menu → KNX commissioning, in the relevant supervision.
• The new file is imported and its dictionary saved, as described in the file import and the dictionary.
• The reimported project and its classification match this supervision.

Read the matching badges

The badges compare the addresses of the detected items with those of the existing components. Only the addresses count: a similar name does not necessarily mean the same component.

Badge	Check to perform
New	Check that it really is a component to add, absent from the existing list.
Already imported	The match does not propose new datapoints. Check the saved component if you expected a difference.
To merge	Datapoints or completions are proposed for an existing component. Open the details before applying.
Conflict	A proposed address requires choosing between the current value and the structure value.
Ambiguous	The match does not identify a single component. Creation with matching ignores this row; have the target confirmed.

A row can remain selectable even with an Already imported or Ambiguous badge. A checked box or the number shown on the Create button therefore does not announce as many creations.

If the same addresses are reused across several installations or gateways, if the grouping has changed significantly or if a known component appears as New, do not force a creation to work around the matching: contact support to confirm the appropriate way to rerun the import.

Apply an update to an existing component

When rerunning on existing components, process one row at a time.

1. In Structure, clear the filters that hide the relevant rows, then click Clear selection to start again from a known selection.
2. Expand the row to process with the chevron on the right. Check its addresses and its sections: Already present, New (structure), Conflicts and Manually added.
3. Check this single row, then click Create 1 component, the main button of the review. Despite its name, it can update the matched component instead of creating another one.
4. If the row is To merge, wait for the result. The message Existing components updated… can announce this update.
5. If a conflicts window opens, follow the next section.
6. Check the component as described in “Check the result” before moving on to the next row.

Manually added groups the existing datapoints that this proposal does not include. This label does not indicate their origin: datapoints removed from the new project can also appear there.

A merge can add datapoints, or complete a command datapoint with its feedback, or the reverse. The names and location of the existing component are not replaced by the review adjustments. Datapoints missing from the new file are not deleted automatically.

Do not use Import without assignment to obtain a merge: this choice is used to create components without a location. To move or rename an existing component, use its form.

Resolve an address conflict

After the row has been started, Resolve address conflicts shows the existing component, the datapoint, the Feedback address or Command address field, then the Current and Structure values.

1. Check the component name and the datapoint shown. If the target is not the expected one, click Cancel, then contact support before making any other change.
2. Keep current is selected by default: the current conflicting address is kept.
3. Choose Take structure only if the proposed address is confirmed for this datapoint. Fictional example: a current feedback address 14/1/9 can be replaced by 14/1/2 when this change is intended and confirmed.
4. Browse the conflicts with the Previous and Next arrows. Keep all and Replace all change the choice of every row in the window: use them only if that decision suits each conflict.
5. Click Apply once and wait for the result.

Keep current protects the conflicting address; the other additions or completions of the merge remain applied. Cancel closes the review without applying these resolutions. It does not undo the creations or updates of other rows that already succeeded during a broader selection.

If several conflicts seem to concern the same datapoint, if a value is unexpected or if you do not know which address to keep, cancel the review and contact support. Do not pick an address at random to unblock the import.

Check the result

1. Find the component in Components and open it, even if the conflicts window closed normally.
2. Review its addresses, then the datapoints actually kept, added or completed.
3. Also check the datapoints that the proposal did not include: they stay in the component until you remove them.

Troubleshooting

Failed to apply conflict resolutions. or a partial creation message indicates that some operations may have succeeded. Check the saved state before trying again, following recovering after a partial result.

If you have already checked the components and retried the specific correction without success, write to support@can-nx.com with the supervision, the components concerned, the messages and the attempts made. Do not send any password or access key.

French labels: Nouveau, Déjà importé, À fusionner, Conflit, Ambigu, Résoudre les conflits d’adresses, Actuel, Structure, Garder l’actuel, Prendre la structure, Tout garder, Tout remplacer, Appliquer, Annuler.