chore: release notes for v2.4.2-beta.3 and the 24-hour energy cap - #295
Merged
Conversation
The base version is unchanged, so manifest.json and the CHANGELOG and README headings stay at 2.4.2 as the beta process requires. This adds the user-facing entries for what landed since beta.2. CHANGELOG gains the energy freeze (#292/#294), the energy decrease warnings (#286), the outdoor-temperature poll warnings and diagnostics stamp (#287), and the unrecognised-fan-speed behaviour (#291). The fan speed sensor itself (#285) was already recorded. README's "What's New" leads with the energy freeze, since it is the one item that silently affected every user, and the new fan speed sensor. docs/api/melcloudhome-telemetry-endpoints.md now records the endpoint's 24-hour truncation next to the parameters it contradicts. That doc described `from` and `to` as if both were honoured, which is what made the freeze hard to see. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Features before fixes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #295 +/- ##
=======================================
Coverage 93.45% 93.45%
=======================================
Files 44 44
Lines 2963 2963
=======================================
Hits 2769 2769
Misses 194 194
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Review of the notes rather than new content. Corrections first: The "Actual fan speed" behaviour for an unrecognised value sat under Changed, but the sensor has never shipped, so there was no prior behaviour to change. Folded into its Added entry. The bullet on state changes opened "Because that ..." and only parsed if you had already read a different section, and it credited outdoor temperature sensors with a change they have had since v2.4.0. Both fixed, the outdoor attribution stated rather than dropped, since that was never called out at the time. Two other bullets referred to "the new source" and "a live one" without naming either, and (#262) had been lost. All restored. Then length. The [2.4.2] bullets ran at a median of 70 words against 12 for every other release in the file, with one at 154. Now 44. What went is mechanism a reader cannot act on, which the linked issues hold; what stayed is every instruction and issue reference. Bold lead-ins dropped: they marked five of sixteen entries with no criterion anyone could state, and no release since 2.4.0 uses them. README's What's New carried six paragraphs for the three things a reader does something about. Three now, plus an "Also in this release" sentence in the v2.4.0 form for the rest, and the changelog link restored to its own paragraph. The fan speed contributor is credited in both files in each file's existing form. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
andrew-blake
added a commit
that referenced
this pull request
Sep 1, 2026
The unreleased section adds a new sensor entity, last-reading timestamps and automation-visible behaviour changes, and removes phantom ATW sensors; under the semver adherence the changelog header declares, that is a minor release, not a patch. The 2.4.2-beta.* pre-releases stay published and order correctly below 2.5.0 in HACS, so beta installs upgrade cleanly. Also restores the changelog H1, which #295 left indented six spaces so GitHub rendered it as a code block. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release notes for the v2.4.2-beta.3 tag, plus a review of the existing ones.
The unrecognised-fan-speed behaviour sat under Changed for a sensor that has never shipped, and is now part of its Added entry. The state-change bullet credited outdoor temperature sensors with a change they have had since v2.4.0; the entry now says so, because it was never called out at the time.
The remaining edits are length and formatting. Bullets ran at a median of 70 words against 12 for every other release in the file, and bold marked five of sixteen entries with no criterion anyone could state.
docs/api/melcloudhome-telemetry-endpoints.mdalso gains the 24-hour truncation warning beside the energy endpoint'sfromandtoparameters, which it had described as if both were honoured. The sweep found nothing else stale: the 48-hour figures indocs/api/ata-api-reference.mddescribe the outdoor temperature trendsummary window, a different code path fromDATA_LOOKBACK_HOURS_ENERGY.Merged since v2.4.2-beta.2
AI Disclosure
Testing
manifest.jsonand the README "What's New" heading both read 2.4.2, matching the base version the release workflow validates against the tag.make pre-commitat the branch tip: all 12 hooks pass.