Bump letpot to 0.7.0

[jpelgrom]

Proposed change

Bump letpot to 0.7.0:

• Changelog https://github.com/jpelgrom/python-letpot/releases/tag/v0.7.0
• Diff jpelgrom/python-letpot@v0.6.4...v0.7.0

This version introduces support for an entirely new category of devices: watering systems/drip irrigation. I've made the necessary changes to the integration to keep it working and not introduce new features yet:

• Updated the integration setup to only create coordinators for hydroponic gardens (= previously the only supported device category)
• Adjust typing where necessary, making it generic to be able to support watering systems in the future (this is heavily inspired by how the eheimdigital integration handles this)

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

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[Copilot]

Pull request overview

This PR updates the LetPot integration to work with python-letpot v0.7.0, which introduces additional device categories (e.g., watering systems), while keeping Home Assistant’s integration behavior scoped to hydroponic gardens for now.

Changes:

• Bump letpot dependency to 0.7.0 across the manifest and requirements files.
• Adjust integration setup/runtime data to only create coordinators for garden devices (and keep room for watering systems later).
• Refactor entity/coordinator typing to be more generic in preparation for multi-device-category support.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
homeassistant/components/letpot/manifest.json	Bumps integration dependency to letpot==0.7.0.
requirements_all.txt	Updates global pinned dependency for letpot to 0.7.0.
requirements_test_all.txt	Updates test pinned dependency for letpot to 0.7.0.
homeassistant/components/letpot/__init__.py	Filters setup to garden devices only and stores coordinators in a new runtime-data container.
homeassistant/components/letpot/coordinator.py	Introduces coordinator container dataclass and generic coordinator base, plus garden/watering coordinator types.
homeassistant/components/letpot/entity.py	Makes the base entity generic over status type to support multiple device categories.
homeassistant/components/letpot/binary_sensor.py	Switches platform setup to coordinators.gardens and introduces generic entity/description typing.
homeassistant/components/letpot/sensor.py	Switches platform setup to coordinators.gardens and introduces generic entity/description typing.
homeassistant/components/letpot/number.py	Switches platform setup to coordinators.gardens and introduces generic entity/description typing.
homeassistant/components/letpot/select.py	Switches platform setup to coordinators.gardens and introduces generic entity/description typing.
homeassistant/components/letpot/switch.py	Switches platform setup to coordinators.gardens and introduces generic entity/description typing.
homeassistant/components/letpot/time.py	Switches platform setup to coordinators.gardens and introduces generic entity/description typing.
tests/components/letpot/__init__.py	Updates test fixtures to use the new garden-status model type.

[jpelgrom]

Not sure how to address this. Changing the exception handler to use LetPotEntity[LetPotDeviceStatus] will create new mypy errors because the individual entities use a subclass of the status model. Changing the exception handler to use LetPotEntity[Any] works but that still results in losing type safety. The type isn't used in the exception handler so Any might be fine if there's no alternative.

[joostlek]

Can we split the new coordinator from the dependency bump?

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[jpelgrom]

Can we split the new coordinator from the dependency bump?

What do you mean with new coordinator?

The actual coordinator hasn't changed, only typing. LetPotGardenCoordinator is a very small description to make things nice but isn't really doing anything other than documenting and could theoretically be replaced by LetPotDeviceCoordinator[LetPotGardenStatus].

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[jpelgrom]

Test failure appears to be unrelated (timeout installing OS dependencies).