Blackymas / NSPanel_HA_Blueprint

This allows you to configure your complete NSPanel via Blueprint with UI and without changing anything in the code
1.26k stars 234 forks source link

`Bug` NSPanel invalid Blueprint version #1966

Closed AntonMilushev76 closed 3 months ago

AntonMilushev76 commented 3 months ago

TFT Version

4.3.1

ESPHome Version

4.3.1

Blueprint Version

4.3.1

Panel Model

EU

What is the bug?

After updating to version 4.3.1, by my mistake I updated the firmware before updating the tft and blueprint, and now I'm getting a mishmash blueprint message from esphome.

NSPanel invalid Blueprint version
ESPHome cannot provide a valid Blueprint version.
Panel:
TFT: 4.3.1
ESPHome: 4.3.1
Blueprint (reported by ESPHome): Unknown
Blueprint (installed): 4.3.1

Steps to Reproduce

No response

Your Panel's YAML

substitutions:
  # Settings - Editable values
  device_name: nspanellr
  wifi_ssid: !secret wifi_ssid
  wifi_password: !secret wifi_password
  nextion_update_url: "https://github.com/Blackymas/NSPanel_HA_Blueprint/raw/main/nspanel_eu.tft"  # Optional for `esp-idf` framework
  # Add-on configuration (if needed)
  # heater_relay: "1"  # Possible values: "1" or "2"

# Customization area
##### My customization - Start #####
##### My customization - End #####

# Core and optional configurations
packages:
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: main
    files:
      - nspanel_esphome.yaml # Core package
      # Optional advanced and add-on configurations
      # - advanced/esphome/nspanel_esphome_advanced.yaml
      # - nspanel_esphome_addon_climate_cool.yaml
      # - nspanel_esphome_addon_climate_heat.yaml
      # - nspanel_esphome_addon_climate_dual.yaml
    refresh: 300s

esp32:
  framework:
    type: esp-idf

ESPHome Logs

No response

Home Assistant Logs

No response

AntonMilushev76 commented 3 months ago

[E][script.check_versions:1872]: Blueprint version mismatch! - This is from the logs of nspanel

edwardtfn commented 3 months ago

Could you please change your substitutions from device_name: nspanellr to name: nspanellr, flash your panel again and let me know if that solved this issue?

AntonMilushev76 commented 3 months ago

Тhanks for the reply. I changed my substitutions from device_name: nspanellr to name: nspanellr and flashed it to nspanel, but the result is the same. In the logs of the panel, as before, this is also appear: [15:54:58][W][component:232]: Component script took a long time for an operation (66 ms). [15:54:58][W][component:233]: Components should block for at most 30 ms.

[E][script.check_versions:1872]: Blueprint version mismatch!

edwardtfn commented 3 months ago

Now please try the last step (reconnect panel) from table in this guide: https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/main/docs/error_initializing.md#blueprint-is-not-detected

You can try the other steps also, but I think in your case it looks more like that last one. 😉

AntonMilushev76 commented 3 months ago

Everything works now, but esphome keeps reporting the same problem with the blueprint. I will wait for the next update, probably the problem comes from the integration. Thanks for help.

edwardtfn commented 3 months ago

esphome keeps reporting the same problem with the blueprint

Could you please share that message from ESPHome? You shouldn’t be receiving any error there, so nothing related to this is being fixed in the coming version, I think.

AntonMilushev76 commented 3 months ago

error1 error2

AntonMilushev76 commented 3 months ago

ppp

AntonMilushev76 commented 3 months ago

I tried everything, system restore before esphome update, then esphome update, then blueprint update, then tft update and finally nspanel firmware update , but I couldn't get rid of the blueprint warning.

AntonMilushev76 commented 3 months ago

And this is ha log 2024-03-22 22:37:36.781 ERROR (MainThread) [homeassistant.components.automation.nspanel_configuration] NSpanellr: Main choices: Automation reloaded: If at step 3: Error executing script. Invalid data for call_service at pos 3: expected int for dictionary value @ data['outdoor_temp_font'] 2024-03-22 22:37:36.783 ERROR (MainThread) [homeassistant.components.automation.nspanel_configuration] NSpanellr: Main choices: Automation reloaded: Error executing script. Invalid data for if at pos 3: expected int for dictionary value @ data['outdoor_temp_font'] 2024-03-22 22:37:36.783 ERROR (MainThread) [homeassistant.components.automation.nspanel_configuration] NSpanellr: Error executing script. Invalid data for choose at pos 3: expected int for dictionary value @ data['outdoor_temp_font'] 2024-03-22 22:37:36.784 ERROR (MainThread) [homeassistant.components.automation.nspanel_configuration] Error while executing automation automation.nspanel_configuration: expected int for dictionary value @ data['outdoor_temp_font'] 2024-03-22 22:37:40.767 ERROR (MainThread) [homeassistant.components.automation.nspanelbath] NSpanelbath: Main choices: Automation reloaded: If at step 3: Error executing script. Invalid data for call_service at pos 3: expected int for dictionary value @ data['outdoor_temp_font'] 2024-03-22 22:37:40.768 ERROR (MainThread) [homeassistant.components.automation.nspanelbath] NSpanelbath: Main choices: Automation reloaded: Error executing script. Invalid data for if at pos 3: expected int for dictionary value @ data['outdoor_temp_font'] 2024-03-22 22:37:40.769 ERROR (MainThread) [homeassistant.components.automation.nspanelbath] NSpanelbath: Error executing script. Invalid data for choose at pos 3: expected int for dictionary value @ data['outdoor_temp_font'] 2024-03-22 22:37:40.772 ERROR (MainThread) [homeassistant.components.automation.nspanelbath] Error while executing automation automation.nspanelbath: expected int for dictionary value @ data['outdoor_temp_font']

edwardtfn commented 3 months ago

2024-03-22 22:37:36.781 ERROR (MainThread) [homeassistant.components.automation.nspanel_configuration] NSpanellr: Main choices: Automation reloaded: If at step 3: Error executing script. Invalid data for call_service at pos 3: expected int for dictionary value @ data['outdoor_temp_font']

Please go to your automation (the one using the Blueprint) and let me know what is selected as the font for outdoor temperature font size.

IMG_6739

AntonMilushev76 commented 3 months ago

Тhis was the reason, after the blueprint update, the font size field was left empty. Now everything is working normally. Thank you very much