KNX structure in Boss’nX: troubleshooting component creation

Empty list, greyed-out checkboxes, unexpected number of components, destination not found, nothing created or a partial result: here are the causes and the checks for the Structure step of Boss’nX (Menu → KNX commissioning), in the building supervision. For the normal path, follow creating from the structure or reimporting on existing components.

Why is the list empty or are the checkboxes greyed out?

1. Clear Search a component…. No component matches your search. may simply come from the search text.
2. Remove the space filter with Reset, next to the Location button. No component in the selected spaces. relates to this filter.
3. Open Filter and remove the type filters with Reset tags. Closing the chips leaves the filters active.
4. If All detected items are non-importable. appears, click Show non-importable items (N), then examine the Unknown or Excluded rows. Their checkbox stays greyed out as long as they are not recognized as importable.
5. Check the dictionary, its keywords, exclusions and scopes, then the success of the new classification. Do not reset the building organization to correct a recognition.

If Structure is locked or if no usable classification is available, see import and dictionary troubleshooting. If the confirmed rules and project still give none of the expected items, contact support.

Why does the number of components to create not match the list?

The Create N components button counts all the selected rows, including those hidden by the search or filters. Select all adds the filtered view to the existing selection, without replacing it.

To create only a specific subset:

1. Click Clear selection.
2. Apply the search or filters you want, then select the rows.
3. Before starting, remove the filters to review the full selection.

The button can also count Already imported or Ambiguous rows, which the matching will not create as new components. It is disabled when nothing is selected, or while a creation or a list update is in progress: wait for the current processing to finish before clicking anything else.

Why is the expected location missing or seemingly unchanged?

The Location button in the toolbar filters the source spaces. To set a destination, open the Location cell of the relevant row.

In Choose a location, use Search a space… and refine the name if a section shows only some of the destinations. Check the parent path and the existing badge. Clear this search to find Auto (detected) and Unassigned again. A building part alone is not offered as a component destination.

After your choice, check the row’s cell: the grouping and the filter may still show the project’s source space. For a matched existing component, change its location in the component form; merging the datapoints does not move it according to the review.

If the destination still cannot be found, have the authorized floor or zone prepared in Building organisation, then come back to prepare the review. For a destination whose name or permissions remain uncertain, contact support.

Why was no component created?

Message	Action
No new component to create (duplicates detected).	Look for the components that are already present, then check the badges and the reimport procedure. Do not rename a row just to force a new creation.
No KNX group can be used for express creation.	Check the importable items, their command or feedback addresses and the classification. A row or an old group that is present does not necessarily have usable datapoints.
Message announcing group(s) without KNX id skipped, or no component ready after the building parts, floors or zones were created	Check the destination and the items already created. Do not invent an identifier and do not reset the topology to try again. If needed, choose a confirmed existing destination in the location cell; if the result remains uncertain, contact support.

Also check Manage topology and Manage components, as well as the scope authorized by the administrator: access to the step does not ensure permission to create all the components or spaces.

What to do after a partial result or closing without confirmation?

Components may be created or updated before a failure, and spaces created without all their components. A success message accompanied by errors therefore indicates a partial result. For example, if you imported two components and only one appears, first check what was saved, then only the missing row.

1. Wait for the processing to finish and keep the messages. Do not click Create or Apply again during the operation.
2. Open Components and check the saved names, addresses, destinations and datapoints. Also check the relevant spaces in Building organisation. If necessary, reload the supervision after the processing has finished to review the available state.
3. Go back to Structure and click Clear selection to start again from a known selection. Check the badges, then select only the item that is still missing or the specific correction still to be applied.
4. For a missing and confirmed new creation, review its destination before creating this single row. For an update of existing components, go back to the merge or conflict review, one row at a time.
5. If you cannot determine what was kept, if a component expected to exist appears as New, or if this specific rerun still fails, contact support before making any other change.

Do not delete the successful components to “start over cleanly”. Clicking Cancel in a window, going back to the previous step or leaving the page does not undo saves that have already been made. After the conflicts window closes, check in the component that Apply actually succeeded.

How do I remove a datapoint deleted from the new KNX file?

A reimport does not automatically delete a datapoint removed from the KNX file. Check its use in the component before removing it manually. If deleting it may affect associated commands, alarms or other uses, have the deletion confirmed first.

Contact support

If you have already checked the result and retried without success, write to support@can-nx.com, specifying:

• the supervision concerned;
• the expected component and the result you actually reviewed;
• the exact message;
• the rerun already attempted.

A screenshot without sensitive data can help.

French labels: Aucun composant ne correspond à la recherche., Aucun composant dans les espaces sélectionnés., Tous les éléments détectés sont non importables., Aucun nouveau composant à créer (doublons détectés)., Échec de l’application des résolutions de conflits.