fix: connect failed - no CPU time for IP stack#1050
Open
devmirek wants to merge 1 commit intoknolleary:masterfrom
Open
fix: connect failed - no CPU time for IP stack#1050devmirek wants to merge 1 commit intoknolleary:masterfrom
devmirek wants to merge 1 commit intoknolleary:masterfrom
Conversation
Author
|
I would prefer yield() as well. I have tested it with yield() first. It didn't work. Small delay was the only option that reliably solved it (ESP32-C3 with WiFiClientSecure). It was a very tricky issue because sometimes it was successfully reconnected (CONNACK was received after reconnection) but the first connect always failed and sometimes the next reconnects randomly failed as well - always due to CONNACK timeout. |
devmirek
changed the title
|
@devmirek Can you reproduce the problem with https://github.com/hmueller01/pubsubclient3 ? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ESP32-C3 is not able to receive CONNACK packet because the waiting loop did not have any delay to let other tasks to process incoming TCP packet data.