New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable wifiManager.setConfigPortalTimeout(xxxx) to avoid OMG issues after a MQTT server restart #350

Closed
ctripodi opened this Issue Jan 25, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@ctripodi
Copy link

ctripodi commented Jan 25, 2019

Hello @1technophile , I has been using this excellent project for the last year. (modules enabled RF433, BT, IR, DHT)
It is working fine, however I could see that sometimes after a power blackout, OMG start more quickly that the MQTT server, so, OMG start the configuration portal, and stay in this status, until a new restart of OMG.
So, I guess that maybe you can add this setting to your code wifiManager.setConfig Portal Timeout(your_config_seconds);
Regards.

@odis68

This comment has been minimized.

Copy link

odis68 commented Jan 26, 2019

I also watch it.

@1technophile 1technophile added this to the V0.9 milestone Jan 27, 2019

@1technophile

This comment has been minimized.

Copy link
Owner

1technophile commented Jan 31, 2019

done

1technophile added a commit that referenced this issue Jan 31, 2019

add wifimanager config portal timeout
#350 in case of power outage so as to avoid to pop up the web page before the mqtt server restart
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment