This guide provides instructions on how to switch between different versions for each component of this project:
Blueprint, ESPHome, and Nextion TFT, allowing users to access development (dev
), beta, or previous versions.
Warning
Use non-main versions at your own risk. Only the main
/latest release is officially supported.
Important
Ensure all three components (Blueprint, ESPHome, TFT) are synchronized at the same version for system stability.
- ESPHome: Start with ESPHome for its straightforward update process.
- TFT: Then proceed with Nextion TFT.
- Blueprint: Finally, update Blueprint, as it requires more manual effort and careful handling.
For available versions and branches, visit: NSPanel_HA_Blueprint Tags.
Take note of the branch (dev
, beta
, or main
) or version name exactly as it is published, as this is case-sensitive.
Note
Understanding Tags in GitHub Tags on GitHub mark specific versions of a project, akin to bookmarks. They're created for each new release, allowing easy access to different project stages.
- dev: The development version, containing the latest code but potentially unstable.
- beta: The pre-release version, more stable than
dev
but still undergoing final testing. - main: The default latest version, where you will find the most recent release code.
Note
When using dev
or beta
, report findings in the issues section, clearly stating the version.
Please do not report issues related to old released versions.
-
Open your device's YAML config and find the key
ref:
, which is underremote_package:
in thepackages:
area: -
Change the value of
ref:
to the version you want to install, likeref: dev
orref: v4.1.4
: -
Save your settings and then install it.
Important
Older versions may require arduino
framework.
Please refer to this guide for setting the framework properly: Change framework
Warning
Older versions of the components may not be compatible with the latest ESPHome compiler or Home Assistant.
Ensure you are using a compatible version of Home Assistant and the compiler when working with older project versions to avoid potential issues. You can use our Version compatibility matrix to identify the minimum requirement per version as a reference for possible version incompatibility, although we don't have a register of the "Maximum version" supported.
The instructions to upload TFT will vary depending on the version you are installing and the framework you are using.
- Go to your device's page under Settings > Devices & services > ESPHome.
- On the Configuration group, press Update TFT display and wait for the upload to complete. The system will automatically find the right TFT file for the ESPHome version you are running.
-
On the GitHub repository, click on your chosen version name on the NSPanel_HA_Blueprint Tags list, then select the tab Code.
-
Double-check that the correct version is shown below the repository name:
-
Locate the TFT file related to your model and download it to your local http server.
-
Double check your
nextion_update_url
substitution is pointing to the right URL where the file you just downloaded is available. -
Go to your device's page under Settings > Devices & services > ESPHome.
-
On the Configuration group, press Update TFT display and wait for the upload to complete.
- Use your preferred code editor to edit the blueprint file under
/homeassistant/blueprints/automation/Blackymas/nspanel_blueprint.yaml
. - Go to the GitHub repository and select the branch (
main
,beta
ordev
) or the tag (for previous versions) you want to use. - Find the file
nspanel_blueprint.yaml
in the root of the branch/tag, then click on it to open the file content visualization. - Click the button "Copy raw file" in the top right area of the code box. This will copy the entire code to the clipboard.
- Go back to your code editor in Home Assistant and replace the entire old code by the one in your clipboard (typically CTRL+A & CTRL+V).
- Go to Developer Tools, select the tab YAML and click the button to reload AUTOMATIONS.
- Please note that the images provided in this guide might become outdated as the project evolves. It's always a good idea to refer to the latest version of the project for current details.
- For the most up-to-date information and updates, refer to the project's documents and check the issues and discussions sections on our GitHub repository.