Connection Error Loading nspanel_us.tft

[jsilveira-ebsco]

Config

• NSPanel version is: 72 (serial: A3653401A544AC68; flash size: 16777216)
• ESPHome: 2023.3.1

Issue Summary

• I'm eventually getting the following message trying to update with nspanel_us.tft: "nspanel2.local: Connection error occurred: Connection lost"
• After successfully flashing with nspanel_blank.tft to get a white screen, I'm trying to flash nspanel_us.tft using EITHER Developer Tools->Services->ESPHome: nspanel2_upload_tft_url, OR Nextion Editor (as described in Issue #166) but I consistently fail at exactly 2424832 bytes at 30% every time (I've tried over 10 times)
• When flashing via Developer Tools->Services->ESPHome: nspanel2_upload_tft_url, at about 20% my log shows "Connection error occurred: Ping response not received after 90.0 seconds", "Can't connect to ESPHome API for nspanel2.local: Hello timed out", and "nspanel2.local: Connection error occurred: Connection lost"
• After noticing the logs in the ESPHome web server for the NSPanel still continued to load the nspanel_us.tft (when flashing via Developer Tools->Services->ESPHome: nspanel2_upload_tft_url), I waited for about an hour when it said it succeeded but once I rebooted the NSPanel (to get rid of the display stuck at 30%) I ended up seeing a sideways "System Data ERROR!"
• 

What I've Tried

• I've read v.3.1.0 - New features and US Version and am still creating this issue because I've also tried everything I've read regarding Issues #166, #177, and #197
• Followed instructions from (EN) First Steps Installation and Setup, and was able to use nspanel_blank.tft to get the white screen to try to upload nspanel_us.tft where eventhough the esphome log in HA shows "Connection error occurred: Connection lost" the esphome web_server log showed it continued where I waited for about 1 hr. until it finished but then ended up with a sideways "System Data ERROR!"
• Followed steps from corradodave from issue #177 (basically revert back to Tasmota, install nspanel_blank.tft, then I tried installing nspanel_blank.tft, then flash esphome again) which resulted in the same sideways "System Data ERROR!"
• From #166, I soldered my TTL to the TF-RX & TF-TX and tried flashing nspanel_us.tft (as well as nspanel_us.HMI) via Nextion Editor - this resulted in my NSPanel getting stuck displaying 30% (2424832 bytes) EXACTLY as it does if I try to flash via Developer Tools in HA (see details below)
• Commenting the logger per this post: NSPanel System Data ERROR after HA yaml update

Context

• I initially flashed with Tasmota, then tried flashing with ESPHome HOW TO - Setup the SIMPLEST Smart Home Scene Controller but got stuck at "Waiting for content..." so I went back to Tasmota but this time in Tasmota consul I flashed with nspanel_blank.tft with the command: FlashNextion http://IP_OF_MY_HOME_ASSISTANT/local/nspanel_blank.tft, before flashing again with ESPHome and that got me by the "Waiting for content..." allowing me to at least start flashing nspanel_us.tft to where I'm stuck at 30%

Details Here are pics of my log while trying to flash nspanel_us.tft. Note the last image "Ping response not received after 90.0 seconds..." occurred after about 20%, but it continued successfully until consistentently (I tried several times) 30% (and 2424832) just like the picuture

After it fails, I reboot the NSPanel and I successfully flash nspanel_blank.tft using Developer Tools->Services->ESPHome: nspanel2_upload_tft_url so I can get back to trying it again

Notice the USART Update show a baud rate of 115200, not sure if lowering to 9600 would solve my problem (as others have suggested) but I did unsuccessfully try to set it in both in my by NSPanel's esphome yaml and the /config/esphome/.esphome/packages/566b10a3/nspanel_esphome.yaml, but every time I flashed, the NSPanel display still showed 115200

[deejaybeam]

• The message "Connection error occurred: Ping response not received after 90.0 seconds" while uploading tft is per design: ESPHome-API shut´s down while uploading TFT to not interrupt the process with other things - the question would be: do you see data counting in the display itself, or does this also stop?
• UART baud rate does not need to be changed, only in some rare cases the nextion does not switch to 115200 baud and so the esp is not able to "talk" with nextion in anyway - in this case update will not start, and you don´t see any information about nextion type, firmware, ... in esphome-log
• If you see "Waiting for content..." this means none of the tft´s from this repo has been installed. "Waiting for content..." is a message from nspanel-lovelace-ui tft

If installation of blank.tft was successfull, you will have just a white page on your display.

Here is also a link to our wiki for users comming from lovelace: https://github.com/Blackymas/NSPanel_HA_Blueprint/wiki/(EN)-Common-Issues-TFT-Upload-When-nspanel-lovelace-ui-has-been-installed

If you want to change someting like uart in the esp-config, you have to download the "full" nspanel_esphome.yaml (or copy the content into your esp-home-project) to be able to alter the code, but you can´t change something inside the automatically created files (../.esphome/packages/...) this will not work.

In worst case, you have to install the tft via ttl-converter see: https://github.com/Blackymas/NSPanel_HA_Blueprint/issues/166

[jsilveira-ebsco]

Hi @deejaybeam, thanks so much for your reply

• The message "Connection error occurred: Ping response not received after 90.0 seconds" while uploading tft is per design:

Thanks, good to know

• ESPHome-API shut´s down while uploading TFT to not interrupt the process with other things - the question would be: do you see data counting in the display itself, or does this also stop?

