(wlan): Use time delay instead of retires to determine fallback AP start #190
Conversation
This file contains 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
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.
Use time delay of >120s after boot instead of number of retires to determine start of fallback AP if initial connection cannot be established (e.g. due to wrong password)
--> This ensures a minimum retry time frame completly independend of underlaying reconnect cycle which could be different on different hardware or ESP-IDF releases
Hardcoded: 120s
Note 1: The actual time is not exactly 120s --> it's 120 seconds plus the time until next connection retry.
Note 2: Optimizes initial implementation of #186