device: fix reconnect #311
Merged
Conversation
This file contains 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
This fix was merged earlier but somehow snuck back. If we reset this flag but don't set the actual UUID to 0, we won't ever request it again and therefore won't ever discover a device again that we have discovered before.
|
Not done on purpose, sorry about that. |
JonasVautherin
approved these changes
Mar 8, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fix was merged earlier but somehow snuck back.
If we reset this flag but don't set the actual UUID to 0, we won't ever
request it again and therefore won't ever discover a device again that
we have discovered before.
This was already removed in #215 but somehow it came back.
@JonasVautherin maybe in a merge? Or was this on purpose?