Overview
You can synchronize the data of attributes and entities to a generic MQTT broker. The MQTT broker needs to be added as a data destination in IIH Essentials. The topic where the data will be sent to, the payload structure and further MQTT parameters can be chosen via the UI of IIH Essentials.
Possible hierarchy
This tables shows different hierarchy structures and if they are able to sync with a generic MQTT broker:
| Top element | Link to parent | Subelement (with attribute) |
Link to parent | Allowed in IIH | Sync with generic MQTT |
|---|---|---|---|---|---|
| Asset | Relation | ||||
| Asset/Aspect | Relation/Composition | Yes | Yes | ||
| Asset/Aspect | Aggregation | Yes | Yes * | ||
| Asset | Composition | ||||
| Asset/Aspect | Relation | No | |||
| Asset/Aspect | Composition | Yes | Yes | ||
| Asset/Aspect | Aggregation | Yes | Yes * | ||
| Aspect | Relation | ||||
| Asset | Relation/Composition | No | |||
| Aspect | Relation/Composition | Yes | Yes | ||
| Asset/Aspect | Aggregation | Yes | Yes * | ||
| Aspect | Composition | ||||
| Asset | Relation/Composition | No | |||
| Aspect | Relation | No | |||
| Aspect | Composition | Yes | Yes | ||
| Asset/Aspect | Aggregation | Yes | Yes * |
*: The subelement will be synced via the Relation/Composition hierarchy.
Firewall settings
The firewall must be opened for the port chosen for the MQTT communication between IIH Essentials and the MQTT broker. The port number needs to be specified while setting up the MQTT broker as a data destination in IIH Essentials.