You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: timlt
6
6
ms.service: iot
7
7
ms.devlang: c
8
8
ms.topic: tutorial
9
-
ms.date: 04/04/2024
9
+
ms.date: 06/11/2024
10
10
#Customer intent: As a device builder, I want to see a working IoT device sample using FreeRTOS to connect to Azure IoT Hub. The device should be able to send telemetry and respond to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
11
11
---
12
12
@@ -67,7 +67,7 @@ To connect the ESP32 DevKit to Azure, you modify configuration settings, build t
67
67
68
68
### Set up the environment
69
69
To launch the ESP-IDF environment:
70
-
1. Select Windows **Start**, find **ESP-IDF 5.0 CMD** and run it.
70
+
1. Select Windows **Start**, find **ESP-IDF 5.0 CMD**, and run it.
71
71
1. In **ESP-IDF 5.0 CMD**, navigate to the *iot-middleware-freertos-samples* directory that you cloned previously.
72
72
1. Navigate to the ESP32-Azure IoT Kit project directory *demos\projects\ESPRESSIF\aziotkit*.
73
73
1. Run the following command to launch the configuration menu:
@@ -211,7 +211,7 @@ To view and edit device properties using Azure IoT Explorer:
211
211
212
212
To use Azure CLI to view device properties:
213
213
214
-
1. In your CLI console, run the [az iot hub device-twin show](/cli/azure/iot/hub/device-twin#az-iot-hub-device-twin-show) command.
214
+
1. Run the [az iot hub device-twin show](/cli/azure/iot/hub/device-twin#az-iot-hub-device-twin-show) command.
215
215
216
216
```azurecli
217
217
az iot hub device-twin show --device-id mydevice --hub-name {YourIoTHubName}
@@ -267,17 +267,17 @@ To use Azure CLI to view device telemetry:
267
267
268
268
## Call a direct method on the device
269
269
270
-
You can also use Azure IoT Explorer to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
270
+
You can also use Azure IoT Explorer to call a direct method that you implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
271
271
272
272
To call a method in Azure IoT Explorer:
273
273
274
274
1. From the **IoT Plug and Play components** (Default Component) pane foryour devicein IoT Explorer, selectthe**Commands** tab.
275
-
1. For the **ToggleLed1** command, select **Send command**. The LED on the ESP32 DevKit toggles on or off. You should also see a notification in IoT Explorer.
275
+
1. For the **ToggleLed1** command, select**Send command**. The LED on the ESP32 DevKit toggles on or off. You should also see a notification in IoT Explorer.
276
276
277
277
:::image type="content" source="media/tutorial-devkit-espressif-esp32-iot-hub/iot-explorer-invoke-method.png" alt-text="Screenshot of calling a method in IoT Explorer.":::
278
278
279
279
1. For the **DisplayText** command, enter some text in the **content** field.
280
-
1. Select **Send command**. The text displays on the ESP32 DevKit screen.
280
+
1. Select **Send command**. The text displays on the ESP32 DevKit screen.
Copy file name to clipboardExpand all lines: articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: timlt
6
6
ms.service: iot
7
7
ms.devlang: c
8
8
ms.topic: tutorial
9
-
ms.date: 04/08/2024
9
+
ms.date: 06/11/2024
10
10
ms.custom: devx-track-azurecli
11
11
12
12
#Customer intent: As a device builder, I want to see a working IoT device sample connecting to IoT Hub and sending properties and telemetry, and responding to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
@@ -66,11 +66,11 @@ resources
66
66
67
67
To install the tools:
68
68
69
-
1.From File Explorer, navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
69
+
1.Navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
70
70
71
71
*getting-started\tools\get-toolchain.bat*
72
72
73
-
1.After the installation, open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
73
+
1.Open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
74
74
1. Run the following code to confirm that CMake version 3.14 or later is installed.
75
75
76
76
```shell
@@ -295,7 +295,7 @@ To use Azure CLI to view device telemetry:
295
295
296
296
## Call a direct method on the device
297
297
298
-
You can also use Azure IoT Explorer to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
298
+
You can also use Azure IoT Explorer to call a direct method that you implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
Copy file name to clipboardExpand all lines: articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: timlt
6
6
ms.service: iot
7
7
ms.devlang: c
8
8
ms.topic: tutorial
9
-
ms.date: 04/08/2024
9
+
ms.date: 06/11/2024
10
10
11
11
#Customer intent: As a device builder, I want to see a working IoT device sample connecting to IoT Hub and sending properties and telemetry, and responding to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
12
12
---
@@ -64,11 +64,11 @@ The cloned repo contains a setup script that installs and configures the require
64
64
65
65
To install the tools:
66
66
67
-
1.From File Explorer, navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
67
+
1.Navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
68
68
69
69
*getting-started\tools\get-toolchain.bat*
70
70
71
-
1.After the installation, open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
71
+
1.Open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
72
72
1. Run the following code to confirm that CMake version 3.14 or later is installed.
73
73
74
74
```shell
@@ -136,7 +136,7 @@ To connect the STM DevKit to Azure, you modify a configuration file for Wi-Fi an
136
136
137
137
1. Copy the binary file named *stm32l475_azure_iot.bin*.
138
138
139
-
1. In File Explorer, find the STM Devkit that's connected to your computer. The device appears as a drive on your system with the drive label **DIS_L4IOT**.
139
+
1. In File Explorer, find the STM Devkit connected to your computer. The device appears as a drive on your system with the drive label **DIS_L4IOT**.
140
140
141
141
1. Paste the binary file into the root folder of the STM Devkit. Flashing starts automatically and completes in a few seconds.
142
142
@@ -300,7 +300,7 @@ To use Azure CLI to view device telemetry:
300
300
301
301
## Call a direct method on the device
302
302
303
-
You can also use Azure IoT Explorer to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
303
+
You can also use Azure IoT Explorer to call a direct method that you implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
Copy file name to clipboardExpand all lines: includes/iot-develop-create-cloud-components.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ In the rest of this quickstart, you use IoT Explorer to register a device to you
57
57
58
58
To add a connection to your IoT hub:
59
59
60
-
1. Install [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases). This tool is a cross-platform utility to monitor and manage Azure IoT resources.
60
+
1. Install [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases). This tool is a cross-platform utility to monitor and manage Azure IoT resources.
61
61
62
62
1. In your CLI app, run the [az iot hub connection-string show](/cli/azure/iot/hub/connection-string#az-iot-hub-connection-string-show) command to get the connection string for your IoT hub.
63
63
@@ -78,12 +78,15 @@ If the connection succeeds, IoT Explorer switches to the **Devices** view.
78
78
To add the public model repository:
79
79
80
80
1. In IoT Explorer, select **Home** to return to the home view.
81
-
1. On the left menu, select **IoT Plug and Play Settings**, then select **+Add** and select **Public repository** from the drop-down menu.
82
-
1. An entry appears for the public model repository at `https://devicemodels.azure.com`.
81
+
1. On the left menu, select **IoT Plug and Play Settings**.
82
+
1. Confirm that there's an existing **Public Repository** entry with an endpoint of `https://devicemodels.azure.com`.
83
+
> [!NOTE]
84
+
> If there's not an entry the public repository, select **+Add**, select **Public repository** from the drop-down menu, specify the `https://devicemodels.azure.com` endpoint value, and then select **Save**.
85
+
86
+
The completed entry for the public repository looks like the following screenshot:
83
87
84
88
:::image type="content" source="media/iot-develop-create-cloud-components/iot-explorer-add-public-repository.png" alt-text="Screenshot of adding the public model repository in IoT Explorer.":::
0 commit comments