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?41 votes
An IoT Edge message correlation id should be provided so that specific message workflows can be diagnosed via module logging.26 votes
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.24 votes
This is definitely a scenario we want to support in the future.
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
Is it possible to run iot edge python module on edge device where Windows 2016 sever is OS? I am using Linux docker container.17 votes
This will be supported by the time Edge reaches GA 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 votes
Supporting Node.js and Python modules on Windows is planned.
IoT edge supports .NET core 2.0 only. But latest vesions are 3.0 and 3.1. And moreover 2.0 isn't even LTS release.
Or does it support all versions greater than 2.0?9 votes
Azure IoT Edge currently uses .NET Core 2.1 which is an LTS release. We plan on moving to 3.1 in the next release which is 1.0.10.
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 votes
We 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.
For the Tier 1 system, the latest IoT Edge Security Damon package is provided in the package repository (https://packages.microsoft.com/)
But for the Tire 2 system, it is not provided.
For example, for Ubuntsu 18.04 of Tire 1, iotedge1.0.4-1amd64.deb is provided, Regarding Debian 9, it still iotedge1.0.0-1amd64.deb yet.
Our products use Debian 9, and we are asked to provide packages that fix bugs from customers.
We will to build it localy and provide it at our own repository, What do you think?2 votes
We plan on hosting the Debian packages on packages.micrsoft.com once we move Debian to Tier 1 support.
I like your temporary workaround of publishing them to your own repository. You don’t even need to build them locally. We provide them with each release. For example, you can find the rpms for the 1.0.6 release at – https://github.com/Azure/azure-iotedge/releases/tag/188.8.131.52
- Don't see your idea?