Nested objects and arrays.
Use case: When the device acts as a protocol translator for another network, example BLE and the payloads are identical but from a different address.
Here is a simplified example:
We have added support for the complex objects with the latest preview update of Azure IoT Central. We also have array support on the roadmap and will share more details as they become available.
Please note that these features are in preview and we are listening to the feedback to further refine them.
You can read more about the new capabilities in the device template here: https://docs.microsoft.com/en-us/azure/iot-central/core/tutorial-define-iot-device-type-pnp?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json#prerequisites
I have not found a way to control which devices are included in Continuous Export (to Blobs), and several devices are being stored including two simulated devices of interest only during testing are being exported. Is there a way to specify which devices are included, and if not, could the "device set" be employed for this purpose - essentially say "export device set X"?4 votes
We recently shipped the new data export which does allow for filtering based on capabilities and device template, device ID, and device name.
We are planning to add more device filters here like simulated, approved, provisioned, etc.
Please let us know what specific kinds of filters you are looking for.
Vivian on behalf of the Azure IoT Central team
- Don't see your idea?