Merge pull request #272569 from dominicbetts/central-device-templates

Central: update device templates

Author: PMEds28

articles/iot-central/.openpublishing.redirection.iot-central.json

@@ -352,17 +352,22 @@
     },
     {
       "source_path_from_root": "/articles/iot-central/core/howto-create-custom-analytics-pnp.md",
-      "redirect_url": "/azure/iot-central/core/howto-create-custom-analytics/",
+      "redirect_url": "/azure/iot/iot-overview-analyze-visualize/",
       "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/iot-central/howto-create-custom-analytics.md",
-      "redirect_url": "/azure/iot-central/core/howto-create-custom-analytics/",
+      "redirect_url": "/azure/iot/iot-overview-analyze-visualize/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/howto-create-custom-analytics.md",
+      "redirect_url": "/azure/iot/iot-overview-analyze-visualize/",
       "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/iot-central/preview/howto-create-custom-analytics.md",
-      "redirect_url": "/azure/iot-central/core/howto-create-custom-analytics/",
+      "redirect_url": "/azure/iot/iot-overview-analyze-visualize/",
       "redirect_document_id": false
     },
     {

articles/iot-central/TOC.yml

@@ -167,8 +167,6 @@
               href: core/howto-export-to-webhook.md
             - name: Transform data internally for export
               href: core/howto-transform-data-internally.md
-        - name: Export data and visualize with Databricks
-          href: core/howto-create-custom-analytics.md
         - name: Transform data internally on ingress
           href: core/howto-map-data.md
         - name: Transform data externally

articles/iot-central/core/howto-configure-rules.md

@@ -3,7 +3,7 @@ title: Configure rules and actions in Azure IoT Central
 description: This how-to article shows you, as a builder, how to configure telemetry-based rules and actions in your Azure IoT Central application.
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/14/2023
+ms.date: 04/16/2024
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -99,7 +99,7 @@ When a rule triggers, it makes an HTTP POST request to the callback URL. The req
     "device": {
         "id": "<device_id>",
         "etag": "<etag>",
-        "displayName": "MXChip IoT DevKit - 1yl6vvhax6c",
+        "displayName": "Refrigerator Monitor - 1yl6vvhax6c",
         "instanceOf": "<device_template_id>",
         "simulated": true,
         "provisioned": true,
@@ -160,8 +160,8 @@ If you have one or more webhooks created and saved before **3 April 2020**, dele
         "enabled": true
     },
     "device": {
-        "id": "mx1",
-        "displayName": "MXChip IoT DevKit - mx1",
+        "id": "rm1",
+        "displayName": "Refrigerator Monitor - rm1",
         "instanceOf": "<device-template-id>",
         "simulated": true,
         "provisioned": true,

articles/iot-central/core/howto-create-custom-analytics.md

@@ -1,6 +1,6 @@
 ---
 title: Define a new IoT device type in Azure IoT Central
-description: How to create an Azure IoT device template in your Azure IoT Central application. You define the telemetry, state, properties, and commands for your device type.
+description: How to create a device template in your Azure IoT Central application. You define the telemetry, state, properties, and commands for your device type.
 author: dominicbetts
 ms.author: dobett
 ms.date: 03/01/2024
@@ -9,6 +9,8 @@ ms.service: iot-central
 services: iot-central
 ms.custom: device-developer
 # This article applies to solution builders and device developers.
+
+#customer intent: As an solution builders, I want define the device types that can connect to my application so that I can manage and monitor them effectively.
 ---
 
 # Define a new IoT device type in your Azure IoT Central application
@@ -36,7 +38,7 @@ To learn how to manage device templates by using the IoT Central REST API, see [
 You have several options to create device templates:
 
 - Design the device template in the IoT Central GUI.
-- Import a device template from the device catalog. Optionally, customize the device template to your requirements in IoT Central.
+- Import a device template from the list of featured device templates. Optionally, customize the device template to your requirements in IoT Central.
 - When the device connects to IoT Central, have it send the model ID of the model it implements. IoT Central uses the model ID to retrieve the model from the model repository and to create a device template. Add any cloud properties and views your IoT Central application needs to the device template.
 - When the device connects to IoT Central, let IoT Central [autogenerate a device template](#autogenerate-a-device-template) definition from the data the device sends.
 - Author a device model using the [Digital Twin Definition Language (DTDL) V2](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.v2.md) and [IoT Central DTDL extension](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.iotcentral.v2.md). Manually import the device model into your IoT Central application. Then add the cloud properties and views your IoT Central application needs.
@@ -45,15 +47,15 @@ You have several options to create device templates:
 > [!NOTE]
 > In each case, the device code must implement the capabilities defined in the model. The device code implementation isn't affected by the cloud properties and views sections of the device template.
 
-This section shows you how to import a device template from the catalog and how to customize it using the IoT Central GUI. This example uses the **ESP32-Azure IoT Kit** device template from the device catalog:
+This section shows you how to import a device template from the list of featured device templates and how to customize it using the IoT Central GUI. This example uses the **Onset Hobo MX-100 Temp Sensor** device template from the list of featured device templates:
 
 1. To add a new device template, select **+ New** on the **Device templates** page.
-1. On the **Select type** page, scroll down until you find the **ESP32-Azure IoT Kit** tile in the **Use a pre-configured device template** section.
-1. Select the **ESP32-Azure IoT Kit** tile, and then select **Next: Review**.
+1. On the **Select type** page, scroll down until you find the **Onset Hobo MX-100 Temp Sensor** tile in the **Featured device templates** section.
+1. Select the **Onset Hobo MX-100 Temp Sensor** tile, and then select **Next: Review**.
 1. On the **Review** page, select **Create**.
-The name of the template you created is **Sensor Controller**. The model includes components such as **Sensor Controller**, **SensorTemp**, and **Device Information interface**. Components define the capabilities of an ESP32 device. Capabilities include the telemetry, properties, and commands.
+The name of the template you created is **Hobo MX-100**. The model includes components such as **Hobo MX-100** and **IotDevice**. Components define the capabilities of a Hobo MX-100 device. Capabilities can include  telemetry, properties, and commands. This device only has telemetry capabilities.
 
-:::image type="content" source="media/howto-set-up-template/device-template.png" alt-text="Screenshot that shows a Sensor controller device template." lightbox="media/howto-set-up-template/device-template.png":::
+:::image type="content" source="media/howto-set-up-template/device-template.png" alt-text="Screenshot that shows a device template." lightbox="media/howto-set-up-template/device-template.png":::
 
 ## Autogenerate a device template
 
@@ -92,7 +94,7 @@ To create a device model, you can:
 
 - Use IoT Central to create a custom model from scratch.
 - Import a DTDL model from a JSON file. A device builder might use Visual Studio Code to author a device model for your application.
-- Select one of the devices from the device catalog. This option imports the device model that the manufacturer published for this device. A device model imported like this is automatically published.
+- Select one of the devices from the list of featured device templates. This option imports the device model that the manufacturer published for this device. A device model imported like this is automatically published.
 
 1. To view the model ID, select the root interface in the model and select **Edit identity**: