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.
For available versions and branches, visit: NSPanel Easy 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 but still undergoing final testing.[!NOTE] When using
devorbeta, 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 under remote_package: in the packages: area:

Change the value of ref: to the version you want to install, like ref: dev or ref: v4.1.4:

Save your settings and then install it.
[!IMPORTANT] Older versions may require
arduinoframework. 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. For guidance on minimum requirements, see our Version compatibility matrix policy.
[!NOTE] The TFT version is automatically matched to your ESPHome version—no manual version selection is required.
/config/blueprints/automation/edwardtfn/nspanel_easy_blueprint.yaml.main, beta or dev)
or the tag (for previous versions) you want to use.nspanel_easy_blueprint.yaml in the root of the branch/tag, then click on it to open the file content visualization.