Skip to content

Add documentation for new Z-Wave Lock configuration option#6736

Closed
mtreinish wants to merge 3 commits intohome-assistant:nextfrom
mtreinish:zwave-notification-state
Closed

Add documentation for new Z-Wave Lock configuration option#6736
mtreinish wants to merge 3 commits intohome-assistant:nextfrom
mtreinish:zwave-notification-state

Conversation

@mtreinish
Copy link
Copy Markdown
Contributor

Description:
This commit adds documentation around setting the new
use_notification_state configuration option being added to
home-assistant in home-assistant/core#17386

Pull request in home-assistant (if applicable): home-assistant/core#17386

Checklist:

  • Branch: next is for changes and new documentation that will go public with the next home-assistant release. Fixes, changes and adjustments for the current release should be created against current.
  • The documentation follow the standards.

This commit adds documentation around setting the new
use_notification_state configuration option being added to
home-assistant in home-assistant/core#17386
@ghost ghost added the to-do label Oct 13, 2018
@mtreinish mtreinish changed the title Add documentation for new zwave_lock configuration option Add documentation for new Z-Wave Lock configuration option Oct 13, 2018
@frenck frenck added Hacktoberfest An PR on this issue (or the PR itself) is eligible towards Hacktoberfest! new-feature This PR adds documentation for a new Home Assistant feature to an existing integration ready-for-review This PR needs to be reviewed next This PR goes into the next branch has-parent This PR has a parent PR in another repo and removed to-do labels Oct 13, 2018
`use_notification_state` flag for your lock. For example, with an Entity ID for the lock of `lock.my_lock you would set the following in your
`configuration.yaml`:

{% configuration %}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't look like a configuration variable section.

I think you wanted to use

zwave:
 device_config:
   lock.my_lock:
     use_notification_state: true

Copy link
Copy Markdown
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi there, @mtreinish! Thank you for the PR.
I and @tjorim left some comments. Could you please take a look? 👍

@frenck frenck added in-progress This PR/Issue is currently being worked on and removed ready-for-review This PR needs to be reviewed labels Oct 18, 2018
frenck and others added 2 commits October 19, 2018 11:40
@mtreinish
Copy link
Copy Markdown
Contributor Author

@frenck I've updated the PR per the suggestions. Sorry for the delay

@frenck frenck added awaits-parent Awaits the merge of an parent PR and removed in-progress This PR/Issue is currently being worked on labels Oct 21, 2018
@frenck
Copy link
Copy Markdown
Member

frenck commented Oct 21, 2018

✅ Approved. Can be merged as soon as the parent PR gets merged.

@mtreinish
Copy link
Copy Markdown
Contributor Author

No longer using a config option in the parent PR, so the documentation doesn't need to be updated anymore.

@mtreinish mtreinish closed this Nov 4, 2018
@ghost ghost removed the awaits-parent Awaits the merge of an parent PR label Nov 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Hacktoberfest An PR on this issue (or the PR itself) is eligible towards Hacktoberfest! has-parent This PR has a parent PR in another repo new-feature This PR adds documentation for a new Home Assistant feature to an existing integration next This PR goes into the next branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants