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 already36 votes
Currently 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.
It would be great to connect the new Azure Sphere to the IoT Hub on Edge to use Sphere in a Transparent Gateway Scenario22 votes
This is a gap that we are aware of, want to fix, and are currently discussing with the Azure Sphere team.
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.20 votes
This is definitely a scenario we want to support in the future.
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.20 votes
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.8 votes
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.5 votes
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-deliv2 votes
We 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.
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.2 votes
Our public preview of IoT Edge integration with Kubernetes is the first step towards running IoT Edge on clusters.
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 vote
It 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.
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?