Repository navigation
release: 1.6.0 - #84
Merged
Merged
Conversation
Bumps get_version() to "1.6.0 esphome" and splits the changelog. 1.5.0 was tagged and released on 2026-09-26 containing the Core 200S filter-life change that turned out to be wrong, so the fixes that followed it cannot sit under that heading - anyone comparing their ESP Version sensor against the changelog would have read a description of code they are not running. The entries are now split by what each release actually shipped: * 1.6.0 carries the revert, the CADR truncation fix, the 3-speed divisor, the Superior 6000S speeds 5-9 fix, the panel-reset push handling and the cross-firmware display and reset keying. * 1.5.0 keeps what it really shipped - the Superior 6000S port, the build fixes and compile tests, the filter_low device class - plus a warning that its Core 200S filter mapping is superseded, naming the 0.0%/1.0% symptom so anyone hitting it can match it to a version. Also adds a note that the Core 200S filter percentage is an estimate and always was, since three independent counters exist on these units and only the ESP's is visible in Home Assistant. That sets the right expectation rather than inviting the next round of "it does not match the filter light". Compile test passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
Bumps
get_version()to1.6.0 esphomeand splits the changelog by what each release actually shipped.Why a split, not just a new heading
1.5.0 was tagged and released on 2026-09-26 containing the Core 200S filter-life change that turned out to be wrong. The fixes that followed it were sitting under the
1.5.0heading, which meant anyone comparing their ESP Version sensor against the changelog would read a description of code they are not running — and the people in #60 who are on 1.5.0 would see their bug described as fixed.filter_lowdevice class — plus a supersession warningThe 1.5.0 warning names the 0.0% / 1.0% symptom explicitly, so anyone hitting it can match it to a version without reading the diff.
One expectation-setting note
1.6.0 carries a callout that the Core 200S filter percentage is an estimate and always was. Three independent counters exist on these units — the VeSync cloud's, the MCU's own timer that drives the red filter light, and ESPHome's CADR estimate — and the MCU never puts a percentage on the wire. Better to say so than to field the next round of "it doesn't match the filter light".
Note on rollout
The device configs use
ref: main, so anyone on the published builder YAML already has these fixes — the tag mainly gives the #60 thread a version number to refer to.Compile test passes.
🤖 Generated with Claude Code