Cooling: a second relay (asked many times, last in #637 by @Jeltel). The thermostat relay closes one contact, and the unit heats or cools according to the mode chosen on its interface. A reversible unit set to separate heating and cooling requests (contact type H/C request, field setting [C-05] = 2) has a second input: a relay on it is now a setting (Settings → Relays, Cooling relay pin), a switch in Home Assistant (switch.altherma_cooling) and an MQTT topic (espaltherma/COOL, ON / OFF, state on espaltherma/COOL_STATE). The two relays are never closed together: switching one on opens the other first. I could not try it on a unit, mine is heating only: tell me how it goes. Details in doc/control.md.
Firmware update: an upload may stall (#663, @elRadix). The web server dropped an upload that received nothing for 3 s, which is short for 1.5 MB over a link that stalls: his uploads were each cut after a few hundred KB, with memory to spare ("cut at 476 KB after 28 s"). An upload now gets 30 s. Checked on an M5StickC with an upload that stops for 6 s: cut on beta.30 with that same message, through on beta.31. This takes effect from the update after this one, since the firmware doing the update is the one you run: if the update to beta.31 is cut on your board, the web installer over USB installs it (answer no to erasing the device and your settings stay).
Targets and power limit (experimental): what a review of the code found. None of these was reported by an owner.
- Power limit on without a value (the switch in Home Assistant, the box of the page) applied the minimum, 1 kW or 4 A, while the number showed the unit's own limit. It now applies that limit.
- Switching the limit off wrote "no limitation" even when the installer had set a continuous limitation of his own, and left ESPAltherma's value in limit 1. The unit's own setting and value are now recorded before the first write and put back.
- Unticking a target or the power limit in the settings left what was written in the unit, with nothing on the page to undo it. The unit's curve, or its own limitation, now goes back first.
- One lost frame made a control "not ready" for 30 s and removed its entities from Home Assistant meanwhile (with the name or area you had given them). A frame is asked a second time, and the entities stay while the unit does not answer.
- A lost reply could make the unit look like another hydro board, which dropped a held target for good.
- The unit's own curve is recorded before the first write (it was after: a write that failed halfway could be recorded as the unit's curve).
- A second target sent while the first one was being written was lost.
Statistics. A unit that stopped answering during a run (a cable, a restart of the heat pump) kept adding heat and electricity to the day at its last power. A cycle without a reading now adds nothing and shows no power. Counters kept from before a restart are checked for figures a day can hold.
After a crash, the event history says where. The board now reads the dump its core writes when it crashes and adds two lines to the history at the next start: the task that crashed, and the calls that led there, as addresses. Copy them in an issue: they are looked up in firmware-elf.zip, new among the files of this release.
Memory. 11 KB more at rest (100 KB of usable memory on an M5StickC, 88 KB on beta.30): the firmware's own Home Assistant sensors take 12 bytes each instead of 64, and the discovery messages share one buffer (@ppuetsch, #665 and #695).
Smaller.
- A release tagged on the same commit as the build you run is now offered as an update (it said "up to date"): this matters for the day 2.0.0 follows its last release candidate.
- The version read on the installer site for the update notice is checked before it goes to Home Assistant.
Update: System → Firmware update → Check for an update, or the web installer. Card: 1.0.36, unchanged.