make MAX_TRIES configurable #2469
Open
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
2 participants
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've been experiencing issues with my Z-wave network: Every once in a while, a message will randomly timeout, most often when sending multiple messages at a time (https://groups.google.com/g/openzwave/c/Jcw-wn2i4FI).
I've not been able to find root cause of the issue, so as a workaround, I have shortened the timeout. This solved the "network freezing for 10 seconds" issue, but the problem is that dropped message could leave my system in inconsistent state. So I've also decided to enable retries.
Unfortunately, there has been no config option for retries until now. Option has only been hardcoded. This PR fixes this.