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-hub-device-update/device-update-agent-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ The [Device Update core interface](https://github.com/Azure/iot-plugandplay-mode
36
36
37
37
### Device information interface
38
38
39
-
The [device information interface](https://github.com/Azure/iot-plugandplay-models/blob/main/dtmi/azure/devicemanagement/deviceinformation-1.json) implements the Azure IoT `DeviceInformation` interface.
39
+
The [device information interface](https://github.com/Azure/iot-plugandplay-models/blob/main/dtmi/azure/devicemanagement/deviceinformation-1.json) implements the Azure IoT Plug and Play (PnP) `DeviceInformation` interface.
Copy file name to clipboardExpand all lines: articles/iot-hub-device-update/device-update-agent-provisioning.md
+46-29Lines changed: 46 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ The Device Update module agent can run along with other system processes and [Io
20
20
21
21
You can create up to 50 module identities under each Azure IoT Hub device identity. Each module identity implicitly generates a module identity twin. On the device side, you can use the IoT Hub device SDKs to create modules that each open an independent connection to IoT Hub.
22
22
23
-
module identity and module identity twin provide similar capabilities to device identity and device twin, but at a finer granularity. For more information, see [Understand and use module twins in IoT Hub](../iot-hub/iot-hub-devguide-module-twins.md).
23
+
Module identity and module identity twin provide similar capabilities to device identity and device twin, but at a finer granularity. For more information, see [Understand and use module twins in IoT Hub](../iot-hub/iot-hub-devguide-module-twins.md).
24
24
25
25
When you provision the Device Update agent as a module identity, all [communications](device-update-plug-and-play.md) between the device and the Device Update service must happen over the Module Twin. Remember to tag the Module Twin of the device when you create [device groups](device-update-groups.md). If you migrate from a device-level agent to adding the agent as a module identity, remove the older agent that communicated over the device twin.
26
26
@@ -37,9 +37,11 @@ Device Update supports the following IoT device over the air update types:
37
37
38
38
## Prepare for package updates
39
39
40
-
To prepare an IoT device or IoT Edge device to install [package based updates](./understand-device-update.md#support-for-a-wide-range-of-update-artifacts), add `packages.microsoft.com` to your machine's repositories by following these steps:
40
+
To set up an IoT device or IoT Edge device to install [package based updates](./understand-device-update.md#support-for-a-wide-range-of-update-artifacts), add `packages.microsoft.com` to your machine's repositories by following these steps:
41
41
42
-
1. In a Terminal window on the machine or IoT device where you want to install the Device Update agent, install the repository configuration that matches your device's operating system, for example:
42
+
1. Open a Terminal window on the machine or IoT device where you want to install the Device Update agent.
43
+
44
+
1. Install the repository configuration that matches your device's operating system, for example:
@@ -61,52 +63,67 @@ To prepare an IoT device or IoT Edge device to install [package based updates](.
61
63
sudo cp ./microsoft.gpg /etc/apt/trusted.gpg.d/
62
64
```
63
65
64
-
Update package lists on your device by running `sudo apt-get update`.
66
+
## Provision the Device Update agent
65
67
66
-
<aname="on-iot-edge-enabled-devices"></a>
67
-
## Install and provision the agent
68
+
You can provision the Device Update agent as a module identity on IoT Edge enabled devices or non-IoT Edge IoT devices. To check if you have IoT Edge enabled on your device, see [View registered devices and retrieve provisioning information](../iot-edge/how-to-provision-single-device-linux-symmetric.md?preserve-view=true&view=iotedge-2020-11#view-registered-devices-and-retrieve-provisioning-information).
68
69
69
-
You can download and unzip sample images from the **Assets** section on the [Releases](https://github.com/Azure/iot-hub-device-update/releases) page. In *Tutorial_RaspberryPi3.zip*, the *swUpdate* file is the base image that you can flash onto a Raspberry Pi B3+ board. The *.gz* file is the update you import through Device Update. For more information, see [Azure Device Update for IoT Hub using a Raspberry Pi image](./device-update-raspberry-pi.md#use-bmaptool-to-flash-the-sd-card).
70
+
You can download and unzip sample images from the **Assets** section on the [Releases](https://github.com/Azure/iot-hub-device-update/releases) page. In *Tutorial_RaspberryPi3.zip*, the *swUpdate* file is the base image that you can flash onto a Raspberry Pi B3+ board. The *.gz* file is the update you can import through Device Update. For more information, see [Azure Device Update for IoT Hub using a Raspberry Pi image](./device-update-raspberry-pi.md#use-bmaptool-to-flash-the-sd-card).
70
71
71
-
- For release candidate (rc) agent versions, download the *.deb* file from [Releases](https://github.com/Azure/iot-hub-device-update/releases) to the machine you want to install the Device Update agent on, and then run the following command:
72
+
### On IoT Edge enabled devices
72
73
73
-
```shell
74
-
sudo apt-get install -y ./"<PATH TO FILE>"/"<.DEB FILE NAME>"
75
-
```
74
+
Follow these instructions to provision the Device Update agent on [IoT Edge enabled devices](../iot-edge/index.yml):
76
75
77
-
- If you're setting up a [Microsoft Connected Cache (MCC) for a disconnected device scenario](connected-cache-disconnected-device-update.md), install the Delivery Optimization APT plugin as follows:
76
+
1. Follow the instructions at [Manually provision a single Linux IoT Edge device](../iot-edge/how-to-provision-single-device-linux-symmetric.md?preserve-view=true&view=iotedge-2020-11#install-iot-edge).
1. Install the Device Update package update agent.
84
81
85
-
You can provision the Device Update agent as a module identity on IoT Edge enabled devices or non-IoT Edge IoT devices. To check if you have IoT Edge enabled on your device, see [View registered devices and retrieve provisioning information](../iot-edge/how-to-provision-single-device-linux-symmetric.md?preserve-view=true&view=iotedge-2020-11#view-registered-devices-and-retrieve-provisioning-information).
82
+
- For latest agent versions from packages.microsoft.com, update package lists on your device and install the Device Update agent package and its dependencies using:
86
83
87
-
- For an [IoT Edge enabled device](../iot-edge/index.yml), follow the instructions at [Manually provision a single Linux IoT Edge device](../iot-edge/how-to-provision-single-device-linux-symmetric.md?preserve-view=true&view=iotedge-2020-11#install-iot-edge).
84
+
```shell
85
+
86
+
sudo apt-get update
87
+
```
88
88
89
-
- For a non-IoT Edge enabled device:
90
-
1. Install the latest version of the IoT Identity Service by following instructions in [Installing the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/installation.html#install-from-packagesmicrosoftcom).
91
-
1. Configure the IoT Identity Service by following the instructions in [Configuring the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/configuration.html).
89
+
```shell
90
+
91
+
sudo apt-get install deviceupdate-agent
92
+
```
92
93
93
-
### Install and configure the Device Update agent
94
+
- For release candidate (rc) agent versions, download the *.deb* file from [Releases](https://github.com/Azure/iot-hub-device-update/releases) to the machine you want to install the Device Update agent on, and then run the following command:
94
95
95
-
1. Install the Device Update image update agent by running the following command:
96
+
```shell
97
+
sudo apt-get install -y ./"<PATH TO FILE>"/"<.DEB FILE NAME>"
98
+
```
96
99
97
-
```shell
98
-
sudo apt-get install deviceupdate-agent
99
-
```
100
+
- If you're setting up a [Microsoft Connected Cache (MCC) for a disconnected device scenario](connected-cache-disconnected-device-update.md), install the Delivery Optimization APT plugin as follows:
Follow these instructions to provision the Device Update agent on Linux IoT devices without IoT Edge installed.
109
+
110
+
1. Install the latest version of the IoT Identity Service by following instructions in [Installing the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/installation.html#install-from-packagesmicrosoftcom).
111
+
112
+
1. Configure the IoT Identity Service by following the instructions in [Configuring the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/configuration.html).
113
+
114
+
1. Install the Device Update agent.
115
+
116
+
## Configure the Device Update agent
100
117
101
-
1.After you install the device update agent, edit the Device Update configuration file by running the following command.
118
+
After you install the device update agent, edit the Device Update configuration file by running the following command.
102
119
103
120
```shell
104
121
sudo nano /etc/adu/du-config.json
105
122
```
106
123
107
-
1.In the *du-config.json* file, set all values that have a `Place value here` placeholder. For agents that use the IoT Identity Service for provisioning, change the `connectionType` to `AIS`, and set the `ConnectionData` field to an empty string. For an example, see [Example "du-config.json" file contents](./device-update-configuration-file.md#example-du-configjson-file-contents).
124
+
In the *du-config.json* file, set all values that have a `Place value here` placeholder. For agents that use the IoT Identity Service for provisioning, change the `connectionType` to `AIS`, and set the `ConnectionData` field to an empty string. For an example, see [Example "du-config.json" file contents](./device-update-configuration-file.md#example-du-configjson-file-contents).
108
125
109
-
### Other IoT devices
126
+
### Use a connection string
110
127
111
128
For testing or on constrained devices, you can also configure the Device Update agent without using the IoT Identity service. You can use a connection string to provision the Device Update agent from the module or device.
0 commit comments