skip to Main Content

Debian – Azure IoTEdge – Custom IoTEdge module unable to connect to Hub with Communication_Error

Our custom IoTEdge module was functioning correctly until recently, when it started experiencing loss of connectivity, with our ConnectionStatusChangeHandler reporting status "ConnectionStatus.Disconnected" and reasons "ConnectionStatusChangeReason.Retry_Expired" and ConnectionStatusChangeReason.Communication_Error". The handler triggers re-initialization of the client as per recommended practices, but the…

VIEW QUESTION

Azure: Subscribing to an external MQTT Broker

One of our customers has MQTT brokers with https://www.emqx.com/ which we need to consume in Azure. Previously we had used Azure Functions with an MQTT trigger on (https://github.com/keesschollaart81/CaseOnline.Azure.WebJobs.Extensions.Mqtt) However, this library is now pretty old and we need to move…

VIEW QUESTION

Azure IoT Edge device not connecting to IoT Hub

I followed this tuturial to the tee: https://learn.microsoft.com/en-us/azure/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric?view=iotedge-1.4&tabs=azure-portal but I'm getting errors I don't know how to resolve here are some: running command iotedge system logs -- -f running command iotedge check --verbose In Azure Clicking on "Error" I get:…

VIEW QUESTION
Back To Top
Search