Merge pull request #288319 from dominicbetts/central-freshness

Freshness

Author: prmerger-automator[bot]

articles/iot-central/core/concepts-device-implementation.md

@@ -3,7 +3,7 @@ title: Device implementation
 description: This article introduces the key concepts and best practices for implementing a device that connects to your IoT Central application.
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/06/2023
+ms.date: 10/14/2024
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -71,11 +71,11 @@ To learn more about the format of the JSON messages that a device exchanges with
 
 ### Device SDKs
 
-Use one of the [Azure IoT device SDKs](../../iot-hub/iot-hub-devguide-sdks.md#azure-iot-hub-device-sdks) to implement the behavior of your device. The code should:
+To implement the code that runs on your device, you should use one of the [Azure IoT device SDKs](../../iot-hub/iot-hub-devguide-sdks.md#azure-iot-hub-device-sdks). Actions your code should implement include:
 
 - Register the device with DPS and use the information from DPS to connect to the internal IoT hub in your IoT Central application.
 - Announce the DTMI of the model the device implements.
-- Send telemetry in the format that the device model specifies. IoT Central uses the model in the device template to determine how to use the telemetry for visualizations and analysis.
+- Send telemetry in the format that the device model specifies. To determine how to use the telemetry for visualizations and analysis, IoT Central uses the model in the device template.
 - Synchronize property values between the device and IoT Central. The model specifies the property names and data types so that IoT Central can display the information.
 - Implement command handlers for the commands specified in the model. The model specifies the command names and parameters that the device should use.
 
@@ -123,7 +123,7 @@ To learn more about registration and provisioning in IoT Central, see [IoT Centr
 
 ### Handle connection failures
 
-For scaling or disaster recovery purposes, IoT Central may update its underlying IoT hubs. To maintain connectivity, your device code should handle specific connection errors by establishing a connection to a new IoT Hub endpoint.
+When IoT Central automatically scales or handles a disaster recovery scenario, it might update its underlying IoT hubs. To maintain connectivity, your device code should handle specific connection errors by establishing a connection to a new IoT Hub endpoint.
 
 If the device gets any of the following errors when it connects, it should reprovision the device with DPS to get a new connection string. These errors mean the connection string is no longer valid:
 

articles/iot-central/core/howto-build-iotc-device-bridge.md

@@ -6,7 +6,7 @@ services: iot-central
 ms.service: iot-central
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/14/2023
+ms.date: 10/14/2024
 ms.topic: how-to
 # Administrator
 ---
@@ -66,7 +66,7 @@ After the deployment is completed, you need to install the npm packages the func
     npm install
     ```
 
-    These commands may take several minutes to run. You can safely ignore any warning messages.
+    These commands might take several minutes to run. You can safely ignore any warning messages.
 
 1. After the package installation finishes, Select **Restart** on the **Overview** page of the function app:
 
@@ -96,7 +96,7 @@ You can include a `timestamp` field in the body to specify the UTC date and time
 
 You can include a `modelId` field in the body. Use this field to assign the device to a device template during provisioning.
 
-The `deviceId` must be alphanumeric, lowercase, and may contain hyphens.
+The `deviceId` must be alphanumeric, lowercase, and can contain hyphens.
 
 If you don't include the `modelId` field, or if IoT Central doesn't recognize the model ID, then a message with an unrecognized `deviceId` creates a new _unassigned device_ in IoT Central. An operator can manually migrate the device to the correct device template. To learn more, see [Manage devices in your Azure IoT Central application > Migrating devices to a template](howto-manage-devices-individually.md).
 
@@ -116,7 +116,7 @@ The Resource Manager template provisions the following resources in your Azure s
 
 The key vault stores the SAS group key for your IoT Central application.
 
-The function app runs on a [consumption plan](https://azure.microsoft.com/pricing/details/functions/). While this option doesn't offer dedicated compute resources, it enables the device bridge to handle hundreds of device messages per minute, suitable for smaller fleets of devices or devices that send messages less frequently. If your application depends on streaming a large number of device messages, replace the consumption plan with a dedicated [App service plan](https://azure.microsoft.com/pricing/details/app-service/windows/). This plan offers dedicated compute resources, which give faster server response times. Using a standard App Service Plan, the maximum observed performance of the function from Azure in this repository was around 1,500 device messages per minute. To learn more, see [Azure Functions hosting options](../../azure-functions/functions-scale.md).
+The function app runs on a [consumption plan](https://azure.microsoft.com/pricing/details/functions/). While this option doesn't offer dedicated compute resources, it enables the device bridge to handle hundreds of device messages per minute, suitable for smaller fleets of devices or devices that send messages less frequently. If your application depends on streaming a large number of device messages, replace the consumption plan with a dedicated [App service plan](https://azure.microsoft.com/pricing/details/app-service/windows/). This plan offers dedicated compute resources, which give faster server response times. With a standard App Service Plan, the maximum observed performance of the function from Azure in this repository was around 1,500 device messages per minute. To learn more, see [Azure Functions hosting options](../../azure-functions/functions-scale.md).
 
 To use a dedicated App Service plan instead of a consumption plan, edit the custom template before deploying. Select  **Edit template**.
 
@@ -138,7 +138,7 @@ Replace the following segment:
 },
 ```
 
-with
+With:
 
 ```json
 {
@@ -172,7 +172,7 @@ The following examples outline how to configure the device bridge for various Io
 
 ### Example 1: Connecting Particle devices through the device bridge
 
-To connect a Particle device through the device bridge to IoT Central, go to the Particle console and create a new webhook integration. Set the **Request Format** to **JSON**.  Under **Advanced Settings**, use the following custom body format:
+To connect a Particle device through the device bridge to IoT Central, go to the Particle console and create a new webhook integration. Set the **Request Format** to **JSON**. Under **Advanced Settings**, use the following custom body format:
 
 ```json
 {
@@ -189,7 +189,7 @@ Paste in the **function URL** from your function app, and you see Particle devic
 
 ### Example 2: Connecting Sigfox devices through the device bridge
 
-Some platforms may not let you specify the format of device messages sent through a webhook. For such systems, you must convert the message payload to the expected body format before the device bridge processes it. You can do the conversion in the same function that runs the device bridge.
+Some platforms might not let you specify the format of device messages sent through a webhook. For such systems, you must convert the message payload to the expected body format before the device bridge processes it. You can do the conversion in the same function that runs the device bridge.
 
 This section shows how to convert the payload of a Sigfox webhook integration to the body format expected by the device bridge. The Sigfox cloud transmits device data in a hexadecimal string format. For convenience, the device bridge includes a conversion function for this format, which accepts a subset of the possible field types in a Sigfox device payload: `int` and `uint` of 8, 16, 32, or 64 bits; `float` of 32 bits or 64 bits; little-endian and big-endian. To process messages from a Sigfox webhook integration, make the following changes to the _IoTCIntegration/index.js_ file in the function app.
 
@@ -219,7 +219,7 @@ context.res = {
 To connect The Things Network devices to IoT Central:
 
 * Add a new HTTP integration to your application in The Things Network: **Application > Integrations > add integration > HTTP Integration**.
-* Make sure your application includes a decoder function that automatically converts the payload of your device messages to JSON before it's sent to the function: **Application > Payload Functions > decoder**.
+* Make sure your application includes a decoder function that automatically converts the payload of your device messages to JSON before sending it to the function: **Application > Payload Functions > decoder**.
 
 The following sample shows a JavaScript decoder function you can use to decode common numeric types from binary data:
 
@@ -283,9 +283,3 @@ req.body = {
 ## Limitations
 
 The device bridge only forwards messages to IoT Central, and doesn't send messages back to devices. This limitation is why properties and commands don't work for devices that connect to IoT Central through this device bridge. Because device twin operations aren't supported, it's not possible to update device properties through the device bridge. To use these features, a device must connect directly to IoT Central using one of the [Azure IoT device SDKs](../../iot-hub/iot-hub-devguide-sdks.md).
-
-## Next steps
-Now that you've learned how to deploy the IoT Central device bridge, here's the suggested next step:
-
-> [!div class="nextstepaction"]
-> [Manage your devices](howto-manage-devices-individually.md)

articles/iot-central/core/howto-control-devices-with-rest-api.md

@@ -3,7 +3,7 @@ title: Use the REST API to manage devices in Azure IoT Central
 description: How to use the IoT Central REST API to control devices in an application by using properties and commands.
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/14/2023
+ms.date: 10/14/2024
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -483,7 +483,3 @@ GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-con
 
 > [!TIP]
 > To call commands in a component in a module, use `/devices/{deviceId}/modules/{moduleName}/components/{componentName}/commands/{commandName}`.
-
-## Next steps
-
-Now that you've learned how to control devices with the REST API, a suggested next step is to learn [How to use the IoT Central REST API to create and manage jobs](howto-manage-jobs-with-rest-api.md).

articles/iot-central/core/howto-export-to-webhook.md

@@ -4,7 +4,7 @@ description: Learn how to use the IoT Central data export capability to continuo
 services: iot-central
 author: dominicbetts
 ms.author: dobett
-ms.date: 05/22/2023
+ms.date: 10/14/2024
 ms.topic: how-to
 ms.service: iot-central
 ---

articles/iot-central/core/howto-query-with-rest-api.md

@@ -4,7 +4,7 @@ description: How to use the IoT Central REST API to query devices in an applicat
 titleSuffix: Azure IoT Central
 author: dominicbetts
 ms.author: dobett
-ms.date: 05/19/2023
+ms.date: 10/14/2024
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -17,7 +17,7 @@ The IoT Central REST API lets you develop client applications that integrate wit
 
 - Get the last 10 telemetry values reported by a device.
 - Find all devices that are in an error state and have outdated firmware.
-- Telemetry trends from devices, averaged in 10-minute windows.
+- Analyze telemetry trends from devices, averaged in 10-minute windows.
 - Get the current firmware version of all your thermostat devices.
 
 This article describes how to use the `/query` API to query devices.
@@ -119,7 +119,7 @@ You can find the component name in the device template:
 
 The following limits apply in the `SELECT` clause:
 
-- There's no wildcard operator.
+- No wildcard operator is available.
 - You can't have more than 15 items in the select list.
 - A query returns a maximum of 10,000 records.  
 
@@ -293,7 +293,3 @@ The current limits for queries are:
 - The maximum length of a query string is 350 characters.
 - You can't use the wildcard (`*`) in the `SELECT` clause list.
 - Queries can retrieve up to 10,000 records.
-
-## Next steps
-
-Now that you've learned how to query devices with the REST API, a suggested next step is to learn [How to use the IoT Central REST API to manage users and roles](howto-manage-users-roles-with-rest-api.md).