Skip to content

Commit 7518a9d

Browse files
committed
Add clarifications to PnP developer guide
1 parent a6fd785 commit 7518a9d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/iot-pnp/concepts-developer-guide.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -177,26 +177,26 @@ result = DigitalTwin_DeviceClient_RegisterInterfacesAsync(
177177

178178
IoT Plug and Play lets you use devices that have registered their capabilities with your IoT hub. For example, you can access the properties and commands of a device directly.
179179

180-
To use an IoT Plug and Play device that's connected to your IoT hub, use either the IoT Hub REST API or one of the IoT language SDKs. The following examples use the IoT Hub REST API.
180+
To use an IoT Plug and Play device that's connected to your IoT hub, use either the IoT Hub REST API or one of the IoT language SDKs. The following examples use the IoT Hub REST API. The current version of the API is `2019-07-01-preview`. Append `?api-version=2019-07-01-preview` to your REST PI calls.
181181

182182
To get the value of a device property, such as the firmware version (`fwVersion`) in the `DeviceInformation` interface in the thermostat, you use the digital twins REST API.
183183

184-
If your thermostat device is called `t-123`, you get the all the properties implemented by your device with a REST API GET call:
184+
If your thermostat device is called `t-123`, you get the all the properties on all the interfaces implemented by your device with a REST API GET call:
185185

186186
```REST
187187
GET /digitalTwins/t-123/interfaces
188188
```
189189

190-
More generally, all properties are accessed with this REST API template where `{device-id}` is the identifier for the device:
190+
More generally, all properties on all interfaces are accessed with this REST API template where `{device-id}` is the identifier for the device:
191191

192192
```REST
193193
GET /digitalTwins/{device-id}/interfaces
194194
```
195195

196-
If you know the name of the interface and want to get properties for that specific interface, scope the request to a specific interface by name:
196+
If you know the name of the interface, such as `deviceInformation`, and want to get properties for that specific interface, scope the request to a specific interface by name:
197197

198198
```REST
199-
GET /digitalTwins/t-123/interfaces/info
199+
GET /digitalTwins/t-123/interfaces/deviceInformation
200200
```
201201

202202
More generally, properties for a specific interface can be accessed through this REST API template where `device-id` is the identifier for the device and `{interface-name}` is the name of the interface:

0 commit comments

Comments
 (0)