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

Adding support for new Lutron RGB tape light #130731

Open
wants to merge 11 commits into
base: dev
Choose a base branch
from

Conversation

RBaragona
Copy link

@RBaragona RBaragona commented Nov 16, 2024

Proposed change

Add support for new device type in Lutron-Caseta to enable support of new color and tunable white products.

Supported by integration via #134906

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)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

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
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format 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.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copy link

@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

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

Hi @RBaragona

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@home-assistant home-assistant bot marked this pull request as draft November 16, 2024 05:19
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@home-assistant
Copy link

Hey there @swails, @danaues, @eclair4151, mind taking a look at this pull request as it has been labeled with an integration (lutron_caseta) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of lutron_caseta can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign lutron_caseta Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@eclair4151
Copy link
Contributor

Also to confirm, you'll need to wait until your pylutron-caseta PR Is merged, then raise 2 PRs here, the first just bumping the Python library version, and this is the second PR which can be merged after the first is merged.

@RBaragona
Copy link
Author

I agree and will link once the pylutron-caseta PR is merged.

Update logic based on device types supporting warm dim and spectrum tune color.
@eclair4151
Copy link
Contributor

@RBaragona I raised the PR for bumping the pylutron version
#134906

@RBaragona RBaragona marked this pull request as ready for review January 7, 2025 03:12
@home-assistant home-assistant bot requested a review from eclair4151 January 7, 2025 03:12
@RBaragona
Copy link
Author

@eclair4151 , I have tested and verified control with hardware as well.

@RBaragona RBaragona changed the title Adding support for new Lutron color tuning device, Supported via https://github.com/gurumitts/pylutron-caseta/pull/177 Adding support for new Lutron RGB tape light Jan 8, 2025
self.supports_warm_dim = light_type == DEVICE_TYPE_SPECTRUM_TUNE
self.supports_spectrum_tune = light_type == DEVICE_TYPE_SPECTRUM_TUNE
self.supports_warm_cool = self.supports_warm_dim = (
light_type in WARM_DEVICE_TYPES
Copy link
Contributor

@eclair4151 eclair4151 Jan 9, 2025

Choose a reason for hiding this comment

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

This is fine with me, but when I originally wrote the PR for ketra color, I was told not to let DEVICE_TYPE_WHITE_TUNE support Warm Dim this way, because Warm Dim should be controlled by a custom device feature, not using the built in 'white mode' as that was meant for something else.

I do have plans to raise another PR to move warm dim from white mode into its own feature, but if we are ok with making DEVICE_TYPE_WHITE_TUNE (light with temp control only, not RGB) supporting warm dim via white mode, then this is fine.

Copy link
Author

Choose a reason for hiding this comment

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

Based on that previous feedback and your planned future work, I'd like to propose I roll this back. Any concerns @joostlek ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants