Migrate Duco to python-duco-connectivity and remove temperature sensors

[ronaldvdmeer]

Note

This PR was created in alignment with @joostlek, who is aware of the changes and indicated that the PR could be submitted in its current form for review.

Breaking change

This PR removes the Duco temperature sensors from Home Assistant. If you currently use the removed temperature entities in dashboards, automations, statistics, or templates, you will need to remove or replace them with a more reliable temperature source. Although the previous integration exposed temperature values, further analysis showed that these readings can differ significantly from the actual room temperature because the sensors can sit close to heat-producing components or be mounted in walls where the surrounding material affects the measurement. Presenting those values as room temperatures is therefore misleading, so the entities are being removed.

Proposed change

This PR migrates the Duco integration from python-duco-client==0.5.0 to python-duco-connectivity==0.2.0 and updates the integration code, diagnostics, system health, and tests to the new library API.

It also removes the Duco box and node temperature entities on purpose. During further analysis it became clear that these values are not reliable enough to present as actual room temperatures because the physical sensor position can skew the readings, for example when a sensor is close to a chip that emits heat or when a unit is built into a wall that influences the measured value.

Removing those entities makes the integration less misleading for users, and the library migration establishes the cleaner, structured base that future Duco work in Home Assistant will build on.

Dependency release notes: https://github.com/ronaldvdmeer/python-duco-connectivity/releases/tag/v0.2.0

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: Remove Duco temperature sensor documentation home-assistant.io#45286
• 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

Migrates the Duco integration from python-duco-client to the newer python-duco-connectivity library and intentionally removes Duco temperature sensor entities to avoid exposing misleading readings.

Changes:

• Switch Duco integration imports/API usage to python-duco-connectivity==0.2.0 and update diagnostics/system health accordingly.
• Remove node and box temperature sensor entities (and related translations/snapshots).
• Update Duco tests/fixtures to reflect the new library and the removed entities.

Reviewed changes

Copilot reviewed 20 out of 20 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
homeassistant/components/duco/__init__.py	Create the Duco client via duco_connectivity (no SSL context construction).
homeassistant/components/duco/config_flow.py	Update config flow validation to use the new client API.
homeassistant/components/duco/coordinator.py	Migrate coordinator to duco_connectivity client/exceptions/models.
homeassistant/components/duco/diagnostics.py	Update diagnostics collection to new exception + write-quota API name.
homeassistant/components/duco/entity.py	Update base entity typing to duco_connectivity Node model.
homeassistant/components/duco/fan.py	Update fan platform imports to new library modules.
homeassistant/components/duco/manifest.json	Swap requirement/loggers to python-duco-connectivity / duco_connectivity.
homeassistant/components/duco/sensor.py	Remove temperature sensor descriptions; adjust ventilation-state enum options.
homeassistant/components/duco/strings.json	Remove sensor translation key for the removed box temperature entity.
homeassistant/components/duco/system_health.py	Update system health to new exception + write-quota API name.
requirements_all.txt	Replace python-duco-client with python-duco-connectivity.
requirements_test_all.txt	Replace python-duco-client with python-duco-connectivity.
tests/components/duco/conftest.py	Update fixtures/models and remove SSL-context patching; update quota API name.
tests/components/duco/test_config_flow.py	Update config flow tests to new client construction (no SSL context).
tests/components/duco/test_diagnostics.py	Update diagnostics tests to new API name and imports.
tests/components/duco/test_fan.py	Update fan tests to new exception import locations.
tests/components/duco/test_init.py	Update setup tests to new client construction and quota API name.
tests/components/duco/test_sensor.py	Remove expectations for temperature entities; update imports/models.
tests/components/duco/test_system_health.py	Update system health test for renamed quota method and exception import.
tests/components/duco/snapshots/test_sensor.ambr	Remove snapshot entries for removed temperature sensors.

[Copilot]

Pull request overview

Copilot reviewed 20 out of 20 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

[Sikerdebaard]

Hi @ronaldvdmeer, @joostlek and HA maintainers,

I'm Thomas Phil, the author of ducopy — the library that the python-duco-client dependency being replaced here is based on.

I want to flag a licensing issue for the record before this PR merges, because it affects the dependency that has been live in Home Assistant releases to date.

The relevant facts:

python-duco-client versions 0.3.7 through 0.5.0 (the version currently pinned in manifest.json as python-duco-client==0.5.0) included a direct copy of the API key generation code from ducopy's apikeygenerator.py, which was first committed to ducopy on 2024-11-02, over 17 months before python-duco-client existed.

The commit that introduced this code into python-duco-client (95717af) contains the message "same algorithm as used in the official ducopy reference library" — an acknowledgment that the code was taken from my library.

Ducopy is licensed under MIT + Commons Clause v1.0. The Commons Clause restricts commercial distribution without written permission from the licensor, and requires that the license notice (including the Commons Clause) be preserved. Neither condition was met in python-duco-client 0.3.7–0.5.0: the Commons Clause was not included, and no permission was sought. An ACKNOWLEDGEMENTS.md was added to the python-duco-client repository only after the code was removed, and only to the git repository — it was never part of any PyPI tarball.

I am not asking this PR to be blocked. Migrating away from python-duco-client is the right outcome, and I support that direction. However, I want the HA maintainers to be aware that:

Every HA release that shipped with python-duco-client==0.5.0 distributed code from my library without a valid license. This is a historical fact that the cleanroom rewrite (python-duco-client==0.5.0 -> python-duco-connectivity==0.2.0 in the manifest file) does not retroactively cure.
If the HA project includes a note in the changelog for the release that removes this dependency — acknowledging the library migration and the licensing situation — I would consider that appropriate recognition of the issue.
I'm happy to answer questions. I wanted to raise this transparently here rather than through other channels, because the HA team deserves to know the full history of the dependency they are replacing.

Sincerely, Thomas Phil (@Sikerdebaard)

Further references:

• License Compliance Violation: Missing Attribution and Commons Clause Non-Compliance ronaldvdmeer/python-duco-client#49