-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
If the MQTT server is offline #429
Comments
This is a known bug with the libraries, see the troubleshooting page.
unfortunantly, there isn't really any work-around.
|
Or disable mqtt when on the road. |
But then I have to log in to the wemos every time i use the heater to turn off the MQTT. |
I'd suggest |
Option C is already implemented. Considering the amount of inconvenience people have with the retry timeout I'll introduce a command to change the 10 seconds to a higher value and leave the consequences to the user. |
Yes you are correct (of course :) It does raise an interesting question though, if wifi is not connected why does try connect and stall? Could be related to this arduino issue where still reports connected but RSSI =0 is it is disconnected? arduino-libraries/WiFi101#86 |
I don't think the arduino-esp8266 project is using wifi101. |
Perfectly resolved in v5.0.6 |
5.0.6 20170510 * Remove hyphen in case of a single DHT sensor connecetd (arendst#427) * Add command MqttRetry <seconds> to change default MQTT reconnect retry timer from minimal 10 seconds (arendst#429)
I have a Wemos D1 in my car.
There are 4 relay modules connected and 4 physical buttons.
If the temperature is below 4 degrees, the wemos turn on the webasto (heater) in my car.
But if I'm on my way and I want to turn on the webasto with the physical button I have to press a few times before the Wemos responds. This is because the MQTT server is not found on the way.
How can I bypass the wemos waiting and giving a timeout if the MQTT server is not online?
The text was updated successfully, but these errors were encountered: