8000 Bump flux_led to 0.27.42 to fix missing CW/WW channels on 0x25 devices by bdraco · Pull Request #63651 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bump flux_led to 0.27.42 to fix missing CW/WW channels on 0x25 devices #63651

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

Conversation

bdraco
Copy link
Member
@bdraco bdraco commented Jan 8, 2022

Proposed change

  • Fixes RGB/WW/CW controller operating mode not being detected after
    a factory reset.

  • When the device is factory reset or setup for the first time the operating
    mode is reported as 0 and its expected the user will set it in the
    Magic Home app. If they skip that step Home Assistant will never be able
    to figure out which operating mode the device is using and the CW and WW
    channels will not work even though the device will operate in RGBWW mode.

  • Changelog: lightinglibs/flux_led@0.27.41...0.27.42

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

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

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.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • 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:

- Fixes RGB/WW/CW controller operating mode not being detected after
  a factory reset.

- When the device is factory reset or setup for the first time the operating
  mode is reported as 0 and its expected the user will set it in the
  Magic Home app. If they skip that step Home Assistant will never be able
  to figure out which operating mode the device is using and the CW and WW
  channels will not work.

- Changelog: lightinglibs/flux_led@0.27.41...0.27.42
@probot-home-assistant
Copy link

Hey there @icemanch, mind taking a look at this pull request as it has been labeled with an integration (flux_led) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)

@balloob balloob merged commit 0b67d7f into home-assistant:dev Jan 8, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jan 9, 2022
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.

3 participants
0