Add target temp range to water heater #2720

gjohansson-ST · 2025-07-07T18:43:02Z

Proposed change

Adds target_temperature_range capability for water_heater
Core PR: home-assistant/core#148222

Type of change

Document existing features within Home Assistant
Document new or changing features for which there is an existing pull request elsewhere
Spelling or grammatical corrections, or rewording for improved clarity
Changes to the backend of this documentation
Remove stale or deprecated documentation

Checklist

I have read and followed the documentation guidelines.
I have verified that my changes render correctly in the documentation.

Additional information

This PR fixes or closes issue: fixes #
Link to relevant existing code or pull request: #148222

Summary by CodeRabbit

New Features
- Water heater entity now supports setting a temperature range in addition to single target temperatures via the new TARGET_TEMPERATURE_RANGE feature.
Documentation
- Added documentation and blog post detailing the expanded water heater temperature range capabilities and usage examples.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2025-07-07T18:45:24Z

📝 Walkthrough

Walkthrough

Documentation updates for water heater entity to document support for setting temperature ranges. Includes updates to the feature documentation table and a new blog post demonstrating the TARGET_TEMPERATURE_RANGE feature with code examples.

Changes

Cohort / File(s)	Summary
Documentation Updates `docs/core/entity/water-heater.md`	Added TARGET_TEMPERATURE_RANGE to Supported features table with description; updated set_temperature method documentation to indicate it can set single temperature or temperature range.
Blog Post `blog/2025-12-01-water-heater-now-supports-set-a-temp-range.md`	New blog post documenting WaterHeaterEntity temperature range feature; includes front matter and Python example using ATTR_TARGET_TEMP_LOW and ATTR_TARGET_TEMP_HIGH attributes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

No code changes; documentation and blog content only
Simple feature documentation additions and formatting adjustments

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding target temperature range support to the water heater documentation.
Description check	✅ Passed	The description follows the template structure with all required sections completed, including a clear proposed change, type of change selection, checklist items, and relevant links to the core PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch gj-20250707-01

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 2

🧹 Nitpick comments (2)

docs/core/entity/water-heater.md (1)

62-62: Use imperative mood in method description

Microsoft style: start with the goal.
Change to “Set the temperature or temperature range the water heater heats water to.”

blog/2025-07-07-water-heater-now-supports-set-a-temp-range.md (1)

11-12: Grammar—plural agreement

“Entities needs to set” → “Entities need to set” (or “Entities must set” for stronger imperative).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 8de9ba5 and e86c6f9.

📒 Files selected for processing (2)

blog/2025-07-07-water-heater-now-supports-set-a-temp-range.md (1 hunks)
docs/core/entity/water-heater.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (6)

`*/**(html|markdown|md)`: - For instructional content in documentation, use a di...

*/**(html|markdown|md): - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted.

Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness.

In step-by-step instructions, front the location phrase in the instructional sentence.

In step-by-step instructions, front the 'goal' in the instructional sentence.

In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence.

do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner'