8000 Use runtime_data in melcloud by epenet · Pull Request #148012 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Use runtime_data in melcloud #148012

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
merged 2 commits into from
Jul 3, 2025
Merged

Use runtime_data in melcloud #148012

merged 2 commits into from
Jul 3, 2025

Conversation

epenet
Copy link
Contributor
@epenet epenet commented Jul 3, 2025

Proposed change

SSIA

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

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend 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
  • 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:

@Copilot Copilot AI review requested due to automatic review settings July 3, 2025 06:10
@home-assistant
Copy link
home-assistant bot commented Jul 3, 2025

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

Code owner commands

Code owners of melcloud 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 melcloud 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
Contributor
@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR refactors the MelCloud integration to use the new entry.runtime_data API instead of storing devices in hass.data. It introduces a typed alias for the config entry, updates all platforms to pull from runtime_data, and cleans up the unload logic.

  • Define MelCloudConfigEntry alias and assign fetched devices to entry.runtime_data
  • Update async_setup_entry in climate, sensor, water_heater, and diagnostics to use runtime_data
  • Simplify async_unload_entry by removing manual hass.data cleanup

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
__init__.py Add MelCloudConfigEntry alias; set and stop using hass.data; simplify unload
climate.py Update imports and async_setup_entry to use entry.runtime_data
sensor.py Remove DOMAIN usage; update imports and setup to use runtime_data
water_heater.py Update imports and async_setup_entry to consume entry.runtime_data
diagnostics.py Switch diagnostics helper to accept MelCloudConfigEntry and drop ConfigEntry import
Comments suppressed due to low confidence (2)

homeassistant/components/melcloud/water_heater.py:33

  • The docstring mentions climate setup in the water_heater module. Update it to reflect water heater entity setup for clarity.
    """Set up MelCloud device climate based on config_entry."""

homeassistant/components/melcloud/water_heater.py:34

  • Consider adding a test for async_setup_entry to verify that entry.runtime_data is correctly populated and consumed by the water heater platform.
    mel_devices = entry.runtime_data

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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, @epenet 👍

../Frenck

@frenck frenck merged commit e422352 into dev Jul 3, 2025
33 of 34 checks passed
@frenck frenck deleted the epenet-20250703-0808 branch July 3, 2025 06:57
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.

2 participants
0