> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/connectivity-as-a-service/connect-devices-via-mqtt/configure-a-publication.md).

# Configure a Publication

Since v12.0.0, BuildingPro Suites can not only act as a subscriber but also as a publisher of MQTT messages.

This chapter explains the interface you use to use BuildingPro Suites as an MQTT publisher.

## Procedure

1. Follow the steps in ↗ Broker Details -> Create new publication.\
   ▷ The "Configure Publication" menu opens.
2. Configure the publication as desired
3. Click on **Save \[C]**

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FVhAn9F19UTsf2cBlttUK%2FGroup%20250.png?alt=media&amp;token=71e0ef9b-b144-481d-b456-66f5af70b44f" alt=""><figcaption><p>The "Configure Publication" menu</p></figcaption></figure>

<table data-full-width="true"><thead><tr><th width="88.33333333333331">Element</th><th width="202.20001220703125">Title</th><th>Details</th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Topic preview</td><td>In this section you will see a preview of the incoming data</td></tr><tr><td><strong>[A1]</strong></td><td>Section "Configuration"</td><td>In this area you specify details about the publication.</td></tr><tr><td><strong>[A2]</strong></td><td>Name</td><td>Give the publication a name</td></tr><tr><td><strong>[A3]</strong></td><td>Topic</td><td>Enter the topic here under which BuildingPro Suites should publish messages</td></tr><tr><td><strong>[A4]</strong></td><td>Format</td><td>Select which format should be applied to the publication</td></tr><tr><td><strong>[A5]</strong></td><td>Create new format</td><td>Click here to create a new format.<br>▷Opens the "Functions" menu</td></tr><tr><td><strong>[B]</strong></td><td>Assets</td><td>In this section you select the assets whose data should be published.<br>◈ Assets are selected using <a href="/collection/mandatory-base/platform-core/workspace-and-identity/tags.md">↗ tags</a>.</td></tr><tr><td><strong>[B1]</strong></td><td>Search tags</td><td>Select one or more tags here. Assets that are tagged with the selected tags appear in field <strong>[B4]</strong></td></tr><tr><td><strong>[B2]</strong></td><td>Assets without tags</td><td>If this field is activated, all assets that are not tagged are selected and appear in <strong>[B4]</strong></td></tr><tr><td><strong>[B3]</strong></td><td>Selected tags</td><td>All tags selected in <strong>[B2]</strong> are listed here</td></tr><tr><td><strong>[B4]</strong></td><td>Pre-selection of assets</td><td>All assets that meet the criteria set in <strong>[B1]</strong> and <strong>[B2]</strong> are listed here. ⚠ These assets have not yet been selected!</td></tr><tr><td><strong>[B5]</strong></td><td>Select assets</td><td>Activate the checkbox next to the respective asset to enable this asset for publishing.</td></tr><tr><td><strong>[B6]</strong></td><td>Search in pre-selection</td><td>Searches the assets selected in <strong>[B4]</strong>.</td></tr><tr><td><strong>[B7]</strong></td><td>More options</td><td>Calls up more options for the selected asset.</td></tr><tr><td><strong>[C]</strong></td><td>Save</td><td>Click here to save the selection.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/connectivity-as-a-service/connect-devices-via-mqtt/configure-a-publication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.