Add loop_start to ensure all messages are published #52
Conversation
This file contains hidden or 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
1 participant
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.
I was having an issue where I could see all the messages being published in the debug logs but not all the messages made it to the broker. When using the
--allflag the first few messages would make it but I would only get down to temperature messages occasionally. The MQTT broker would logSocket error on client <client id>, disconnecting.presumably before the client finished publishing all messages. This was happening over a somewhat compromised WiFi connection on older hardware.Adding
loop_start()resolved the issue for me. I'm now getting all data and I no longer get errors in the broker log.