Replies: 1 comment
|
Closing this as done. Release 2026.8 has shipped, so this beta field report has served its purpose. Thanks for testing the beta. Please open a new discussion or issue for anything found on a current stable release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Ran 2026.8-beta1 for a day on a Tecalor TTC 05 Cool (WPM 3i, controller 391),
Home Assistant 2026.7.4, upgraded from 2026.7.3 through HACS.
Clean. The entity set is identical before and after: nothing disappeared,
nothing newly unavailable. No repair issue, no error in the log. The metadata
changes all took effect. A write went through end to end: setting Comfort Water
Temperature Target to 54 °C showed up in the entity immediately instead of at the
next poll, and it held across four polls before I set it back, so the controller
took the value rather than the interface assuming it.
Expect one statistics issue. The flow-rate sensor moves from
l/minto HomeAssistant's canonical
L/min. Those are different units to the recorder, so itraises
units_changedand stops extending that statistic. Developer Tools,Statistics offers a repair that updates the stored unit and keeps the whole
history, which is what I used; no values change, the two spellings are the same
quantity. Worth saying because the log line reads worse than the situation is:
The four
Todaysensors raise the expectedstate_class_removedissue, asannounced in #618.
One documentation gap, now #643: the narrowed write ranges were undocumented.
The effect is easy to misread, so it is worth stating precisely. A write outside
the new range failed before this release too, because the library enforced its
own range underneath the wider one the entities offered. Nothing that used to
succeed starts failing; the rejection just arrives up front now, naming the
range.
Not covered here: this is a WPM 3i, so the circulation pump moving from
switch to binary sensor never happened, that entity does not exist on this
controller. Someone on a WPMsystem or LWZ R290 should confirm that migration.
All reactions