Skip to content

Conversation

@Andry925
Copy link
Member

PR description

The documentation updated for Thingsboard IOT gateway MQTT connector.

Link checker

The links will be checked by the build agent automatically once you create or update your PR.

You can use the following command to check the broken links locally.

docker run --rm -it --network=host --name=linkchecker ghcr.io/linkchecker/linkchecker --check-extern --no-warnings http://0.0.0.0:4000/

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Comment on lines 67 to 68
These settings cover the basic connection parameters, mqtt version protocol that will be used for security configuration, and
authentication modes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rewrite this sentence

Basic<small></small>%,%basic%,%templates/iot-gateway/mqtt-connector/connection-to-broker-basic-section.md%br%
Advanced<small></small>%,%advanced%,%templates/iot-gateway/mqtt-connector/connection-to-broker-advanced-section.md{% endcapture %}
This subsection specifies the target MQTT broker and how the gateway interacts with it. It includes the broker's host,
port, mqtt version protocol, client id.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...port, mqtt version protocol and client id.

Comment on lines 82 to 98
#### Anonymous

{% capture mqttsecuritysubsection %}
Basic<small></small>%,%basic%,%templates/iot-gateway/mqtt-connector/security-subsection-basic.md%br%
Advanced<small></small>%,%advanced%,%templates/iot-gateway/mqtt-connector/security-subsection-advanced.md{% endcapture %}
{% include /templates/iot-gateway/mqtt-connector/security-subsection-anonymous.md %}

{% include content-toggle.liquid content-toggle-id="mqttsecuritysubsection" toggle-spec=mqttsecuritysubsection %}
#### Basic

{% include /templates/iot-gateway/mqtt-connector/security-subsection-basic.md %}

#### Certificates

{% include /templates/iot-gateway/mqtt-connector/security-subsection-certificates.md%}

{% capture difference %}
All configuration parameters list for each authentication mode, and their detailed description can be found in the
[Advanced configuration](/docs/iot-gateway/config/mqtt/#advanced-configuration) section.
{% endcapture %}
{% include templates/info-banner.md content=difference %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move these to selectable blocks

### Subsection "Data conversion"

- **Payload type** - The incoming data type that will be processed as `JSON`, `Bytes`, `Custom` (more information about supported Payload types see in the [Additional information](/docs/iot-gateway/config/mqtt/#convertor-types) *Convertor types section* ).
- **Name** - The name of the device in ThingsBoard. It can be parsed from `Message`, `Topic`, `Constant`, (more information about sources with screenshot examples can be found in the [Usage examples](/docs/iot-gateway/config/mqtt/#usage-examples) section).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device name


- **Payload type** - The incoming data type that will be processed as `JSON`, `Bytes`, `Custom` (more information about supported Payload types see in the [Additional information](/docs/iot-gateway/config/mqtt/#convertor-types) *Convertor types section* ).
- **Name** - The name of the device in ThingsBoard. It can be parsed from `Message`, `Topic`, `Constant`, (more information about sources with screenshot examples can be found in the [Usage examples](/docs/iot-gateway/config/mqtt/#usage-examples) section).
- **Profile name** - The device profile in ThingsBoard. It can be parsed from `Message`, `Topic`, `Constant` (more information about sources with screenshot examples can be found in the [Usage examples](/docs/iot-gateway/config/mqtt/#usage-examples) section).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device profile name

@@ -0,0 +1,110 @@
For Attribute updates, the gateway needs to know which devices should receive updates for which attributes. You configure this using regular expressions for both device names and attribute names. When an attribute is updated in ThingsBoard, the gateway publishes the new value to a configured MQTT topic.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comments as for connect/disconnect requests examples

@@ -0,0 +1,141 @@
For an Attribute request, the gateway must know which device name to target and which attribute to request. You can extract the device name either from the `Message` payload using [json-path](/docs/iot-gateway/config/mqtt/#json-path)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comments as for connect/disconnect requests examples

@@ -0,0 +1,111 @@
## Reserved RPC Methods
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comments as for connect/disconnect requests examples

@@ -0,0 +1,132 @@
RPC to Device allows sending RPC commands to the device that is connected to ThingsBoard directly or via Gateway.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comments as for connect/disconnect requests examples

Attribute request <small></small>%,%sharedidentifier%,%templates/iot-gateway/mqtt-connector/examples/request-mapping/attribute-request.md%br%
Attribute update <small></small>%,%rpctodevice%,%templates/iot-gateway/mqtt-connector/examples/request-mapping/attribute-update.md%br%
Reserved RPCs<small></small>%,%reservedrpc%,%templates/iot-gateway/mqtt-connector/examples/request-mapping/reserved-rpc.md%br%
Configurable RPC methods to device <small></small>%,%rpctoconnector%,%templates/iot-gateway/mqtt-connector/examples/request-mapping/configurable-rpc.md{% endcapture %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RPC to Device

@Andry925 Andry925 changed the title [WIP]: Updated documentation for MQTT connector. Updated documentation for MQTT connector. Nov 25, 2025
@Andry925 Andry925 changed the title Updated documentation for MQTT connector. Updated documentation for MQTT connector Nov 26, 2025
@ashvayka ashvayka merged commit b4033cd into thingsboard:master Nov 26, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants