Azure IoT Edge
Azure IoT Edge moves analytics and logic out of the cloud and onto your on-premises devices. Using a cloud interface, you can deploy either Azure service logic or your own code to devices without having to physically access them. And offline capabilities mean that you can extract business insights anywhere, without worrying about maintaining constant communication with a cloud service.
More details about the services are available in the documentation.
-
Code sample for identity translation pattern.
If the development team is busy, some guidance on how does the module(who understand native protocols and gives device identity) receive the connection string will be helpful. Hard coding connection strings is not is not an option.
94 votes -
Azure blob file upload
We are planning to upgrade an existing production application from V1 to V2. In addition to streaming data (as messages to Azure IotHub), we also upload hourly aggregated data to Azure blob store. Can you share approximate time-lines when V2 can have support for Azure blob upload?
45 votes -
Store Private key for X.509 based DPS securely on HSM
Use the X.509-based enrollment in DPS in IoTEdge without storing the private key on file system.
The idea is to store the Private Key in a HSM and let it never leave.
At this moment, the x.509 provisioning mode only supports a private key on the file system...
31 votes -
Remote login to IoT Gateway
If an IoT Gateway is deployed in the industrial plant and if some application crashes in Gateway or some need of login to the gateway.
In that case, Azure IoT edge should allow users to remotely log in to the IoT gateway using ssh/telnet. This will very easy to monitor the status and debugging/maintenance.21 votes -
BLE Sample
Will a BLE sample be available?
As I understand, it will require the module container to run in privileged mode to gain access to hardware devices... Is this supported?
19 votes -
Support Node.js and Python Edge modules on Windows
Currently Node.js and Python custom Edge modules are only supported in Linux containers and therefore are not supported on Windows IoT or IoT Core platforms/devices as Linux containers are not supported on Windows in production. Linux containers should be supported on Windows (IoT Enterprise and IoT Core) or Python and Node.js modules should compile & run in Windows containers.
15 votesSupporting Node.js and Python modules on Windows is planned.
-
Rust SDK Azure IoT Edge
Since Rust is becoming increasingly popular it would be amazing to use Rust for creating custom IoT Edge modules. Rust would be a good fit for IoT Edge modules which require high performance and safety!
14 votesThis is definitely interesting; however is unplanned at the moment. Supporting SDKs in 5 languages is already a large task and we’re not likely to add another language to that matrix anytime soon.
-
Add Feature to Check Upstream Connection Status (Expose to Modules)
Is there some connection state to IoT Hub from IoT Edge that can be made available to edge modules? We are trying to get the upstream connection status to IoT Hub from the edge module context (.NET).
We would like this status check to be available during first-time-configuration as well as outside of the first-time-configuration use case so that, if needed, we can leverage this for troubleshooting devices in the field.
9 votesWe will consider this for the next round of feature planning which will cover work done in the first half of 2021.
-
ARM Python SDK for Azure IoT Edge
Make the Python SDK for creating IoT Edge Modules also available for ARM cpu's and Windows.
The vast selection of python libraries, and ARM devices with python support, makes it an ideal choice for rapid development of Edge Modules.
8 votesThe Python SDK is going through a rewrite at the moment. Once that is complete it will be supported on both Linux and Windows. You can find a preview of the rewrite at – github.com/Azure/azure-iot-sdk-python-preview
-
Container Encryption
Provide container encryption technologies (e.g. Vormetric from Thales) to Azure IoT Edge to make sure that partners protect their IP
8 votes -
Support hierarchical module input structure
Currently the input channel is determined by a single name. But from my point of view it could be interesting to support a hierarchy of inputs in a module (e.g. something like /modules/{{mid}}/inputs/{{input}}/{{subchannel}} would be possible) - this would be interesting in scenarios where the module just registers a generic handler for messages and uses the information contained in the hierarchy of the input channel (e.g. for routing purposes) - for sure something similar could be achieved by just using/interpreting a different 'split char', but it would be nice if a simple '/' could be used. Also this wouldn't allow…
7 votes -
Example of C based module for Transparent gateway
Can you please add code sample for transparent gateway use case? We use the v1 modules implementation for communication with other
network protocol based on this example: https://github.com/Azure/iot-edge/blob/master/v1/samples/ble_gateway/iot-hub-iot-edge-physical-device.md. We would like to move the solution to v2. Modbus module is not very useful for our solution. Thank you.7 votesWe are planning on providing an example of this for the SensorTag which speaks BLE. That said, it probably won’t be available for a couple months so it’d be great if you created an example as well.
Please see the following comment where we discuss gateway scenarios a little more.
https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/32307181-example-tutorial-for-transparent-gateways -
Enable Azure Media Services streaming an analytics through IoT Edge.
Live media streams requires usually a good bandwith. By running the Azure Media Services, through the IoT Edge, it should be possible to employ ML, and vision analytics on the edge before streaming to cloud.
4 votes -
Module needs the ability to detec if offline
In my PoC, I would have liked to route messages from a device WHERE ($hubIsUnavailable) directly to a module, and otherwise passed it directly upstream. The ability to have an edge module run business logic that sets flags to influence routing might be powerful. Instead I was able to implement the routing/forwarding in the module itself.
3 votes -
Upload Docker Compose yaml to IoT Edge
writing docker compose file is easier than writing IoT Edge template. Uploading a docker-compose file instead of writing an IoT Edge module would make it easier then map communications between modules can be done in the portal. or maybe do this in CLI so it can be automated. If you think this is a good idea, please vote so it can be prioritized.
2 votes -
Out of box IoT edge custom modules for Pinter server
One of my current customer and another customer from last fiscal year had a requirement to connect their local office printer as an edge device to the IoT Hub(cloud) and start sending their print jobs to their local printer. Is there way product team build a generic IoT edge module may be in collaboration with partners like HP and others and cater to the needs of such customers and solve their business problems? This could bring tons of ACR for MSFT.
I’m not a network expert but there may be ip address, port and firewall may need to be configured…
2 votesAzure IoT Edge is an open source project and we’d be happy to have a partner (.eg HP, Xerox, Brother) contribute a module that works with their printers. They could even add it to the module marketplace for easy discovery.
-
API call
I am trying to create a module of the type IoT Edge Custom Module via a direct POST API call. And it seems as if the data for the module is getting distributed under $edgeAgent and $edgeHub. Can someone guide me properly on how to go about it please? Basically I want to reciprocate what I am able to do via the portal, through the REST API call. Thanks.
1 vote -
Stream Analytic Job should use desired properties as reference data
Assume I am using ASA to filter and trigger alerts. I would like to change thresholds using the module twin
1 vote -
Messages delivered to IoT Edge device instead of Leaf device to IoT hub
I have setup Azure IoT Edge in Transparent Proxy pattern. Created a leaf device. When Messages from leaf devices are sent upstream
"leafdeviceToUpstream":"FROM /messages/* WHERE NOT IS_DEFINED($connectionModuleId) INTO $upstream"")"
Messages are correctly delivered to leaf device in IoT Hub.
Now I created a custom module. Messages from leaf device are piped to custom module and from custom module (after processing) are sent upstream.
Here, I was expecting that messages are delivered to leaf device. However, instead they are delivered to IoT Edge device. Looks like since the custom module creates new message, source of origin changes from leafdevice ID to…1 vote -
Azure Blob Storage on IoT Edge: cloudToDeviceDownload
We see lots of needs where customers use a connected Edge device as data gateway for leaf devices.
ABSonIoTEdge module allowed us to implement upload scenarios so far, is possible to get it working the other way around too?For example, I'd have the need to deliver regularly to thousands of leaf devices that cannot connect to the internet the same file (e.g. a few MB firmware) through a couple of Edge devices.
azcopy sync and a local file share works, but it would be so much better if we could have the IoT related data in the same place.…
1 voteHello, is the need here specific to hosting firmware and updating leaf devices or hosting any generic file?
- Don't see your idea?