Skip to content

Add vera config entries support#29880

Merged
MartinHjelmare merged 21 commits intohome-assistant:devfrom
vangorra:vangorra_vera_config_entries
Apr 3, 2020
Merged

Add vera config entries support#29880
MartinHjelmare merged 21 commits intohome-assistant:devfrom
vangorra:vangorra_vera_config_entries

Conversation

@vangorra
Copy link
Copy Markdown
Contributor

@vangorra vangorra commented Dec 12, 2019

Breaking Change:

None

Description:

Adding config entries support to vera component.

Related issue (if applicable): None

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#11663

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist

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

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

  • The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

Comment thread homeassistant/components/vera/common.py Outdated
@MartinHjelmare MartinHjelmare changed the title Adding vera config entries support. Add vera config entries support Dec 12, 2019
Comment thread homeassistant/components/vera/common.py Outdated
Comment thread homeassistant/components/vera/common.py
Copy link
Copy Markdown
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

We also need tests for the config flow.

Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/common.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
@frenck
Copy link
Copy Markdown
Member

frenck commented Dec 15, 2019

Added the docs-missing label. Documentation needs to be adjusted for this change.

@frenck
Copy link
Copy Markdown
Member

frenck commented Dec 15, 2019

Thank you for your contribution thus far! 🎖 Since this is a significant contribution, we would appreciate you'd added yourself to the list of code owners for this integration. ❤️

Please, add your GitHub username to the manifest.json of this integration.

For more information about "code owners", see: Architecture Decision Record 0008: Code owners.

Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread homeassistant/components/vera/__init__.py Outdated
@vangorra
Copy link
Copy Markdown
Contributor Author

@frenck What sorts of documentation are needed? This change only adds config entries support, it doesn't change the config structure for the component.

@springstan
Copy link
Copy Markdown
Member

@vangorra I think the smartthings integration documentation is a good example for that.
Hope this helps you :)

@vangorra
Copy link
Copy Markdown
Contributor Author

The vera integration already has sufficient documentation here: https://www.home-assistant.io/integrations/vera/
I don't see how this change would effect the existing documentation.

@vangorra
Copy link
Copy Markdown
Contributor Author

What additional changes are needed? The documentation request is not particularly clear.

@cogneato
Copy link
Copy Markdown

cogneato commented Dec 29, 2019

You would want to add that is is available as an integration like the smartthings example provided earlier.

Comment thread homeassistant/components/vera/config_flow.py
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread homeassistant/components/vera/__init__.py
Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread homeassistant/components/vera/__init__.py Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread tests/components/vera/test_init.py Outdated
Comment thread tests/components/vera/test_init.py Outdated
Comment thread tests/components/vera/test_init.py Outdated
Comment thread homeassistant/components/vera/strings.json Outdated
Comment thread homeassistant/components/vera/config_flow.py Outdated
@stale
Copy link
Copy Markdown

stale Bot commented Mar 21, 2020

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

@stale stale Bot added the stale label Mar 21, 2020
Copy link
Copy Markdown
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

Please rebase on latest dev branch.

Comment thread homeassistant/components/vera/config_flow.py Outdated
Comment thread tests/components/vera/test_init.py Outdated
Comment thread tests/components/vera/test_init.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread tests/components/vera/test_config_flow.py Outdated
Comment thread tests/components/vera/common.py Outdated
Comment thread homeassistant/components/vera/strings.json Outdated
Copy link
Copy Markdown
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

Great!

@MartinHjelmare MartinHjelmare merged commit ae22b51 into home-assistant:dev Apr 3, 2020
@mrand
Copy link
Copy Markdown

mrand commented Apr 3, 2020

I'm sorry, I can't determine - will the integration import existing yaml configs? Will entity id's be the same with the integration as they were with yaml configs? If not, and there is no way to migrate, I hope this gets extra bold notes in the breaking changes because people with large Z-wave networks will need to plan for such a big change.

@vangorra
Copy link
Copy Markdown
Contributor Author

vangorra commented Apr 3, 2020

This integration WILL import existing yaml configs. Entity ids WILL remain the same as they always have. No breaking changes.

@vangorra vangorra deleted the vangorra_vera_config_entries branch April 3, 2020 13:44
@lock lock Bot locked and limited conversation to collaborators Apr 4, 2020
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.

7 participants