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
[Azure Logic Apps](../logic-apps/index.yml) can help you orchestrate workflows across on-premises and cloud services, multiple enterprises, and various protocols. A logic app begins with a trigger, which is then followed by one or more actions that can be sequenced using built-in controls, such as conditions and iterators. This flexibility makes Logic Apps an ideal IoT solution for IoT monitoring scenarios. For example, the arrival of telemetry data from a device at an IoT Hub endpoint can initiate logic app workflows to warehouse the data in an Azure Storage blob, send email alerts to warn of data anomalies, schedule a technician visit if a device reports a failure, and so on.
19
+
[Azure Logic Apps](../logic-apps/index.yml) can help you orchestrate workflows across on-premises and cloud services, multiple enterprises, and various protocols. A logic app begins with a trigger, which is then followed by one or more actions that can be sequenced using built-in controls, such as conditions and iterators. This flexibility makes Logic Apps an ideal IoT solution for IoT monitoring scenarios. For example, the arrival of data from a device at an IoT Hub endpoint can initiate logic app workflows to warehouse the data in an Azure Storage blob, send email alerts to warn of data anomalies, schedule a technician visit if a device reports a failure, and so on.
20
20
21
21
In this tutorial, you perform the following tasks:
22
22
@@ -99,25 +99,9 @@ Create a Service Bus namespace and queue. Later in this article, you create a ro
99
99
100
100
1. Copy the value of **Primary connection string** and save it to use later in this tutorial when you configure the logic app.
101
101
102
-
<!-- 1. Back on the **Service Bus Namespace** pane, select **Queues** from the **Entities** section of the resource menu. Then, select the queue that you just created from the list
103
-
104
-
:::image type="content" source="./media/iot-hub-monitoring-notifications-with-azure-logic-apps/queues-select-queue.png" alt-text="Screenshot that shows the list of queues in your namespace.":::
105
-
106
-
1. On the **Service Bus Queue** pane, select **Shared access policies** from the **Settings** section of the resource menu. Then, select **Add** to add a policy.
107
-
108
-
:::image type="content" source="./media/iot-hub-monitoring-notifications-with-azure-logic-apps/queue-shared-access-policies-add.png" alt-text="Screenshot that shows adding a shared access policy to a Service Bus queue.":::
109
-
110
-
1. In the **Policy name** field, provide a name for the policy. Check **Manage**, and then select **Create**.
111
-
112
-
:::image type="content" source="./media/iot-hub-monitoring-notifications-with-azure-logic-apps/add-sas-policy.png" alt-text="Screenshot that shows creating a shared access policy.":::
113
-
114
-
1. After your policy is created, select it from the list of policies to open the details.
115
-
116
-
1. Copy the value of the **Primary connection string** and save it to use later in this tutorial when you configure the logic app. -->
117
-
118
102
## Add a custom endpoint and routing rule to your IoT hub
119
103
120
-
Add a custom endpoint for the Service Bus queue to your IoT hub. Then, create a message routing rule to direct messages that contain a temperature alert to that endpoint, where they will be picked up by your logic app. The routing rule uses a routing query, `temperatureAlert = "true"`, to forward messages based on the value of the `temperatureAlert` application property set by the client code running on the device. To learn more, see [Message routing query based on message properties](./iot-hub-devguide-routing-query-syntax.md#query-based-on-message-properties).
104
+
Add a custom endpoint for the Service Bus queue to your IoT hub. Then, create a message routing rule to direct messages that contain a temperature alert to that endpoint, where they're picked up by your logic app. The routing rule uses a routing query, `temperatureAlert = "true"`, to forward messages based on the value of the `temperatureAlert` application property set by the client code running on the device. To learn more, see [Message routing query based on message properties](./iot-hub-devguide-routing-query-syntax.md#query-based-on-message-properties).
121
105
122
106
### Add a custom endpoint and route
123
107
@@ -167,7 +151,7 @@ In the preceding section, you set up your IoT hub to route messages containing a
167
151
| Parameter | Value |
168
152
| --------- | ----- |
169
153
|**Resource group**| Select the same resource group that contains your IoT hub. |
170
-
|**Name**| Provide a name for your the logic app. |
154
+
|**Name**| Provide a name for your logic app. |
171
155
|**Region**| Select a location close to you. |
172
156
|**Plan type**| Select **Consumption**, which is sufficient for this tutorial. |
173
157
@@ -256,7 +240,7 @@ In the preceding section, you set up your IoT hub to route messages containing a
256
240
|**Subject**|`High temperature detected`. |
257
241
|**Body**|`High temperature detected`. |
258
242
259
-
If the **Add dynamic content** dialog opens, select **Hide** to close it. You do not use dynamic content in this tutorial.
243
+
If the **Add dynamic content** dialog opens, select **Hide** to close it. You don't use dynamic content in this tutorial.
260
244
261
245
262
246
@@ -270,7 +254,7 @@ In the preceding section, you set up your IoT hub to route messages containing a
270
254
271
255
1. On the **smtp API Connection** pane, under **General**, select **Edit API connection**.
272
256
273
-
1. On the **Edit API Connection** pane, select **Enable SSL?**, re-enter the password for your email account, and select **Save**.
257
+
1. On the **Edit API Connection** pane, select **Enable SSL?**, reenter the password for your email account, and select **Save**.
274
258
275
259
276
260
@@ -289,17 +273,17 @@ Start sending temperature messages from your IoT device to test the monitoring a
289
273
290
274
## Clean up resources
291
275
292
-
If you don't need the resources that you created in this tutorial any longer, delete it and the resource group in the portal. To do so, select the **tutorial-iot-hub-rg**resource group that contains your IoT hub and select **Delete**.
276
+
If you don't need the resources that you created in this tutorial any longer, delete it and the resource group in the portal. To do so, select the resource group that contains your IoT hub and select **Delete**.
293
277
294
278
Alternatively, use the CLI:
295
279
296
280
```azurecli-interactive
297
281
# Delete your resource group and its contents
298
-
az group delete --name tutorial-iot-hub-rg
282
+
az group delete --name <RESOURCE_GROUP_NAME>
299
283
```
300
284
301
285
## Next steps
302
286
303
-
You have successfully created a logic app that connects your IoT hub and your mailbox for temperature monitoring and notifications.
287
+
In this tutorial, you created a logic app that connects your IoT hub and your mailbox for temperature monitoring and notifications.
Copy file name to clipboardExpand all lines: articles/iot-hub/iot-hub-raspberry-pi-kit-node-get-started.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,7 @@ Prepare the microSD card for installation of the Raspberry Pi OS image.
100
100
101
101
c. Select the microSD card drive. Etcher may have already selected the correct drive.
102
102
103
-
d. Click Flash to install Raspberry Pi OS with desktop to the microSD card.
103
+
d. Select Flash to install Raspberry Pi OS with desktop to the microSD card.
104
104
105
105
e. Remove the microSD card from your computer when installation is complete. It's safe to remove the microSD card directly because Etcher automatically ejects or unmounts the microSD card upon completion.
106
106
@@ -112,16 +112,16 @@ Prepare the microSD card for installation of the Raspberry Pi OS image.
112
112
113
113
2. Start Pi and then sign into Raspberry Pi OS by using `pi` as the user name and `raspberry` as the password.
114
114
115
-
3.Click the Raspberry icon > **Preferences** > **Raspberry Pi Configuration**.
115
+
3.Select the Raspberry icon > **Preferences** > **Raspberry Pi Configuration**.
116
116
117
117
118
118
119
-
4. On the **Interfaces** tab, set **SSH** and **I2C** to **Enable**, and then click**OK**.
119
+
4. On the **Interfaces** tab, set **SSH** and **I2C** to **Enable**, and then select**OK**.
120
120
121
121
| Interface | Description |
122
122
| --------- | ----------- |
123
123
|*SSH*| Secure Shell (SSH) is used to remote into the Raspberry Pi with a remote command-line. This is the preferred method for issuing the commands to your Raspberry Pi remotely in this document. |
124
-
|*I2C*| Inter-integrated Circuit (I2C) is a communications protocol used to interface with hardware such as sensors. This interface is required for interfacing with physical sensors in this topic.|
124
+
|*I2C*| Inter-integrated Circuit (I2C) is a communications protocol used to interface with hardware such as sensors. This interface is required for interfacing with physical sensors in this article.|
125
125
126
126
If you don't have physical sensors and want to use simulated sensor data from your Raspberry Pi device, you can leave **I2C** disabled.
127
127
@@ -142,14 +142,14 @@ For sensor pins, use the following wiring:
142
142
143
143
| Start (Sensor & LED) | End (Board) | Cable Color |
@@ -255,14 +255,14 @@ For more ways to process data sent by your device, continue on to the next secti
255
255
256
256
## Clean up resources
257
257
258
-
You can use the resources created in this topic with other tutorials and quickstarts in this document set. If you plan to continue on to work with other quickstarts or with the tutorials, do not clean up the resources created in this topic. If you do not plan to continue, use the following steps to delete all resources created by this topic in the Azure portal.
258
+
You can use the resources created in this article with other tutorials and quickstarts in this document set. If you plan to continue on to work with other quickstarts or with the tutorials, don't clean up the resources created in this article. If you don't plan to continue, use the following steps to delete all resources created by this article in the Azure portal.
259
259
260
260
1. From the left-hand menu in the Azure portal, select **All resources** and then select the IoT Hub you created.
261
-
1. At the top of the IoT Hub overview pane, click**Delete**.
262
-
1. Enter your hub name and click**Delete** again to confirm permanently deleting the IoT hub.
261
+
1. At the top of the IoT Hub overview pane, select**Delete**.
262
+
1. Enter your hub name and select**Delete** again to confirm permanently deleting the IoT hub.
263
263
264
264
## Next steps
265
265
266
-
You've run a sample application to collect sensor data and send it to your IoT hub.
266
+
In this article, you ran a sample application to collect sensor data and send it to your IoT hub.
0 commit comments