Connect your Sidewalk device and view uplink metadata format - AWS IoT Core

Connect your Sidewalk device and view uplink metadata format

After you've added your Sidewalk credentials and added the destination, you can provision your Sidewalk endpoints and connect your device.

Connect your Sidewalk device

You can provision your device as a Sidewalk endpoint by generating the device certificates and application server certificates from the Sidewalk Developer Service (SDS) console. For more information, see Provision and Configure your Sidewalk Endpoints.

After you connect your device, you'll see your Sidewalk device in the Devices page of the AWS IoT console, on the Sidewalk tab. When your device is connected and starts sending data, you'll see the date and time for the Last uplink received at field.

After you've connected your device, you can subscribe to the topic (for example, project/sensor/observed) that you specified when creating the Sidewalk destination rule to observe uplink messages from the device. To subscribe to the topic, go to the MQTT test client on the Test page of the AWS IoT console, enter the topic name (for example, project/sensor/observed), and then choose Subscribe.

The following example shows the format of the uplink messages that are sent from Sidewalk devices to AWS IoT. The WirelessMetadata contains metadata about the message request.

{ “WirelessDeviceId”: “8dccc5978df94950b57a58116c6f52e6", “PayloadData”: “AAAAAAAA//8=“, “TransmitMode”: “0", “WirelessMetadata”: "WirelessMetadata(sidewalk=Sidewalk(seq=1983, messageType=null, cmdExStatus=null, nackExStatus=null)) } }

The following table shows a definition of the different parameters in the uplink metadata. For information about parameters WirelessDeviceID, PayloadData, and messageType, see SidewalkDevice and SidewalkSendDataToDevice.

Uplink metadata parameters
Parameter Description Type Required

The transmission mode for data that is sent from the wireless device. Can be 0 for unconfirmed mode, 1 for confirmed, and 2 for unused.

Integer Yes

Command runtime status. Response-type messages shall include the status code, COMMAND_EXEC_STATUS_SUCCESS. However, notifications might not include the status code.

Enumeration No

Response nack status, which can be RADIO_TX_ERROR or MEMORY_ERROR.

Array of strings No