Bugfix[zwave][lock]Wrong info in discovery schema#6779
Merged
Conversation
|
@turbokongen, thanks for your PR! By analyzing the history of the files in this pull request, we identified @balloob and @andrey-git to be potential reviewers. |
Contributor
|
John, do you have such a lock? |
Contributor
Author
|
Yes I do. There was no value passed in, because the label: Access Control is not present in the config option. |
andrey-git
approved these changes
Mar 25, 2017
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Description:
The config option value to detect what type of report was active for Danalock V2BTZE, had wrong info in discovery schema.