Skip to content

ClientContext: break timeout delays also on error while writing or connecting #6454

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

Merged
merged 2 commits into from
Aug 27, 2019

Conversation

d-a-v
Copy link
Collaborator

@d-a-v d-a-v commented Aug 26, 2019

closes and replaces #6440
fixes arendst/Tasmota#1992 (comment)

@ascillato @mike2nl @Jason2866 Can you check this one ?

edit:
This PR stops the 1ms-delay loop also when a tcp error occurs (previously this was done only when tcp had just connected or a write/send had succeeded).
The tcp error can be any, in this case with pubsubclient it is "connection refused" after the mqtt server disappeared and pubsubclient tries to reconnect.

@ascillato
Copy link
Contributor

Hi,

Tested and works!!!!

Please, merge this PR. Thanks a lot. Great work 👍

@d-a-v d-a-v merged commit 0937b07 into esp8266:master Aug 27, 2019
@d-a-v d-a-v deleted the cc-err-reschedule branch August 27, 2019 13:26
Jason2866 referenced this pull request in letscontrolit/ESPEasy Aug 27, 2019
[LoRa/TTN] Add raw packed decoder (more values, less data) & reduce joins
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Lag when MQTT Server is down (possible workaround)
2 participants