Configure the Home Assistant BACnet integration

After setup, click Configure on the integration card. A menu opens with three entries. Changes take effect immediately: the integration reloads by itself.

The options menu with Settings, Rescan device and Customize objects

Settings

The Settings page with the COV, polling interval, description and usage statistics options

OptionWhat it doesDefault
Enable COVUse Change of Value subscriptions for real-time updates. The device sends a message when a value changes, instead of waiting for the next poll. Present values use the standard SubscribeCOV service, which nearly all controllers support.On
COV incrementMinimum value change before a COV notification is sent (analog objects only). 0 uses the device default.0
Polling intervalHow often all objects are polled, in seconds (minimum 10). Polling always runs; COV only adds faster updates in between.30
Use descriptionName entities after the BACnet description (property 28) instead of objectName.Off
Live metadata propertiesOpt in per property (object_name, description, units) for a live push update. See Live metadata properties.None
Share usage statisticsEvery 6 hours, send this device's manufacturer, model, firmware and a few counts. See Privacy and usage statistics.Off

If a device does not support COV, or a subscription fails, polling takes over for that object. Nothing needs to be configured for that.

Note: If you set COV increment above 0, the value is written to the covIncrement property of each imported analog object (with COV) whose device value differs. This is the only setting that makes the integration write something without you switching an entity. The default 0 leaves the device value alone.

Live metadata properties

By default, changes to an object's metadata on the device (objectName, description, units, stateText, limits) are picked up within about an hour, or sooner if the object has active COV traffic. The Refresh object metadata button (under Configuration on the device page) checks immediately.

To see such changes at once, enable one or more properties under Live metadata properties. This uses the BACnet SubscribeCOVProperty service to get a push the moment the property changes. Keep in mind:

Rescan device

The Rescan device page with the fields Objects to add and Objects to remove

Re-reads the device's object list so you can add or remove objects. The page has three fields, all empty by default:

Both object fields are searchable by abbreviation (AI, BO 3), instance or name. Submitting without changes keeps the current selection; objects the device no longer has are dropped. Settings of removed objects are remembered and come back if you add the object again. Next comes Customize objects, so new objects can be set up right away.

Customize objects

Customize objects: picking the objects to change

Customize objects with entity type, COV and state class for a sensor

This page has a searchable list of your objects. Pick the ones you want to change; objects that already have a custom setting are already picked. The next page shows, for just those objects:

Step by step: Water meter and Energy meter. The Energy dashboard only lists sensors. A writable Analog Value is a number by default, so set its type to sensor in the same save.

Objects you do not pick use the defaults, described in Entities and attributes.

Note: A Value object is a switch or number only if it is commandable. Versions before 1.0.47 could save the wrong type when you saved the options. If that happened, a Repairs message offers to reset those objects to their defaults or to keep them. Keep them when you chose the type on purpose, for example a Binary Value without a Priority Array that still accepts writes.

Reconfigure

To change the local IP address, port, BBMD settings or the device address, open the ⋮ menu of the integration entry and choose Reconfigure. Entities, their history and all options are kept, and the integration reloads with the new settings.

Device information

During setup the integration reads the identity of the device and shows it in the Home Assistant device registry: