Skip to content

Commit fff9a9c

Browse files
Merge pull request #226150 from vimeht/main
Update device-update-plug-and-play.md
2 parents 1e070af + 47848f1 commit fff9a9c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/iot-hub-device-update/deploy-update.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ An Azure CLI environment:
7272
1. Schedule your deployment to start immediately or in the future.
7373

7474
> [!TIP]
75-
> By default, the **Start** date and time is 24 hours from your current time. Be sure to select a different date and time if you want the deployment to begin earlier.
75+
> By default, the **Start** date and time is set to Immediately. Be sure to select a different date and time if you want the deployment to begin later.
7676
7777
:::image type="content" source="media/deploy-update/create-deployment.png" alt-text="Screenshot that shows the Create deployment screen" lightbox="media/deploy-update/create-deployment.png":::
7878

articles/iot-hub-device-update/device-update-plug-and-play.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Understand how Device Update for IoT Hub uses IoT Plug and Play | Microso
33
description: Device Update for IoT Hub uses to discover and manage devices that are over-the-air update capable.
44
author: eshashah-msft
55
ms.author: eshashah
6-
ms.date: 1/26/2022
6+
ms.date: 2/2/2023
77
ms.topic: conceptual
88
ms.service: iot-hub-device-update
99
---
@@ -43,7 +43,7 @@ The Device Update agent uses agent metadata fields to send information to Device
4343
|resultDetails|string|device to cloud|Customer-defined free form string to provide additional result details. Returned to the twin without parsing||
4444
|stepResults|map|device to cloud|The result reported by the agent containing result code, extended result code, and result details for step updates. | "step_1": { "resultCode": 0,"extendedResultCode": 0, "resultDetails": ""}|
4545
|state|integer|device to cloud| An integer that indicates the current state of the Device Update agent. | See [State](#state) section for details. |
46-
|workflow|complex|device to cloud| A set of values that indicate which deployment the agent is currently working on, ID of current deployment, and acknowledgment of any retry request sent from service to agent.|"workflow": {"action": 3,"ID": "11b6a7c3-6956-4b33-b5a9-87fdd79d2f01","retryTimestamp": "2022-01-26T11:33:29.9680598Z"}|
46+
|workflow|complex|device to cloud| A set of values that indicate which deployment the agent is currently working on, ID of current deployment, and acknowledgment of any retry request sent from service to agent. Note that the workflow ID reports a "nodeployment" value once the deployment is cancelled. |"workflow": {"action": 3,"ID": "11b6a7c3-6956-4b33-b5a9-87fdd79d2f01","retryTimestamp": "2022-01-26T11:33:29.9680598Z"}|
4747
|installedUpdateId|string|device to cloud|An ID of the update that is currently installed (through Device Update). This value is a string capturing the Update ID JSON or null for a device that has never taken an update through Device Update.|installedUpdateID{\"provider\":\"contoso\",\"name\":\"image-update\",\"version\":\"1.0.0\"}"|
4848

4949
#### Device properties

0 commit comments

Comments
 (0)