--- title: Create or edit a component and its datapoints in Boss’nX description: "Create or edit a Boss’nX component: name, type, floor, zone and gateway, then add KNX, BACnet or Modbus datapoints, save and fix validation messages." canonical: https://wiki.can-nx.com/en/guides/boss-component-edit/ language: en product: Boss’nX audience: - administrateur - installateur context: "Boss’nX, supervision or hypervision: component form on a computer, with the Manage components right" --- # Create or edit a component and its datapoints in Boss’nX Context: Boss’nX, supervision or hypervision: component form on a computer, with the Manage components right The Boss’nX component form brings together the name, type, location (building, floor, zone), gateway and the list of datapoints, KNX or other protocols. It is used to create a component or edit an existing one, in a supervision opened directly or from the hypervision. Intended for administrators and installers with **Manage components**. The steps below describe the form on a computer. ## Before you start - Your account has **Manage components**. Viewing or command-sending rights do not replace this editing right. - Prepare the name, the location, the gateway and the parameters of the datapoints to configure. - To start from an existing item, you can also [duplicate a component and organize its datapoints](https://wiki.can-nx.com/en/guides/boss-component-copy-points/). ## Open the form 1. In the relevant supervision, open **Components** in your bar or through **Menu → Components**. On a tablet or phone, the bar and **Menu** are at the bottom of the screen. 2. Check the title **Component Management**. 3. To create one, click **Add component**, at the top. The title becomes **Create component**. 4. To edit one, find the right card with [the Components filters](https://wiki.can-nx.com/en/guides/boss-components-find/), then click its **Edit component** pencil, at the top right. The pencil is also available in the detail sheet, to the right of the name. Wait for **Loading component...** to finish, then check the loaded values. At creation, the suggested name and type do not describe your device: replace them with the appropriate values. ## Fill in the general parameters | Field | What to do | | --- | --- | | **Component name** | Give a non-empty, recognizable name, for example **Test ventilation**, a fictional example. | | **Type** | Choose the category that matches the component. It does not replace the choice of the protocol of its datapoints. | | **Building** | Select the building part you want, or leave **All buildings** to choose among the available floors. This selection filters the floors. | | **Floor** | Choose the actual floor rather than the first floor displayed. **Unassigned** is offered if you are preparing a component without assignment to a floor. | | **Zone** | Choose a zone of this floor. **Floor root** corresponds to an assignment directly to the floor, without a zone. The list is greyed out if no zone is offered. | | **Gateway** | Choose the gateway planned for the component. **None** lets you prepare the parameters without choosing a gateway; the **Gateway memo to install (optional)** field is then used as a note, without creating or attaching a gateway. | | **Favorite** | Check to use this component among the favorites. See [dashboard favorites](https://wiki.can-nx.com/en/guides/boss-dashboard-favorites/). | | **Integrator comment** | Add, if useful, a configuration note intended for the people who edit the component. | The building, floor and zone lists let you search and then select a result. After changing the building or the floor, **check the floor and the zone again**: incompatible choices may be replaced or cleared. Before moving an existing component to another zone, check the rules of the original zone that use it: rules left without a reference in this zone may be removed during the move. Then check with the installer the expected uses in the old and the new zone. If you change the component’s **Gateway**, also check the specific gateways of its KNX datapoints: see [inheritance and choice per datapoint](https://wiki.can-nx.com/en/guides/boss-point-knx/). ## Add the datapoints 1. Click **Add point**, under the list of datapoints. 2. Fill in its **Label**, choose its protocol and configure the fields that match its use with the help of the table below. 3. Leave the last field you entered, then review the values before saving. | Need | Guide to follow | | --- | --- | | KNX datapoint | [Configure the addresses and the DPT](https://wiki.can-nx.com/en/guides/boss-point-knx/), then [the formats and commands](https://wiki.can-nx.com/en/guides/boss-point-display/) | | BACnet datapoint: device and object | [BACnet datapoints](https://wiki.can-nx.com/en/guides/boss-point-bacnet/) | | Modbus datapoint: registers and no-signal check | [Modbus datapoints](https://wiki.can-nx.com/en/guides/boss-point-modbus/) | | Trigger linked to an action or a scenario | [Configure a Linknx datapoint](https://wiki.can-nx.com/en/guides/boss-point-linknx/) | | Several datapoints already available, through the **Import** menu | [KNX](https://wiki.can-nx.com/en/guides/boss-import-knx/), [BACnet](https://wiki.can-nx.com/en/guides/boss-import-bacnet/) or [Modbus from monitoring](https://wiki.can-nx.com/en/guides/boss-import-modbus/) import | | Alarm datapoint | [Thresholds and lists](https://wiki.can-nx.com/en/guides/boss-point-alarm/), [simple comparison](https://wiki.can-nx.com/en/guides/boss-point-alarm-comparison/) and [heartbeat, BACnet source and troubleshooting](https://wiki.can-nx.com/en/guides/boss-point-alarm-help/) | The paths of the **Import** menu depend on the addresses and devices already configured. ## Save the component 1. Click **Create** for a new component, or **Save** for an edit. This button is fixed at the bottom right; **Saving...** indicates the operation in progress. 2. After success, the interface returns to the original page, for example the component list or the detail sheet. To abandon the pending changes, use **Back**, the arrow at the top left, before saving. This button does not undo a change that has already been saved: to correct it, reopen the form and save the corrected values. ## Check the result 1. Find the component, reopen **Edit component**, then review its name, its location, its gateway and its datapoints. 2. Then check the expected display and operation in the supervision, following the installation’s procedure. Communication with the hardware is checked on the installation, not by saving the form alone. ## Troubleshooting | Message or symptom | Action | | --- | --- | | **Name is required.** | Fill in **Component name**. | | **Label is required**, **Feedback address required**, **Command address required** | These errors indicate the datapoint concerned. Correct the fields that match the functions enabled on this datapoint. Closing the error summary does not correct them. | | **Unable to fetch gateways.** | Check the supervision and your connection, then reopen the form. Do not replace a known gateway with **None** just to work around this message. | | **Restricted access** or missing pencil | Have the administrator check **Manage components** and the account’s scope. | | Form still open after **Create** or **Save**, without a clear result | Do not consider the save as done. Note the visible messages and keep the useful parameters. Reopen the list to check whether the component exists and which parameters were saved, before starting again or creating a duplicate. | If the uncertainty persists, contact support@can-nx.com with the supervision, the component name, the attempted action and your checks, without a password, access key or confidential data. French labels: **Composants → Gestion des Composants → Ajouter un composant**, **Modifier le composant**, **Menu**, **Nom du composant**, **Type**, **Bâtiment**, **Étage**, **Zone**, **Passerelle**, **Aucune**, **Favori**, **Commentaire de l'intégrateur**, **Ajouter un point**, **Créer**, **Enregistrer**, **Sauvegarde...**, **Retour**, **Tous les bâtiments**, **Non assigné**, **Racine de l'étage**.