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

Revert "Bump pydaikin 2.9.1 (#93635)" #94469

Merged
merged 1 commit into from Jun 12, 2023
Merged

Conversation

mover85
Copy link
Contributor

@mover85 mover85 commented Jun 12, 2023

Proposed change

Reverts #93635.

The above PR uncovered a few issues which caused some units to not function correctly.

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

To help with the load of incoming pull requests:

@home-assistant
Copy link

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

Code owner commands

Code owners of daikin 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 daikin Removes the current integration label and assignees on the pull request, add the integration domain after the command.

@mover85
Copy link
Contributor Author

mover85 commented Jun 12, 2023

@fredrike @MartinHjelmare I have recreated my branch

@emontnemery emontnemery merged commit eb0485e into home-assistant:dev Jun 12, 2023
51 checks passed
@emontnemery emontnemery added this to the 2023.6.2 milestone Jun 12, 2023
@emontnemery
Copy link
Contributor

emontnemery commented Jun 12, 2023

Tagged for 2023.6.2 since pydaikin 2.9.1 is in HA Core 2023.6.0

@barshow
Copy link

barshow commented Jun 12, 2023

I would love to bump to the latest version since 2.9.0 has a bug where units will not set to off with scene recalling.

#94214

@github-actions github-actions bot locked and limited conversation to collaborators Jun 13, 2023
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.

Daikin service climate.turn_on not working
5 participants