Is it possible to deploy IoT Edge(https://learn.microsoft.com/en-us/azure/iot-edge/) modules on Azure Sphere? If so, is there a tutorial I can follow?
This feature is not supported yet. Please vote for that feature here: https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/35859580-document-how-to-connect-azure-sphere-device-as-dow
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
We want to use Azure IoT Edge as an identity translation gateway with the protocol translation gateway. Because we are working with an OBD-II device that strictly uses TCP/IP as communication protocol. We can only add IP, PORT, and APN in the device nothing else.
We want to use these devices with the Azure IoT Hub. As we know Azure IoT hub works only with MQTT, AMQP, and HTTPS.
We want to use Identity translation for:
Creating IDs for these lots of devices from the IoT edge and register them in IoT Hub.
If possible, we want to automatically make the device to Azure IoT Hub communication via IoT Edge.
We want to use protocol translation for:
Acting as a medium to communicate between the Devices working on the TCP/IP and the Azure IoT Hub, which supports MQTT, AMQP, and HTTPS communication protocol.
We want to have a Bi-directional communication with the Azure IoT cloud. So we can send messages back to the devices when needed and do FOTA.
My Questions:
Is there a module available for the TCP/IP implementation in this sample?
Can this repository be used for production-level implementation for the above?
Is there any full detailed documentation like this sample for implementing the actual asked for production level?
Does this Implementation way provide two-way communication? Device to edge to cloud and then Cloud to edge to the device?
Is this identity translation gateway in development and is actually not fully blown for the production purpose?
Is there any working example or a full developer guide for Implementing Azure IoT Edge gateway as an Identity translation gateway with protocol translation gateway?
IoT Edge as a translation gateway (protocol translation and identity translation) is only supported by third-party modules. That custom or third-party module will be responsible for pre-processing the incoming messages and turn them into a format that can be understood by IoT Hub.
The IoT Edge runtime does not include protocol or identity translation
capabilities. These patterns requires custom or third-party modules
that are often specific to the hardware and protocol used. Azure
Marketplace contains several protocol translation modules to choose
from. For a sample that uses the identity translation pattern, see
Azure IoT Edge LoRaWAN Starter Kit.
Ref: Device capabilities behind translation gateways
There is a full developer guide and best practices for implementing Azure IoT Edge as a transparent gateway in the following doc: Connect a downstream IoT Edge device to an Azure IoT Edge gateway
Like mentioned in the github repo you are referring to Azure IoT Edge Identity Translation Lite: Sample on implementing Identity Translation at the edge , that is a:
'lite' implementation of the Identity Translation pattern as it only
supports the basic identity translation flows based on symmetric keys
Leverage github issues section and suggest pull requests there with your implementation - that sample started being implemented by Microsoft Engineers though it is not officially supported by IoT Edge runtime.
I am building an IoT solution based on devices that are not programmable (3rd party devices).
I can just configure the server they must connect to and I have the messaging (sending messages and receiving commands).
What is the best way to integrate them in an Azure IoT Solution (IoT Hub) ?
It looks like we can use Azure IoT Edge as Gateway (https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/iot-edge/iot-edge-as-gateway.md) in a "Identity translation" pattern, but I still not figure out how to do it.
I also find Azure IoT Protocol Gateway (https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-protocol-gateway) that seems to do the job but it is not sufficiently clear for me what to do.
Thanks in advance for your help.
The question is which protocols your devices support and how configurable your devices are. For instance you might be able to talk MQTT directly to the IoT Hub without using the SDK: https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support#using-the-mqtt-protocol-directly-as-a-device
Same is possible for HTTP using the REST API directly: https://learn.microsoft.com/en-us/rest/api/iothub/device
If neither is an option then yes, you need some kind of gateway - like in the examples which you linked.
It's great that Azure Iot hub and sdk supports blob uploading. However it seems blob metadata uploading is not there. Any plan to add the feature? It's a very handy feature for small projects.
Or it's already supported but I missed something?
That's correct. There is no method (support) for the blob metadata uploading in the Azure IoT Device Client SDK.
However, the following workaround can be used for this feature. It's based on the uploading files with IoT Hub using the REST API calls.
Step 1: The device ask an Azure IoT Hub for upload references
Step 2: Upload blob and metadata
Step3: Complete the device uploading process:
This feature is tracked by https://github.com/Azure/azure-iot-sdk-csharp/issues/165 for the .NET Azure IoT SDK.
I am designing an IoT solution's Disaster Recovery approach on Azure. I am following IoT Hub High Availability and DR in MSDN. The solution need to keep keep geo-replicated backups of device identities from primary, and upload them to the secondary IoT hub before switching the active endpoint for the devices.
I am not able to find out any documentation on how to take backup of Identity Registry from primary and upload it in secondary.
Just found out that I should be using IoT Hub Device Identities in bulk - https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-bulk-identity-mgmt.
The topic came up today regarding IoT Hubs and DR. It sounds like you are doing the same work. Is there any other information you can share. We have an IoT Hub centric app only in one Regional DataCenter. What happens if an earthquake etc hits the data center. I have to come up with the architecture. Anything that you can share would be greatly appreciated. Thanks! MIke
I intend to use the IoT Hub to update firmware of my Edison device utilising its bi-directional capability although I am not sure of where to look for detailed instructions on how to do it. The only information I have found on the subject is HERE but doesn't go into detail on how exactly to do it, more a high level overview. Does anyone have any knowledge on how this is to be done or know any links that will help?
Thanks
The link you provided returns 404 for me right now; maybe that's temporary...
I work for Microsoft, on the Device Management SDK team for IoT Hub. The new Device Management capabilities we announced at Build last week should give you exactly what you need, but there isn't much info because the features aren't available to the public just yet.
For a preview, take a look at this video from Build where we demo'd firmware update on the Intel Edison. The device management segment starts at about 35 min, demo at 40 min.
To do firmware update using only what's available publicly today in IoT Hub, you'd probably start by sending a cloud-to-device message to your Edison. Of course, exactly how you go about downloading and updating the firmware after that is specific to your device and scenario.
Here is the link to the repo which allows you to update firmware remotely using the IoT Hub. Thanks MS!
https://github.com/Azure/azure-iot-sdks/tree/dmpreview