Device ID and Payload Mapping in Downlink

Mapping Device ID in Topic downlink

Device ID can be mapped within an MQTT topic to send downlink data when performing read and write requests. You can include the keyword "#deviceid" anywhere in the mapped topic name.

Topic Handling in Application downlink

To interwork with generally available MQTT devices it is possible to use arbitrary topic names with no design limitation or predefine nomenclature rules when sending read or write downlink messages.

Read request

While performing a read request, you must map the MQTT topics for both the device bound and the server bound responses to the same IMPACT resource. This means that a single IMPACT resource can be mapped to one topic for Reading and one for the Read response.

Topic names can be mapped within an MQTT topic for MQTT devices to send a read message from an application.

Example

Write request

It is possible to map the Device ID within an MQTT topic to send downlink requests when performing a write request.

Topic name can be mapped within an MQTT topic to send downlink requests when performing a write request.

After the device is configured with an MQTT device and SUBSCRIBED to the mapped topic in the script, the application initiates a downlink write by issuing a PUBLISH message to an MQTT topic.

Example

Read and Write request using IMPACT Console

Read request

Write request

Sample script

Following is a sample script file which parses the payload.