Fix Duco mode end time sensor name

[ronaldvdmeer]

Note

If appropriate, could this follow-up Duco bugfix be included in milestone 2026.6.1? When the ventilation state sensor naming was updated, this related time_state_end sensor rename should have been included as well, but was missed.

Proposed change

This PR fixes the remaining Duco timestamp sensor name so it stays consistent with the renamed ventilation state sensor.

The time_state_end entity currently still uses Mode end time, while the related enum sensor uses Ventilation state. This follow-up renames the timestamp sensor to State end time so both entities reflect the same state model.

This should ideally be considered for the first milestone as a small bugfix follow-up. When the ventilation state sensor naming was adjusted, this companion timestamp sensor should have been renamed in the same change but was missed.

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: follow-up to PR Use Duco state codes for ventilation state labels #172314
• Link to documentation pull request: current: Fix Duco state end time sensor name in docs home-assistant.io#45754, next: Fix Duco state end time sensor name in next docs home-assistant.io#45757
• 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

Note

Copilot was unable to run its full agentic suite in this review.

This PR renames the Duco sensor entity "Mode end time" to "State end time" to better align the user-facing name with the underlying key time_state_end defined in strings.json.

Changes:

• Renamed the time_state_end sensor's display name from "Mode end time" to "State end time" in the strings file.
• Updated test snapshots to reflect the new entity name and derived entity IDs.

Reviewed changes

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

File	Description
homeassistant/components/duco/strings.json	Renames the time_state_end sensor label from "Mode end time" to "State end time".
tests/components/duco/snapshots/test_sensor.ambr	Updates snapshot expectations for the renamed sensor entity, including entity_id, friendly_name, and object_id_base.

[TheJulianJES]

I think this is fine to include. Due to how translations work, they end up in patch releases anyway, even if they're not tagged – so we may as well include this in the release notes by tagging it.

Thanks!

[jbouwh]

LGTM,
Thanks @ronaldvdmeer 👍