Blackymas / NSPanel_HA_Blueprint

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

ESPHome 2023.11.6 brakes my panel #1350

Closed synack666 closed 8 months ago

synack666 commented 8 months ago

After update ESPHome to 2023.11.6 my panel wont come back. Still in "initializing..." Have tried power off/on, and reboot. During the flashing after update in log was a "exit reparse". With ESPHome i can see logs wirelessly.

Any idea what could solve this?

edwardtfn commented 8 months ago

On the blue boot screen, which versions are shown for TFT, ESPHome and Blueprint?

NC1609 commented 8 months ago

Good morning same here. TFT: 4.1.1 ESPHome: nothing Blueprint: Retry 1...2...3 and so on.

synack666 commented 8 months ago

only TFT with 4.1, the other wont come

Zealand67 commented 8 months ago

Same issue here. Update ESPHome to 2023.11.6 break both my NSPanels. Panel show same information as NC1609

carter013 commented 8 months ago

Hello, same here

NC1609 commented 8 months ago

Hello, some additional information of the logs:

[W][component:214]: Component esphome.coroutine took a long time for an operation (1.53 s). [W][component:215]: Components should block for at most 20-30ms. [E][on_boot:054]: No response from Nextion display

edwardtfn commented 8 months ago

I'm trying to duplicate this...

Anyone could please capture logs from a restart from the boot for around 2 minutes and share it here?

randomcoffeesnob commented 8 months ago

Same here. I think it even started on 2023.11.4 I hoped .6 would fix it, but I am still in the mentioned loop.

edwardtfn commented 8 months ago

On your ESPHome yaml, what is the value for ref: under remote_package?

NC1609 commented 8 months ago

On your ESPHome yaml, what is the value for ref: under remote_package?

ref: main

synack666 commented 8 months ago

logs_nspanel_logs.txt

ref: main

randomcoffeesnob commented 8 months ago

logs_nspanel_logs.txt

edwardtfn commented 8 months ago

Could you please change to ref: beta, install it to your panel (wirelessly is ok), and capture the logs again, please?

edwardtfn commented 8 months ago

I've reverted all to v4.1.1, with ESPHome 2023.11.6 and cannot duplicate the issue you are reporting. My panel works just fine. 😞

randomcoffeesnob commented 8 months ago

logs_nspanel_run.txt

Nothing changed in my case after switching to beta.

edwardtfn commented 8 months ago

Could you please share your ESPHome yaml? Please hide any sensitive info before sharing.

NC1609 commented 8 months ago

Could you please share your ESPHome yaml? Please hide any sensitive info before sharing.


substitutions:
CHANGE ME START

device_name: "badezimmer_panel" wifi_ssid: "'###" wifi_password: "#################"

nextion_update_url: "http://192.168.178.102:8123/local/nspanel_eu.tft" # URL to local tft File

nextion_update_url: "http://192.168.178.102:8123/local/nspanel_blank.tft" # URL to local tft File

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

edwardtfn commented 8 months ago

Ok, nothing special... very similar to mine, which is working.

synack666 commented 8 months ago

logs_nspanel_run.txt

substitutions:

###### CHANGE ME ######

  device_name: "nspanel" 
  wifi_ssid: xxxxxxxx
  wifi_password: xxxxxxxxxxxxxxx

##### CHANGE ME #####

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

  nextion_update_url: "http://192.168.0.171:8123/local/nspanel_eu.tft" # URL to local tft File
packages:
  ##### download esphome code from Github
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: beta
    files: [nspanel_esphome.yaml]
    refresh: 300s

##### DO NOT CHANGE ANYTHING! #####
edwardtfn commented 8 months ago

image I think I could duplicate... Working on it.

edwardtfn commented 8 months ago

So, as a temporary solution, changing from ref: main to ref: "v4.1" worked for me. I will continue investigating for a more permanent solution.

edwardtfn commented 8 months ago

I don't understand... now ref: main is working again.

Anyone else tried ref: "v4.1" successfully?

NC1609 commented 8 months ago

"v4.1"

flashing to v4.1 -> don´t work flashing to main again -> same result don´t work

synack666 commented 8 months ago

same as NC1609

rjperezcolmenar commented 8 months ago

Same here. flashing to beta: not working flashing to v4.1: not working flashing again to main: not working

I have this line when showing the logs: [09:21:17][E][on_boot:054]: No response from Nextion display

damminh88 commented 8 months ago

same here: all not working

albkk commented 8 months ago

Same here. I did restore from backup with ESPHome 2023.11.4 and flashed panel with ESPHome 2023.11.4, but still stuck initializing...

synack666 commented 8 months ago

Same here. I did restore from backup with ESPHome 2023.11.4 and flashed panel with ESPHome 2023.11.4, but still stuck initializing...

yes, one of my unsuccessful attempts too

Cody8Bit commented 8 months ago

