This repository has been archived by the owner on Feb 9, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Minimize blocking during multi-wifi reconnect #6
Labels
enhancement
New feature or request
Comments
Hi @jjskaife Thanks for your interest in the library and your good research to understand the internal working of it. I'll certainly make those parameters configurable in the next release, even the configurable parameters are already too many for normal users to handle ;-) I also suggest that you redesign your code to prevent possible issue with any blocking code in the loop(), for example either
Good Luck, |
In the mean time, you can modify the library code as follows to test
then specify somewhere in your code, for example
|
Your contribution has been noted in Contributions and Thanks Releases v1.6.1
|
thanks for the link to your ESP8266TimerInterrupt code. That looks like a great solution. I've been using the blynk timers and will try yours. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
ESP8266
If wifi is lost, the device will wait CONFIG_TIMEOUT until attempting a reconnect. The reconnect (connectMultiWifi) attempts to reconnect a hard coded 10 times (with ~3 second delays).
The problem that I have for a remote IOT device (PID temperature controller, 1 second sampling frequency) is that the reconnect attempts are blocking. the amount of time stuck in reconnect can be significant (at least 60 seconds for minimum 2 reconnect attempts + 30second connect attempt after reset).
Describe the solution you'd like
I'd like the reconnect attempts (connectMultiWifi) to be adjustable (or less) to limit time spent blocking main loop. Currently this is hardcoded.
Describe alternatives you've considered
changing specific hardcoded attempts to a define.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: