search

Blackymas / NSPanel_HA_Blueprint

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

TFT stopped #870

Closed Jens-Wymeersch closed 8 months ago

Jens-Wymeersch commented 1 year ago

Hi,

I've had the panel working previously till it started to show a blue screen. Yesterday, I pressed Update TFT display - button. At approx 50%, it stopped and gave me the following error message

[E][uart:015]: Reading from UART timed out at byte 0! [W][nextion:072]: Nextion is not connected!

Today, I reflashed the board and tried the process again with unfortunately the same result. Any idea what I can do ?

edwardtfn commented 1 year ago

I would suggest you to install ESPHome back to your panel and then follow this guide to upload TFT: https://github.com/Blackymas/NSPanel_HA_Blueprint/wiki/(EN)-Common-Issues-TFT-Upload

edwardtfn commented 1 year ago

I've had the panel working previously till it started to show a blue screen.

When you mention a blue screen, I suspect you are talking about the boot screen, which is blue and contains some useful information for troubleshooting:

  1. Is it showing the IP address in the top?
  2. What are the versions for TFT, ESPHome and Blueprint shown on your screen.

The most common reason it gets stuck on this screen is a mismatch between the version (usually caused by ESPHome automatically updating to the latest version and requiring manual update of Blueprint and TFT). If the versions are all the same, a restart should fix this issue (Settings > Devices and Services > ESPHome > Your device > Press restart).

Jens-Wymeersch commented 1 year ago

@edwardtfn Thank you for your comments. I've re-installed Esphome again without success multiple times without success. I've added also the following :

external_components:
  - source: github://pr#2956
    components: [nextion]
    refresh: 1h

I had the blue screen initially you indicated above. But after pressing Update TFT display button, the update went till 50% and stopped. Now I'm actually getting a black screen and an error System Data ERROR. Not sure what to do now ?

rleongcs commented 1 year ago

@Jens-Wymeersch It is fine with the System Data Error screen. I would suggest killing the power to the switch and re-applying power. After that, you can update the blank tft first and see if everything is fine. If all is good, then update the normal tft.

edwardtfn commented 1 year ago

As @rleongcs mentioned, you can just try again. And the nspanel_blank.tft is always a good idea. If you get the blue screen again, please don't try to install the TFT or ESPHome again, as that bluescreen is most likely from the TFT already installed. Take a picture instead, and share here so we will be able to help more. Based on what you are saying, looks like a version mismatch between TFT, ESPHome and the Blueprint, and that screen should show which one is behind.

Jens-Wymeersch commented 1 year ago

@rleongcs @edwardtfn I've put the nspanel_blank.tft. This ran perfectly, but instead of getting the blue screen, I got my QR code to the github page. The logs don't show any errors any more.

This is what i see in the logs :

[19:07:20][D][main:790]: Nextion start - Inform Home Assistant display is ready [19:07:20][D][binary_sensor:036]: 'nsapt Nextion display': Sending state ON [19:07:20][D][main:795]: Nextion start - Done! [19:07:21][D][api:102]: Accepted XX.YY.ZZ.UU [19:07:22][D][api.connection:959]: Home Assistant 2023.6.1 (XX.YY.ZZ.UU): Connected successfully

When I press, Update TFT display it goes to the installation field. It reads the information but doesn't start writting.

Commented 

external_components:
  - source: github://pr#2956
    components: [nextion]
    refresh: 1h

this now results in the following warning

[W][nextion:396]: Nextion reported variable name invalid!

edwardtfn commented 1 year ago

Could you please share your current esphome yaml? Please remove any sensitive information before sharing.

Jens-Wymeersch commented 1 year ago

@edwardtfn thank you for taking the time. Here you go

substitutions:

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

  device_name: "nsapt" 
  wifi_ssid: "wifi_name"
  wifi_password: "wifi_pw"

  nextion_update_url: "http://XX.YY.ZZ.UU:8123/local/nspanel_eu.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 #####
external_components:
  - source: github://pr#2956
    components: [nextion]
    refresh: 1h

##### 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! #####
edwardtfn commented 1 year ago

As you are not coming from Sonoff's original TFT, you don't need that pr#2956 anymore.

This should work:

substitutions:

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

  device_name: "nsapt" 
  wifi_ssid: "wifi_name"
  wifi_password: "wifi_pw"

  nextion_update_url: "http://XX.YY.ZZ.UU:8123/local/nspanel_eu.tft"
##### 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! #####

