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-pnp/concepts-developer-guide.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
@@ -177,26 +177,26 @@ result = DigitalTwin_DeviceClient_RegisterInterfacesAsync(
177
177
178
178
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.
179
179
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.
181
181
182
182
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.
183
183
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:
185
185
186
186
```REST
187
187
GET /digitalTwins/t-123/interfaces
188
188
```
189
189
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:
191
191
192
192
```REST
193
193
GET /digitalTwins/{device-id}/interfaces
194
194
```
195
195
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:
197
197
198
198
```REST
199
-
GET /digitalTwins/t-123/interfaces/info
199
+
GET /digitalTwins/t-123/interfaces/deviceInformation
200
200
```
201
201
202
202
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