Panels with a climate entity started a full Blueprint run on every update of that entity, even when nothing shown on the panel changed. Climate entities that update their attributes often, such as Better Thermostat (internal values every minute) or the panel's own thermostat (current temperature), made every panel run at the same time, again and again, which could keep Home Assistant busy for many seconds at a time on systems with several panels. These updates are now ignored unless they change something the panel shows.
Important
Newer ESPHome and Home Assistant required
This release requires ESPHome 2026.10.0 or newer to compile the firmware, and Home Assistant 2026.10.0 or newer to use the Blueprint.
Please update ESPHome (ESPHome Device Builder) and Home Assistant before updating your panel. If ESPHome is older than required, the compilation stops with a message asking you to update it, instead of failing with an add_waveform_data error as it did with ESPHome 2026.9.0 and 2026.9.1.
NSPanel Easy now targets Home Assistant and ESPHome versions released no more than one month before each release (previously two months). See Version compatibility.
If your panel's configuration replaces the Nextion component with an external_components entry (for example the old TFT upload workaround github://pr#16205), remove it: that older code lacks a function the firmware uses, and the compilation fails with the same add_waveform_data error.
The climate add-on documentation now explains how to set a finer target temperature step, e.g. 0.1 °C for underfloor heating, replacing the temp_step setting that has had no effect for a while. The underfloor heating example is corrected accordingly.
Details:
- The climate trigger (
climate_state, astate_changedevent trigger) fires on attribute-only updates as well. Its handler only updates the home page climate chip and, while it is visible, the climate page. - While the climate page is visible, every update still refreshes it, as before.
- While it is closed, a run continues only when the state,
hvac_action,iconorcolorchanged (what the climate chip shows), or when there is no previous state. - Updates of the panel's embedded thermostat are skipped entirely while the climate page is closed, as the firmware draws its chip.
- A
state_changedevent without a new state (entity removed) no longer starts a run: there is nothing to show, and the climate page handler failed on it. min_esphome_compiler_versionand the Blueprint's Home Assistantmin_versionare2026.10.0. The versioning workflow now targets the previous month and only raisesmin_esphome_compiler_version, never lowers it.- The OTA encryption guide no longer mentions ESPHome 2026.9.x, now below the minimum.
Closes #641
Related to #636, #644, #645, #646, #647
What's Changed
Other Changes
- fix: Skip Blueprint runs for climate updates that change nothing shown on the panel by @panel-easy-assistant[bot] in #642
- docs: Explain how to change the climate target temperature step by @meiser79 in #644
- fix: Require ESPHome and Home Assistant 2026.10.0 or newer by @panel-easy-assistant[bot] in #647
- fix: Skip Blueprint runs for climate updates that change nothing shown on the panel by @edwardtfn in #643
Full Changelog: v2026.11.6...v2026.11.7