AWS IoT Device disconnect

Hello,

Firstly, according to the documentation [1] the disconnectReason: CONNECTION_LOST signifies that "The client-server connection is cut off. This can happen during a period of high network latency or when the internet connection is lost". In simpler terms, it indicates a disruption in communication from the client to the IoT Core over the network.

A possible resolution for this type of disconnect would be to enhance the network route's latency and subsequently ensuring the stability of the internet connection. Therefore, it is advisable to validate the network connectivity, ensuring a consistent and reliable internet connection.

It's worth noting that the timeout problem may be intertwined with network instability, and a specific timeout configuration on the client side [2]. For fundamental troubleshooting of connectivity issues, referencing [3, 4] is recommended, where Device Advisor is suggested in [5]. As per [4], it is also important to adjust your client-side setup to make sure your devices can be automatically reconnected to the AWS IoT after a disconnect event.

References:

[1]. https://docs.aws.amazon.com/iot/latest/developerguide/life-cycle-events.html#connect-disconnect:~:text=CONNECTION_LOST,Yes.

[2] https://docs.aws.amazon.com/iot/latest/developerguide/device-advisor-tests-mqtt.html#connect

[3] https://docs.aws.amazon.com/iot/latest/developerguide/diagnosing-connectivity-issues.html

[4] https://docs.aws.amazon.com/iot/latest/developerguide/ota-troubleshooting-fleet-disconnects.html

[5] https://docs.aws.amazon.com/iot/latest/developerguide/device-advisor.html