The display consistently stops showing exactly 30% (and 2424832) every time - as the image I posted shows (I've done this several times and the percent and number is always the same)

• UART baud rate does not need to be changed, only in some rare cases the nextion does not switch to 115200 baud and so the esp is not able to "talk" with nextion in anyway - in this case update will not start, and you don´t see any information about nextion type, firmware, ... in esphome-log

Thanks, I understand that you're saying that since it started, the baud rate of (115200) isn't a factor in my issue

• If you see "Waiting for content..." this means none of the tft´s from this repo has been installed. "Waiting for content..." is a message from nspanel-lovelace-ui tft

I got by and no longer see the "Waiting for content..." because I successfully installed nspanel_blank.tft, see the Context section of my post for more details

If installation of blank.tft was successfull, you will have just a white page on your display.

Yes, successfully installing nspanel_blank.tft left me with a blank gray display and is what allowed me to at that point successfully start the installation of nspanel_us.tft, which leaves me at the issue I've described

Here is also a link to our wiki for users comming from lovelace: https://github.com/Blackymas/NSPanel_HA_Blueprint/wiki/(EN)-Common-Issues-TFT-Upload-When-nspanel-lovelace-ui-has-been-installed

Yes, I'm familiar with it and it is the page that led me to installing nspanel_blank.tft

If you want to change someting like uart in the esp-config, you have to download the "full" nspanel_esphome.yaml (or copy the content into your esp-home-project) to be able to alter the code, but you can´t change something inside the automatically created files (../.esphome/packages/...) this will not work.

Ahh... gotcha', though the only thing I was thinking of modifying there was the baud rate buy you've informed me that's not causing my problem so I'll just leave it as is

In worst case, you have to install the tft via ttl-converter see: #166

As the issue described in #166 "Model does not match" isn't the same as the issue I've described ("nspanel2.local: Connection error occurred: Connection lost"), I'll wait and hope I can get some help with my issue before looking into #166 which says:

" I figured out that you can flash the Nextion Display direct via ttl and Nextion Editor. All you need is solder two wires on the Points "TF -RX" and "TF_TX". Then you support the Panel with 5V via the main connector (DO NOT USE J1 with 5V!!). Flash the Nextion Display directly via Nextion Editor and blackymas' .HMI file and all works excellent!"

If I do eventually give #166 a shot as an option to try to get by my "nspanel2.local: Connection error occurred: Connection lost" to possibly resolve my issue of not being able to load nspanel_us.tft:

1. What on my TTL converter should attach to "TF -RX" and "TF_TX" on the switch, should it reverse as typically is the case where "TF -RX" goes to TX and "TF -TX" goes to RX? I assume there's not flash mode I have to put it in?
2. Is it saying I should power my switch with the main 5V power (and keep my TTL converter on 3.3V mode) when flashing?
3. When flashing I specify nspanel_us.HMI?
4. When flashing, can I use ESPFlasher or upload the nspanel_us.HMI to my config/www folder in HA and use Developer Tools->Services->ESPHome: nspanel2_upload_tft_url (which is what I now do to reinstall nspanel_blank.tft after a failed attempt to load nspanel_us.tft)

[jsilveira-ebsco]

Does the fact that I get prompted with this Sign In when I go to nspanel2.local help explain my issue of my eventually getting the following message trying to update with nspanel_us.tft: "nspanel2.local: Connection error occurred: Connection lost"?

• If I somehow disabled this Sign In might the nspanel_us.tft update finally complete successfully?
• To be honest, I have no idea what credentials to specify to sign in
• Note, the state it's in now is nspanel_blank.tft has been installed and it's showing the blank white screen

[jsilveira-ebsco]

Hi again @deejaybeam, I'd like to try to change config in nspanel_esphome.yaml, but I'm not sure where to put it where I'll be allowed to change the config?

• I created a /config/esphome/nspanel_esphome.yaml and copied the contents of nspanel_esphome.yaml to it but config changes don't seem to take
• I ask because I'm guessing my "nspanel2.local: Connection error occurred: Connection lost" issue may be related to the installation not being able to connect to the esphome web_server configured in nspanel_esphome.yaml for authentication reasons (per my last post showing the "Sign In"). I'm guessing if I can remove the values for username / password maybe it'll continue as expected

[deejaybeam]

webserver-access: username: admin password: your wifi-password

But the webserver is just an additional component which can be used to access the panel via web-browser, this has nothing to do with any kind of functionallity

if you have: connection lost" than this is what happens - the panel has lost the wifi-connection this is also the reason why the upload fails the upload need a rock-solid-connection just sending status-updates may work, because they are "queued", but sending the whole tft is something other

[jsilveira-ebsco]

@deejaybeam , thanks again for your reply Yeah, thanks, I get that the web server shouldn't have anything to do with my problem. I also get what you're saying about needing rock solid wifi because the tft is large.

That said, it's WAY too coincidental that every single time I try (and I've tried > 10 times now) I get the same exact message at the same exact percentage (30%) at the same exact bytes (2424832). I mean it's incredibly specific and incredibly consistent. Does this consistency mean anything or help to solve this issue?

In case it helps, I've now tried this with 2 SSIDs (from 2 different routers - both are just being used as access points) and in both cases, I plugged the NSPanel right next to the routers and here's the signal from each

[jsilveira-ebsco]

Hi @deejaybeam, I've updated my original issue post to summarize everything I've tried (including the following). Do you think at this point this should be considered a defect/bug instead of a "question" per everything I've tried and still not getting the expected behavior? I'm also wondering if we might be able to get some help from Blackymas as the developer?

Note:

• NSPanel version is: 72 (serial: A3653401A544AC68; flash size: 16777216)
• ESPHome: 2023.3.1

Per the below I did discover the following who seem be in a similar situation as I am so I tried commenting out the logger which seemed to work for someone in the first post but not the 2nd post but that didn't work for me. I also tried reverting back to Tasmota then flashed via FlashNextion first nspanel_blank.tft, then nspanel_us.tft (at that point the screen was black), then I flashed with esphome but still get the sideways "System Data Error!" (this approach came from corradodave from TFT upload error

