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

Bump ZHA to 0.0.54 #141447

Merged
merged 4 commits into from
Mar 26, 2025
Merged

Conversation

TheJulianJES
Copy link
Member

@TheJulianJES TheJulianJES commented Mar 26, 2025

Proposed change

This bumps ZHA to 0.0.54 (full diff: zigpy/zha@0.0.53...0.0.54). These dependency upgrades are bundled with it:

This ZHA release also massively improves cover handling (thanks to @jeverley), which has been somewhat broken since a long time. See zigpy/zha#376 for details.
The HA tests are updated to account for the correct behavior. There were a lot of issues with these tests that are now fixed (including lift and tilt being swapped before).

This zigpy release also adds application level retrying and opens serial ports exclusively to avoid other processes interrupting ZHA.

This zha-quirks release also adds a few entities via the quirks v2 API. The entity names are added to strings.json.

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:

@home-assistant
Copy link

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

Code owner commands

Code owners of zha 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 zha 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.

Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Thanks, @TheJulianJES 👍

../Frenck

@thecode thecode merged commit 02f8322 into home-assistant:dev Mar 26, 2025
44 checks passed
@frenck frenck removed this from the 2025.4.0b0 milestone Mar 26, 2025
@mikeschmick
Copy link

I'm new here and I'm sure I'm wasting your time. Does this mean that it is "ready to be fixed on next roll out" or that I should already see the fix?

I got here from #98933 and got notice it was marked "Closed".

I still see the "opening" and "closing" stuck and not reporting "closed" or "open" on Aqara E1 Roller Shades.

Thank you for all of your efforts!

@puddly
Copy link
Contributor

puddly commented Mar 26, 2025

@mikeschmick Issues are closed when code is merged into the dev branch and will end up in either the beta or a patch release. These fixes will actually be part of the Home Assistant beta release scheduled for later today. If you want to test it out, please do! https://www.home-assistant.io/common-tasks/os/#running-a-beta-version

@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
7 participants