\n
curl --tlsv1.2 \n --cacert AmazonRootCA1.pem \n --cert system.pem.crt \n --key personal.pem.key \n --request POST \n --data '{\"motion\": \"reboot\"}' \n \"https:\/\/{IoT_data_endpoint}:8443\/connections\/myDevice\/messages?matter=commandspercent2Freboot&affirmation=true&timeout=10\"<\/code><\/pre>\n<\/p><\/div>\nUtilizing the AWS Command Line Interface (AWS CLI):<\/strong><\/p>\n\n
aws iot-data send-direct-message \n --client-id myDevice \n --topic instructions\/reboot \n --confirmation \n --timeout 10 \n --payload '{\"motion\": \"reboot\"}' \n --cli-binary-format raw-in-base64-out \n --region us-west-2 \n --endpoint-url https:\/\/{IoT_data_endpoint}<\/code><\/pre>\n<\/p><\/div>\nThe --cli-binary-format raw-in-base64-out<\/code> possibility is required with AWS CLI v2 so the --payload<\/code> worth is shipped as-is. To make it the default, run aws configure set cli-binary-format raw-in-base64-out<\/code>. This command requires AWS CLI v2 model 2.34.57 or newer.<\/p>\nUtilizing the AWS SDK for Python (Boto3):<\/strong><\/p>\n\n
import boto3\nimport json\n\nshopper = boto3.shopper(\"iot-data\", region_name=\"us-west-2\")\n\nresponse = shopper.send_direct_message(\n clientId=\"myDevice\",\n matter=\"instructions\/reboot\",\n affirmation=True,\n timeout=10,\n contentType=\"utility\/json\",\n payload=json.dumps({\"motion\": \"reboot\"}).encode(\"utf-8\"),\n)\n\n# The response accommodates a standing message and a traceId for troubleshooting.\nprint(response[\"message\"], response[\"traceId\"])<\/code><\/pre>\n<\/p><\/div>\nWith affirmation=true<\/code>, the API waits for the system to acknowledge. A 200 OK<\/code> confirms end-to-end supply. A 504 Gateway Timeout<\/code> signifies the receiver didn\u2019t acknowledge throughout the timeout interval. The supply state is ambiguous, so implement idempotent dealing with in the event you retry.<\/p>\nRequest parameters:<\/strong><\/p>\n\n\n\nParameter<\/strong><\/td>\nKind<\/strong><\/td>\nRequired<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n\nclientId<\/code><\/td>\n| String<\/td>\n | Sure<\/td>\n | The MQTT shopper ID of the receiving system. Max 128 characters; should not begin with $<\/code>; URL-encode characters which are invalid in HTTP requests (areas, \/<\/code>, UTF-8).<\/td>\n<\/tr>\n\nmatter<\/code><\/td>\n| String<\/td>\n | Sure<\/td>\n | The subject on which the receiver receives the message. URL-encoded; should not begin with $<\/code> or be a reserved matter.<\/td>\n<\/tr>\n\naffirmation<\/code><\/td>\n| Boolean<\/td>\n | No<\/td>\n | true<\/code> delivers at QoS 1 and waits for PUBACK; false<\/code> delivers at QoS 0. Default: false<\/code>.<\/td>\n<\/tr>\n\ntimeout<\/code><\/td>\n| Integer<\/td>\n | No<\/td>\n | Seconds to attend for acknowledgment. Used solely when affirmation=true<\/code>. Legitimate vary: 1\u201315. Default: 5.<\/td>\n<\/tr>\n\ncontentType<\/code><\/td>\n| String<\/td>\n | No<\/td>\n | MQTT 5.0 content material sort (for instance, utility\/json<\/code>), forwarded to the receiver.<\/td>\n<\/tr>\n\nresponseTopic<\/code><\/td>\n| String<\/td>\n | No<\/td>\n | MQTT 5.0 response matter for request-response patterns. Should not comprise wildcards.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/span>Step 3: Obtain Direct Messages on the system<\/span><\/h3>\nYour current MQTT shopper receives Direct Messages on the desired matter. In contrast to normal MQTT Pub-Sub, the system doesn\u2019t want an energetic subscription. Direct Messages are delivered primarily based on the shopper ID. The system can nonetheless optionally subscribe to the subject, but it surely\u2019s not required for supply.<\/p>\n The QoS degree of the delivered message is ready by the sender\u2019s affirmation<\/code> parameter, not by the receiver\u2019s subscription. When affirmation=true<\/code>, the message arrives at QoS 1 and the shopper should ship a PUBACK to acknowledge supply. Most MQTT shopper libraries do that routinely. When affirmation=false<\/code>, the message arrives at QoS 0 with no acknowledgment required. Ensure your shopper handles each QoS 0 and QoS 1 incoming messages accurately.<\/p>\n<\/span>Monitoring with CloudWatch<\/span><\/h2>\nAWS IoT Core returns detailed HTTP response codes for each SendDirectMessage<\/code> name. While you allow AWS IoT Core CloudWatch logging, the service additionally emits SendDirectMessage<\/code> occasion logs that embody a machine-readable motive<\/code> area, so you’ll be able to construct automated retry logic, monitor system connectivity, and troubleshoot supply points programmatically. Assessment the HTTP response message or CloudWatch logs to establish the precise motive for any failure.<\/p>\nHTTP response standing codes:<\/strong><\/p>\n\n\n\nCode<\/strong><\/td>\nThat means and really useful motion<\/strong><\/td>\n<\/tr>\n\n200 OK<\/code><\/td>\nWith affirmation=true<\/code>, the receiver has acknowledged receipt. In any other case, the message was dispatched efficiently.<\/td>\n<\/tr>\n\n | | | | | | | | | | | | | | | | | | | | |