Skip to content
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

Add zwave_js.bulk_set_partial_config_parameters service #48306

Merged
merged 4 commits into from
Mar 30, 2021

Conversation

raman325
Copy link
Contributor

@raman325 raman325 commented Mar 25, 2021

Proposed change

Adds a new service called zwave_js.bulk_set_partial_config_parameters. We had originally discussed extending the existing zwave_js.set_config_parameter service to support this functionality, but it's cleaner to keep it as a separate service and we can document it as being for advanced use. The service accepts either a raw integer value to use for the entire parameter or a mapping of bitmasks to values. In the latter case, the library will calculate the correct integer value to send.

This must follow #48094

Additional resources for background:

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

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.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

To help with the load of incoming pull requests:

@raman325 raman325 force-pushed the bulk_set_config_parameter branch from 6f6ab61 to 1d57129 Compare March 29, 2021 20:30
@raman325 raman325 marked this pull request as ready for review March 29, 2021 20:30
@raman325 raman325 requested a review from MartinHjelmare March 29, 2021 20:32
@balloob
Copy link
Member

balloob commented Mar 29, 2021

Do we still need this when we add #48134 ?

@raman325
Copy link
Contributor Author

Do we still need this when we add #48134 ?

Yes because some devices require multiple partial parameters to be set at the same time, e.g. in a single call

Copy link
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.

Looks good!

@raman325 raman325 merged commit 9a75019 into home-assistant:dev Mar 30, 2021
@raman325 raman325 deleted the bulk_set_config_parameter branch March 30, 2021 03:07
@github-actions github-actions bot locked and limited conversation to collaborators Mar 31, 2021
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.

4 participants