Skip to content

Commit 718a864

Browse files
authored
adding modelID format for non_PnP devices
adding modelID format for non_PnP devices
1 parent 50ba02a commit 718a864

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

articles/iot-central/core/concepts-get-connected.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -175,15 +175,20 @@ IoT Central supports the following attestation mechanisms for individual enrollm
175175
176176
- **Trusted Platform Module (TPM) attestation:** A [TPM](https://docs.microsoft.com/azure/iot-dps/concepts-tpm-attestation) is a type of hardware security module. Using a TPM is one of the most secure ways to connect a device. This article assumes you're using a discrete, firmware, or integrated TPM. Software emulated TPMs are well suited for prototyping or testing, but they don't provide the same level of security as discrete, firmware, or integrated TPMs. Don't use software TPMs in production. To create an individual enrollment that uses a TPM, open the **Device Connection** page, select **Individual enrollment** as the connection method, and **TPM** as the mechanism. Enter the TPM endorsement key and save the device connection information.
177177
178-
## Connect devices with IoT Plug and Play (preview)
179-
180-
One of the key features of IoT Plug and Play (preview) with IoT Central is the ability to associate device templates automatically on device connection. Along with device credentials, devices can now send the **CapabilityModelId** as part of the device registration call. This capability enables IoT Central to discover and associate the device template with the device. The discovery process works as follows:
178+
## Automatically associate a device template
181179
180+
One of the key features of IoT Central is the ability to associate device templates automatically on device connection. Along with device credentials, devices can send the **CapabilityModelId**( URN for the capability model) as part of the device registration call. This capability enables IoT Central to discover and associate the device template with the device. The discovery process works as follows:
182181
1. Associates with the device template if it's already published in the IoT Central application.
183-
1. Fetches from the public repository of published and certified capability models.
182+
1. For Pre-Certified Plug and Play devices, if the device template is not already published in IoT Central the template is fetched from the public repository.
183+
184+
Below is the format of the additional payload the device would send during the DPS registration call.
184185
185-
Below is the format of the additional payload the device would send during the DPS registration call
186+
This is the format for devices using non PnP device SDK
187+
```javascript
188+
iotcModelId: '< this is the URN for the capability model>';
189+
```
186190

191+
This is the format for devices using Public Preview PnP device SDK
187192
```javascript
188193
'__iot:interfaces': {
189194
CapabilityModelId: <this is the URN for the capability model>

0 commit comments

Comments
 (0)