[BUG] coreMQTT keep alive handling fails and never reconnects

[lhammond]

Describe the bug
Please provide a clear and concise description explaining the bug.

System information

• Hardware board: [ esp32s3 (Seeed Xiao) ]
• IDE used: [ VSCode ]
• Operating System: [ MacOS ]
• Code version: (v202212.00-23-gd25036b
• Project/Demo: [ Temperature LED demo with AWS pub/sub ]

Expected behavior
Expected behavior would be for the MQTT subsystem to continue retries until reconnected.

Screenshots or console output

Steps to reproduce bug
Example:
1. "I am using project [ ... ], and have configured with [ ... ]"
2. "When run on [ ... ], I observed that [ ... ]"

Code to reproduce bug

idf.py -p /dev/cu.usbmodem14101 flash monitor

[Skptak]

Hey @lhammond, thanks for submitting this issue!
It appears this is an issue many people are running since #41, #45, #46, and #47 all appear to similar issues with the coreMQTT connection to the AWS IoT broker.

I've reached out to the team that works directly with coreMQTT and with the ESP32 boards to see if we can get to the bottom of what is causing these issues.

[lhammond]

Hello :) and thank you. We have a small batch of production hardware that needs this fix and are eager to support resolution. cheers from our team!

…

On Tue, Sep 5, 2023 at 8:12 PM Soren Ptak ***@***.***> wrote: Hey @lhammond <https://github.com/lhammond>, thanks for submitting this issue! It appears this is an issue many people are running since #41 <#41>, #45 <#45>, #46 <#46>, and #47 <#47> all appear to similar issues with the coreMQTT connection to the AWS IoT broker. I've reached out to the team that works directly with coreMQTT and with the ESP32 boards to see if we can get to the bottom of what is causing these issues. — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABYBYUCXHM3V6WUDJPBR7LXY65XFANCNFSM6AAAAAA4MCFBUU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lhammond]

@Skptak Is there anything we can do to help push towards resolution? Should I be monitoring this situation in another place? Thank you!

[rawalexe]

@lhammond,
Can you please give a bit more insight on the problem, what version of esp-idf are you using? have you flashed your credential to the device and is your Thing name and endpoint at the correct account? Did you provision your device?

I was not able to reproduce your problem and here is a small sectional screenshot of my logs

For tour reference I followed this readme: https://github.com/FreeRTOS/iot-reference-esp32c3/blob/2dccbcad1a0e54ec2e32cc242d4bf4f4ab6c1274/GettingStartedGuide.md

[rawalexe]

Can you also please passte your skdconfig file for s3

[gavin-hy]

@rawalexe Have you tested it over a long period of time?
When I tested it, this happened within four hours! When I reconfigured the network it was able to reconnect to broke, but the above problem still occurred after a while. There is another problem. After I unplug the AP's network cable, after a while, I plug it in again and it will no longer be able to actively report information.
Below is a screenshot of my log and sdkconfig.

[lhammond]

Hi @rawalexe you can see the version at the top of this issue thread .. v202212.00-23-gd25036b
I am using the LED pub sub demo, not OTA.

You will see the issue I'm experiencing in the screenshot in the original post. If left alone, the device eventually disconnects and continues to output the "no command structure" forever.

[Skptak]

Hey @lhammond, sorry for the delay in getting back to you. The team has been looking into this issue to try and provide support. I've ordered an ESP32-S3 so I can try and replicate your exact environment as we can't seem to replicate this issue on the ESP32-C3.

While I wait for the board to get here I'm wondering if you tried this potential fix that @ActoryOu mentioned in #46?

It seems like 1 second timeout is not enough for the device to finish TLS flow.
Could you help to set Featured FreeRTOS IoT Integration -> TLS Transport Send / Receive timeout in milliseconds to 10000 by idf.py menuconfig and retest?

I'm wondering if the timeout on the TLS transport send/receives might be what is causing the MQTT agent to go down.

Thanks again for your patience with this!

[lhammond]

@gavin-hy what MCU are you running?

[lhammond]

Hey @Skptak .. I'm away from my lab for a day and will try the potential fix you mention upon return. Thanks!

[gavin-hy]

@gavin-hy what MCU are you running?

ESP32-C3

[rawalexe]

Hi @rawalexe you can see the version at the top of this issue thread .. v202212.00-23-gd25036b I am using the LED pub sub demo, not OTA.

You will see the issue I'm experiencing in the screenshot in the original post. If left alone, the device eventually disconnects and continues to output the "no command structure" forever.

Hello @lhammond and @gavin-hy
I am running all the demos, if you look into my attached screenshot. I'll try to replicate your issue by just running the temp sub pub over long period of time.

[lhammond]

great, thank you very much.

…

On Thu, Sep 14, 2023 at 1:47 PM rawalexe ***@***.***> wrote: Hi @rawalexe <https://github.com/rawalexe> you can see the version at the top of this issue thread .. v202212.00-23-gd25036b I am using the LED pub sub demo, not OTA. You will see the issue I'm experiencing in the screenshot in the original post. If left alone, the device eventually disconnects and continues to output the "no command structure" forever. I am running all the demos, if you look into my attached screenshot. I'll try to replicate your issue by just running the temp sub pub over long period of time. — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABYBYSQFEZZZ566DJEWGRDX2M7MDANCNFSM6AAAAAA4MCFBUU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[anubhavrawal]

@lhammond can you please provide your whole skdconfig file for S3. With your endpoint removed. So that I have a 1-1 for replication your issue for S3.

Thank you,
AR

[rawalexe]

Hello @lhammond @gavin-hy,
I've tried killing the connection and then bring it back up, keeping it alive for long hours and am still not able to reproduce the bug.

Have you changed the code to any degree? Can you please send me a zip of your repo?

Best Regards,
AR