Skip to content

Releases: Blackymas/NSPanel_HA_Blueprint

v1.0.1 Blueprint

Choose a tag to compare

@Blackymas Blackymas released this 04 Oct 09:07
6ff0e4e

v1.0.1 Blueprint

  • Fix issue Weatherpage 4
  • move "Date Sensors" from sensor.yaml file to Blueprint
  • improved HA Entity Status

v2026031 – Light Temperature Fix, Timezone Removal & CI Updates

Choose a tag to compare

@edwardtfn edwardtfn released this 16 Mar 18:11
e9af8b0

Summary

This release fixes the inverted light color temperature selector, removes the now-incompatible timezone support following a breaking change in ESPHome v2026.3.0, and restores CI test workflows broken by recent upstream updates.

Bug Fixes

Inverted Light Color Temperature Selector

Fixed a bug where the color temperature selector for lights was working in reverse. (#3250)

Details:

  • Moving the slider towards warmer tones was incorrectly resulting in cooler color temperatures being applied, and vice versa
  • The display value and the actual light behavior were misaligned, leading to a confusing and unintuitive user experience

Result: The color temperature slider now behaves as expected — warmer selections produce warmer light, and cooler selections produce cooler light.

Breaking Changes

Timezone Support Removed

Removed the previously implemented timezone support due to a breaking change in ESPHome v2026.3.0.

Details:

  • ESPHome v2026.3.0 introduced a fully rebuilt timezone engine
  • The new implementation is incompatible with the solution previously used in this project
  • Continuing to ship the old implementation would result in incorrect or unpredictable behavior

Action required: If you were relying on timezone configuration provided by this project, please refer to the ESPHome
Time Component documentation for the timezone option available natively in the time platform of your choice (e.g. homeassistant, sntp).

Maintenance

CI Test Workflows Revised

Updated the GitHub Actions merge workflows to restore automated testing.

Details:

  • Recent upstream changes had broken the existing merge test configurations
  • Workflows have been revised to align with the current upstream state and restore reliable CI coverage

Result: Automated tests are now passing again for merge requests.


Release addressing an inverted light temperature selector, removal of incompatible timezone support following ESPHome v2026.3.0, and restoration of CI test workflows.

v2026030 - Fix color temperature service call for Home Assistant 2026.3.0 compatibility

Choose a tag to compare

@edwardtfn edwardtfn released this 04 Mar 20:40
21bf4bb

What's Changed

🔧 Fix: Light color temperature now uses color_temp_kelvin

Home Assistant 2026.3.0 removes the deprecated color_temp (Mireds) and kelvin parameters from light.turn_on. This release updates the light page to use the non-deprecated color_temp_kelvin parameter instead.

The TFT slider now operates natively in Kelvin, keeping the value flow clean end-to-end without any unit conversion.

⚠️ Important

This release requires updating all three components (ESPHome, TFT, and Blueprint) together. Using mismatched versions across this change will result in color temperature control no longer working.

v2026020 - Climate Page Fixes & UI Improvements

Choose a tag to compare

@edwardtfn edwardtfn released this 28 Feb 06:03
fd5c4de

Summary

This release fixes critical issues with climate page temperature handling, resolves UI color
inconsistencies, and includes various bug fixes and improvements.

Bug Fixes

Climate Page Temperature Handling

Fixed erratic UI behavior when changing temperature on panel using Fahrenheit - resolved
issue where temperature changes on the climate page caused unpredictable UI behavior in
Fahrenheit mode.

Issues Reference: #3206

Result: Stable and predictable temperature adjustment behavior on climate page when using
Fahrenheit units.

Climate Add-on Temperature Range Fix

Fixed climate add-on temperature set-point limitation - resolved issue preventing
temperature adjustment above 74°F in climate add-on configuration.

Issues Reference: #3241

Result: Climate add-on now supports full temperature range without artificial limitations.

Home Page Value Color Consistency

Fixed home_value02 label and icon color being ignored - resolved issue where custom colors
for the second home page value label and icon were not being applied.

Issues Reference: #3226

Result: home_value02 label and icon colors now correctly follow configured color settings.

Improvements

Temperature Rounding for Climate

Improved temperature value precision - temperature values are now rounded to 4th digit
before being sent to climate entities, ensuring consistent and accurate temperature reporting.

Result: More precise temperature handling and reduced floating-point precision issues in
climate control.

Home Page Icon Color Engine

Rebuilt home_valueXX icon_color engine - refactored the color handling engine for home page
value icons to improve reliability and maintainability.

Result: More robust color handling for home page value icons.

OTA Configuration Update

Updated OTA settings to use actions/stale@v10.2.0 - modernized OTA (Over-The-Air) update
configuration with latest action version.

Result: Improved OTA update reliability and compatibility.

Documentation Improvements

Fixed instructions for changing WiFi password - corrected documentation to properly use
ota_std reference for WiFi password changes.

Fixed broken documentation links - resolved various broken links in documentation.

Result: More accurate and accessible documentation.

Jinja Expression Validation

Updated value color/icon guards to use valid Jinja expressions - improved template
validation and reliability for color and icon value guards.

Result: More robust template processing and error prevention.


Climate page fixes, UI color improvements, and documentation updates.

v2026015 – Hotfix for Blueprint Load Crash

Choose a tag to compare

@edwardtfn edwardtfn released this 29 Jan 20:18
1dd6261

Summary

This is a hotfix release that resolves an issue causing the blueprint to crash or fail to load on some systems. The problem was introduced in v2026010 as part of changes made to accommodate the new blueprint input validation introduced by Home Assistant 2026.1.0.

Bug Fixes

Blueprint Crash on Load (Introduced in v2026010)

Fixed a bug where the blueprint could crash or fail to load on certain systems.

Details:

  • The issue was introduced in v2026010
  • It was related to adjustments made to handle the new blueprint input validation rules introduced in Home Assistant 2026.1.0
  • In some environments, these changes caused the blueprint to fail during loading or initialization

Result: The blueprint now loads correctly across affected systems, restoring normal operation.


Hotfix release addressing a blueprint load crash introduced in v2026010 while adapting to Home Assistant 2026.1.0 input validation changes.

v2026014 – Hotfix for Indoor Temperature Sensor Blueprint Crash

Choose a tag to compare

@edwardtfn edwardtfn released this 27 Jan 21:12
e45df2b

Summary

This is a hotfix release that resolves a critical issue causing the blueprint to crash when an indoor temperature sensor is selected.

Bug Fixes

Blueprint Crash with Indoor Temperature Sensor (Issue #3215)

Fixed a bug where selecting an indoor temperature sensor caused the blueprint to crash.

Details:

  • The issue occurred when an indoor temperature sensor entity was selected in the blueprint
  • This caused the automation to fail during loading or execution

Result: The blueprint now handles indoor temperature sensors correctly, preventing crashes and restoring normal operation.
(Tracked as #3215)


Hotfix release addressing a blueprint crash when using an indoor temperature sensor.

v2026013 – Fahrenheit Temperature Handling Fixes and Fixed Baud Rate

Choose a tag to compare

@edwardtfn edwardtfn released this 27 Jan 05:59
b0a8dd2

Summary

This release focuses on fixing temperature unit handling when using Fahrenheit, addressing multiple issues related to incorrect display, reporting, and UI behavior. It also standardizes the serial communication speed to 115200 bps, removing configurable speed selectors to reduce the risk of baud rate mismatches between the TFT and ESPHome.

Climate and Temperature Fixes

Fahrenheit (°F) Temperature Handling

Fixed multiple issues affecting temperature display and behavior when using Fahrenheit.

Scope:

  • Corrected cases where temperatures were always reported or displayed as Celsius
  • Fixed erratic UI behavior when changing temperature values in Fahrenheit
  • Ensured hardware temperature sensors report the correct unit when temp_units: "°F" is configured
  • Improved consistency between Home Assistant, ESPHome, and panel UI when operating in Fahrenheit

Result: Correct, consistent, and predictable temperature handling when using Fahrenheit across the entire climate stack.

Communication and Stability Improvements

Fixed Baud Rate at 115200 bps

Standardized the communication baud rate to 115200 bps across the project.

Changes:

  • Removed baud rate / speed selectors to avoid configuration mismatches
  • The TFT file now enforces 115200 bps
  • The ESPHome configuration is hard-coded to 115200 bps

Reason:

  • Reduces the likelihood of communication issues caused by mismatched baud rates
  • Improves reliability during panel upgrades and restarts

Result: More robust and predictable communication between ESPHome and the TFT, with fewer connection-related issues.


Fixes Fahrenheit temperature handling issues and enforces a fixed 115200 bps baud rate to improve reliability.

v2026012 – Climate Page Fixes, Alarm Page Regression Fix, and ESPHome 2026.2 Preparation

Choose a tag to compare

@edwardtfn edwardtfn released this 22 Jan 13:07
11c2c85

Summary

This release fixes multiple issues related to climate page temperature handling, resolves a critical regression in the alarm page introduced in v2026010, and addresses a deprecation warning announced for ESPHome 2026.2.0.
Starting with this version, ESPHome 2026.1.0 is now required.

Breaking Changes

ESPHome 2026.1.0 Required

ESPHome 2026.1.0 or newer is now required.

Reason:

  • The fixes and refactoring included in this release depend on changes introduced in ESPHome 2026.1.0
  • Ensures correct behavior and avoids compatibility issues with older ESPHome versions

Required action:

  • Upgrade ESPHome to 2026.1.0 or newer before updating to this release

Result: Guaranteed compatibility with current and upcoming ESPHome releases.

Climate Page Fixes

Fahrenheit (°F) Handling Improvements

Fixed issues affecting climate entities when operating in Fahrenheit mode.

Scope:

  • Corrected temperature handling and display inconsistencies when using °F
  • Prevented erratic or incorrect temperature values on the climate page
  • Improved robustness of climate logic for Fahrenheit-based entities

Result: Stable and correct climate page behavior when using Fahrenheit.

Alarm Page Fixes

Alarm Action Not Sent Correctly (Regression since v2026010)

Fixed a critical regression where alarm state change actions were not being sent correctly.

Details:

  • The regression was introduced in v2026010
  • Alarm page interactions appeared correct in the UI but did not reliably propagate the action

Result: Alarm actions are now sent and processed correctly again.

Compatibility and Maintenance

ESPHome 2026.2.0 Deprecation Warning

Resolved a deprecation warning scheduled to be introduced with ESPHome 2026.2.0 (expected end of February).

Details:

  • Updated affected code paths to align with upcoming ESPHome changes
  • Prevents future warnings and potential breakage

Result: Clean builds and forward compatibility with ESPHome 2026.2.0.


Requires ESPHome 2026.1.0+. Includes climate page Fahrenheit fixes, alarm page regression fix, and preparation for ESPHome 2026.2.0.

v2026011 – Rollback of Home Assistant 2026.1 Blueprint Changes and Fixes

Choose a tag to compare

@edwardtfn edwardtfn released this 20 Jan 20:12
cf0f08e

Summary

This release rolls back the blueprint changes introduced in v2026010 for Home Assistant 2026.1.0 compatibility,
as they caused automation breakage for many users.
The original Home Assistant issue was limited to UI behavior and did not break functionality,
so restoring stability is prioritized.
This release also fixes an ESPHome compilation issue affecting temperature entities configured in Fahrenheit.

Rollback Details

Blueprint Changes for Home Assistant 2026.1.0

Reverted the blueprint modifications introduced to support Home Assistant 2026.1.0.

Reason:

  • The changes broke automations for a significant number of users
  • The underlying Home Assistant issue affected only the UI and not core functionality
  • The regression impact outweighed the benefit of the UI-related fix

Result: Restored the previously stable and working automation behavior.

User Guidance

If issues persist after updating to this release, it is recommended to re-set or re-save automations affected by recent changes,
as some problems may be related to formatting changes introduced in v2026010.

Result: Re-applying the configuration should restore correct behavior in remaining edge cases.

Bug Fixes

Temperature Entity (Fahrenheit) – ESPHome Compile Error

Fixed an issue with temperature entities configured in Fahrenheit that prevented ESPHome from compiling.

Result: ESPHome now compiles correctly when using Fahrenheit-based temperature entities.

Compatibility Notes

Home Assistant 2026.1.0

  • Compatible with Home Assistant 2026.1.0
  • Blueprint changes related to HA 2026.1.0 have been reverted
  • A known UI limitation may remain, but functionality is preserved

Result: Stable operation without automation regressions.


Rollback release prioritizing automation stability, with additional fixes for Fahrenheit temperature entities and ESPHome compilation.

v2026010 – ESPHome 2026.1 Compatibility and Climate Page Fixes

Choose a tag to compare

@edwardtfn edwardtfn released this 18 Jan 10:41
3ffe693

Summary

This release updates the codebase for compatibility with ESPHome 2026.1.0,
fixes issues introduced by Home Assistant 2026.1.0,
and includes fixes and improvements related to the climate page UI.

Compatibility Notes

ESPHome 2026.1.0 Support (Upcoming)

This release prepares the project for ESPHome 2026.1.0, scheduled for release on January 21st.

Notes:

  • Forward-compatible changes aligned with ESPHome 2026.1 internal updates
  • Fixes build issues observed with early ESPHome 2026.1 development versions
  • No functional behavior changes are expected for earlier supported ESPHome versions

Result: The project will continue to build and operate correctly once ESPHome 2026.1.0 is released.

Home Assistant 2026.1.0 Compatibility

Fixed issues introduced by Home Assistant 2026.1.0 (released January 7th).

Scope:

  • Adjustments required due to internal changes in Home Assistant 2026.1.0
  • Fixes regressions affecting normal operation and entity handling

Result: Restored correct behavior when running Home Assistant 2026.1.0.

Climate Page Fixes and Improvements

Maximum Temperature Selection (Bug #3137)

Fixed an issue where the climate page could not correctly set or display target temperatures above 9.4 °C when a large number of temperature steps was allowed.

Details:

  • The issue occurred with climate entities exposing fine-grained temperature steps
  • Internally, the temperature range overflowed when more than 256 steps were available

Result: Correct maximum temperature handling for climate entities with high-resolution step configurations. (Tracked as #3137)

Standardized Temperature Information (Enhancement #2343)

Standardized the display of temperature information across climate and weather-related views.

Result: Consistent and clearer temperature presentation using the configured temperature unit (°C / °F). (Tracked as #2343)


ESPHome 2026.1.0 compatibility, Home Assistant 2026.1.0 fixes, and climate page UI improvements.