AWS IoT Core Client
Available on the BSC-Pro from version 3.7.0
The export module "AWS IoT Core Client" enables a bidirectional connection to Amazon Web Services. It uses the IoT Core Data Model and thus enables not only the control of devices but also the management of automation rules.
The Simple IoT Core data model is used to transfer sensor and actuator data. The management of logic functions is implemented on the basis of the IoT Logic Core data model. Corresponding commands are defined in the IoT Command Core data model.
The export connection can be created and the parameters configured in the IoT Export area of the web configuration or the BSC Remote.
After the device has been created in AWS, the necessary certificates and keys must be downloaded. These are entered as parameters when creating the IoT export.
Parameter | Default value | Possible values | Description |
|---|---|---|---|
Endpoint | | | The AWS endpoint to be used. |
Port | 8883 | | The port to be used. |
QoS Level | 1 |
| The QoS level to be used. |
Retain Messages | Enabled |
| Specifies whether messages are saved on the server. |
Certificate | | | The device certificate. |
Key | | | The private device key. |
Root CA Certificate | | | If necessary, the root CA certificate. |
Watchdog Timeout | Disabled |
| If the connection is in a faulty or disconnected state for this period, the system is restarted. |
Refresh all objects after connect | Disabled |
| If activated, all objects are synchronized after each successful connection establishment. After restarting the device, all objects are initially synchronized regardless of this setting. |
DTO Container | Disabled |
| If this option is activated, the DTO objects are transferred in a DTOContainer. |
Send thing descriptions | Disabled |
| Control whether descriptions of the supported devices should be transferred. |
Object Topics | Enabled |
| If this option is activated, supported DTO objects are sent to another subtopic that corresponds to the object ID. |
Base Topic | iot/<Hardware ID> | | The basic topic, which precedes all others. |
Client ID | <Hardware ID> | | The client ID to be used. |
The topics are implemented on the basis of the "Resource Path" of the object types from the IoT Core Data Model. The "Base Topic" is always placed in front.
If the "Object Topics" option is activated, object messages are each sent in a subtopic. The topic is then made up of "Base Topic", "Resource Path" and the object ID. This option is ignored for DTO objects without ID support.
