Skip to content

Commit fbee217

Browse files
committed
Removed old device twin versions
1 parent a36474d commit fbee217

File tree

4 files changed

+9
-24
lines changed

4 files changed

+9
-24
lines changed

articles/iot-hub/TOC.yml

Lines changed: 2 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -284,25 +284,8 @@
284284
displayName: file upload, upload files
285285
href: how-to-file-upload.md
286286
- name: Get started with device twins
287-
items:
288-
- name: New version
289-
displayName: New version
290-
href: how-to-device-twins.md
291-
- name: CLI
292-
displayName: device twins
293-
href: device-twins-cli.md
294-
- name: .NET
295-
displayName: device twins
296-
href: device-twins-dotnet.md
297-
- name: Python
298-
displayName: device twins
299-
href: device-twins-python.md
300-
- name: Node.js
301-
displayName: device twins
302-
href: device-twins-node.md
303-
- name: Java
304-
displayName: device twins
305-
href: device-twins-java.md
287+
displayName: device twins
288+
href: how-to-device-twins.md
306289
- name: Get started with module twins
307290
items:
308291
- name: Portal

articles/iot-hub/how-to-device-twins.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,8 @@ This article shows you how to develop two types of applications:
6060

6161
For more information about IoT Hub shared access policies and permissions, see [Access control and permissions](/azure/iot-hub/authenticate-authorize-sas).
6262

63+
* If an application uses the MQTT protocol, make sure that **port 8883** is open in your firewall. The MQTT protocol communicates over port 8883. This port may be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see [Connecting to IoT Hub (MQTT)](../iot/iot-mqtt-connect-to-iot-hub.md#connecting-to-iot-hub).
64+
6365
* Language SDK requirements:
6466
* **.NET SDK** - Requres Visual Studio.
6567
* **Python SDK** - [Python version 3.7 or later](https://www.python.org/downloads/) is recommended. Make sure to use the 32-bit or 64-bit installation as required by your setup. When prompted during the installation, make sure to add Python to your platform-specific environment variable.

includes/iot-hub-howto-device-twins-dotnet.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ _deviceClient = DeviceClient.CreateFromConnectionString(DeviceConnectionString,
6161

6262
### Retrieve a device twin and examine properties
6363

64-
Call [GetTwinAsync](/dotnet/api/microsoft.azure.devices.client.deviceclient.gettwinasync?#microsoft-azure-devices-client-deviceclient-gettwinasync) to retrieve the current device twin properties. There are many [Twin](/dotnet/api/microsoft.azure.devices.shared.twin?) object [properties](/dotnet/api/microsoft.azure.devices.shared.twin?&branch=main#properties) that you can use to access specific areas of the Twin JSON data including Twin `Properties`, `Status`, `Tags`, and `Version`.
64+
Call [GetTwinAsync](/dotnet/api/microsoft.azure.devices.client.deviceclient.gettwinasync?#microsoft-azure-devices-client-deviceclient-gettwinasync) to retrieve the current device twin properties. There are many [Twin](/dotnet/api/microsoft.azure.devices.shared.twin?) object [properties](/dotnet/api/microsoft.azure.devices.shared.twin?&#properties) that you can use to access specific areas of the `Twin` JSON data including `Properties`, `Status`, `Tags`, and `Version`.
6565

6666
This example retrieves device twin properties and prints the twin values in JSON format.
6767

@@ -178,7 +178,7 @@ After making twin field updates, call [UpdateTwinAsync](/dotnet/api/microsoft.az
178178

179179
Use the device twin [Tags](/dotnet/api/microsoft.azure.devices.shared.twin.tags?#microsoft-azure-devices-shared-twin-tags) property to read and write device tag information.
180180

181-
##### Update using a Twin object
181+
##### Update tags using a twin object
182182

183183
This example creates a `location` tag patch, assigns it to the `Twin` object using the `Tags` property, and then applies the patch using `UpdateTwinAsync`.
184184

includes/iot-hub-howto-device-twins-node.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.custom: mqtt, devx-track-js
1313

1414
## Overview
1515

16-
This article describes how to use the [Azure IoT SDK for JavaScript](https://github.com/Azure/azure-iot-sdk-node) to create device and backend service application code for device twins.
16+
This article describes how to use the [Azure IoT SDK for Node.js](https://github.com/Azure/azure-iot-sdk-node) to create device and backend service application code for device twins.
1717

1818
## Create a device application
1919

@@ -55,7 +55,7 @@ npm install azure-iot-device-mqtt --save
5555

5656
For more information about the differences between MQTT, AMQP, and HTTPS support, see [Cloud-to-device communications guidance](../articles/iot-hub/iot-hub-devguide-c2d-guidance.md) and [Choose a communication protocol](../articles/iot-hub/iot-hub-devguide-protocols.md).
5757

58-
### Create a Client module
58+
### Create a client module
5959

6060
Create a `Client` module using the installed package.
6161

@@ -65,7 +65,7 @@ For example:
6565
const Client = require('azure-iot-device').Client;
6666
```
6767

68-
### Create a Protocol module
68+
### Create a protocol module
6969

7070
Create a `Protocol` module using an installed transport package.
7171

0 commit comments

Comments
 (0)