Hello, I have the same error, the log shows: [W][component:214]: Component esphome.coroutine took a long time for an operation (1.53 s). [W][component:215]: Components should block for at most 20-30ms. [E][on_boot:054]: No response from Nextion display

mariusvaida commented 8 months ago

Same here with the same error in the logs as @Cody8Bit wrote.

edwardtfn commented 8 months ago
[W][component:214]: Component esphome.coroutine took a long time for an operation (1.53 s).
[W][component:215]: Components should block for at most 20-30ms.
[E][on_boot:054]: No response from Nextion display

This is ESPHome trying to recover from a non-responsive display. It turn off the display for a couple of seconds, then turn on, wait a few more seconds... all the waits are causing this took a long time for an operation...

edwardtfn commented 8 months ago

Could someone please try adding this to the ESPHome yaml, install it (wireless is ok) and let me know the results (logs, please)?

external_components:
  - source: github://pr#5829
    components:
      - nextion
    refresh: 1s
lloydbayley commented 8 months ago

Bingo! Well discovered @edwardtfn

edwardtfn commented 8 months ago

Ok, now I have to work in a permanent fix for this. Please keep those lines for now. I will let you know when those are not needed anymore.

lloydbayley commented 8 months ago

I've just tested it out on both the US Panel (Portrait-Only) & the EU Panel. All features working and nothing to report.

damminh88 commented 8 months ago

Could someone please try adding this to the ESPHome yaml, install it (wireless is ok) and let me know the results (logs, please)?

external_components:
  - source: github://pr#5829
    components:
      - nextion
    refresh: 1s

it works

synack666 commented 8 months ago

stupid.... where exact i have to insert?

edwardtfn commented 8 months ago

where exact i have to insert?

Try like this:

substitutions:

###### CHANGE ME ######

  device_name: "nspanel" 
  wifi_ssid: xxxxxxxx
  wifi_password: xxxxxxxxxxxxxxx

##### CHANGE ME #####

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

  nextion_update_url: "http://192.168.0.171:8123/local/nspanel_eu.tft" # URL to local tft File
packages:
  ##### download esphome code from Github
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: beta
    files: [nspanel_esphome.yaml]
    refresh: 300s

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

##### Temporary code #####
external_components:
  - source: github://pr#5829
    components:
      - nextion
    refresh: 1s
wobi07 commented 8 months ago

Danke ! FĂźr die ganzen Infos. Ich habe gleiche Probleme, werde aber nun erst einmal abwarten.

Parateam commented 8 months ago

läuft bei mir auch wieder, danke!

synack666 commented 8 months ago

where exact i have to insert?

Try like this:

substitutions:

###### CHANGE ME ######

  device_name: "nspanel" 
  wifi_ssid: xxxxxxxx
  wifi_password: xxxxxxxxxxxxxxx

##### CHANGE ME #####

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

  nextion_update_url: "http://192.168.0.171:8123/local/nspanel_eu.tft" # URL to local tft File
packages:
  ##### download esphome code from Github
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: beta
    files: [nspanel_esphome.yaml]
    refresh: 300s

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

##### Temporary code #####
external_components:
  - source: github://pr#5829
    components:
      - nextion
    refresh: 1s

thanks a lot, it works!!

bevore i have had a space in line to much....yaml dont like that g, my fault

lloydbayley commented 8 months ago

Danke ! FĂźr die ganzen Infos. Ich habe gleiche Probleme, werde aber nun erst einmal abwarten.

@edwardtfn arbeitet schnell daran! (Or should that be darauf?... My German could do with some refreshing) :)

synack666 commented 8 months ago

just my thought, even big established companies don't get that kind of support, thank you very much

smarthomefamilyverrips commented 8 months ago
##### Temporary code #####
external_components:
  - source: github://pr#5829
    components:
      - nextion
    refresh: 1s

@edwardtfn do have to use beta version or can let "ref:" on main

synack666 commented 8 months ago

should i close down here, a solution has been found?

smarthomefamilyverrips commented 8 months ago
##### DO NOT CHANGE ANYTHING! #####

@synack666 maybe you also can answer my question, do I need to use "ref: beta" or can i let it on "ref: main" ?

synack666 commented 8 months ago
##### DO NOT CHANGE ANYTHING! #####

@synack666 maybe you also can answer my question, do I need to use "ref: beta" or can i let it on "ref: main" ?

i have it on "main"

smarthomefamilyverrips commented 8 months ago
##### DO NOT CHANGE ANYTHING! #####

@synack666 maybe you also can answer my question, do I need to use "ref: beta" or can i let it on "ref: main" ?

i have it on "main"

Thanks will try it now, hope will work for me also 👍

lorddagobert commented 8 months ago

Thank you ... I had the same issue ... now it work fine again

Cody8Bit commented 8 months ago

Thank you very much for the quick solution, I had the problem and it has been solved.