h3n3/NSPanel_HA_Blueprint
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
b086ccc16d359ffbcf0ab6f91fcb716ddc2e99a4
NSPanel_HA_Blueprint/ReleaseNotes.md
Edward Firmo c97be551c0 Enhanced control for automation entities on buttons 
Solves #1291
Solves #810
Solves #1249
Solves #1291
Solves #320
Solves #331
2023-12-18 12:11:57 +01:00

12 KiB
Raw Blame History

v4.2 <= pending update

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 ;)

Paypal

 

General <= pending update

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

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:

  1. nspanel_eu.tft, nspanel_us.tft or nspanel_us_land.tft - v4.2
  2. nspanel_esphome.yaml - v4.2
  3. nspanel_blueprint.yaml - v4.2

Instructions

You can find the update procedures following here:

 

Breaking changes

  1. The background parameter in the esphome.xxxxx_set_component_color service is now deprecated.
  2. With the introduction of additional custom buttons, the layout of other buttons on the home page has been adjusted.
  3. 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 as LIGHT, 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 #####

  1. The default baud rate for advanced mode has been reverted to 115200 bps to resolve issues that arise when rendering button pages.

  2. 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.

  3. 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.

  4. Documentation in German is no longer maintained. This change allows us to more efficiently update and maintain the remaining documentation.

  5. 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.

 

Overview of noteworthy changes

  1. Standardized entity's icons
  2. Additional custom buttons on Home page
  3. Outdoor temperature selectable font size
  4. Select icon size for button's pages
  5. Support to Chinese (Taiwan) and prepared for other CJK languages
  6. Upload baud rate selectable as substitution
  7. Multiple Alarm Control Panels
  8. Support to remote
  9. Home page chips now supports covers
  10. Chips can be inverted
  11. Add swipe control to screensaver page
  12. Enhanced control for automation entities on buttons

 

Details of noteworthy changes

1. Standardized entity's 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.

 

2. Additional custom buttons on Home page

It's that simple, now you have 7 buttons where used to be 3. Well, where used to be 4, as the space previously used by the Alarm button is now a custom button. 😉

 

3. Outdoor temperature selectable font size

Now you can select the font size of your outdoor temperature display:

image

Important: Long text with bigger fonts may exceed the limit of space reserved for this with incomplete information shown.

 

4. Select icon size for button's pages

You can also select the size of the icons on the buttos pages:

<> <<add page screenshot (US and EU)>>

 

5. Support to Chinese (Taiwan) and prepared for other CJK languages

You will find 3 new TFT files on the repository for the CJK languages. These files are considerably bigger, as the fonts requires more memory, but it should work fine in your panel. Currently only translations to Chinese (Taiwan) are available, but as soon we get the strings for other languages we will be happy to add to the blueprint selection. << Add screenshots of blueprint >>

 

6. Upload baud rate selectable as substitution

You can select an alternative baud rate for your TFT uploads. This allows faster TFT uploads and also supports displays previously set with baud rates not supported by this project (currently 115200 bps and 921600 bps).

To enable an alternative upload TFT baud rate, add the desired value in your substitutions like this:

  upload_tft_baud_rate: "921600"

If an invalid value is entered or this substitution is not present, the current baud rate will be used.

The system will always fall back to the standard baud rate (115200 bps) if other tentatives fails.

 

7. Multiple Alarm Control Panels

Now alarm control panel entities can be assigned to chips and custom buttons in the Home page, but also to hardware buttons, any of the buttons pages or entities pages, similarly to other domains.

 

8. Support to remote

Entities from the remote domain can now be assigned to buttons (hardware and buttons pages) and custom buttons (home and climate pages).

The service remote.toggle will be called when the button is pressed.

 

9. Home page chips now supports covers

That's it! Chips now include cover visualization, allowing for easy monitoring of covers directly from the Home page.

 

10. Chips can be inverted

Chips now have an 'invert' option on the blueprint settings, providing additional customization flexibility.

 

11. Add swipe control to Screensaver page

You can now navigate to button pages from the screensaver while your panel is in sleep mode. The swipe controls will function as they do on the Home page.

 

12. Enhanced control for automation entities on buttons

We're pleased to announce a new feature that offers users enhanced control over their smart home setups. Now, you can globally select between Toggle and Trigger actions for button presses on automation entities. This update allows for a more personalized and efficient control experience, tailored to your unique preferences.

Key features:

  • Toggle: This action will enable or disable the automation. It is set as the default option.
  • Trigger: This action will execute the automation regardless of its current state, providing more flexibility.

How to use:

  1. Access your configuration for automation under Services > Automations & Scenes. Select the automation associated with your panel setup.
  2. Scroll to the ADVANCED SETTINGS section at the end.
  3. From the menu, select your desired action - either Toggle or Trigger.
  4. Apply the setting. This will then be effective across all relevant entities.

This update is specially designed to cater to diverse user needs, ensuring a more intuitive and responsive smart home experience.  

What's Next?

Discover what's next and what we are working on right now in our Milestones

 

Special thanks to:

New Contributors

Previous releases

Reference in New Issue View Git Blame Copy Permalink