In this article, you create two Java console apps: Query devices from your back-end app using filters on the tags and properties previously created. Use a simulated device app to report its connectivity channel as a reported property on the device twin. For more information about querying, see IoT Hub query language. The following illustration shows device twin organization:Īdditionally, the solution back end can query device twins based on all the above data.įor more information about device twins, see Understand device twins. Tags and properties can't contain arrays, but can contain nested objects. JSON objects modifiable by the device app and readable by the solution back end. JSON objects modifiable by the solution back end and observable by the device app. Device metadata accessible only by the solution back end.ĭesired properties. IoT hubs store device twins, which contain the following elements: For more information about device twins, including when to use device twins, see Understand device twins. Query your device metadata, configuration, or state.ĭevice twins are designed for synchronization and for querying device configurations and conditions.
Synchronize the state of long-running workflows, such as firmware and configuration updates, between a device app and a back-end app. Report current state information such as available capabilities and conditions, for example, the connectivity method used, from your device app. Store device metadata from your solution back end. For more information about the basic and standard/free IoT Hub tiers, see Choose the right IoT Hub tier for your solution. The features described in this article are available only in the standard tier of IoT Hub.
0 kommentar(er)
