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.
-
when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for rea
when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for real time monitoring. This is similar to the one posted already
37 votesCurrently IoT Hub and Edge Hub guarantee that messages will be delivered in order. Would folks want this promise to be broken? How would people want to rationalize ordering with other messages.
-
Document how to connect Azure Sphere Device as Downstream Device to Edge
It would be great to connect the new Azure Sphere to the IoT Hub on Edge to use Sphere in a Transparent Gateway Scenario
28 votesThis is a gap that we are aware of, want to fix, and are currently discussing with the Azure Sphere team.
-
C2D Messaging
I know direct methods are possible but sometimes you just want to have a queue of C2D messages which are delivered to devices when they come online. Direct methods only work when a device is connected and it would require some effort to implement the aforementioned scenario. Also one would need some routing logic to deliver those messages to modules.
24 votes -
Hierarchy possibilities for edge devices.
The purpose is to have for example 5 incoming sensors in the 'sensor' edge device where we can do some calculations on the edge. The output goes to another edge device, where again we can do some calculations on the edge with input from other similar 'sensor' edge devices. The last edge device in the chain will send the data to the IoT Hub.
22 votesThis is definitely a scenario we want to support in the future.
-
Need a way to distribute communication at edge devices when offline with IoT hub
During offline with IoT hub, is it possible to have a mechanism at Edge device to distribute the messages among other Edge devices? This will help to address a scenario were one Edge device needs to share message/information with another Edge device as there is no cloud data storage share available due to
connectivity issue.10 votes -
Low bandwidth / partially connected: message delivery priority
For scenarios with low bandwidth and connectivity issues sending messages in the FIFO order of the message cache after being offline is not working. We need a way to specify "important" messages (delivery priority) that needs to be sent before trying to send all other messages from the msg cache. Specifying different TTL values for different priorities would be necessary as well.
6 votes -
Log a Warning if messages are deleted from the StoreAndForward/offline cache (because of TTL)
Currently there is no way to figure out that messages were deleted because of the Time To Live/TTL StoreAndForward configuration. There should be a warning in the Logs if this happens to hint the deletion of messages that were not sent to IoT Hub. Ideally there is a configurable second warning before this happens (e.g. 10 minutes before messages get deleted because of TTL).
In addition it would be great to add more control to the StoreAndForward/Caching/Queuing functionality of messaging - refer to ideas https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/33534802-more-options-or-configuration-parameters-of-stor and https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/36632884-low-bandwidth-partially-connected-message-deliv3 votesWe are currently adding the ability to pull metrics from the runtime so that customers can understand how their Edge devices are performing in the field. Message drops due to TTL is one of the metrics we’ll be exposing. I do not expect this feature for a few months, likely 1.0.10.
-
Local Edge N+M high availability and scalability (no cloud connection required after setup)
1) Deploy Edges as local clusters such that they can suffer failure and there is a high availability strategy that doesn't require a cloud connection.
2) Edge scalability to horizontally add nodes to the Local Edge Cluster. Maybe it kind of behaves like Docker Swarm. i.e. Say I have a pretty intense preprocessor for data prep before handing it to ML Inference. That could get scaled out across multiple nodes in a Local Edge Cluster.
3 votesOur public preview of IoT Edge integration with Kubernetes is the first step towards running IoT Edge on clusters.
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-kubernetes
-
Support storing the module identities within edgeAgent on the filesystem
At the moment the module identities are stored within edgeAgent which get destroyed as soon as the edgeAgent container is removed. It would be great to have an option to store the identities on the filesystem (for example by bind mounting a folder in which they are stored in somehow).
Doing this would make running IoT Edge in offline scenarios a lot easier. Given the following scenario:
- An IoT Edge device is used offline
- The firmware is being updated, measures are being taken to persist the docker images so the modules will be able to start after the…2 votes -
Edge devices connected to the same local network to communicate with each other directly.
I wish to use Azure IoT Edge to deploy our modules to a fleet of robots. It would be awesome if edge modules could send messages to modules of other devices within the same local network.
1 vote -
Remote Restart of the IoT EDGE Daemon for re-provisining services
For DPS re-provision scenarios, such as moving the device to a new IoT hub or setting new configuration of the device, the daemon needs to restarted in order to use the config.yaml file to communicate with DPS, so the configuration can be updated.
it would be useful to be able to restart the daemon remotely ( via a direct method of the edge agent as an example )
1 vote -
Add sha256 support for authenticating downstream devices with self signed certificates
I set up an edge device, added a child device to it and modified the child device's connection string to point to the edge device. The device is using self signed certs. If I add the device to the hub using the sha256 thumbprint, the edge cannot authenticate the device. If I add the device using the sha1 thumbprint, it works. I followed the instructions here, which says to use sha1: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-authenticate-downstream-device
But, when I use a Device Provisioning Service to add the device to the hub, it uses the sha256 thumbprint, so my device won't connect to the edge.
…
1 vote -
Using Bluetooth to communicate with mobile app
I can't find any C# tutorial which uses the built-in Bluetooth chip on the Raspberry Pi 3 (everyone seems to be using SensorTags) to chat with mobile app. I have been able to connect to mobile phone and receive messages on my Edge module in Python, but I can't find any reliable and full tutorial to do it in C#
1 voteIt would be great to have the community contribute a sample that shows this; however at the moment it is hard until IoT Edge fully supports identity translation.
-
Certificate based Proxy Authentication
Can you please provide support for certificate based proxy authentication on IoT Edge. The certificate are client signed certificates used to securely authenticate within the client network.
1 vote
- Don't see your idea?