Description IoT Edge 1.2 brings a (currently in preview) MQTT broker, that can be used by local modules or external applications. A SAS token will be needed for authentication. If you want to use the broker from within an IoT Edge module, you can generate the SAS token by calling the workload API. The current SDK does not offer this functionality, as the MQTT broker is still in preview. The sample I’ve created uses the SecurityDaemonClient class from the event-grid-iot-edge SDK as reference and is written in C#.
Me: Yeah! Another Simulated Temperature Sensor solution. You: Hold on. Why do you create another one again? Me: Well, mine is more flexible than the existing ones. You: OK. Show me Me: "SendData": true, "SendInterval": 500, "InstanceCount": 10 You: 🥺 Me: This module gives you the flexibility to have multiple sensors sending from one module. This can be configured by the InstanceCount. The existing solution allows you to set the send interval in seconds only.
Today my VisionAI DevKit was not deploying a module. In the logs (sudo journalctl -u iotedge -f) I could see the deployment was received: Successfully pulled image machinelearndfd8df7d.azurecr.io/mobilenetimagenet:3<br>Creating module VisionSampleImagenet…<br>Could not create module VisionSampleImagenet<br>caused by: No such image: machinelearndfd8df7d.azurecr.io/mobilenetimagenet:3 Strange. During troubleshooting I started docker images and saw a lot of older images and versions. After deleting a log of them with docker image rm xyz the deployment succeeded and the module started.