177)

• NSPanel System Data ERROR after HA yaml update
• System data error nspanel

Not sure if this is considered progress or not, but when my NSPanel got stuck displaying 30% (2424832 bytes) like it always does, I opened up the esphome web server for my NSPanel and noticed the logs were still moving and looked like this

So I waited it out (about an hour) to where it finally said it "Successfully updated Nextion!"

It seemed to reconnect to some extent and my esphome web server looked good, but my NSPanel was still just displaying 30% (2424832 bytes)

But because the display was still showing 30% (2424832 bytes), I unplugged it, waited, then plugged it back in but all I get is this sideways error "System Data ERROR!"

So although the display is stuck with this sideways error "System Data ERROR!", the NSPanel looks like it's functional, you can see here where I triggered the switch via the esphome web server (where I did here it click when I did)

[edwardtfn]

So, how are you now with this? Are you still with System Data ERROR! message?

[jsilveira-ebsco]

Hi @edwardtfn, thanks for asking 👍. Yes, System Data ERROR! is the furthest point I've been able to get to

• Note, I can always easily reflash with nspanel_blank.tft to get back to the blank white screen

[edwardtfn]

What if you type in your Web browser (in your computer) the address to the TFT file, like this:

http://homeassistant.local:8123/local/nspanel_us.tft

Will the browser download the TFT file? Most important, does the file have the full size as the one in the GitHub repository or is this downloaded file smaller? I'm trying to ensure that the problem is not in y o ur web server or TFT file, so we focus our efforts in the right place.

[edwardtfn]

This looks to be related to this and looks like he had a problem in the Web server and the user solved by using another Web server to host the TFT file temporarily.

https://github.com/Blackymas/NSPanel_HA_Blueprint/issues/619#issuecomment-1501606719

[doron1]

Unfortunately it did not fix it for me. Using a separate instance of nginx, I tried uploading the target nspanel_eu.tft - same situation. Power reset and then tried to load nspanel_blank.tft via that separate nginx. Same issue.

[edwardtfn]

What do you mean by "same issue"? What is the problem you have right now?

[doron1]

Sorry, wrong thread. My problem was this. I now have a usable workaround, but that is on separate issue thread #641.

[jsilveira-ebsco]

Hello @edwardtfn and @doron1, thanks so much for your replies, I really appreciate it.

• @edwardtfn, yes my browser does sucessfully download my nspanel_us.tft file, and it is the same size (7,829) as the one I put in the HA config/www when I download it via my browser using http://homeassistant.local:8123/local/nspanel_us.tft

• That said, I eliminated downloading the file via wifi as a factor by following the steps in #166 where I soldered my TTL to the TF-RX & TF-TX and tried flashing nspanel_us.tft (as well as nspanel_us.HMI) via Nextion Editor - this resulted in my NSPanel getting stuck displaying 30% (2424832 bytes) EXACTLY as it does if I try to flash via Developer Tools in HA which I've tried over 10 times all with the same EXACT result (see below image)

• From here, my earlier post shows how despite this, I did notice that although the screen doesn't progress beyond 30% (2424832 bytes), the esphome logs showed it progressed (slowly) and eventually logged "Successfully updated Nextion!" but after I rebooted it, I was left at the sideways "System Date ERROR!" on the display which really reflects the farthest I've gotten

