---
title: "BACnet datapoint in Boss’nX: troubleshooting and FAQ"
description: "BACnet device required, object not found, typed name not kept or no value after saving: causes and checks for a BACnet datapoint in Boss’nX."
canonical: https://wiki.can-nx.com/en/guides/boss-point-bacnet-help/
language: en
product: Boss’nX
audience:
  - administrateur
  - installateur
context: "Boss’nX on a computer: component editor, BACnet datapoint of a declared device"
---

# BACnet datapoint in Boss’nX: troubleshooting and FAQ

Context: Boss’nX on a computer: component editor, BACnet datapoint of a declared device

Save refused, BACnet device or object not found, object name not kept, value or command not responding after saving: here are the causes and checks for a BACnet datapoint in the Boss’nX component editor. These answers are for administrators and installers with the **Manage components** permission, on a computer. To go through the full procedure again, follow [configuring a BACnet datapoint](https://wiki.can-nx.com/en/guides/boss-point-bacnet/).

## Why is creating or saving the component blocked?

A required field of a datapoint is missing. After **Create** or **Save**, read the error summary at the bottom of the screen, then check the component name and the **Label** of the datapoint indicated.

| Message | Check and action |
| --- | --- |
| **BACnet device required** | Choose the correct device in **BACnet device**. If it is missing, check the supervision and the device’s declaration before declaring another one, so as not to create a duplicate. |
| **BACnet feedback object required** | For **Feedback**, actually select a read object. With autocomplete, click the suggestion; with manual entry, choose the type and fill in the confirmed instance. |
| **BACnet action object required** | Check the selected object and the **Cmd** function. If the datapoint should only read, correct its function rather than choosing a fictitious command. |

A successful save takes you back to the original page. If this does not happen after the correction, follow [saving and errors in the common form](https://wiki.can-nx.com/en/guides/boss-component-edit/). Then reopen the component list to check whether the component already exists before starting a new creation.

## Why does the BACnet device not appear in the list?

First check that the correct supervision is open, then that the device is listed in [BACnet devices](https://wiki.can-nx.com/en/guides/boss-bacnet-devices/). If you can edit components but cannot administer devices, have the separate **Manage BACnet** permission checked.

Do not change the component’s general gateway at random to try to make a device appear.

## Why do a type button and a numeric field replace the object search?

No discovered object list is available for this device in this form. The form then switches to manual entry: this is not a sign of a failure. You have two options:

- run [object discovery](https://wiki.can-nx.com/en/guides/boss-bacnet-discovery/) to enable autocomplete;
- manually enter a type and an instance that are already confirmed.

## Why does the object search return no results?

Check that the chosen device is the correct one, then try part of the name or the type and instance reference, for example **AI:42** (fictitious example). Also view the discovery result, which may be partial.

If the reference remains unknown, contact support. Do not replace the expected object with a suggestion that only looks similar.

## Why is the typed name not kept?

The field is used to search and then select: click the correct suggestion to link the object. Deleting the text does not remove the previous link, which can remain selected. To remove it, use the **Clear** cross, then choose the object you want.

## What should I check after changing the device?

Choose the object again on the new device. Before saving, check the type, the instance, **Cmd / Feedback** and the options. The same number can designate another object on another device.

## Why does the value or the command not respond after saving?

Saving keeps the datapoint’s configuration. A saved configuration, or a device marked **Configured**, does not certify communication with the hardware: check it separately.

1. Reopen the datapoint and check the settings actually kept: device, object, read or command, options.
2. Check the result displayed on the component’s card using the [datapoint viewing guide](https://wiki.can-nx.com/en/guides/boss-component/).
3. Have the installer confirm the object, its read and write capabilities and the communication settings. A checked **Cmd** box describes the datapoint’s configuration; the device must also accept this command.
4. If the problem persists, contact support. Do not successively change the write priority, the object and the read mode without a confirmed mapping.

## I discovered the objects: why does my component have no datapoint?

Discovery prepares the list of the device’s objects; it does not create a datapoint. Then add the datapoint in the component, choose the device and the object, and save.

## Can I enter an instance without discovery?

Yes, if the form shows the manual selector and the installer has confirmed the type and the instance. Enter the object instance, without confusing it with the device instance.

## Does checking history recover the old values?

Not necessarily. The checkbox expresses a choice to record history, without guaranteeing that earlier measurements are recovered. To recover history, contact support with the period and the datapoint concerned.

## Why was the command unchecked after I chose the object?

An input object is offered as read-only. Check the function actually intended for the datapoint, without forcing a command to work around this choice.

## Does the bell mean the object is in alarm?

Not necessarily. It relates to the object’s intrinsic reporting and does not on its own indicate a current alarm. To interpret it, see [BACnet objects and their intrinsic alarming](https://wiki.can-nx.com/en/guides/boss-bacnet-objects/).

## Where do I define a command list or custom boolean labels?

**Value kind** alone does not define the commands and labels you want. For a procedure suited to your BACnet datapoint and your interface, contact support and describe the expected result.

## Contact support

If the problem persists after these checks, write to support@can-nx.com with the supervision, the component and the datapoint, the chosen device, the object type and instance, the expected functions, the exact symptom and the tests already done. A screenshot without sensitive data can help; no password or access key is needed.

French labels: **Équipement BACnet requis**, **Objet BACnet de retour requis**, **Objet BACnet d'action requis**, **Équipement BACnet**, **Re.Etat**, **Vider**, **Configuré**, **Type de valeur**, permissions **Gérer les composants** and **Gérer le BACnet**.