Skip to content

Commit 9561c1c

Browse files
authored
Merge pull request #196874 from dominicbetts/central-edge-version-note
IoT Central - IoT Edge version warning
2 parents d38c0ba + 208c659 commit 9561c1c

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

articles/iot-central/core/concepts-telemetry-properties-commands.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,9 @@ IoT Central lets you view the raw data that a device sends to an application. Th
5151

5252
If the telemetry is defined in a component, add a custom message property called `$.sub` with the name of the component as defined in the device model. To learn more, see [Tutorial: Create and connect a client application to your Azure IoT Central application](tutorial-connect-device.md).
5353

54+
> [!IMPORTANT]
55+
> To display telemetry from components hosted in IoT Edge modules correctly, use [IoT Edge version 1.2.4](https://github.com/Azure/azure-iotedge/releases/tag/1.2.4) or later. If you use an earlier version, telemetry from your components in IoT Edge modules displays as *_unmodeleddata*.
56+
5457
### Primitive types
5558

5659
This section shows examples of primitive telemetry types that a device streams to an IoT Central application.

articles/iot-central/core/troubleshoot-connection.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,10 +194,11 @@ To detect which categories your issue is in, run the most appropriate Azure CLI
194194
195195
You may be prompted to install the `uamqp` library the first time you run a `validate` command.
196196
197-
The two common types of issue that cause device data to not appear in IoT Central are:
197+
The three common types of issue that cause device data to not appear in IoT Central are:
198198
199199
- Device template to device data mismatch.
200200
- Data is invalid JSON.
201+
- Old versions of IoT Edge cause telemetry from components to display incorrectly as unmodeled data.
201202
202203
### Device template to device data mismatch
203204
@@ -243,6 +244,10 @@ If there are no errors reported, but a value isn't appearing, then it's probably
243244

244245
You can't use the validate commands or the **Raw data** view in the UI to detect if the device is sending malformed JSON.
245246

247+
### IoT Edge version
248+
249+
To display telemetry from components hosted in IoT Edge modules correctly, use [IoT Edge version 1.2.4](https://github.com/Azure/azure-iotedge/releases/tag/1.2.4) or later. If you use an earlier version, telemetry from components in IoT Edge modules displays as *_unmodeleddata*.
250+
246251
## Next steps
247252

248253
If you need more help, you can contact the Azure experts on the [Microsoft Q&A and Stack Overflow forums](https://azure.microsoft.com/support/community/). Alternatively, you can file an [Azure support ticket](https://portal.azure.com/#create/Microsoft.Support).

0 commit comments

Comments
 (0)