GET https://{subdomain}.{centralDnsSuffixInPath}/api/preview/devices/{device_id}/modules/{module_name}/components/{component_name}/telemetry/{telemetry_name}
in this api where can i find a module name in azure iot central
to get the list of device modules:
GET https://{subdomain}.centralDnsSuffixInPath}/api/preview/devices/{device_id}/modules
Related
I have been reading and collecting telemetry data on Azure resources using the MXChip AZ3166 for quite awhile now. May I know if it is possible to observe and extract the telemetry data without using Azure services?
May I know if it is possible to observe and extract the telemetry data without using Azure services?
Apart from using the Azure IoT Central portal, as per documentation:
You can also monitor telemetry from the device by using the Termite app.
You can refer to Quickstart: Connect an MXCHIP AZ3166 devkit to IoT Central, Termite: a simple RS232 terminal and Getting Started with Azure RTOS and Azure IoT
How can I connect devices connected to loriot to Azure IoT Central?
I've got the documentation of connecting it to an Azure IoT Hub, but I'm actually using IoT central, so this seems to work differently.
Log in to the Azure portal (Microsoft Azure account required).
Create a IoT Hub
Copy Shared access primary key from IoT Hub > Settings > Shared
access policies > device
Use this primary key and the IoT Hub Name to configure your LORIOT
application output
From IoT Hub > Explorers > IoT devices: create a device using the
Device EUI as Device ID
Messages will have the following format:
https://docs.loriot.io/display/LNS5/Uplink+Data+Message
Loroiot setup only allows "IoT Hub Name" & "Primary Key" which IoT Central application does not expose unless a Device Provisioning Call is made to it from device or API. It is possible to get the device key from Azure CLI or IoT Central portal, but IoTHub name is only via the DPS call.
One option is to get this IoTHub name seperately and then configure Loroiot, but in case of HA/DR the IoTHub name could change (IoT Central manages multiple IoTHubs for HA/DR and scale).
In absence of Loroiot having this functionality, check if its API allows configuration then orchestrate provisioning via script, function, etc.
https://learn.microsoft.com/en-us/rest/api/iot-dps/device/runtime-registration
So basically i'm working on a project which involves getting data using a sensor (say analyzing temperature/vibration etc.) and then transfer the data to cloud (Azure) which in turn can be used to show users the data - in an app/website. Do i use Azure IoT Hub or Azure IoT Central to store , stream and make use of data so that i can display the respective data of each user when they logon to the website?
Azure IoT Central is a set of pre-built IoT applications while IoT Hub is a service. You either use or build your own solution.
can I access to the Iot Hub behind the Azure Iot Central? I need to use:
IoT Edge feature
Device Provisioning
Get to Event-Hub Endpoint to process data
Cheers
Azure IoT Central has evolved since many of these answers were posted.
Today, IoT Central IoT Edge Support is preview and the Device Templates are in place to support it.
For the original data access requirement, use the continuous data export feature in Azure IoT Central to export your data to Azure Event Hubs, Azure Service Bus, or Azure Blob storage instances.
Azure IoT Central is a fully managed solution, you can't access underlying services including Azure IoT Hub. They are not exposed.
Reference "Compare Azure IoT Central and Azure IoT options".
What you can do is device connection. You can send device-to-cloud message and update device twin.
Reference "Device connectivity in Azure IoT Central".
Compare to Azure IoT Central, Azure IoT solution accelerators(original name: Azure IoT Suite) gives you more control of the underlying services. You have access to the underlying Azure services to manage them, or replace them as needed. For your use case, you can consider Azure IoT solution accelerators.
your requirement '3. Get to Event-Hub Endpoint to process data' can be done using your IoT Central App feature such as Continuous Data Export to the Event Hub.
The other way is to obtain an internal IoT Hub access to the events default endpoint from your IoT Central application access token like is shown here.
This approach allows to obtain an eventhubSasToken like is shown in the following code snippet:
"eventhubSasToken": {
"sasToken": "SharedAccessSignature sr=sb%3A%2F%2Fep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net%2Fep-ehub-saas-iothu-1044564-xxxxxxxxxx&sig=xxxxxx&se=1546197703&skn=service",
"entityPath": "ep-ehub-saas-iothu-1044564-xxxxxxxxxx",
"hostname": "sb://ep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net/"
}
IoT Edge is not supported in IoT Central. If you would like to request this feature, please add it to UserVoice and describe your use case.
Device Provisioning Service is supported in IoT Central. See https://learn.microsoft.com/en-us/azure/iot-central/concepts-connectivity
While there is no way to access the underlying services, you can export your data using Continuous Data Export to your own Event Hub endpoint in your own Azure subscription. From there you can process the data how you like.
I am just reading up on the new IoT Central, currently in preview.
Our customers seldom let their devices connect to cloud by themselves,
but are rather connected to some kind of management system that in turn connects to Azure.
We however consider using IoT Central for demo purposes and would like to know if devices defined in IoT Central sends their data to an IoT Hub of choice or if is handled in any other way behind the scenes?
Microsoft IoT Central does use an IoT Hub internally. If you look here you can see that when you add a physical device to an IoT Central application it generates an IoT Hub device connection string: https://learn.microsoft.com/microsoft-iot-central/tutorial-add-device#get-connection-string-for-real-device-from-application.
However, you cannot get admin access to the IoT Hub or use an IoT Hub of your own choosing - all you have is the device connection string.