AWS IoT Core Client

available on the bsc pro from version 3 7 0 introduction the export module "aws iot core client" enables a bidirectional connection to amazon web services it uses the iot core data model docid\ uv3 mck6dtxwysimop4mz and thus enables not only the control of devices but also the management of automation rules the simple iot core docid 5y ebsqs4y5f2pqiacvlt 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 docid\ khqqklgdjkioaqd8w kdf data model corresponding commands are defined in the iot command core docid\ dwtdyep4erjygooftsvch data model configuration the export connection can be created and the parameters configured in the iot export area of the web configuration or the bsc remote parameters 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 0 1 2 the qos level to be used retain messages enabled enabled disabled 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 disabled 1 min 7 days if the connection is in a faulty or disconnected state for this period, the system is restarted refresh all objects after connect disabled enabled 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 enabled disabled if this option is activated, the dto objects are transferred in a iot core data model docid\ uv3 mck6dtxwysimop4mz send thing descriptions disabled enabled disabled control whether descriptions of the supported devices should be transferred object topics enabled enabled disabled 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 topic structure the topics are implemented on the basis of the "resource path" of the object types from the iot core data model docid\ uv3 mck6dtxwysimop4mz 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