Skip to content

Commit f3bd40f

Browse files
committed
Remove plug and play bridge
1 parent 3c417cd commit f3bd40f

6 files changed

Lines changed: 8 additions & 158 deletions

File tree

articles/iot-develop/.openpublishing.redirection.iot-develop.json

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -332,8 +332,13 @@
332332
},
333333
{
334334
"source_path_from_root": "/articles/iot-pnp/concepts-iot-pnp-bridge.md",
335-
"redirect_url": "/azure/iot-develop/concepts-iot-pnp-bridge",
336-
"redirect_document_id": true
335+
"redirect_url": "/azure/iot-develop/overview-iot-plug-and-play",
336+
"redirect_document_id": false
337+
},
338+
{
339+
"source_path_from_root": "/articles/iot-develop/concepts-iot-pnp-bridge.md",
340+
"redirect_url": "/azure/iot-develop/overview-iot-plug-and-play",
341+
"redirect_document_id": false
337342
},
338343
{
339344
"source_path_from_root": "/articles/iot-pnp/concepts-model-discovery.md",

articles/iot-develop/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,8 +91,6 @@
9191
href: concepts-developer-guide-service.md
9292
- name: Digital twins
9393
href: concepts-digital-twin.md
94-
- name: IoT Plug and Play bridge
95-
href: concepts-iot-pnp-bridge.md
9694
- name: Security
9795
items:
9896
- name: Guidelines for secured embedded development

articles/iot-develop/concepts-iot-pnp-bridge.md

Lines changed: 0 additions & 151 deletions
This file was deleted.
Binary file not shown.
Binary file not shown.

articles/iot-develop/overview-iot-plug-and-play.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,6 @@ The web UI in IoT Central lets you monitor device conditions, create rules, and
4747

4848
IoT Hub - a managed cloud service - acts as a message hub for secure, bi-directional communication between your IoT application and your devices. When you connect an IoT Plug and Play device to an IoT hub, you can use the [Azure IoT explorer](../iot/howto-use-iot-explorer.md) tool to view the telemetry, properties, and commands defined in the DTDL model.
4949

50-
If you have existing sensors attached to a Windows or Linux gateway, you can use [IoT Plug and Play bridge](./concepts-iot-pnp-bridge.md), to connect these sensors and create IoT Plug and Play devices without the need to write device software/firmware (for [supported protocols](./concepts-iot-pnp-bridge.md#supported-protocols-and-sensors)).
51-
5250
To learn more, see [IoT Plug and Play architecture](concepts-architecture.md)
5351

5452
## Develop an IoT device application
@@ -57,7 +55,7 @@ As a device builder, you can develop an IoT hardware product that supports IoT P
5755

5856
1. Define the device model. You author a set of JSON files that define your device's capabilities using the [DTDL](https://github.com/Azure/opendigitaltwins-dtdl). A model describes a complete entity such as a physical product, and defines the set of interfaces implemented by that entity. Interfaces are shared contracts that uniquely identify the telemetry, properties, and commands supported by a device. You can reuse interfaces across different models.
5957

60-
1. Implement your device software or firmware such that your telemetry, properties, and commands follow the [IoT Plug and Play conventions](concepts-convention.md). If you're connecting existing sensors attached to a Windows or Linux gateway, the [IoT Plug and Play bridge](./concepts-iot-pnp-bridge.md) can simplify this step.
58+
1. Implement your device software or firmware such that your telemetry, properties, and commands follow the [IoT Plug and Play conventions](concepts-convention.md).
6159

6260
1. Ensure the device announces the model ID as part of the MQTT connection. The Azure IoT SDKs include constructs to provide the model ID at connection time.
6361

0 commit comments

Comments
 (0)