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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Color Palette Select entities to WLED #51994

Merged
merged 2 commits into from Jun 24, 2021
Merged

Add Color Palette Select entities to WLED #51994

merged 2 commits into from Jun 24, 2021

Conversation

frenck
Copy link
Member

@frenck frenck commented Jun 18, 2021

Proposed change

This adds the select platform to WLED, providing controls to select the color palette.

image

image

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

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:

@frenck
Copy link
Member Author

frenck commented Jun 19, 2021

The whole master light stuff of WLED bites me with this PR, as this palette entity only applies to segments, and segments can be dynamic.

This means those segment lights and this select is appearing when segments are created, but also completely removed when the segment is removed.

When this entity is disabled by default, testing the dynamic part becomes really problematic. As stuff, just all of a sudden disappears.

This made me realize that this is not only really bad for testing, but also really bad for the user. Customizations on entities are fully lost is a segment is removed. This is not correct.

Reworking that part now first, before finishing this one.

@frenck
Copy link
Member Author

frenck commented Jun 24, 2021

Done. Updated with dev, the palette selects are available, but disabled by default.

@frenck frenck marked this pull request as ready for review June 24, 2021 11:13
Dev automation moved this from Needs review to Reviewer approved Jun 24, 2021
@balloob balloob merged commit fba7118 into dev Jun 24, 2021
@balloob balloob deleted the frenck-2021-1823 branch June 24, 2021 18:25
Dev automation moved this from Reviewer approved to Done Jun 24, 2021

# Process new segments, add them to Home Assistant
for segment_id in segment_ids - current_ids:
current[segment_id] = WLEDPaletteSelect(coordinator, segment_id)
Copy link
Member

Choose a reason for hiding this comment

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

There's no reason to store the entity. It's enough to store the segment id in a set.

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah, that is a nice more generic improvement, thanks! 馃憤

@github-actions github-actions bot locked and limited conversation to collaborators Jun 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Dev
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

4 participants