8000 Add network_key as a config option by robbiet480 · Pull Request #7637 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add network_key as a config option #763 8000 7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 19, 2017

Conversation

robbiet480
Copy link
Member

Description:

Related issue (if applicable): fixes #7635

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>

Example entry for configuration.yaml (if applicable):

Checklist:

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • New dependencies have been added to the REQUIREMENTS variable (example).
  • New dependencies are only imported inside functions that use them (example).
  • New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
  • New files were added to .coveragerc.

If the code does not interact with devices:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • Tests have been added to verify that the new code works.

@mention-bot
Copy link

@robbiet480, thanks for your PR! By analyzing the history of the files in this pull request, we identified @turbokongen, @balloob and @andrey-git to be potential reviewers.

Copy link
Contributor
@andrey-git andrey-git left a comment

Choose a reason for hiding this comment

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

Whoever uses this less the ability to use ozwcp with secure devices, right?

@balloob
Copy link
Member
balloob commented May 18, 2017

@andrey-git I think it depends on where the network key gets passed into OZWCP ?

@balloob
Copy link
Member
balloob commented May 19, 2017

So I am going to merge this as it's an opt-in and won't brake anything else. We'll continue the discussion in the issue.

@balloob balloob merged commit 7daa922 into home-assistant:dev May 19, 2017
balloob pushed a commit that referenced this pull request May 19, 2017
* Add network_key as a config option

* Update __init__.py
@balloob
Copy link
Member
balloob commented May 19, 2017

Cherry-picked for 0.45

@balloob
Copy link
Member
balloob commented May 20, 2017

We're going to revert this. Instead have users copy options.xml to their config folder.

Update: leaving this for now, promoting options.xml in the future.

@balloob balloob mentioned this pull request Jun 2, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Sep 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow setting Z-Wave network key via options
5 participants
0