Have you tried to use the same url (http://xx.yy.zz.uu:8123/local/nspanel_eu.tft) to download the TFT file to your computer? Does the file have the same size as the original from GitHub?

Jens-Wymeersch commented 1 year ago

@edwardtfn I confirm that I can reach the file (download) and it has the same size (6.4MB).

edwardtfn commented 1 year ago

So, the o nky thing I can suggest is to try the Upload TFT and keep trying until you have it completed. Again, if you get to the ble screen, don't try to transfer TFT again, don't try Tasmota. Share a picture of your screen and we will be able to help from there.

germaguire commented 1 year ago

Hi Edward, I also seem to have an issue that has the same issues as Jens, seems to do the tft upload but is sitting with a verifying DATA loader screen at 2% with the same error messages in logs for invalid variable name and the UART timeout. Is there anything you would like me to test also ?

edwardtfn commented 1 year ago

Have you tried downloading the TFT file to your computer using the same url provided to ESPHome? Is the file size correct?

Take a look at this: https://github.com/Blackymas/NSPanel_HA_Blueprint/wiki/(EN)-Common-Issues-TFT-Upload#5-check-the-file-size-by-downloading-to-your-computer

germaguire commented 1 year ago

Yes, I have tried all the trouble shooting steps with no luck, here is the output from logs from last attempts.

17:03:54 [D] [button:010] 'nspanel Update TFT display' Pressed.
17:03:54 [D] [binary_sensor:036] 'nspanel Nextion display': Sending state OFF
17:03:54 [D] [nextion_upload:169] Connected
17:03:54 [D] [nextion_upload:175] Requesting URL: http://192.168.172.10:8123/local/nspanel/nspanel_eu.tft
17:03:54 [D] [nextion_upload:175] Requesting URL: http://192.168.172.10:8123/local/nspanel/nspanel_eu.tft
17:03:54 [D] [nextion_upload:209] Updating Nextion NX4832F035_011C...
17:03:55 [D] [nextion_upload:235] Waiting for upgrade response
17:03:55 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:55 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:55 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:55 [D] [nextion_upload:239] Upgrade response is 4
17:03:55 [D] [nextion_upload:242] Available 0 : 0x00
17:03:55 [D] [nextion_upload:242] Available 0 : 0x00
17:03:55 [D] [nextion_upload:242] Available 1 : 0x00
17:03:55 [D] [nextion_upload:242] Available 2 : 0x00
17:03:55 [D] [nextion_upload:242] Available 3 : 0x05
17:03:55 [D] [nextion_upload:246] preparation for tft update done
17:03:55 [D] [nextion_upload:246] preparation for tft update done
17:03:55 [D] [nextion_upload:283] Allocating buffer size 65536, Heap size is 172268
17:03:55 [D] [nextion_upload:305] Updating tft from "http://192.168.172.10:8123/local/nspanel/nspanel_eu.tft" with a file size of 6432100 using 65536 chunksize, Heap Size 102508
17:03:55 [D] [nextion_upload:305] Updating tft from "http://192.168.172.10:8123/local/nspanel/nspanel_eu.tft" with a file size of 6432100 using 65536 chunksize, Heap Size 102508
17:03:55 [D] [nextion_upload:044] Requesting range: bytes=0-16383
17:03:56 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:56 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:56 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:56 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:56 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:57 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:58 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:58 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:58 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:58 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:58 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:58 [E] [uart:015] Reading from UART timed out at byte 0!
17:03:58 [D] [nextion_upload:117] Nextion reported new range 134744072
17:03:58 [D] [nextion_upload:316] Heap Size 104732, Bytes left -128311972
17:03:58 [D] [nextion_upload:316] Heap Size 104732, Bytes left -128311972
17:03:58 [D] [nextion_upload:318] Successfully updated Nextion!
17:03:58 [D] [nextion_upload:324] Restarting Nextion
17:04:00 [D] [nextion_upload:327] Restarting esphome
germaguire commented 1 year ago

I was able to resolve the problem by downloading the entire github repository, unzipping and sftping the tft image to HA. Maybe either the original file download of using the HA editor for uploading the file was corrupting it but its back working again now.

rleongcs commented 1 year ago

I always download the zip and then unzip it in my NAS and copy the necessary files over to HA through the Samba share. This has always worked fine.

edwardtfn commented 1 year ago

Hi @Jens-Wymeersch, have you succeeded in installing the TFT?

Jens-Wymeersch commented 1 year ago

@edwardtfn thank you for reaching out. After trying 10+, I am ready to go give up. Anything else I can do ?

edwardtfn commented 1 year ago

If nothing else works, you can always try to transfer TFT via serial (take a look at this post), but transfer via http should work and is easier, so you have something you might be missing. I would review all he points from this document before trying serial transfer.

geni0602 commented 12 months ago

I am haveing the same issue here. Tried to update to 3.4. One Ns Panel was totally fine and the second stoped at upload of the tft file. Same Error.

16:09:54 [E] [uart:015] Reading from UART timed out at byte 0!

I am updating local from my server. It was able to recover with the blank file, but the update after that was again unsuccessful.

it ist quite strange.

edwardtfn commented 12 months ago

You should just try again...

geni0602 commented 12 months ago

You should just try again...

Thx. Know it's working. After a couple of times the update was successful.

KoalaWerewolf commented 12 months ago

Hi, I'm having the same issue. Blueprint is 3.4, esphome.yaml gets downloaded by the config, file size of local TFT matches what was downloaded from GitHub. I've retried multiple times and this is what I get:

[09:40:03][D][button:010]: 'nspanel Update TFT display' Pressed. [09:40:03][D][binary_sensor:036]: 'nspanel Nextion display': Sending state OFF

[09:40:03][D][nextion_upload:175]: Requesting URL: http://VV.XX.YY.ZZ:8123/local/nspanel_eu.tft [09:40:03][D][nextion_upload:209]: Updating Nextion ... [09:40:03][D][nextion_upload:235]: Waiting for upgrade response [09:40:03][E][uart:015]: Reading from UART timed out at byte 0! [09:40:03][E][uart:015]: Reading from UART timed out at byte 0! [09:40:03][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][D][nextion_upload:239]: Upgrade response is 20 [09:40:05][D][nextion_upload:242]: Available 0 : 0x00 [09:40:05][D][nextion_upload:242]: Available 1 : 0x00 [09:40:05][D][nextion_upload:242]: Available 2 : 0x00 [09:40:05][D][nextion_upload:242]: Available 3 : 0x00 [09:40:05][D][nextion_upload:242]: Available 4 : 0x00 [09:40:05][D][nextion_upload:242]: Available 5 : 0x00 [09:40:05][D][nextion_upload:242]: Available 6 : 0x00 [09:40:05][D][nextion_upload:242]: Available 7 : 0x00 [09:40:05][D][nextion_upload:242]: Available 8 : 0x00 [09:40:05][D][nextion_upload:242]: Available 9 : 0x00 [09:40:05][D][nextion_upload:242]: Available 10 : 0x00 [09:40:05][D][nextion_upload:242]: Available 11 : 0x00 [09:40:05][D][nextion_upload:242]: Available 12 : 0x00 [09:40:05][D][nextion_upload:242]: Available 13 : 0x00 [09:40:05][D][nextion_upload:242]: Available 14 : 0x00 [09:40:05][D][nextion_upload:242]: Available 15 : 0x00 [09:40:05][D][nextion_upload:242]: Available 16 : 0x00 [09:40:05][D][nextion_upload:242]: Available 17 : 0x00 [09:40:05][D][nextion_upload:242]: Available 18 : 0x00 [09:40:05][D][nextion_upload:242]: Available 19 : 0x00 [09:40:05][D][nextion_upload:248]: preparation for tft update failed 0 "" [09:40:05][D][nextion_upload:310]: Restarting Nextion [09:40:07][D][nextion_upload:313]: Restarting esphome

geni0602 commented 12 months ago

Hi, I'm having the same issue. Blueprint is 3.4, esphome.yaml gets downloaded by the config, file size of local TFT matches what was downloaded from GitHub. I've retried multiple times and this is what I get:

[09:40:03][D][button:010]: 'nspanel Update TFT display' Pressed. [09:40:03][D][binary_sensor:036]: 'nspanel Nextion display': Sending state OFF [09:40:03][D][nextion_upload:169]: Connected [09:40:03][D][nextion_upload:175]: Requesting URL: http://VV.XX.YY.ZZ:8123/local/nspanel_eu.tft [09:40:03][D][nextion_upload:209]: Updating Nextion ... [09:40:03][D][nextion_upload:235]: Waiting for upgrade response [09:40:03][E][uart:015]: Reading from UART timed out at byte 0! [09:40:03][E][uart:015]: Reading from UART timed out at byte 0! [09:40:03][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:04][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][E][uart:015]: Reading from UART timed out at byte 0! [09:40:05][D][nextion_upload:239]: Upgrade response is 20 [09:40:05][D][nextion_upload:242]: Available 0 : 0x00 [09:40:05][D][nextion_upload:242]: Available 1 : 0x00 [09:40:05][D][nextion_upload:242]: Available 2 : 0x00 [09:40:05][D][nextion_upload:242]: Available 3 : 0x00 [09:40:05][D][nextion_upload:242]: Available 4 : 0x00 [09:40:05][D][nextion_upload:242]: Available 5 : 0x00 [09:40:05][D][nextion_upload:242]: Available 6 : 0x00 [09:40:05][D][nextion_upload:242]: Available 7 : 0x00 [09:40:05][D][nextion_upload:242]: Available 8 : 0x00 [09:40:05][D][nextion_upload:242]: Available 9 : 0x00 [09:40:05][D][nextion_upload:242]: Available 10 : 0x00 [09:40:05][D][nextion_upload:242]: Available 11 : 0x00 [09:40:05][D][nextion_upload:242]: Available 12 : 0x00 [09:40:05][D][nextion_upload:242]: Available 13 : 0x00 [09:40:05][D][nextion_upload:242]: Available 14 : 0x00 [09:40:05][D][nextion_upload:242]: Available 15 : 0x00 [09:40:05][D][nextion_upload:242]: Available 16 : 0x00 [09:40:05][D][nextion_upload:242]: Available 17 : 0x00 [09:40:05][D][nextion_upload:242]: Available 18 : 0x00 [09:40:05][D][nextion_upload:242]: Available 19 : 0x00 [09:40:05][D][nextion_upload:248]: preparation for tft update failed 0 "" [09:40:05][D][nextion_upload:310]: Restarting Nextion [09:40:07][D][nextion_upload:313]: Restarting esphome

Try to update again at first with nspanel_blank.tft. you can find the file in/custom_components. After that should be possible to update again the nspanel_eu.tft. I don't know if this helped, but I've downloaded the zip from the repo directly in my destination folder and unzip it there. The update after that was successful.

KoalaWerewolf commented 12 months ago

Just tried that. Same thing happens for the nspanel_blank.tft.

[09:56:46][D][binary_sensor:036]: 'nspanel Nextion display': Sending state OFF

[09:56:46][D][nextion_upload:175]: Requesting URL: http://VV.XX.YY.ZZ:8123/local/nspanel_blank.tft [09:56:46][D][nextion_upload:209]: Updating Nextion ... [09:56:46][D][nextion_upload:235]: Waiting for upgrade response [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:47][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:48][E][uart:015]: Reading from UART timed out at byte 0! [09:56:49][E][uart:015]: Reading from UART timed out at byte 0! [09:56:49][D][nextion_upload:239]: Upgrade response is 20 [09:56:49][D][nextion_upload:242]: Available 0 : 0x00 [09:56:49][D][nextion_upload:242]: Available 1 : 0x00 [09:56:49][D][nextion_upload:242]: Available 2 : 0x00 [09:56:49][D][nextion_upload:242]: Available 3 : 0x00 [09:56:49][D][nextion_upload:242]: Available 4 : 0x00 [09:56:49][D][nextion_upload:242]: Available 5 : 0x00 [09:56:49][D][nextion_upload:242]: Available 6 : 0x00 [09:56:49][D][nextion_upload:242]: Available 7 : 0x00 [09:56:49][D][nextion_upload:242]: Available 8 : 0x00 [09:56:49][D][nextion_upload:242]: Available 9 : 0x00 [09:56:49][D][nextion_upload:242]: Available 10 : 0x00 [09:56:49][D][nextion_upload:242]: Available 11 : 0x00 [09:56:49][D][nextion_upload:242]: Available 12 : 0x00 [09:56:49][D][nextion_upload:242]: Available 13 : 0x00 [09:56:49][D][nextion_upload:242]: Available 14 : 0x00 [09:56:49][D][nextion_upload:242]: Available 15 : 0x00 [09:56:49][D][nextion_upload:242]: Available 16 : 0x00 [09:56:49][D][nextion_upload:242]: Available 17 : 0x00 [09:56:49][D][nextion_upload:242]: Available 18 : 0x00 [09:56:49][D][nextion_upload:242]: Available 19 : 0x00 [09:56:49][D][nextion_upload:248]: preparation for tft update failed 0 "" [09:56:49][D][nextion_upload:310]: Restarting Nextion

geni0602 commented 12 months ago

Hm, did you try to cut the power of the panel, power on and start the update again.

If you open the local-link in your browser, you can download the file on your PC, right?

KoalaWerewolf commented 12 months ago

I have not physically cut the power to the panel yet. I can get the file from my PC. The recompiling that gets done for each try is a partial recompile, only main.cpp gets compiled from what I can see. Is there a way to force ESPHome to recompile the entire project?

KoalaWerewolf commented 12 months ago

Sorry, found it. "Clean Build Files".

KoalaWerewolf commented 12 months ago

And now I've cut the power. It allowed me to install nspanel_blank, I could then get it to upload nspanel_eu again. As it completed it went into the same state again. For me it's a blank (white) screen a max brightness.

I'll try the nspanel_eu from a zip download next.

KoalaWerewolf commented 12 months ago

No dice.

The nspanel_eu.tft from the zip-download gives the same result. I'm including screenshots of the update process with time line comments:

  1. Errors during the upload process: image image

  2. As the upload completes: image

  3. After the restart: image

At this point the NSPanel is white with full brightness.

  1. After cutting power to the NSPanel after a successful(?) upload: image

At this point the NSPanel has a text message on the display stating "System Data ERROR!"

  1. Trying a new TFT update: image

The NSPanel displays the upload screen stuck on 0%

  1. After cutting power to the NSPanel after another reportedly successful update: image

Back to "System Data ERROR!"

KoalaWerewolf commented 12 months ago

Is it possible to change the nspanel_esphome.yaml "ref" to "v.3.3" (currently set to "main") to try to revert to 3.3?

edwardtfn commented 12 months ago

For me it's a blank (white) screen a max brightness.

You either installed an older version of nspanel_blank.tft or something was wrong, as the latest version should display a QR code and not a white screen. Please make sure you have the latest files from GitHub.

At this point the NSPanel has a text message on the display stating "System Data ERROR!"

Looks like the transfer was incomplete, wither by a network problem or you have a corrupt file in your local server. Please take a look at step 5 of our guide to troubleshoot TFT transfer issues: https://github.com/Blackymas/NSPanel_HA_Blueprint/wiki/(EN)-Common-Issues-TFT-Upload#5-check-the-file-size-by-downloading-to-your-computer

Is it possible to change the nspanel_esphome.yaml "ref" to "v.3.3" (currently set to "main") to try to revert to 3.3?

No. In order to install a previous version you have to download the files from that release notes and change your yaml to look for a local nspanel_esphome.yaml, however, that is not gonna solve the problem you have and you will end up at the same point. Please double check your TFT file if your local server is correct and try the transfer again.

KoalaWerewolf commented 12 months ago

The nspanel_blank.tft is outdated then. Would that break this process? I’ve verified the nspanel_eu.tft multiple times. Verified size by downloading it from my local location to my laptop, I’ve also extracted it from the zip archive of the code base. The size reported for the nspanel_eu.tft by the update process is 6551964, is that the correct size?

rleongcs commented 12 months ago

The nspanel_blank.tft is outdated then. Would that break this process?

It should not.

The size reported for the nspanel_eu.tft by the update process is 6551964, is that the correct size?

That is the correct size.

My NSPanel log below during the update: [22:19:53][D][nspanel:946]: start page-timer delay 20 [22:19:53][D][nextion_textsensor:014]: Processed text_sensor "nspanelevent" state "{"page": "home", "component": "currentpage", "value": "pagechange"}" [22:19:53][D][text_sensor:064]: 'room3_nspanel Settings Entity': Sending state '{"page": "home", "component": "currentpage", "value": "pagechange"}' [22:20:08][D][sensor:094]: 'room3_nspanel uptime': Sending state 30.42500 s with 0 decimals of accuracy [22:20:13][D][nspanel:953]: no page-jump [22:20:14][D][button:010]: 'room3_nspanel Update TFT display' Pressed. [22:20:14][D][binary_sensor:036]: 'room3_nspanel Nextion display': Sending state OFF [22:20:14][D][nextion_upload:169]: Connected [22:20:14][D][nextion_upload:175]: Requesting URL: http://192.168.12.111:8123/local/nspaneleu.tft [22:20:14][D][nextion_upload:209]: Updating Nextion NX4832F035_011C... [22:20:14][D][nextion_upload:235]: Waiting for upgrade response [22:20:14][E][uart:015]: Reading from UART timed out at byte 0! [22:20:14][E][uart:015]: Reading from UART timed out at byte 0! [22:20:14][E][uart:015]: Reading from UART timed out at byte 0! [22:20:14][D][nextion_upload:239]: Upgrade response is 4 [22:20:14][D][nextion_upload:242]: Available 0 : 0x00 [22:20:14][D][nextion_upload:242]: Available 1 : 0x00 [22:20:14][D][nextion_upload:242]: Available 2 : 0x00 [22:20:14][D][nextion_upload:242]: Available 3 : 0x05 [22:20:14][D][nextion_upload:246]: preparation for tft update done [22:20:14][D][nextion_upload:274]: Allocating buffer size 65536, Heap size is 168120 [22:20:14][D][nextion_upload:291]: Updating tft from "http://192.168.12.111:8123/local/nspaneleu.tft" with a file size of 6551964 using 65536 chunksize, Heap Size 102020 [22:20:14][D][nextion_upload:048]: Requesting range: bytes=0-16383 [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:16][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:17][E][uart:015]: Reading from UART timed out at byte 0! [22:20:18][E][uart:015]: Reading from UART timed out at byte 0! [22:20:19][D][nextion_upload:302]: Heap Size 111408, Bytes left 6535580 [22:20:19][D][nextion_upload:048]: Requesting range: bytes=16384-81919 [22:20:25][D][nextion_upload:302]: Heap Size 101728, Bytes left 6470044 [22:20:25][D][nextion_upload:048]: Requesting range: bytes=81920-147455 [22:20:31][D][nextion_upload:302]: Heap Size 106672, Bytes left 6404508 [22:20:31][D][nextion_upload:048]: Requesting range: bytes=147456-212991 [22:20:37][D][nextion_upload:302]: Heap Size 106672, Bytes left 6338972 [22:20:37][D][nextion_upload:048]: Requesting range: bytes=212992-278527 [22:20:43][D][nextion_upload:302]: Heap Size 106640, Bytes left 6273436 [22:20:43][D][nextion_upload:048]: Requesting range: bytes=278528-344063 [22:20:49][D][nextion_upload:302]: Heap Size 101912, Bytes left 6207900 [22:20:49][D][nextion_upload:048]: Requesting range: bytes=344064-409599 [22:20:56][D][nextion_upload:302]: Heap Size 101944, Bytes left 6142364 [22:20:56][D][nextion_upload:048]: Requesting range: bytes=409600-475135 [22:21:02][D][nextion_upload:302]: Heap Size 99620, Bytes left 6076828 [22:21:02][D][nextion_upload:048]: Requesting range: bytes=475136-540671 [22:21:08][D][nextion_upload:302]: Heap Size 99580, Bytes left 6011292 [22:21:08][D][nextion_upload:048]: Requesting range: bytes=540672-606207 [22:21:14][D][nextion_upload:302]: Heap Size 97208, Bytes left 5945756 [22:21:14][D][nextion_upload:048]: Requesting range: bytes=606208-671743 [22:21:20][D][nextion_upload:302]: Heap Size 97216, Bytes left 5880220 [22:21:20][D][nextion_upload:048]: Requesting range: bytes=671744-737279 [22:21:26][D][nextion_upload:302]: Heap Size 97208, Bytes left 5814684 [22:21:26][D][nextion_upload:048]: Requesting range: bytes=737280-802815 [22:21:32][D][nextion_upload:302]: Heap Size 92488, Bytes left 5749148 [22:21:32][D][nextion_upload:048]: Requesting range: bytes=802816-868351 [22:21:39][D][nextion_upload:302]: Heap Size 92484, Bytes left 5683612 [22:21:39][D][nextion_upload:048]: Requesting range: bytes=868352-933887 [22:21:45][D][nextion_upload:302]: Heap Size 92456, Bytes left 5618076 [22:21:45][D][nextion_upload:048]: Requesting range: bytes=933888-999423 [22:21:51][D][nextion_upload:302]: Heap Size 87756, Bytes left 5552540 [22:21:51][D][nextion_upload:048]: Requesting range: bytes=999424-1064959 [22:21:57][D][nextion_upload:302]: Heap Size 87760, Bytes left 5487004 [22:21:57][D][nextion_upload:048]: Requesting range: bytes=1064960-1130495 [22:22:04][D][nextion_upload:302]: Heap Size 84940, Bytes left 5421468 [22:22:04][D][nextion_upload:048]: Requesting range: bytes=1130496-1196031 [22:22:10][D][nextion_upload:302]: Heap Size 79756, Bytes left 5355932 [22:22:10][D][nextion_upload:048]: Requesting range: bytes=1196032-1261567 [22:22:16][D][nextion_upload:302]: Heap Size 79976, Bytes left 5290396 [22:22:16][D][nextion_upload:048]: Requesting range: bytes=1261568-1327103 [22:22:22][D][nextion_upload:302]: Heap Size 79980, Bytes left 5224860 [22:22:22][D][nextion_upload:048]: Requesting range: bytes=1327104-1392639 [22:22:28][D][nextion_upload:302]: Heap Size 79220, Bytes left 5159324 [22:22:28][D][nextion_upload:048]: Requesting range: bytes=1392640-1458175 [22:22:34][D][nextion_upload:302]: Heap Size 78940, Bytes left 5093788 [22:22:34][D][nextion_upload:048]: Requesting range: bytes=1458176-1523711 [22:22:41][D][nextion_upload:302]: Heap Size 76120, Bytes left 5028252 [22:22:41][D][nextion_upload:048]: Requesting range: bytes=1523712-1589247 [22:22:47][D][nextion_upload:302]: Heap Size 76088, Bytes left 4962716 [22:22:47][D][nextion_upload:048]: Requesting range: bytes=1589248-1654783 [22:22:53][D][nextion_upload:302]: Heap Size 76116, Bytes left 4897180 [22:22:53][D][nextion_upload:048]: Requesting range: bytes=1654784-1720319 [22:22:59][D][nextion_upload:302]: Heap Size 76124, Bytes left 4831644 [22:22:59][D][nextion_upload:048]: Requesting range: bytes=1720320-1785855 [22:23:06][D][nextion_upload:302]: Heap Size 76116, Bytes left 4766108 [22:23:06][D][nextion_upload:048]: Requesting range: bytes=1785856-1851391 [22:23:12][D][nextion_upload:302]: Heap Size 76124, Bytes left 4700572 [22:23:12][D][nextion_upload:048]: Requesting range: bytes=1851392-1916927 [22:23:18][D][nextion_upload:302]: Heap Size 76116, Bytes left 4635036 [22:23:18][D][nextion_upload:048]: Requesting range: bytes=1916928-1982463 [22:23:25][D][nextion_upload:302]: Heap Size 76124, Bytes left 4569500 [22:23:25][D][nextion_upload:048]: Requesting range: bytes=1982464-2047999 [22:23:31][D][nextion_upload:302]: Heap Size 76116, Bytes left 4503964 [22:23:31][D][nextion_upload:048]: Requesting range: bytes=2048000-2113535 [22:23:37][D][nextion_upload:302]: Heap Size 76124, Bytes left 4438428 [22:23:37][D][nextion_upload:048]: Requesting range: bytes=2113536-2179071 [22:23:44][D][nextion_upload:302]: Heap Size 76116, Bytes left 4372892 [22:23:44][D][nextion_upload:048]: Requesting range: bytes=2179072-2244607 [22:23:50][D][nextion_upload:302]: Heap Size 76124, Bytes left 4307356 [22:23:50][D][nextion_upload:048]: Requesting range: bytes=2244608-2310143 [22:23:56][D][nextion_upload:302]: Heap Size 76116, Bytes left 4241820 [22:23:56][D][nextion_upload:048]: Requesting range: bytes=2310144-2375679 [22:24:03][D][nextion_upload:302]: Heap Size 76124, Bytes left 4176284 [22:24:03][D][nextion_upload:048]: Requesting range: bytes=2375680-2441215 [22:24:09][D][nextion_upload:302]: Heap Size 76116, Bytes left 4110748 [22:24:09][D][nextion_upload:048]: Requesting range: bytes=2441216-2506751 [22:24:15][D][nextion_upload:302]: Heap Size 76124, Bytes left 4045212 [22:24:15][D][nextion_upload:048]: Requesting range: bytes=2506752-2572287 [22:24:22][D][nextion_upload:302]: Heap Size 76116, Bytes left 3979676 [22:24:22][D][nextion_upload:048]: Requesting range: bytes=2572288-2637823 [22:24:28][D][nextion_upload:302]: Heap Size 76124, Bytes left 3914140 [22:24:28][D][nextion_upload:048]: Requesting range: bytes=2637824-2703359 [22:24:34][D][nextion_upload:302]: Heap Size 76116, Bytes left 3848604 [22:24:34][D][nextion_upload:048]: Requesting range: bytes=2703360-2768895 [22:24:40][D][nextion_upload:302]: Heap Size 76124, Bytes left 3783068 [22:24:40][D][nextion_upload:048]: Requesting range: bytes=2768896-2834431 [22:24:46][D][nextion_upload:302]: Heap Size 76080, Bytes left 3717532 [22:24:46][D][nextion_upload:048]: Requesting range: bytes=2834432-2899967 [22:24:53][D][nextion_upload:302]: Heap Size 76088, Bytes left 3651996 [22:24:53][D][nextion_upload:048]: Requesting range: bytes=2899968-2965503 [22:24:59][D][nextion_upload:302]: Heap Size 76116, Bytes left 3586460 [22:24:59][D][nextion_upload:048]: Requesting range: bytes=2965504-3031039 [22:25:06][D][nextion_upload:302]: Heap Size 76124, Bytes left 3520924 [22:25:06][D][nextion_upload:048]: Requesting range: bytes=3031040-3096575 [22:25:12][D][nextion_upload:302]: Heap Size 75940, Bytes left 3455388 [22:25:12][D][nextion_upload:048]: Requesting range: bytes=3096576-3162111 [22:25:18][D][nextion_upload:302]: Heap Size 76124, Bytes left 3389852 [22:25:18][D][nextion_upload:048]: Requesting range: bytes=3162112-3227647 [22:25:24][D][nextion_upload:302]: Heap Size 76116, Bytes left 3324316 [22:25:24][D][nextion_upload:048]: Requesting range: bytes=3227648-3293183 [22:25:31][D][nextion_upload:302]: Heap Size 76124, Bytes left 3258780 [22:25:31][D][nextion_upload:048]: Requesting range: bytes=3293184-3358719 [22:25:37][D][nextion_upload:302]: Heap Size 76116, Bytes left 3193244 [22:25:37][D][nextion_upload:048]: Requesting range: bytes=3358720-3424255 [22:25:43][D][nextion_upload:302]: Heap Size 76124, Bytes left 3127708 [22:25:43][D][nextion_upload:048]: Requesting range: bytes=3424256-3489791 [22:25:50][D][nextion_upload:302]: Heap Size 76080, Bytes left 3062172 [22:25:50][D][nextion_upload:048]: Requesting range: bytes=3489792-3555327 [22:25:56][D][nextion_upload:302]: Heap Size 76124, Bytes left 2996636 [22:25:56][D][nextion_upload:048]: Requesting range: bytes=3555328-3620863 [22:26:02][D][nextion_upload:302]: Heap Size 76124, Bytes left 2931100 [22:26:02][D][nextion_upload:048]: Requesting range: bytes=3620864-3686399 [22:26:08][D][nextion_upload:302]: Heap Size 76116, Bytes left 2865564 [22:26:08][D][nextion_upload:048]: Requesting range: bytes=3686400-3751935 [22:26:14][D][nextion_upload:302]: Heap Size 76124, Bytes left 2800028 [22:26:14][D][nextion_upload:048]: Requesting range: bytes=3751936-3817471 [22:26:20][D][nextion_upload:302]: Heap Size 76116, Bytes left 2734492 [22:26:20][D][nextion_upload:048]: Requesting range: bytes=3817472-3883007 [22:26:27][D][nextion_upload:302]: Heap Size 76124, Bytes left 2668956 [22:26:27][D][nextion_upload:048]: Requesting range: bytes=3883008-3948543 [22:26:33][D][nextion_upload:302]: Heap Size 76116, Bytes left 2603420 [22:26:33][D][nextion_upload:048]: Requesting range: bytes=3948544-4014079 [22:26:40][D][nextion_upload:302]: Heap Size 76124, Bytes left 2537884 [22:26:40][D][nextion_upload:048]: Requesting range: bytes=4014080-4079615 [22:26:46][D][nextion_upload:302]: Heap Size 76116, Bytes left 2472348 [22:26:46][D][nextion_upload:048]: Requesting range: bytes=4079616-4145151 [22:26:53][D][nextion_upload:302]: Heap Size 76124, Bytes left 2406812 [22:26:53][D][nextion_upload:048]: Requesting range: bytes=4145152-4210687 [22:26:59][D][nextion_upload:302]: Heap Size 76116, Bytes left 2341276 [22:26:59][D][nextion_upload:048]: Requesting range: bytes=4210688-4276223 [22:27:05][D][nextion_upload:302]: Heap Size 76124, Bytes left 2275740 [22:27:05][D][nextion_upload:048]: Requesting range: bytes=4276224-4341759 [22:27:12][D][nextion_upload:302]: Heap Size 76116, Bytes left 2210204 [22:27:12][D][nextion_upload:048]: Requesting range: bytes=4341760-4407295 [22:27:18][D][nextion_upload:302]: Heap Size 76124, Bytes left 2144668 [22:27:18][D][nextion_upload:048]: Requesting range: bytes=4407296-4472831 [22:27:24][D][nextion_upload:302]: Heap Size 76120, Bytes left 2079132 [22:27:24][D][nextion_upload:048]: Requesting range: bytes=4472832-4538367 [22:27:30][D][nextion_upload:302]: Heap Size 66356, Bytes left 2013596 [22:27:30][D][nextion_upload:048]: Requesting range: bytes=4538368-4603903 [22:27:37][D][nextion_upload:302]: Heap Size 76124, Bytes left 1948060 [22:27:37][D][nextion_upload:048]: Requesting range: bytes=4603904-4669439 [22:27:43][D][nextion_upload:302]: Heap Size 76124, Bytes left 1882524 [22:27:43][D][nextion_upload:048]: Requesting range: bytes=4669440-4734975 [22:27:49][D][nextion_upload:302]: Heap Size 76116, Bytes left 1816988 [22:27:49][D][nextion_upload:048]: Requesting range: bytes=4734976-4800511 [22:27:55][D][nextion_upload:302]: Heap Size 76124, Bytes left 1751452 [22:27:55][D][nextion_upload:048]: Requesting range: bytes=4800512-4866047 [22:28:01][D][nextion_upload:302]: Heap Size 76116, Bytes left 1685916 [22:28:01][D][nextion_upload:048]: Requesting range: bytes=4866048-4931583 [22:28:07][D][nextion_upload:302]: Heap Size 76124, Bytes left 1620380 [22:28:07][D][nextion_upload:048]: Requesting range: bytes=4931584-4997119 [22:28:13][D][nextion_upload:302]: Heap Size 76116, Bytes left 1554844 [22:28:13][D][nextion_upload:048]: Requesting range: bytes=4997120-5062655 [22:28:20][D][nextion_upload:302]: Heap Size 76124, Bytes left 1489308 [22:28:20][D][nextion_upload:048]: Requesting range: bytes=5062656-5128191 [22:28:26][D][nextion_upload:302]: Heap Size 76116, Bytes left 1423772 [22:28:26][D][nextion_upload:048]: Requesting range: bytes=5128192-5193727 [22:28:33][D][nextion_upload:302]: Heap Size 76124, Bytes left 1358236 [22:28:33][D][nextion_upload:048]: Requesting range: bytes=5193728-5259263 [22:28:39][D][nextion_upload:302]: Heap Size 76116, Bytes left 1292700 [22:28:39][D][nextion_upload:048]: Requesting range: bytes=5259264-5324799 [22:28:45][D][nextion_upload:302]: Heap Size 76124, Bytes left 1227164 [22:28:45][D][nextion_upload:048]: Requesting range: bytes=5324800-5390335 [22:28:51][D][nextion_upload:302]: Heap Size 76080, Bytes left 1161628 [22:28:51][D][nextion_upload:048]: Requesting range: bytes=5390336-5455871 [22:28:57][D][nextion_upload:302]: Heap Size 76124, Bytes left 1096092 [22:28:57][D][nextion_upload:048]: Requesting range: bytes=5455872-5521407 [22:29:04][D][nextion_upload:302]: Heap Size 76116, Bytes left 1030556 [22:29:04][D][nextion_upload:048]: Requesting range: bytes=5521408-5586943 [22:29:11][D][nextion_upload:302]: Heap Size 76124, Bytes left 965020 [22:29:11][D][nextion_upload:048]: Requesting range: bytes=5586944-5652479 [22:29:17][D][nextion_upload:302]: Heap Size 76124, Bytes left 899484 [22:29:17][D][nextion_upload:048]: Requesting range: bytes=5652480-5718015 [22:29:23][D][nextion_upload:302]: Heap Size 76124, Bytes left 833948 [22:29:23][D][nextion_upload:048]: Requesting range: bytes=5718016-5783551 [22:29:30][D][nextion_upload:302]: Heap Size 76116, Bytes left 768412 [22:29:30][D][nextion_upload:048]: Requesting range: bytes=5783552-5849087 [22:29:36][D][nextion_upload:302]: Heap Size 76124, Bytes left 702876 [22:29:36][D][nextion_upload:048]: Requesting range: bytes=5849088-5914623 [22:29:43][D][nextion_upload:302]: Heap Size 76116, Bytes left 637340 [22:29:43][D][nextion_upload:048]: Requesting range: bytes=5914624-5980159 [22:29:49][D][nextion_upload:302]: Heap Size 76124, Bytes left 571804 [22:29:49][D][nextion_upload:048]: Requesting range: bytes=5980160-6045695 [22:29:55][D][nextion_upload:302]: Heap Size 76116, Bytes left 506268 [22:29:55][D][nextion_upload:048]: Requesting range: bytes=6045696-6111231 [22:30:01][D][nextion_upload:302]: Heap Size 75776, Bytes left 440732 [22:30:01][D][nextion_upload:048]: Requesting range: bytes=6111232-6176767 [22:30:08][D][nextion_upload:302]: Heap Size 76116, Bytes left 375196 [22:30:08][D][nextion_upload:048]: Requesting range: bytes=6176768-6242303 [22:30:14][D][nextion_upload:302]: Heap Size 76124, Bytes left 309660 [22:30:14][D][nextion_upload:048]: Requesting range: bytes=6242304-6307839 [22:30:20][D][nextion_upload:302]: Heap Size 76124, Bytes left 244124 [22:30:20][D][nextion_upload:048]: Requesting range: bytes=6307840-6373375 [22:30:27][D][nextion_upload:302]: Heap Size 76124, Bytes left 178588 [22:30:27][D][nextion_upload:048]: Requesting range: bytes=6373376-6438911 [22:30:33][D][nextion_upload:302]: Heap Size 76116, Bytes left 113052 [22:30:33][D][nextion_upload:048]: Requesting range: bytes=6438912-6504447 [22:30:39][D][nextion_upload:302]: Heap Size 76124, Bytes left 47516 [22:30:39][D][nextion_upload:048]: Requesting range: bytes=6504448-6551964 [22:30:44][D][nextion_upload:302]: Heap Size 76116, Bytes left -1636 [22:30:44][D][nextion_upload:304]: Successfully updated Nextion! [22:30:44][D][nextion_upload:310]: Restarting Nextion

I have just updated 2 of my NSPanel from v3.3 to v3.4 with no issues. The process I follow are as below...

  1. Download zip file from github.
  2. Extract files to a folder.
  3. Copy nspanel_blueprint.yaml to \config\blueprints\automation\Blackymas folder.
  4. Copy nspanel_eu.tft to \config\www folder.
  5. Rename nspanel_eu.tft to nspaneleu.tft. (I faced some issues before and found a thread where the user remove the _ and tft uploads ok. I tried it and it seems to solve my problem. Since then, I always remove the _.
  6. Go to ESPHome and do a Clean Build Files for the NSPanel I am trying to update.
  7. Install wirelessly once Clean Build Files completes.
  8. Once firmware is uploaded to NSPanel, confirm all looks good on the log.
  9. Go to Devices & Services and open the NSPanel under ESPHome.
  10. Click on Update TFT display.
  11. See the progress bar on the panel completes to 100%.
  12. Go to Automations & Scenes and open the NSPanel automation file.
  13. Update all necessary fields due to new version and save.
  14. Go to Developer Tools and reload AUTOMATIONS.
indicato commented 12 months ago

Nice description. But no solution:

20:30:32][D][button:010]: 'nspanel Update TFT display' Pressed. [20:30:32][D][binary_sensor:036]: 'nspanel Nextion display': Sending state OFF

[20:30:32][D][nextion_upload:175]: Requesting URL: http://192.168.241.100:8006/local/nspaneleu.tft [20:30:33][D][nextion_upload:209]: Updating Nextion ... [20:30:33][D][nextion_upload:235]: Waiting for upgrade response [20:30:33][E][uart:015]: Reading from UART timed out at byte 0! [20:30:33][E][uart:015]: Reading from UART timed out at byte 0! [20:30:33][E][uart:015]: Reading from UART timed out at byte 0! [20:30:33][E][uart:015]: Reading from UART timed out at byte 0! [20:30:33][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:34][E][uart:015]: Reading from UART timed out at byte 0! [20:30:35][E][uart:015]: Reading from UART timed out at byte 0! [20:30:35][E][uart:015]: Reading from UART timed out at byte 0! [20:30:35][E][uart:015]: Reading from UART timed out at byte 0! [20:30:35][E][uart:015]: Reading from UART timed out at byte 0! [20:30:35][E][uart:015]: Reading from UART timed out at byte 0! [20:30:35][D][nextion_upload:239]: Upgrade response is 20 [20:30:35][D][nextion_upload:242]: Available 0 : 0x00 [20:30:35][D][nextion_upload:242]: Available 1 : 0x00 [20:30:35][D][nextion_upload:242]: Available 2 : 0x00 [20:30:35][D][nextion_upload:242]: Available 3 : 0x00 [20:30:35][D][nextion_upload:242]: Available 4 : 0x00 [20:30:35][D][nextion_upload:242]: Available 5 : 0x00 [20:30:35][D][nextion_upload:242]: Available 6 : 0x00 [20:30:35][D][nextion_upload:242]: Available 7 : 0x00 [20:30:35][D][nextion_upload:242]: Available 8 : 0x00 [20:30:35][D][nextion_upload:242]: Available 9 : 0x00 [20:30:35][D][nextion_upload:242]: Available 10 : 0x00 [20:30:35][D][nextion_upload:242]: Available 11 : 0x00 [20:30:35][D][nextion_upload:242]: Available 12 : 0x00 [20:30:35][D][nextion_upload:242]: Available 13 : 0x00 [20:30:35][D][nextion_upload:242]: Available 14 : 0x00 [20:30:35][D][nextion_upload:242]: Available 15 : 0x00 [20:30:35][D][nextion_upload:242]: Available 16 : 0x00 [20:30:35][D][nextion_upload:242]: Available 17 : 0x00 [20:30:35][D][nextion_upload:242]: Available 18 : 0x00 [20:30:35][D][nextion_upload:242]: Available 19 : 0x00 [20:30:35][D][nextion_upload:248]: preparation for tft update failed 0 "" [20:30:35][D][nextion_upload:310]: Restarting Nextion [20:30:37][D][nextion_upload:313]: Restarting esphome`

It seems a lot of people are having trouble with this update. Is there an error in the code?

rleongcs commented 12 months ago

@indicato Are you able to update to the blank tft successfully?

indicato commented 12 months ago

After I uploaded the blank template 3 times. followed by aborted template upload at 20-30%. It finally worked the 3rd time. Thanks for your help rleongcs.

edwardtfn commented 12 months ago

It seems a lot of people are having trouble with this update. Is there an error in the code?

We had no changes on the code related to uploading TFT since a while now. Even the "Exit reparse" button introduced in v3.3 wasn't changing this code of updating TFT and the button was recommended only for new users. The upload of TFT is always an issue, I think it is even worse with ESPHOME. If you Google you will find lots of issues related to this even in other projects. Unfortunately every time we release a new version a bunch of users gets some trouble uploading the new TFT.

rleongcs commented 12 months ago

After I uploaded the blank template 3 times. followed by aborted template upload at 20-30%. It finally worked the 3rd time. Thanks for your help rleongcs.

I guessed we need to have perseverance in this uploading of TFT task! 😉

Anzic23 commented 11 months ago

5. Rename nspanel_eu.tft to nspaneleu.tft. (I faced some issues before and found a thread where the user remove the _ and tft uploads ok. I tried it and it seems to solve my problem. Since then, I always remove the _.

this is what helped me. Before that, I tried to revive it for 2 hours, without success.

edwardtfn commented 9 months ago

@Jens-Wymeersch, in the end, have you had any progress with this?

Jens-Wymeersch commented 9 months ago

@edwardtfn I gave up. The panel is bricked. Never got it to work anymore. Any suggestion would be helpful.

edwardtfn commented 9 months ago

In the end we had so many different things being discussed in this thread that I'm a bit lost on where you are. If you wanna try a bit more, I would be happy to help, but will need also your support to recap...

  1. What you see in your screen right now?
  2. Have you ever succeeded installing any of the tft files on this panel?

I have built a new nspanel_blank.tft. It is only at dev at this moment, but it should be totally compatible with the version on main, so I would give a try. This is where you can find the new file: https://github.com/Blackymas/NSPanel_HA_Blueprint/raw/dev/custom_configuration/nspanel_blank.tft

Also, I would try another PR (5016 in this case) for that Nextion library, so please try this:

substitutions:

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

  device_name: "nsapt" 
  wifi_ssid: "wifi_name"
  wifi_password: "wifi_pw"

  nextion_update_url: "http://homeassistant.local:8123/local/nspanel_blank.tft"
##### CHANGE ME END #####

###### USE THIS ONLY FOR YOUR FIRST TFT UPLOAD, ONCE IT WORKED, REMOVE THESE LINES ######
external_components:
  - source: github://pr#5016
    components: [nextion]
    refresh: 1h
###############################################################################

##### 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! #####
Jens-Wymeersch commented 9 months ago

@edwardtfn I've re-flashed the board. I see the panel in home assistant but the TFT display didn't change. It is still a QR code (linking me to nspanel github page). What do you suggest I do from here ? (please note that I've never soldered in my life)

edwardtfn commented 9 months ago

If you see the QRcode (nspanel_blank.tft) then you can remove that code related to pr#5016, as you already left reparse mode.

What happens (ESPHome logs) when you click "Upload TFT"?

haywiremk commented 8 months ago

I have had similar issue with 1 of 5 panels I am currently using. The one panel will get stuck at random places updating the TFT file. Once a panel tft file gets stuck you will need to edit config to recompile to flash the blank tft, upload that, edit cofig and reflash to go back to the panel tft file, .... Due to some diff checking once failed always will fail. Wish there was a button to flash blank tft from the github to avoid the ESP install step to go back an forth on tft files.

Now for the real issue on this one panel. It seems to be the power supply. With the 3.4 update I moved the front of the panel to another power supply base after 4-5 unsuccessful attempts. Worked first try. Then for this 4.0.2 update I just first moved it and the one panel previously giving me issues every time just worked. So if you are randomly getting stuck pull the front off and move to another base power supply if you have more than one unit. Otherwise might need to find another way to power the front part of the panel.

edwardtfn commented 8 months ago

Wish there was a button to flash blank tft from the github to avoid the ESP install step to go back an forth on tft files.

Try this: https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/main/docs/en/customization.md#button-to-upload-nspanel_blanktft 😉

edwardtfn commented 8 months ago

Maybe you wanna also try the latest suggestion from https://github.com/Blackymas/NSPanel_HA_Blueprint/discussions/1117#discussioncomment-7143975

Jens-Wymeersch commented 8 months ago

@edwardtfn Sorry for my late reply. Basically nothing happened when i push the button.

[19:41:09][D][number:012]: 'aptnspanel Display Brightness': Sending state 100.000000
[19:41:09][D][number:012]: 'aptnspanel Display Brightness Dimdown': Sending state 10.000000
[19:41:09][D][binary_sensor:036]: 'aptnspanel Nextion display': Sending state ON
[19:41:09][D][script:077]: Script 'timer_dim' restarting (mode: restart)
[19:41:09][D][script:077]: Script 'timer_sleep' restarting (mode: restart)
[19:41:09][D][text_sensor:064]: 'aptnspanel Notification Label': Sending state ''
[19:41:09][D][text_sensor:064]: 'aptnspanel Notification Text': Sending state ''
[19:41:09][D][switch:016]: 'aptnspanel Notification unread' Turning OFF.
[19:41:09][D][main:245]: Nextion start - Done!
[19:41:09][W][component:204]: Component nextion.display took a long time for an operation (0.06 s).
[19:41:09][W][component:205]: Components should block for at most 20-30ms.
[19:41:09][W][nextion:396]: Nextion reported variable name invalid!
[19:41:09][W][nextion:396]: Nextion reported variable name invalid!
[19:41:09][W][nextion:396]: Nextion reported variable name invalid!
[19:41:09][W][nextion:396]: Nextion reported variable name invalid!
[19:41:09][W][nextion:396]: Nextion reported variable name invalid!
[19:41:09][D][api:102]: Accepted 192.168.2.48
[19:41:09][D][api.connection:1031]: Home Assistant 2023.9.3 (192.168.2.48): Connected successfully
[19:41:09][D][time:045]: Synchronized time: 2023-09-29 19:41:09
[19:41:09][D][sensor:094]: 'aptnspanel API uptime': Sending state 1696005632.00000  with 0 decimals of accuracy
[19:41:09][D][sensor:094]: 'aptnspanel Device uptime': Sending state 1696005632.00000  with 0 decimals of accuracy
[19:41:09][D][main:1764]: System clock synchronized
[19:41:09][W][nextion:396]: Nextion reported variable name invalid!
[19:41:09][W][nextion:396]: Nextion reported variable name invalid!
edwardtfn commented 8 months ago

You shared only 1sec (or less) of log and I cannot find the log related to the button press.