A demo of the web interface: espaltherma.pages.dev/demo. The page your board serves, in a browser, without a board: the drawing, the values, the settings, the diagnostics. It is answered by recordings of a real unit (an EPGA 11-16 kW), ten minutes each, played in a loop: standby, hot water, room heating, chosen at the top of the page. Change what you like, nothing reaches a heat pump and a reload puts it back. It is built from the same page as the firmware at each release, so it always shows the current interface.
Room temperature from the external sensor (R6T) (#699, @allstrike). A unit whose field setting [C-08] is "room sensor" regulates on its external sensor, and the home page went on showing the unit's own room sensor. Settings → Heat pump connection has a second choice next to the outdoor one: Room temperature on the home page, the unit's own sensor or the external sensor. The unit has one such sensor, so choosing it for the room gives the outdoor temperature back to the unit's sensor, and the other way round. Only the page changes: both readings stay in the values and in Home Assistant. Select Auxiliary sensor (R6T) among the values, or the room shows no reading.
Hot water down to 25 °C, in the working memory only (hydro board software 20002203) (#664, @ppuetsch). With Keep the targets in the unit's working memory only ticked, the hot water target goes down to 25 °C instead of 45 °C on this software: the unit takes a lower curve in its RAM than its settings allow. The memory cannot hold such a target, so unticking the box with one held puts the unit's own curve back. A scheduled disinfection still runs, to the unit's own temperature. Details in doc/control.md.
Home Assistant: the device has its name and model on every board (@sorin-oancea, #599). The "ESPAltherma" device took its name, maker and model from the Smart Grid select, which only a board with Smart Grid relays publishes: without them the device had none, or kept "M5StickC PLUS ESP32-PICO" from 1.x. The entity every board publishes now carries them. Nothing to do in Home Assistant.
Values read beyond the end of a reply (#667, @ppuetsch). A definition made for a longer reply than the unit gives read its last values from the checksum and from what followed it, and published them as readings. Such a value is now skipped.
Two values under one name (#674, @ppuetsch). Seventeen definitions named the two O/U MPU ID bytes of registry 0xA0 the same: one MQTT key and one Home Assistant entity for two values, the second replacing the first. They are now O/U MPU ID (xx) (0xA0) and (yy) (0xA0). If you had selected it, Home Assistant gets two new entities and the old one stays unavailable: delete it there.
With an admin password, the home page no longer asks for it on a mere look (#679, @ppuetsch). The page sent the browser's UTC offset to the board for the day's statistics, which is a change of settings. With a password set it no longer does: the offset is a field in Settings → Energy and cycles, with a button for the browser's own. Set it again when the clocks change. Without a password nothing changes.
Memory (@ppuetsch, #696, #697, #680). The MQTT message of the values was built in a buffer of 7 KB kept for good: it is now taken for the time of the publish, 7 KB more at rest. Sending a poll to an open page took 39 KB at its lowest point with 128 values, 26 KB now. And the values are no longer locked while their MQTT messages are written: a broker that is slow to take them does not hold the readings.
Smaller.
- Settings: the This browser's button of the offset no longer touches its field.
- Docs, from @ppuetsch's measurements on an EHBX08EF6V (20002203): where the cooling and additional zone targets, the tank hysteresis and the backup heater setting are in the memory (#698), and what the port can and cannot do to the pump and the three-way valve (#700). Nothing of it is used by the firmware yet.
Update: System → Firmware update → Check for an update, or the web installer. Card: 1.0.36, unchanged.