Update The Things Network sample

Author: dominicbetts

articles/iot-central/core/howto-build-iotc-device-bridge.md

@@ -266,13 +266,17 @@ function Decoder(bytes, port) {
 After you define the integration, add the following code before the call to `handleMessage` in line 21 of the *IoTCIntegration/index.js* file of your function app. This code translates the body of your HTTP integration to the expected format.
 
 ```javascript
-device: {
-    deviceId: req.body.hardware_serial.toLowerCase()
-},
-measurements: req.body.payload_fields
+req.body = {
+  device: {
+    deviceId: req.body.end_device_ids.device_id.toLowerCase()
+  },
+  measurements: req.body.uplink_message.decoded_payload
 };
 ```
 
+> [!NOTE]
+> The previous snippet uses the human-friendly device ID. The Things Network message also includes a technical ID that you can access using `req.body.dev_eui.toLowerCase()`. To learn more, see [The Things Network - Data Formats](https://www.thethingsindustries.com/docs/reference/data-formats/).
+
 ## Limitations
 
 The device bridge only forwards messages to IoT Central, and doesn't send messages back to devices. That's why, properties and commands don't work for devices that connect to IoT Central through this device bridge. Because device twin operations aren't supported, it's not possible to update device properties through the device bridge. To use these features, a device must connect directly to IoT Central using one of the [Azure IoT device SDKs](../../iot-hub/iot-hub-devguide-sdks.md).