• NOTE:, in case it helps get anyone up to speed quickly, because I know my post is long (due to all the details of all the things I've tried), I've also included a bulleted summary under the "What I've Tried" section in my original post

[edwardtfn]

@jsilveira-ebsco, sorry for the late reply here, but I think I got out of ideas to help you.

Are you still having the same issue?

[jsilveira-ebsco]

Hi @edwardtfn, no worries, I've been away a few days myself. I haven't been able to think of anything else myself and haven't received any other feedback so unfortunately I'm blocked.

I'm still hopeful someone else might have an epiphany, or @Blackymas might have a suggestion, or maybe a new release might get me by my hurdle.

[edwardtfn]

v3.2.3 is already in beta, but I'm not aware of any change related to this problem you are facing, although one of the changes is related to the communication of TFT files in a fresh new panel. Maybe you can try that... You will have to download TFT files again and upload to your local server, update your blueprint (and ideally deleting your current automationk, if any, and creating it again and, in your ESPHome file, in the remote package area, change from ref: main to ref: beta.

By the way, do you mind sharing your ESPHome yaml? Just make sure to remove any private info like wifi credentials before sharing.

[jsilveira-ebsco]

Thanks @edwardtfn, I'll give that a try! I won't be able to get to it until next weekend, but I'll definitely let you know how it goes. My ESPhome.yaml is super basic but I'll be happy to share it then as well.

[Doughboy68]

@edwardtfn can you explain how to use the button exit reparse-mode? I just did a new device with 3.3 and still did not work to update tft... I tried pressing the button in device and it did do something but would usually reboot the panel... no matter what I did, I could not load tft file. I had to put that external components lines in to do initial blank tft. then I removed and re-flash, then I can upload any tft now.

[edwardtfn]

3. "Exit reparse" button

One of the biggest challenges to a new user is to upload the TFT file for the first time. This is due to Sonoff using the Protocol Reparse Mode to control the communication with the Nextion display. This prevents ESPHome to communicate with the display using its default libraries and therefore prevents installing the new TFT. With this version you will have a new button named "Exit reparse", which will send a command to the Nextion to exit that mode for a few seconds, giving to the use a chance to then upload the TFT file without the need to change your ESPHome settings or using older Nextion libraries. Once you have successfully uploaded any of the TFT files from this project (nspanel_blank.tft, nspanel_eu.tft or nspanel_us.tft), the reparse mode will be permanently disabled and this button is not needed anymore.

If you have your panel displaying the Sonoff original screen, please follow the following steps to install your TFT file:

1. Go to the front of your panel with a portable device with access to Home Assistant
2. Open the device related to your panel under Settings > Device & Services > ESPHome
3. Press the new button "Exit reparse" and wait for your panel to change it's screen to another page (which will take around 10s)
4. While the new page is shown (it will be there for just a couple of seconds), press the button "Upload TFT"
5. You should then see the progress bar in your display and after no more than 20 minutes the new TFT will be displayed._

[edwardtfn]

Please let me know if that works, although if you have already installed a need TFT that means you are not in reparse mode anymore.

[maddoxjny]

Please let me know if that works, although if you have already installed a need TFT that means you are not in reparse mode anymore.

unfortunately I didnt load the blank and my screen now reads System data error is there anyway to recover ? I hsve tried this on 3 of these before I move to the love lace. shame because i like this better.

[Doughboy68]

Please let me know if that works, although if you have already installed a need TFT that means you are not in reparse mode anymore.

I already flashed the tft using the other way. I like these panels so I am ordering another one so will try on that one when I receive it.

[edwardtfn]

my screen now reads System data error

You have a corrupt TFT file loaded to your device.

is there anyway to recover ?

Yes! Try this:

1. Download the TFT file again from GitHub
2. Make sure the downloaded file have the same size as the one in GitHub (approx 6.13mb for EU and 7.64mb for US).
3. Upload the file to your local www server
4. Using your computer's browser, try to type the url of the file in your local server and download it to your computer.
5. Make sure the file size is exactly the same you downloaded originally from GitHub
6. Make sure the url you used to download the file from your local server is the same url set in your ESPHome settings (yaml)
7. Click Upload TFT button

Please let me know what happens when you click upload TFT... Does the download starts at least?

[maddoxjny]

this is what I always get. I verified i can download the tft

[20:23:02][D][button:010]: 'kitnspanelwh Update TFT display' Pressed. [20:23:02][D][binary_sensor:036]: 'kitnspanelwh Nextion display': Sending state OFF

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

[maddoxjny]

I am pretty sure it doesnt see the Nextion

[20:22:49][C][nextion:118]: Device Model:
[20:22:49][C][nextion:119]: Firmware Version: [20:22:49][C][nextion:120]: Serial Number:
[20:22:49][C][nextion:121]: Flash Size:
[20:22:49][C][nextion:122]: Wake On Touch: True

[edwardtfn]

Mmmmm Could you please share the ESPHome yaml you are using? Please make sure you have removed any private info like wifi credentials before sharing.

[edwardtfn]

By the way, when you press the Upload TFT button, do you see anything changing in your panel screen?

[maddoxjny]

sure I renamed the tft because of the posts I have seen substitutions:

CHANGE ME START

device_name: "kitnspanelwh" wifi_ssid: "" wifi_password: ""

nextion_update_url: "http://192.168.1.72:8123/local/nspanelblank.tft" # URL to local tft File

nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_us.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!

[maddoxjny]

I have 4 of these and have yet to make any of them work. The 4th just failed 60 percent into the full tft

substitutions:

CHANGE ME START

device_name: "kitwhtns" wifi_ssid: "" wifi_password: ""

nextion_update_url: "http://192.168.1.72:8123/local/nspanelus.tft" # URL to local tft File

nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_us.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!

[edwardtfn]

The 4th just failed 60 percent into the full tft

This is something between your panel and your local server. Maybe an unstable wifi? I don't have anything different to suggest. Just try again...

[maddoxjny]

l tried putting files on my iis and still failed. I would agree with the network issue but the lovelace has woked the first time on all of them. I am not bashing this plugin just saying I think there is something wrong. Different chips? or something. Sucks I like this one much better

[maddoxjny]

made it a bit further stuck on the please wait screen

[edwardtfn]

made it a bit further stuck on the please wait screen

Could you please share a picture of this screen wo I know what are you talking about?

[edwardtfn]

I am not bashing this plugin just saying I think there is something wrong. Different chips? or something.

There are lots of differences. This project uses ESPHome, which uses a different library to manage the communication with the Nextion display. The TFT file here might be much bigger (I'm guessing), etc. But don't give up. This process for upload TFT is painful at the first time, after that is much more smoother.

[Doughboy68]

made it a bit further stuck on the please wait screen

Did you upgrade to new blueprint? If you are running old panels you may be using old blueprint which is not compatible - I had this happen when adding a new panel and needed to upgrade blueprint and reflash and update tft on old also.

[maddoxjny]

The Blueprint update worked. I deleted it and reimported it. I do have another question when moving from the lovelace version it says I have to upload the blank tft but you have to do that with lovelace still installed. But the command to upload to the nspanel is available until I flash with this version? I linked to the instructions below

https://github.com/Blackymas/NSPanel_HA_Blueprint/wiki/(EN)-Common-Issues-TFT-Upload-When-nspanel-lovelace-ui-has-been-installed

[bam27beer]

3. "Exit reparse" button

One of the biggest challenges to a new user is to upload the TFT file for the first time. This is due to Sonoff using the Protocol Reparse Mode to control the communication with the Nextion display. This prevents ESPHome to communicate with the display using its default libraries and therefore prevents installing the new TFT. With this version you will have a new button named "Exit reparse", which will send a command to the Nextion to exit that mode for a few seconds, giving to the use a chance to then upload the TFT file without the need to change your ESPHome settings or using older Nextion libraries. Once you have successfully uploaded any of the TFT files from this project (nspanel_blank.tft, nspanel_eu.tft or nspanel_us.tft), the reparse mode will be permanently disabled and this button is not needed anymore.

If you have your panel displaying the Sonoff original screen, please follow the following steps to install your TFT file:

1. Go to the front of your panel with a portable device with access to Home Assistant
2. Open the device related to your panel under Settings > Device & Services > ESPHome
3. Press the new button "Exit reparse" and wait for your panel to change it's screen to another page (which will take around 10s)
4. While the new page is shown (it will be there for just a couple of seconds), press the button "Upload TFT"
5. You should then see the progress bar in your display and after no more than 20 minutes the new TFT will be displayed._

got 1 of mine working cheers fella , only had them since the kickstarter lol

[germanlaso]

Followed these steps and its working, but taking sooo long. Its been uploading the TFT for 12 hours and still in 44%, steadily increasing though `Try this:

Download the TFT file again from GitHub Make sure the downloaded file have the same size as the one in GitHub (approx 6.13mb for EU and 7.64mb for US). Upload the file to your local www server Using your computer's browser, try to type the url of the file in your local server and download it to your computer. Make sure the file size is exactly the same you downloaded originally from GitHub Make sure the url you used to download the file from your local server is the same url set in your ESPHome settings (yaml) Click Upload TFT button Please let me know what happens when you click upload TFT... Does the download starts at least?`

[edwardtfn]

Its been uploading the TFT for 12 hours and still in 44%, steadily increasing though

This is not normal. It should take less than half hour for 100% (I would expect more like 15min). I would cancel and try again.

[germanlaso]

Its been uploading the TFT for 12 hours and still in 44%, steadily increasing though

This is not normal. It should take less than half hour for 100% (I would expect more like 15min). I would cancel and try again.

I know its not normal….. but if I try again with the same method the result should be the same. Or not?….. I don’t wanna loose the last 12 hours 😬

[edwardtfn]

I know its not normal….. but if I try again with the same method the result should be the same. Or not?….. I don’t wanna loose the last 12 hours 😬

It's hard to say for sure what is happening, but I bet it won't work at the end of the 24h transfer. I might be wrong, but I have an impression that everytime someone mentioned here about taking many hours they mention it didn't worked.

It definetely shouldn't take more than 15 to 20 minutes. I don't know what is going wrong, but I definetely would save my time and try again and if it still projecting in hours and not minutes I would look for what could be causing this slowness. But I fully understand if you decide to wait. In the end, I don't know if it will work or not.

[germanlaso]

I know its not normal….. but if I try again with the same method the result should be the same. Or not?….. I don’t wanna loose the last 12 hours 😬

It's hard to say for sure what is happening, but I bet it won't work at the end of the 24h transfer. I might be wrong, but I have an impression that everytime someone mentioned here about taking many hours they mention it didn't worked.

It definetely shouldn't take more than 15 to 20 minutes. I don't know what is going wrong, but I definetely would save my time and try again and if it still projecting in hours and not minutes I would look for what could be causing this slowness. But I fully understand if you decide to wait. In the end, I don't know if it will work or not.

Hi Edward: Thanks for your time!!!! Followed your advice and started again..... tried again and it was as slow as before. Tried uploading nspanel_blank and it uploaded without issues.... when I try to upload nspanel_us.tft on top of it.... it gives me the following error:

`INFO Reading configuration /config/esphome/nspanel.yaml... WARNING GPIO4 is a Strapping PIN and should be avoided. Attaching external pullup/down resistors to strapping pins can cause unexpected failures. See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins INFO Starting log output from nspanel.local using esphome API INFO Successfully connected to nspanel.local

[12:46:03][I][app:102]: ESPHome version 2023.4.4 compiled on May 9 2023, 12:23:04

[12:46:03][C][wifi:363]: Local MAC: C4:DD:57:E9:BD:44 [12:46:03][C][wifi:364]: SSID: 'VTR-3173778'[redacted] [12:46:03][C][wifi:365]: IP Address: 192.168.0.6 [12:46:03][C][wifi:367]: BSSID: E4:57:40:A6:A1:A5[redacted]

[12:46:03][C][wifi:370]: Signal strength: -41 dB ▂▄▆█ [12:46:03][C][wifi:374]: Channel: 1 [12:46:03][C][wifi:375]: Subnet: 255.255.255.0 [12:46:03][C][wifi:376]: Gateway: 192.168.0.1 [12:46:03][C][wifi:377]: DNS1: 190.160.0.15 [12:46:03][C][wifi:378]: DNS2: 200.83.1.5

[12:46:03][C][logger:295]: Level: DEBUG [12:46:03][C][logger:296]: Log Baud Rate: 0 [12:46:03][C][logger:297]: Hardware UART: UART0 [12:46:03][C][uart.arduino_esp32:108]: UART Bus 1: [12:46:03][C][uart.arduino_esp32:109]: TX Pin: GPIO16 [12:46:03][C][uart.arduino_esp32:110]: RX Pin: GPIO17 [12:46:03][C][uart.arduino_esp32:112]: RX Buffer Size: 256 [12:46:03][C][uart.arduino_esp32:114]: Baud Rate: 115200 baud [12:46:03][C][uart.arduino_esp32:115]: Data Bits: 8 [12:46:03][C][uart.arduino_esp32:116]: Parity: NONE [12:46:03][C][uart.arduino_esp32:117]: Stop bits: 1 [12:46:03][C][ledc.output:160]: LEDC Output: [12:46:03][C][ledc.output:161]: Pin GPIO21 [12:46:03][C][ledc.output:162]: LEDC Channel: 0 [12:46:03][C][ledc.output:163]: PWM Frequency: 1000.0 Hz [12:46:03][C][ledc.output:164]: Bit depth: 16 [12:46:03][C][template.binary_sensor:018]: Template Binary Sensor 'nspanel Nextion display' [12:46:03][C][template.binary_sensor:018]: Device Class: 'connectivity' [12:46:03][C][uptime.sensor:031]: Uptime Sensor 'nspanel uptime' [12:46:03][C][uptime.sensor:031]: Device Class: 'duration' [12:46:03][C][uptime.sensor:031]: State Class: 'total_increasing' [12:46:03][C][uptime.sensor:031]: Unit of Measurement: 's' [12:46:03][C][uptime.sensor:031]: Accuracy Decimals: 0

[12:46:03][C][template.sensor:023]: Template Sensor 'nspanel Display Target Temperature' [12:46:03][C][template.sensor:023]: State Class: '' [12:46:03][C][template.sensor:023]: Unit of Measurement: '' [12:46:03][C][template.sensor:023]: Accuracy Decimals: 1 [12:46:03][C][template.sensor:024]: Update Interval: 10.0s [12:46:03][C][template.text_sensor:021]: Template Sensor 'nspanel Notification Label' [12:46:03][C][template.text_sensor:021]: Template Sensor 'nspanel Notification Text' [12:46:03][C][template.text_sensor:021]: Template Sensor 'nspanel Settings Entity' [12:46:03][C][template.switch:075]: Template Switch 'nspanel Notification unread' [12:46:03][C][template.switch:098]: Restore Mode: always OFF [12:46:03][C][template.switch:060]: Restore State: YES [12:46:03][C][template.switch:061]: Optimistic: YES [12:46:03][C][template.switch:075]: Template Switch 'nspanel Notification sound' [12:46:03][C][template.switch:098]: Restore Mode: restore defaults to OFF [12:46:03][C][template.switch:060]: Restore State: YES [12:46:03][C][template.switch:061]: Optimistic: YES [12:46:03][C][template.switch:075]: Template Switch 'nspanel Confirmation Message' [12:46:03][C][template.switch:098]: Restore Mode: always OFF [12:46:03][C][template.switch:060]: Restore State: NO [12:46:03][C][template.switch:061]: Optimistic: YES [12:46:03][C][switch.gpio:075]: GPIO Switch 'nspanel Relay 1' [12:46:03][C][switch.gpio:098]: Restore Mode: restore defaults to OFF [12:46:03][C][switch.gpio:031]: Pin: GPIO22 [12:46:03][C][switch.gpio:075]: GPIO Switch 'nspanel Relay 2' [12:46:03][C][switch.gpio:098]: Restore Mode: restore defaults to OFF [12:46:03][C][switch.gpio:031]: Pin: GPIO19 [12:46:03][C][switch.gpio:075]: GPIO Switch 'nspanel Screen Power' [12:46:03][C][switch.gpio:098]: Restore Mode: always ON [12:46:03][C][switch.gpio:031]: Pin: GPIO4 [12:46:03][C][template.switch:075]: Template Switch 'nspanel Sleep mode' [12:46:03][C][template.switch:086]: Device Class: 'switch' [12:46:03][C][template.switch:098]: Restore Mode: restore defaults to OFF [12:46:03][C][template.switch:060]: Restore State: YES [12:46:03][C][template.switch:061]: Optimistic: NO [12:46:03][C][template.switch:075]: Template Switch 'nspanel Relay 1 Local Fallback' [12:46:03][C][template.switch:098]: Restore Mode: restore defaults to OFF [12:46:03][C][template.switch:060]: Restore State: YES [12:46:03][C][template.switch:061]: Optimistic: YES [12:46:03][C][template.switch:075]: Template Switch 'nspanel Relay 2 Local Fallback' [12:46:03][C][template.switch:098]: Restore Mode: restore defaults to OFF [12:46:03][C][template.switch:060]: Restore State: YES [12:46:03][C][template.switch:061]: Optimistic: YES [12:46:03][C][template.number:050]: Template Number 'nspanel Display Brightness' [12:46:03][C][template.number:050]: Unit of Measurement: '%' [12:46:03][C][template.number:051]: Optimistic: YES [12:46:03][C][template.number:052]: Update Interval: 60.0s [12:46:03][C][template.number:050]: Template Number 'nspanel Display Brightness Dimdown' [12:46:03][C][template.number:050]: Unit of Measurement: '%' [12:46:03][C][template.number:051]: Optimistic: YES [12:46:03][C][template.number:052]: Update Interval: 60.0s [12:46:03][C][template.number:050]: Template Number 'nspanel Temperature Correction' [12:46:03][C][template.number:050]: Unit of Measurement: '°C' [12:46:03][C][template.number:051]: Optimistic: YES [12:46:03][C][template.number:052]: Update Interval: 60.0s [12:46:03][C][template.number:050]: Template Number 'nspanel Page Timeout' [12:46:03][C][template.number:051]: Optimistic: YES [12:46:03][C][template.number:052]: Update Interval: 60.0s [12:46:04][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'nspanel Left Button' [12:46:04][C][gpio.binary_sensor:016]: Pin: GPIO14 [12:46:04][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'nspanel Right Button' [12:46:04][C][gpio.binary_sensor:016]: Pin: GPIO27

[12:46:04][C][restart.button:017]: Restart Button 'nspanel Restart' [12:46:04][C][adc:087]: ADC Sensor 'ntc_source' [12:46:04][C][adc:087]: Device Class: 'voltage' [12:46:04][C][adc:087]: State Class: 'measurement' [12:46:04][C][adc:087]: Unit of Measurement: 'V' [12:46:04][C][adc:087]: Accuracy Decimals: 2 [12:46:04][C][adc:097]: Pin: GPIO38 [12:46:04][C][adc:112]: Attenuation: 11db [12:46:04][C][adc:126]: Update Interval: 60.0s [12:46:04][C][resistance:010]: Resistance Sensor 'resistance_sensor' [12:46:04][C][resistance:010]: State Class: 'measurement' [12:46:04][C][resistance:010]: Unit of Measurement: 'Ω' [12:46:04][C][resistance:010]: Accuracy Decimals: 1

[12:46:04][C][resistance:011]: Configuration: DOWNSTREAM [12:46:04][C][resistance:012]: Resistor: 11200.00Ω [12:46:04][C][resistance:013]: Reference Voltage: 3.3V [12:46:04][C][version.text_sensor:021]: Version Text Sensor 'nspanel ESPhome Version'

[12:46:04][C][nextion:124]: Device Model: NX4832F035_011C [12:46:04][C][ntc:014]: NTC Sensor 'nspanel Temperature' [12:46:04][C][ntc:014]: Device Class: 'temperature' [12:46:04][C][ntc:014]: State Class: 'measurement' [12:46:04][C][ntc:014]: Unit of Measurement: '°C' [12:46:04][C][ntc:014]: Accuracy Decimals: 1 [12:46:04][C][captive_portal:088]: Captive Portal: [12:46:04][C][web_server:151]: Web Server: [12:46:04][C][web_server:152]: Address: nspanel.local:80

[12:46:04][C][mdns:109]: Hostname: nspanel [12:46:04][C][ota:093]: Over-The-Air Updates: [12:46:04][C][ota:094]: Address: nspanel.local:3232 [12:46:04][C][ota:097]: Using Password. [12:46:04][C][api:138]: API Server: [12:46:04][C][api:139]: Address: nspanel.local:6053 [12:46:04][C][api:143]: Using noise encryption: NO [12:46:04][C][wifi_info:009]: WifiInfo IPAddress 'nspanel IP' [12:46:04][C][wifi_info:011]: WifiInfo SSID 'nspanel SSID' [12:46:04][C][wifi_info:012]: WifiInfo BSSID 'nspanel BSSID' [12:46:04][C][wifi_signal.sensor:009]: WiFi Signal 'nspanel RSSI' [12:46:04][C][wifi_signal.sensor:009]: Device Class: 'signal_strength' [12:46:04][C][wifi_signal.sensor:009]: State Class: 'measurement' [12:46:04][C][wifi_signal.sensor:009]: Unit of Measurement: 'dBm' [12:46:04][C][wifi_signal.sensor:009]: Accuracy Decimals: 0 [12:46:08][D][api:102]: Accepted 192.168.0.50 [12:46:08][D][api.connection:961]: Home Assistant 2023.3.5 (192.168.0.50): Connected successfully [12:46:19][D][button:010]: 'nspanel Exit reparse' Pressed. [12:46:25][D][sensor:110]: 'nspanel uptime': Sending state 41.43900 s with 0 decimals of accuracy [12:46:31][D][sensor:110]: 'ntc_source': Sending state 1.68300 V with 2 decimals of accuracy [12:46:31][D][resistance:039]: 'resistance_sensor' - Resistance 11657.1Ω [12:46:31][D][sensor:110]: 'resistance_sensor': Sending state 11657.14258 Ω with 1 decimals of accuracy [12:46:31][D][ntc:026]: 'nspanel Temperature' - Temperature: 21.6°C [12:46:31][D][sensor:110]: 'nspanel Temperature': Sending state 21.58875 °C with 1 decimals of accuracy [12:46:31][D][binary_sensor:036]: 'nspanel Nextion display': Sending state OFF

[12:46:31][D][nextion_upload:175]: Requesting URL: http://192.168.0.50:8123/local/nspanel_us.tft [12:46:31][D][nextion_upload:209]: Updating Nextion NX4832F035_011C... [12:46:31][D][nextion_upload:235]: Waiting for upgrade response [12:46:31][E][uart:015]: Reading from UART timed out at byte 0! [12:46:31][E][uart:015]: Reading from UART timed out at byte 0! [12:46:31][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:32][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][E][uart:015]: Reading from UART timed out at byte 0! [12:46:33][D][nextion_upload:239]: Upgrade response is 19 [12:46:33][D][nextion_upload:242]: Available 0 : 0x00 [12:46:33][D][nextion_upload:242]: Available 1 : 0x00 [12:46:33][D][nextion_upload:242]: Available 2 : 0x00 [12:46:33][D][nextion_upload:242]: Available 3 : 0x00 [12:46:33][D][nextion_upload:242]: Available 4 : 0x00 [12:46:33][D][nextion_upload:242]: Available 5 : 0x00 [12:46:33][D][nextion_upload:242]: Available 6 : 0x00 [12:46:33][D][nextion_upload:242]: Available 7 : 0x00 [12:46:33][D][nextion_upload:242]: Available 8 : 0x00 [12:46:33][D][nextion_upload:242]: Available 9 : 0x00 [12:46:33][D][nextion_upload:242]: Available 10 : 0x00 [12:46:33][D][nextion_upload:242]: Available 11 : 0x00 [12:46:33][D][nextion_upload:242]: Available 12 : 0x00 [12:46:33][D][nextion_upload:242]: Available 13 : 0x00 [12:46:33][D][nextion_upload:242]: Available 14 : 0x00 [12:46:33][D][nextion_upload:242]: Available 15 : 0x00 [12:46:33][D][nextion_upload:242]: Available 16 : 0x00 [12:46:33][D][nextion_upload:242]: Available 17 : 0x00 [12:46:33][D][nextion_upload:242]: Available 18 : 0x00 [12:46:33][D][nextion_upload:248]: preparation for tft update failed 0 "" [12:46:33][D][nextion_upload:324]: Restarting Nextion WARNING nspanel.local: Connection error occurred: [Errno 104] Connection reset by peer INFO Processing unexpected disconnect from ESPHome API for nspanel.local WARNING Disconnected from API INFO Successfully connected to nspanel.local [12:46:44][C][wifi_info:011]: WifiInfo SSID 'nspanel SSID' [12:46:44][C][wifi_info:012]: WifiInfo BSSID 'nspanel BSSID' [12:46:44][C][wifi_signal.sensor:009]: WiFi Signal 'nspanel RSSI' [12:46:44][C][wifi_signal.sensor:009]: Device Class: 'signal_strength' [12:46:44][C][wifi_signal.sensor:009]: State Class: 'measurement' [12:46:44][C][wifi_signal.sensor:009]: Unit of Measurement: 'dBm' [12:46:44][C][wifi_signal.sensor:009]: Accuracy Decimals: 0 [12:46:44][E][uart:015]: Reading from UART timed out at byte 0! [12:46:44][W][nextion:078]: Nextion is not connected! [12:46:45][E][uart:015]: Reading from UART timed out at byte 0! [12:46:45][W][nextion:078]: Nextion is not connected! [12:46:45][E][uart:015]: Reading from UART timed out at byte 0! [12:46:45][W][nextion:078]: Nextion is not connected! [12:46:46][E][uart:015]: Reading from UART timed out at byte 0! [12:46:46][W][nextion:078]: Nextion is not connected! [12:46:46][E][uart:015]: Reading from UART timed out at byte 0! [12:46:46][W][nextion:078]: Nextion is not connected! [12:46:47][E][uart:015]: Reading from UART timed out at byte 0! [12:46:47][W][nextion:078]: Nextion is not connected! [12:46:48][E][uart:015]: Reading from UART timed out at byte 0! [12:46:48][W][nextion:078]: Nextion is not connected! [12:46:48][E][uart:015]: Reading from UART timed out at byte 0! [12:46:48][W][nextion:078]: Nextion is not connected! [12:46:48][D][api:102]: Accepted 192.168.0.50 [12:46:49][D][api.connection:961]: Home Assistant 2023.3.5 (192.168.0.50): Connected successfully [12:46:49][E][uart:015]: Reading from UART timed out at byte 0! [12:46:49][W][nextion:078]: Nextion is not connected! [12:46:50][E][uart:015]: Reading from UART timed out at byte 0! [12:46:50][W][nextion:078]: Nextion is not connected! [12:46:50][E][uart:015]: Reading from UART timed out at byte 0! [12:46:50][W][nextion:078]: Nextion is not connected! [12:46:51][E][uart:015]: Reading from UART timed out at byte 0! `

[edwardtfn]

What you see in your panel's display right now? Have you successfully uploaded the nspanel_blank.tft to this device? And if you paste this link into your laptop, can you get the TFT file into your laptop? What is the file size after this download and how long it takes to download to your computer? http://192.168.0.50:8123/local/nspanel_us.tft It should be around 7.6Mb.

[germanlaso]

What you see in your panel's display right now? Have you successfully uploaded the nspanel_blank.tft to this device? And if you paste this link into your laptop, can you get the TFT file into your laptop? What is the file size after this download and how long it takes to download to your computer? http://192.168.0.50:8123/local/nspanel_us.tft It should be around 7.6Mb.

• Display is showing a completely white screen, so I guess the nspanel_blank.tft file was OK
• The size of the nspanel_us.tft when downloades from http://192.168.0.50:8123/local/nspanel_us.tft is 8.006.416 bytes
• Also deleted the "external components" lines from the nspanel.yaml after succesfully uploading nspanel_blank.tft

Thanks!!

[germanlaso]

This is my nspanel.yaml file:

`substitutions:

device_name: "nspanel" wifi_ssid: "MY SSID" wifi_password: "WIFI PASS"

nextion_update_url: "http://192.168.0.50:8123/local/nspanel_us.tft" # URL to local tft File

packages: remote_package: url: https://github.com/Blackymas/NSPanel_HA_Blueprint ref: main files: [nspanel_esphome.yaml] refresh: 300s

[edwardtfn]

• Display is showing a completely white screen, so I guess the nspanel_blank.tft file was OK

The nspanel_blank.tft on v3.3 is a QR code instead. They do the same, so using an older version shouldn't be any issue, but make sure you have the right file for nspanel_us.tft.

The size of the nspanel_us.tft when downloades from http://192.168.0.50:8123/local/nspanel_us.tft is 8.006.416 bytes

I'm using my mobile now, so I can't see the exactly size from the file from GitHub. Have you double checked if the file size is the same?

[germanlaso]

The nspanel_blank.tft on v3.3 is a QR code instead. They do the same, so using an older version shouldn't be any issue, but make sure you have the right file for nspanel_us.tft.

Where can I find that nspanel_blank.tft. I didn't find it so I made it using the Nextion editor

I'm using my mobile now, so I can't see the exactly size from the file from GitHub. Have you double checked if the file size is the same?

Yes, exactly the same size

[germanlaso]

tried setting baud rate to 9600. Same error, but log changed a bit though:

`[14:16:31][D][nextion_upload:242]: Available 12 : 0x00 [14:16:31][D][nextion_upload:242]: Available 13 : 0x00 [14:16:31][D][nextion_upload:242]: Available 14 : 0x00 [14:16:31][D][nextion_upload:242]: Available 15 : 0x00 [14:16:31][D][nextion_upload:242]: Available 16 : 0x00 [14:16:31][D][nextion_upload:242]: Available 17 : 0x00 [14:16:31][D][nextion_upload:242]: Available 18 : 0x00 [14:16:31][D][nextion_upload:248]: preparation for tft update failed 0 "" [14:16:31][D][nextion_upload:310]: Restarting Nextion

WARNING nspanel.local: Connection error occurred: [Errno 104] Connection reset by peer INFO Processing unexpected disconnect from ESPHome API for nspanel.local WARNING Disconnected from API INFO Successfully connected to nspanel.local [14:16:42][W][nextion:072]: Nextion is not connected! [14:16:42][W][nextion:072]: Nextion is not connected! [14:16:43][W][nextion:072]: Nextion is not connected!`