How often are there TFT updates?

[andreaskoelsch]

I just recently flashed a panel with NSPanel Easy and like it so far. I also want to use it as bt proxy, but then I saw that there's already a new TFT version out which means manual effort every time. So, I'm wondering if there's an estimate how often the TFT changes. Is it with every blueprint release, i.e. every few days, or not that often?
Thanks

[edwardtfn]

If your panel have access to github, the TFT upload shouldn't be any manual work, as the panel is capable to update it automatically when needed.
The TFT doesn't have to be updated with every release, but every time we implement a change in the TFT side, it is required to update... Some time it stays stable for a couple of months, but sometimes happens that we have two TFT updates in the same week.

I would definitely focus on enabling the auto update.

[edwardtfn]

Yes, it work with BT proxy and the docs shouldn't say otherwise.

Note that this has nothing to do with web_server. It is just normal settings for your panel... if you don't specify the Nextion URL, it will try to get the TFT directly from GitHub and unless your network blocks that, it should be transparent.

Maybe it would be better if you share your panel's yaml and I would be able to recommend something. 😉

[andreaskoelsch]

Hmm, I wasn't talking about web_server. The docs state in multiple places that bluetooth proxy and tft update should not be enabled at the same time.

https://github.com/edwardtfn/NSPanel-Easy/blob/main/docs/install.md#practical-example-bluetooth-proxy-integration
https://github.com/edwardtfn/NSPanel-Easy/blob/main/docs/addon_upload_tft.md#memory-considerations

The TFT upload process requires a significant amount of free memory on the ESP32. If you are running memory-intensive components such as Bluetooth Proxy alongside this add-on, the TFT upload may fail due to insufficient memory.

Bluetooth components commented out during TFT updates
- esphome/nspanel_esphome_addon_upload_tft.yaml # Enable for updates

For reference, this is my current yaml

  # Settings - Editable values
  device_name: "nspanel_schlafzimmer"
  friendly_name: "NSPanel Schlafzimmer"
  wifi_ssid: !secret wifi_ssid
  wifi_password: !secret wifi_password
  ota_password: ""  # Optional: set OTA password, or use ${wifi_password} for backward compatibility (see migration guide)
  language: de      # Language code - see docs/localization.md for all supported codes
  boot_sound: false
  # Add-on configuration (if needed)
  ## Upload TFT
  upload_tft_automatically: true
  ## Climate add-on
  # heater_relay: "1"  # Possible values: "1" or "2"

# Customization area
##### My customization - Start #####
# Optimized Bluetooth Proxy configuration
# Enable either TFT Upload or Bluetooth!
bluetooth_proxy:

esp32_ble_tracker:
  scan_parameters:
    continuous: false

api:
  encryption:
    key: "---redacted---"
  on_client_connected:
    then:
      - esp32_ble_tracker.start_scan:
          continuous: true
  on_client_disconnected:
    then:
      - esp32_ble_tracker.stop_scan:

##### My customization - End #####

# Core and optional configurations
packages:
  remote_package:
    url: https://github.com/edwardtfn/NSPanel-Easy
    ref: latest
    refresh: 300s
    files:
      # - nspanel_esphome.yaml # Basic package
      - esphome/nspanel_esphome_core.yaml
      - esphome/nspanel_esphome_standard.yaml
      # Enable either TFT Upload or Bluetooth!
      # - esphome/nspanel_esphome_addon_upload_tft.yaml

[HACS-bank]

There is now an addon_bluetooth_proxy.yaml which includes a few tweaks to improve coexistence. I use it with automatic updates of TFT, no problems.

[HACS-bank]

https://edwardtfn.github.io/NSPanel-Easy/addon_bluetooth_proxy.html

this was just published a few weeks ago 😄

[panel-easy-assistant[bot]]

Hi @andreaskoelsch, I'm the assistant helping @edwardtfn with the project.

You are right, those sections of the docs are outdated, sorry for the confusion. The TFT upload add-on now stops the Bluetooth stack and releases its memory before starting the upload, so both can be enabled at the same time. The docs are being updated in #584.

Two notes on your yaml:

1. upload_tft_automatically: true has no effect while esphome/nspanel_esphome_addon_upload_tft.yaml is commented out, so automatic TFT updates are currently not active on your panel.
2. There is now a dedicated Bluetooth Proxy add-on that replaces the custom block. It only scans while Home Assistant is connected and ignores logger-only connections.

Here is your yaml with these changes applied (replace the redacted encryption key with yours):

substitutions:
  # Settings - Editable values
  device_name: "nspanel_schlafzimmer"
  friendly_name: "NSPanel Schlafzimmer"
  wifi_ssid: !secret wifi_ssid
  wifi_password: !secret wifi_password
  ota_password: ""  # Optional: set OTA password, or use ${wifi_password} for backward compatibility (see migration guide)
  language: de      # Language code - see docs/localization.md for all supported codes
  boot_sound: false
  # Add-on configuration (if needed)
  ## Upload TFT
  upload_tft_automatically: true
  ## Climate add-on
  # heater_relay: "1"  # Possible values: "1" or "2"

# Customization area
##### My customization - Start #####
api:
  encryption:
    key: "---redacted---"
##### My customization - End #####

# Core and optional configurations
packages:
  remote_package:
    url: https://github.com/edwardtfn/NSPanel-Easy
    ref: latest
    refresh: 300s
    files:
      - nspanel_esphome.yaml  # Basic package (includes the TFT upload add-on)
      # Optional add-ons
      - esphome/nspanel_esphome_addon_bluetooth_proxy.yaml

Edit: replaced the suggested files list with your full yaml, using the basic package, which already includes core, standard and the TFT upload add-on.

If an upload ever fails, please open an issue with the details requested in the bug template, including your panel yaml and the ESPHome logs from the upload attempt.