Error: "Authentification invalid. Is the password correct?"

[CristianN87]

TFT Version

No response

Firmware Version

No response

Blueprint Version

No response

Panel Model

None

What is the bug?

When I try to install this yaml configuration on my NSpanel, which was used in the past with an custom configuration like an thermostat, I strugle with this issue regarding the "Authentification invalid". What can I do more or what I am not doing correct?

Steps to Reproduce

No response

Your Panel's YAML

substitutions:
  # Settings - Editable values
  device_name: "termostat-living"
  friendly_name: "Termostat Living"
  wifi_ssid: !secret wifi_ssid
  wifi_password: !secret wifi_password
  # Optional
  nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/v4.2.5/nspanel_eu.tft"
  # 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
# we try dev instead of main due to commits for the tft uplaod problem
packages:
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: main
    refresh: 300s
    files:
      - nspanel_esphome.yaml # Basic package
      # Optional advanced and add-on configurations
      # - esphome/nspanel_esphome_advanced.yaml
      # - esphome/nspanel_esphome_addon_ble_tracker.yaml
      # - esphome/nspanel_esphome_addon_bluetooth_proxy.yaml
      # - esphome/nspanel_esphome_addon_climate_cool.yaml
      # - esphome/nspanel_esphome_addon_climate_heat.yaml
      # - esphome/nspanel_esphome_addon_climate_dual.yaml
      # - esphome/nspanel_esphome_addon_cover.yaml

ESPHome Logs

No response

Home Assistant Logs

No response

[edwardtfn]

Do you still know the previous ota password used on this device, if any?

Please try adding this as a customization to your panel's Yaml:

ota:
  - id: !extend ota_std
    password: !remove

[CristianN87]

Hello @edwardtfn , thank you for your very fast answer.
Yes, I have one file saved on my PC with the old YAML configuration.

ota:

• id: !extend ota_std
  password: !remove
  This will remove the old password, or what will do?

[edwardtfn]

Hello @edwardtfn , thank you for your very fast answer.

🙂

Yes, I have one file saved on my PC with the old YAML configuration.

Good!
So please try this:

ota:
  - id: !extend ota_std
    password: <<your-old-ota-password>>

ota:

• id: !extend ota_std
  password: !remove
  This will remove the old password, or what will do?

This will try to install without using any password.

[edwardtfn]

If nothing works, you can always flash it using a serial/USB cable, as this password is not required in that case. 😉

[CristianN87]

I managed to flash-it with your recomandation, but right now I don't know if is OK flashed because right now, the HMI is showing only the hour and is not active when I touch it.(is freez like this).

[edwardtfn]

On the automation you created using the Blueprint, please make sure the panel is selected.

[CristianN87]

Attached you can find the logs after the flashing. Are they normal? I see a error like : Nextion reported variable name invalid! and also TFT: Unknown! Is this normal?...:)
logs_termostat-living_run (2).txt

[edwardtfn]

The Nextion reported variable name invalid! is most likely related to an older TFT installed.
Please go to the device's page in Home Assistant (under Settings > Devices & services > ESPHome) and click Update TFT.

I also see some error related to API:

[11:34:52][W][api.connection:108]: : Reading failed: BAD_INDICATOR errno=11

This one is most likely related to some instability in your network or HA.

[CristianN87]

I think something I do wrong when I am flashing or maybe when I am upload the TFT, because the device is not available in Home Assistant under the ESPHome.

[CristianN87]

Also, after I uploaded the TFT file nspanel_eu.tft and I used my old configuration the display of the NSpanel look like in the picture attached, but the device where active in HomeAssistent under ESPHome. I really don't know what I am doing wrong!!

[CristianN87]

HI @edwardtfn ,
I managed to solve the availability in ESP Home of this NSpanel by adding the api encryption and the password for the api in YAML file.
I will inform you how I progress with this.
Thank you!

[CristianN87]

It's working, finally!!! Thank you for support!
It looks amazing, you did a very good job with!!
Thank you again!

[edwardtfn]

Nice to hear that...
It should work without the API encryption or password, but in this case you have to remove it from Home Assistant and wait a couple of minutes until it is detected again and can integrate without the security.

[jafreenas]

Hi ,
can you describe how to do this in yaml?