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 235 forks source link

After the NSPANEL restart, it does not connect to WiFi.`Bug` #1896

Closed KoKolaj closed 2 months ago

KoKolaj commented 3 months ago

TFT Version

4.3

ESPHome Version

4.3

Blueprint Version

4.3

Panel Model

EU

What is the bug?

After the NSPANEL restart, it does not connect to WiFi. I noticed that after the restart, when the panel triggers, it reports the ESPHOME 4.2.6 version. Immediately afterwards, he will not join WiFi. I have to record Yaml again, and then the panel reports the right version of ESPHOME 4.3. And it will join WiFi. But if I restart the panel again, it is repeated. The panel again shows version 4.2.6 at the start WiFi will not join again ... This error is the same for all panels I own. 3x EU panel and 1x Us panel ...

Steps to Reproduce

No response

Your Panel's YAML

substitutions:

###### CHANGE ME START ######

 device_name: "nspanel_room"
 wifi_ssid: !secret wifi_ssid
 wifi_password: !secret wifi_password

 nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_eu.tft" # URL to Github

##### CHANGE ME END #####

##### DO NOT CHANGE ANYTHING! #####

packages:
  ##### download esphome code from Github
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: main
    files: [nspanel_esphome.yaml]
    refresh: 300s

##### DO NOT CHANGE ANYTHING! #####

ESPHome Logs

No response

Home Assistant Logs

No response

plasterer41 commented 3 months ago

I suspect you are still on Arduino and haven’t flashed the esp-idf version yet

KoKolaj commented 3 months ago

I suspect you are still on Arduino and haven’t flashed the esp-idf version yet

Meaculpa

It's as you write. The addition helped ESP32: Framework: Type: ESP-IDF

Thank you very much.

edwardtfn commented 3 months ago
edwardtfn commented 2 months ago

Hey @KoKola, are you still having this issue or should we close this?