Daily we are experiencing IOTHUB_CLIENT_CONFIRMATION_MESSAGE_TIMEOUT errors.
We are using the azure-iot-arduino, azure-iot-arduino-protocol-mqtt, azure-iot-arduino-utility repositories and tlsio_mbedtls
Last message in IoTHub:
I (68946033) Statistics: [01-12-17 09:03:22Z] Uptime: 000.19:09:01 IPv4: 192.168.178.92 Free Heap: 63048 Temperature: 67
Three other messages are sent to the Azure IoT Hub, about 3 minutes pass then the Confirmation Message timeout occurs.
Log file
Any idea why this is happening, and or how we can reduce the disconnected time.
In our old issue we noticed a disconnect mqtt message and followed by no activity on the socket. This same problem also occurred after the sas-token lifetime expired(which is now solved). Where the connection would timeout.
Daily we are experiencing IOTHUB_CLIENT_CONFIRMATION_MESSAGE_TIMEOUT errors. We are using the azure-iot-arduino, azure-iot-arduino-protocol-mqtt, azure-iot-arduino-utility repositories and tlsio_mbedtls
Three other messages are sent to the Azure IoT Hub, about 3 minutes pass then the Confirmation Message timeout occurs. Log file
Any idea why this is happening, and or how we can reduce the disconnected time.
In our old issue we noticed a disconnect mqtt message and followed by no activity on the socket. This same problem also occurred after the sas-token lifetime expired(which is now solved). Where the connection would timeout.