Releases: Blackymas/NSPanel_HA_Blueprint
v4.2 - Multi-Alarm Control, Dual Thermostat Functionality, and More
Support this project
As always, we would like to thank everyone who donated to this project and remind you that every donation helps to support this project
So if you haven't made a donation yet, now would be a good time ;)
General
Hello everyone! Our latest update introduces a range of enhancements designed to elevate your experience with the firmware.
This update is focused on improving user interaction, featuring a more intuitive TFT upload process and expanded customization options.
Key enhancements include upgraded functionality for Alarm Control Panels & Thermostats and new personalization features on the Home page.
We're enthusiastic about our ongoing work to make the NSPanel firmware more user-friendly and accessible.
This release marks significant progress in this direction, with improvements such as the
streamlined TFT upload process and initial steps towards adopting esp-idf
as the default framework.
Additionally, our documentation has been revamped for greater clarity and user-friendliness.
Expect more user-centric updates coming your way soon!
Dive into the details below to see how these changes can enhance your daily use of NSPanel.
We value your feedback and are eager to hear your thoughts!
Upcoming Change: Switching to ESP-IDF Framework by March 2024
We have some important updates for our community – by March 2024, we're moving to the ESP-IDF as our standard framework.
This shift aims to significantly boost the memory capacity on the ESP, allowing for the addition of new features and broader customizations.
There's ample time before this transition takes place, so no need to hurry.
When it's time to switch, flashing your device using a serial cable will be necessary, similar to the initial custom firmware setup.
For those who might need a serial firmware installation before March,
trying out esp-idf
earlier could be a beneficial move towards adapting to future developments.
If you're unable to switch by March or if serial flashing isn't an option for you,
the arduino
framework will still be available for Over-The-Air (OTA) updates.
For detailed guidance on framework customization, check out our customization documentation.
We're dedicated to facilitating a smooth transition and are here to assist with any queries or concerns.
Updating
Updates may come with changes on the blueprint inputs and we highly recommend you review your settings and make sure all fields have the correct selection.
We did our best to support your legacy settings and avoid breaking your system, but please double check your settings if you see something not working as expected.
Files that need to be reloaded
- nspanel_eu.tft, nspanel_us.tft or nspanel_us_land.tft - v4.2
- nspanel_esphome.yaml - v4.2
- nspanel_blueprint.yaml - v4.2
Instructions
You can find the update procedures following here:
Breaking changes
-
The
background
parameter in theesphome.xxxxx_set_component_color
service is now deprecated. -
On the home and climate pages, the button layout has changed.
This adjustment was made to incorporate additional custom buttons on the home page and new target temperature indicators on the climate page.
-
Wi-Fi power save mode has been reset to
NONE
as the default setting.This was the standard up to v4.0. We switched it in v4.1 to accommodate Bluetooth components.
However, since this feature isn't widely used, we're reverting to the original setting.
For Bluetooth usage, you should manually set a different mode, such asLIGHT
, as shown in the customization example below:##### My customization - Start ##### # Enable Bluetooth proxy bluetooth_proxy: # Set Wi-Fi power save mode to "LIGHT" as required for Bluetooth on ESP32 wifi: power_save_mode: LIGHT ##### My customization - End #####
-
The default baud rate for advanced mode has been reverted to 115200 bps to resolve issues that arise when rendering button pages.
-
ESPHome v2023.12.0 has been established as the minimum required version to ensure optimal performance and compatibility, particularly with the recent developments in the Nextion component.
-
The Alarm section in the blueprint settings has been removed. All configurations previously made in this section have been automatically transferred to custom button 07.
-
Documentation in German is no longer maintained. This change allows us to more efficiently update and maintain the remaining documentation.
-
Reversion to "Toggle" as default action for automation entities on buttons.
In this update, we have reverted the default action for button presses on automation. entities back to "Toggle".
This change reverses the adjustment made in version 4.1, where "Trigger" was set as the default action.Impact:
- Default Behavior: With this reversion, pressing a button linked to an automation entity will now enable or disable the automation, as it did prior to version 4.1.
- Consistency and Familiarity: This change aims to align with user expectations and maintain consistency in the user experience.
- Customization Still Available: Users still have the option to manually set "Trigger" as the action for their
automation.
entities, as per their preference.
We understand that changes in default settings can impact your workflows.
We appreciate your understanding as we strive to balance new features with the familiarity and stability of the user experience. -
Advanced mode no longer enforces a specific framework.
In the past, the enforcement of framework changes by the advanced mode could inadvertently result in users switching frameworks during OTA updates.
This practice was not recommended due to the potential for errors. -
Alarm page cannot be used as wake-up page.
As multiple alarms are supported now, the system don't know which one to show on the wake-up.
-
Refinement of Icon Presentation
In our continuous pursuit to refine the user experience, we've embarked on standardizing the presentation of icons across various pages.
This initiative may lead to noticeable changes in icon appearance and behavior,
encompassing aspects like the introduction of new colors for alarms, lights, climate icons,
and the adoption of fresh icon designs.Our aim with these modifications is to establish a default presentation that adheres to a unified standard,
enhancing both consistency and user experience across the platform.
While this approach simplifies the overall design,
it still preserves a degree of customization through blueprint settings.The complexity of managing icon colors, especially for items with multi-state attributes like alarm control panels,
climate controls, and lights with adjustable brightness and color, has prompted us to rethink our approach.
The current version implements domain-based colors for multi-state items, with specific states for alarms and climate being hard-coded.
We're exploring ways to offer user-selectable colors for these states in future updates.The new color logic is as follows:
- For the
off
state: Icons will be displayed in gray. - For states other than
off
:- For alarms and climate: Each state will have a specific, hard-coded color for immediate recognition.
- For lights: If supported, the icon will reflect the light's RGB color, proportionally dimmed to match its brightness.
- For other domains: Icons will be displayed in white.
This transition towards a more standardized icon presentation is a step forward in enhancing
the interface's intuitiveness while balancing it with the flexibility of customization.
We understand this change might be an adjustment from previous versions,
but our goal is to streamline the experience without compromising the essence of personalization. - For the
-
Action required: Reset your wake-up page selection.
We've enhanced the wake-up page functionality for improved consistency after power cycles.
Previously, the system didn't remember your selection following a power outage.
With our latest update, this issue has been resolved.
However, this improvement requires you to reselect your wake-up page one more time.
Thanks for your cooperation in making these settings more reliable for everyday use.
Overview of noteworthy changes
- Standardized entity icons
- Additional custom buttons on Home page
- Outdoor temperature selectable font size
- Select icon size for button's pages
- Support to CJK languages (experimental)
- Improved TFT transfer
- Multiple Alarm Control Panels
- Support to
remote
- Home page chips now supports covers
- Chips can be inverted
- Add swipe control to screensaver page
- Enhanced control for automation entities on buttons
- Dual thermostat controller support (add-on)
- Dual thermostat display
- Enhanced timeout flexibility for Sleep, Page fallback, and Dimming settings
- Display time on the
screensaver
page
Details of noteworthy changes
1. Standardized entity icons
The engine for defining the icons to be shown and it's color was standardize between all the pages, so now you may see a more consistent User's Interface.
We've upgraded the ic...
v4.1.4 - Support to Home Assistant 2023.12.0
Welcome to the v4.1.4 patch!
The main goal for this update is to support the new weather.get_forecasts
service introduced with Home Assistant 2023.12.0 to replace weather.get_forecast
and avoid the message of the deprecated service in use.
We also moves some files around to make the repository a bit cleaner. If you are missing some files, please take a look under advanced
folder.
And, as a bonus, in additional to the existing logs, we improved a bit the user's interface on the panel when uploading TFT. This will be more visible after you install the latest TFT (v4.1.4), but we still have something if you are already with a TFT v4.x.x.
Below is a detailed list of changes. We recommend reviewing them to understand how this update impacts your setup.
Compatibility Note: This patch is fully compatible with components from v4.1, v4.1.1, v4.1.2 and v4.1.3. Your system will operate seamlessly with a mix of v4.1, v4.1.1, v4.1.2, v4.1.3 and v4.1.4 components, though we advise updating all components to the latest version for optimal performance.
Update Instructions
For detailed update procedures, please visit:
- English guide: How To - Update (EN)
- German guide: How To - Update (DE)
Overview of Changes
Change | Criticality | Page/Area | Components Affected |
---|---|---|---|
Supports new weather.get_forecasts introduced by Home Assistant 2023.12.0 |
Medium | weatherXX |
Blueprint |
Manual line break on multiline text with \r |
Enhancement | All | ESPHome |
Upload TFT User's interface on panel | Enhancement | N/A | TFT ESPHome |
v4.1.3 - Bug fixes
Welcome to the v4.1.3 patch!
This update fixes some minor bugs.
Below is a detailed list of changes. We recommend reviewing them to understand how this update impacts your setup.
Compatibility Note: This patch is fully compatible with components from v4.1, v4.1.1 and v4.1.2. Your system will operate seamlessly with a mix of v4.1, v4.1.1, v4.1.2 and v4.1.3 components, though we advise updating all components to the latest version for optimal performance.
Update Instructions
For detailed update procedures, please visit:
- English guide: How To - Update (EN)
- German guide: How To - Update (DE)
Overview of Changes
Change | Criticality | Page/Area | Components Affected |
---|---|---|---|
Upload TFT remove dependency to from ESPHome Nextion component | Minor | N/A | ESPHome |
Fix light icon color on buttons | Minor | buttonpageXX |
Blueprint |
Fix climate page not updating properly | Minor | climate |
Blueprint ESPHome |
v4.1.2 - Bug fixes and minor enhancements
Welcome to the v4.1.2 patch!
This update fixes some bugs and enable the use of your panel with ESPHome 2023.11.6.
Below is a detailed list of changes. We recommend reviewing them to understand how this update impacts your setup.
Compatibility Note: This patch is fully compatible with components from v4.1 and v4.1.1. Your system will operate seamlessly with a mix of v4.1, v4.1.1 and v4.1.2 components, though we advise updating all components to the latest version for optimal performance.
Update Instructions
For detailed update procedures, please visit:
- English guide: How To - Update (EN)
- German guide: How To - Update (DE)
Overview of Changes
Change | Criticality | Page/Area | Components Affected |
---|---|---|---|
Fix Nextion not communicating with ESPHome 2023.11.6 | Critical | N/A | ESPHome |
Fix for icons not updating on Home page | Medium | home |
Blueprint |
Fix light icon color not being used for buttons | Minor | buttonpageXX |
Blueprint |
Don't show thermostat chip when state is auto and no action is available |
Minor | home |
Blueprint |
Fallback to legacy forecast (attributes based) when new method (service based) fails | Minor | weatherXX |
Blueprint |
Fix for button image update when local fallback is enabled | Minor | home |
ESPHome |
Add option to wake-up to Climate page | Enhancement | climate |
ESPHome |
New switch "Nextion display - Power" which can turn the screen on/off | Enhancement | Diagnostics | ESPHome |
v4.1.1: UI Enhancements and Reintroduction of `play_rtttl` Service
Welcome to the v4.1.1 patch! This update reintroduces the play_rtttl
service, which was removed in v4.1, and includes enhancements from @bkbartk for better icon display and climate entity information on the Home and button pages.
Below is a detailed list of changes. We recommend reviewing them to understand how this update impacts your setup.
Compatibility Note: This patch is fully compatible with components from v4.1. Your system will operate seamlessly with a mix of v4.1 and v4.1.1 components, though we advise updating all components to the latest version for optimal performance.
Update Instructions
For detailed update procedures, please visit:
- English guide: How To - Update (EN)
- German guide: How To - Update (DE)
Overview of Changes
Change | Criticality | Page/Area | Components Affected |
---|---|---|---|
Reintroduced esphome.xxxxx_play_rtttl service to core package |
N/A | N/A | ESPHome |
Eliminated fallback to Home page during Notification or Confirm page display | N/A | confirm , notification |
ESPHome |
Enabled display of current temperature on buttons, even when climate is off | N/A | buttonpageXX |
Blueprint |
Home and Button pages to show entity's icon when available | N/A | buttonpageXX , home |
Blueprint |
v4.1 - Easier TFT transfer
Support this project
As always, we would like to thank everyone who donated to this project and remind you that every donation helps to support this project - so if you haven't made a donation yet, now would be a good time ;)
General
The focus this time was on making easier to transfer the TFT files.
As this project grows with features, it becomes more hungry of resources from all sides (ESPHome, your Home Assistant server and even the Nextion display) and with that the chances of something going wrong when updating increased.
So at this release we concentrated on cleaning up de code everywhere and shave some unnecessary elements, making the system easier to install and opening some space for future features. But you still can find a couple of nice new things not related to the cleaning.
Updating
Since in this update lots of input to the blueprint changed, we highly recommend you review your settings and make sure all fields have the correct selection. We did our best to support your legacy settings and avoid breaking your system, but please double check your settings if you see something not working as expected.
Files that need to be reloaded:
- nspanel_eu.tft, nspanel_us.tft or nspanel_us_land.tft - v4.1
- nspanel_esphome.yaml - v4.1
- nspanel_blueprint.yaml - v4.1
Instructions
You can find the update procedures following here:
- (EN) How To - All important thing you should know - Update
- (DE) How To - Alle wichtigen Dinge die man wissen sollte - Update
Breaking changes
-
Home Assistant 2023.9.0 or later is now required
This is necessary in order to support the new Weather Forecast Service.
The legacy forecast based on attributes will be deprecated in Home Assistant on the begining of 2024. -
The following components are now deprecated:
- Buttons:
- Exit reparse (
button.xxxxx_exit_reparse
) - It shouldn't be necessary with the new TFT upload engine
- Exit reparse (
- Services:
- Play rtttl (
esphome.xxxxx_play_rtttl
)
- Play rtttl (
- Sensors:
- API uptime
- Device uptime
- RSSI
- ESPhome Version
- IP
- SSID
- BSSID
- ESPHome components:
- Web server
You can still add these components (except by "Exit reparse") by adding the file
nspanel_esphome_advanced.yaml
in your ESPHome settings as in the example bellow, but please have in mind that these are not used by the blueprint and will be using some memory of your ESPHome. - Buttons:
...
packages:
remote_package:
url: https://github.com/Blackymas/NSPanel_HA_Blueprint
ref: main
files:
- nspanel_esphome.yaml # Core package
- nspanel_esphome_advanced.yaml # activate advanced (legacy) elements - can be useful for troubleshooting
...
-
Very long press on hardware buttons
If you have a custom automation using very long hold (more than 15s) of hardware buttons it may fail as now the panel will restart with button hold for 15s. -
Logger via UART is disable
You can add it back as a customization. -
Service
notification_show
parametertext
was renamed tomessage
to support ESPHome 2023.11.0. -
Buttons now will run an automation
On the previous versions, a button with an automation will enable or disable the automation. Now the button will trigger the automation.
If you want the legacy behavior, please create a script to enable/disable the automation and assign this to your button. 😉
Overview of noteworthy changes
- New Upload TFT engine
- Hardware restarts with button hold for 15s
- Support to
esp-idf
framework - Support to 921600 bps
- Font size for chips
- Short click to open Climate and Media Player
Details of noteworthy changes
1. New Upload TFT engine
We rebuilt the Upload TFT engine and now it will be using less resources from ESPHome during the transfer and, in addition, will provide more logs for troubleshooting.
The original engine from Nextion component still as a fallback in case the new engine fails, but it might be removed in a future version.
2. Hardware restarts with button hold for 15s
Now if you press the hardware buttons for more than 15s, the panel will act as the following:
Button | Action | Details |
---|---|---|
Left | Power cycle the screen | It can remove the need to power cycle the panel when the screen can't stablish connection to ESPHome (Nextion is not connected! on logs). |
Right | Restarts the panel | It is equivalent to press the "Restart" button on the Settings page or from Home Assistant, but is available even when the Wi-Fi isn't connected or Home Assistant is out. |
3. Support to esp-idf
framework
Although this project still using ESPHome default framework (currently arduino
), we started supporting the framework esp-idf
as this is a recomendation from ESPHome team since an year ago or so.
The arduino
protocol still more popular and therefore more components are available, but there are some advantages with the ESP-IDF framework:
- It is updated more frequently by EspressIF, which means it is more secure and stable.
- It reduces a layer, as Arduino is developed in top of ESP-IDF, so basically we are changing from ESPHome -> Arduino -> ESP-IDF -> Hardware to ESPHome -> ESP-IDF -> Hardware.
- By reducing a layer, more memory is available for future features and for the custom components you might want to add to your panel.
- The memory management is more efficient, which makes critical tasks, like uploading a TFT file, more reliable.
In the future we will probably make this as the default framework, so if you are a new user or if for some reason you have to flash your panel via serial/usb, it's a good idea to change to ESP-IDF now.
Please look at customizations docs in the Wiki for more details on how to change the framework.
-> The ESP-IDF framework will be used when you enable the advanced mode.
4. Support to 921600 bps
Until this point, the communication between ESPHome and the Nextion display is at 115200 bps. This is not changing for now, but we are preparing to change this in the near future to a higer rate of 921600 bps, which is 8 times higher than the one used currently.
After installing the latest TFT v4.1, you will be able to change the speed as a customization and your system will switch to the higher transfer rate after the next boot.
In most of the cases, you are not going to see any diference related tho this change, but it will reduce significantly the time to upload a TFT file.
5. Font size for chips
We ran a poll, the maiority select one option, but we respect the minority and... we supported both options. 😃
Now you can have your chips a bit bigger, making it easier to see from the distance:
24px | 32px |
---|---|
As before | New option |
If you wanna try the new option, just go to your blueprint setting and select the font size:
6. Short click to open Climate and Media Player
Now on any button page, buttons assigned to Climate or Media Player entities will always open the detailed page. As it is hard to define an adequate toggle action for all the different cases, it makes more sense to just open the page and let the control to the users.
Next topics we are currently working on
See here: https://github.com/Blackymas/NSPanel_HA_Blueprint/labels/roadmap
Special thanks to:
- @misery - Fixing a typo in the docs (#1176)
- @Floppe - Adding space for value fields on Home page (#1180)
New Contributors
Previous releases
- v4.0.2 - Bug fixes
- v4.0.1 - Bug fixes
- v4.0 - Alarm and Media player pages, Climate add-ons and a more robust panel
- v3.4.1 - Patch for issues when compiling with ESPHome 2023.7.0
- v3.4 - New climate page and some bug fixes
- v3.3 - New improvements and some issues fixed
- [v3.2.2 - fixed some bugs performance improvement](https://github.com/Blackymas/NSPanel_HA_Blueprin...
v4.0.2 - Bug fixes
General
This patch includes bug fixes only, with no new functionality implemented.
You can see the list of changes below and decided what to update based on how you are affected by the different changes.
There is compatibility between components with v4.0, v4.0.1 and v4.0.2, then your system will work with no issues with a mix of those versions, althoug we recommend always updating all the components to the latest version available.
Instructions
You can find the update procedures following here:
- (EN) How To - All important thing you should know - Update
- (DE) How To - Alle wichtigen Dinge die man wissen sollte - Update
Overview of all changes
Change | Criticality | Page/area | Components affected |
---|---|---|---|
Fix incorrect addressing on short press of button02 at buttonpage03 | Critical | buttonpage03 |
TFT (US model only) |
Fix incorrect service call for Media Player on short press at button pages | Medium | buttonpageXX |
Blueprint |
Update to customization instructions | Low | N/A | GitHub page (docs) |
Use UTC for date selection on weather pages | Low | weatherXX |
Blueprint |
Removed unnecessary refresh of relay's chips | Low | home |
ESPHome |
v4.0.1 - Bug fixes
General
This patch includes bug fixes only, with no new functionality implemented.
You can see the list of changes below and decided what to update based on how you are affected by the different changes.
There is compatibility between components with v4.0 and v4.0.1, then your system will work with no issues with a mix of those versions, althoug we recommend always updating all the components to the latest version available.
Instructions
You can find the update procedures following here:
- (EN) How To - All important thing you should know - Update
- (DE) How To - Alle wichtigen Dinge die man wissen sollte - Update
Overview of all changes
Change | Criticality | Page/area | Components affected |
---|---|---|---|
Incorrect button addressing on long press at buttonpage03 | Critical | buttonpage03 |
TFT (US model only) |
Volume button not working | Medium | media_player |
TFT |
Fixes on instructions | Minor | N/A | Blueprint GitHub page (docs) |
Prevents media player crashing when called before media_position_updated_at is able to provide a value. |
Minor | media_player |
Blueprint |
Add instructions to enforce a timezone selection in customizations | Minor | N/A | GitHub page (docs) |
Translations to Dutch | Minor | settings |
Blueprint |
Translations to Finish (review) | Minor | All | Blueprint |
Removed display_current_brightness messages from log |
Minor | N/A | ESPHome |
Version control to support patches | Minor | N/A | ESPHome |
Support for flexible time format | Minor | home |
Blueprint |
Added date format for Finish | Minor | home |
Blueprint |
Reset sleep timer when brightness settings changes | Minor | All | ESPHome |
Special thanks to:
New Contributors
v4.0 - Alarm and Media player pages, Climate add-ons and a more robust panel
Support this project
As always, we would like to thank everyone who donated to this project and remind you that every donation helps to support this project - so if you haven't made a donation yet, now would be a good time ;)
General
Big news: v4.0 has finally landed! Here’s the scoop:
🚨 We've added an Alarm control panel – safety first, right?
🎵 The Media Player control is here for all our tunes and binge-watching needs.
🌬️ Dial in your comfort with the new Fan speed and Embedded climate control settings.
Plus, we've beefed up the panel's resilience to those annoying network or server glitches.
Give it a spin and let us know your thoughts. Thanks for being on this journey with us!
Updating
Since in this update lots of input to the blueprint changed, we highly recommend you review your settings and make sure all fields have the correct selection. We did our best to support your legacy settings and avoid breaking your system, but please double check your settings if you see something not working as expected.
Files that need to be reloaded:
- nspanel_blueprint.yaml - v4.0
- nspanel_eu.tft or nspanel_us.tft - v4.0
- nspanel_esphome.yaml - v4.0
Instructions
You can find the update procedures following here:
- (EN) How To - All important thing you should know - Update
- (DE) How To - Alle wichtigen Dinge die man wissen sollte - Update
Enable "Current page" sensor
If have used v3.3 or earlier, and then updated to v3.4, there's a chance the entity sensor.xxxxx_current_page
was disabled. As this entity is used again with v4.0, please go to your panel's page (Settings > Devices and Services > ESPHome) and make sure the sensor "Current page" is enabled.
Breaking changes
- New requirements: Home Assistant and ESPHome v2023.5.0 or later.
- Existing users will have to select again the language for the panel, otherwise English will be used to display strings.
- Removed entity
sensor.xxxxx_settings_entity
and serviceesphome.xxxxx_set_settings_entity
. - Removed entity
sensor.xxxxx_nspanel_event
related to sensor "NSPanel Event". So no more of those ugly json-like strings polluting the device's page.
The sensor "Current page" is back with the information about the page currently visible in your panel, so please update your automation if you are using the event sensor.
Attention!! If you have disabled the entitysensor.xxxxx_current_page
in a previous version you will be required to manually enable it back after the update. - Due to the changes on the time display engine, you might have to select your time format again in the blueprint settings.
- The network settings was moved to under
networks
on thewifi
section. If you are using advanced/custom settings for Wi-Fi on ESPHome, you may have to update it in order to follow the new format. - The sensor "Uptime" is deprecated. It was replaced by "API timestamp" and "Device timestamp" sensors, which makes it more readable to humans on Home Assistant interface and shows respectively the last time the API got connected (between the panel and Home Assistant) and the last time the device started. Thanks to @WZYProjects (#986 and #998) for the new sensors.
- Service
esphome.xxxxx_qr_code
is deprecated. It was replaced by serviceqrcode
which can be used for changing the QRcode value even when the QRcode page is not visible (useful when using dynamic Wi-Fi credentials). - Removed switches "Relay 1 Local Fallback" and "Relay 2 Local Fallback". Now when you assign your panel's relay to it's respective button the control will be fully local and therefore will have the same behavior as the "fallback" in previous versions, and you can still force a fallback in the blueprint settings when you want to have it working locally (to the respective relays) even when the buttons are assigned to other entities.
- The "Hardware button long press hold delay" input was removed and the delay (800ms) is now hard coded in ESPHome.
- The service
esphome.xxxxx_wake_up_display
was deprecated. Please useesphome.xxxxx_wake_up
instead. - The services
esphome.xxxxx_send_command_font_color
andesphome.xxxxx_send_command_background_color
where deprecated. Please useesphome.xxxxx_set_component_color
instead, and you can use RGB arrays forforeground
andbackground
colors, a 1-element array with the Nextion color code or an empty array if you don't want to change that specific parameter. - Old color selection (based in a text input where you typed a number) is being deprecated gradually.
The icons colors selected before the implementation of the color picker (when it was about typing a number) might fail now, so if you haven't done this yet, please select the color using the new color selector. Open the Blueprint and if the colors are shown properly, you are good, otherwise, please select a color. - The panel selection based on a text box (where you manually typed the panel name).
The new device selection was introduce a few releases ago and is more reliable. The previous selections are still valid, but requires extra processing every time the automation is triggered, so it will be removed.
If you can see your device name on the blueprint settings screen, you are good, otherwise, pick your panel from the new drop down list. - The entity
switch.xxxxx_confirmation_message
was removed and now the confirmation is processed directly on the Nextion display. - With the new flows for dimming and sleeping, you might have to adjust the page timeout as this have a slightly different name now.
- The switch "Sleep mode" (
switch.xxxxx_sleep_mode
) was removed and it was replaces by "Timeout sleep" (number.xxxxx_timeout_sleep
) where you can set the time to sleep or 0s to disable the sleep mode.
Overview of all changes
- Add-ons support
- Embedded thermostat (cooler or heater) (#917)
- Alarm control panel
- Support to sensor display precision from Home Assistant (#880)
- Filtered device list (#881)
- New language selector (#882)
- Removed json sensors (#887)
- Support for US model on landscape mode (#890)
- API status indication on the panel (#5ff5d35)
- Light & cover settings pages will show only the supported features (#896)
- New "Fan speed page" (#897)
- Select wake-up page (#898)
- Panel's local control
- New "Confirm" pop-up
- Page "Settings" now supports translations
- Media Player control
- Custom buttons on Home page
- New controls for dimming and sleeping time
Details of all changes
1. Support to add-ons
We are trying to make your panel more useful and more robust by changing some of the functionalities to run internally in the panel, even when the Wi-Fi network or Home Assistant are not available, however, every new functionality takes a bit from the ESP embedded in your panel and increases the complexity, and having a code capable to adapt to all the different user cases will be very complex and certainly will exceed the available memory.
The first add-on available is an embedded thermostat, able to control it locally even when your Wi-Fi is out or Home Assistant is unavailable.
Please refer to the documentation to get more details on how to enable this add-on.
2. Alarm control panel
Now you can control an Alarm Control Panel from your NSPanel, which will allow you to set the alarm mode between the standard modes supported by Home Assistant (Home, Away, Night, Vacation or Custom bypass) or disarm the alarm.
On this first release, only the basic functionality will be available, so please share your ideas for future improvements.
For more details, instructions and security considerations, please take a look at the Alarm Control Panel docs. You may also want to join this discussion about the alarm implementation and some ideas for the future releases.
Important: At this moment, this functionality is available only for alarms without a code or alarms using a numeric code. Alarms with text code are not yet supported.
3. Support to sensor display precision from Home Assistant
Now the values shown in your panel will follow the sensor display precision provided by Home Assistant.
- If you have problems with a value exceeding the available space in your panel, please reduce the number of decimals using Home Assistant sensor display precision.
4. Filtered device list
When selecting the NSPanel on the automation, only ESP32 devices will be shown, making easier to find your panel.
5. New language selector
Starts using the new language selector release with HA 2023.5.0 and based on RFC 5646, which will increase reliability and standardization of the code.
Althougt this is not visibl...
v3.4.1 - Patch for issues when compiling with ESPHome 2023.7.0
This is a small patch to fix an issue related to restore_state
option not supported by the latest ESPHome, which was preventing compiling.