Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Can’t update a new device using 3.2.2 #605

Closed
T3mplate-wow opened this issue Apr 5, 2023 · 13 comments · Fixed by #675
Closed

Bug: Can’t update a new device using 3.2.2 #605

T3mplate-wow opened this issue Apr 5, 2023 · 13 comments · Fixed by #675

Comments

@T3mplate-wow
Copy link

Hey there,
yesterday a completely new device arrived. So there was sonoff preinstalled on it.
I was using 3.2.2 to flash the device and this worked for the device itself. I saw the entity in HA and was able to switch the relays and see the temperature, state of the buttons ect.
But the screen shows the sonoff page. As I tried to upgrade the screen nothing happens on the screen. The device lost the connection to HA shortly but there was no refreshing/installing on the tft.
As I switched to 3.0 (this one I used for initial installing before, so I knew this version was working) I was able to upgrade the screen.

On my existing devices using 3.1 I was able to upgrade to 3.2.2. So I beliefe it is a problem just happening on a newly purchased device.

@EvilDemos
Copy link

Im having the same issue. Newly purchased device. Followed the instructions carefully. Flash was sucessfull and integration was successful. Entities are there but can not upgrade the screen. ESPhome log for the nspanel shows

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

Would really appreciate the help

@NC1609
Copy link

NC1609 commented Apr 5, 2023

Hello friends,

I have the same problem. My display is relatively new.
I have bought it 2 weeks ago.
I have already tried to flash the blank.tft and then go to 3.2.2. All unfortunately without success.

@edwardtfn
Copy link
Collaborator

What if you try copying the URL for the TFT file and past into your browser, can you successfully download the TFT file to your computer? And could you please double check the file size after the download with your browser?

@T3mplate-wow
Copy link
Author

I am not able to reproduce this anymore, because I installed 3.0 and this one was working.
I am extremely sure that I did everything right. The tft was downloadable/reachable even through the browser.
Update from 3.0 to 3.2.2 or from 3.1 to 3.2.2 works fine. It is just happening when the display is clean with Sonoff from factory

@Azimuth0r
Copy link

I just bought a new NSPanel and have the same issue. How do you deploy version 3.0?

@T3mplate-wow
Copy link
Author

I believe 3.1 will also work. Here you can find 3.0 https://github.com/Blackymas/NSPanel_HA_Blueprint/tree/v.3.0.0
and here 3.1 https://github.com/Blackymas/NSPanel_HA_Blueprint/tree/v.3.1.0

you need to download the nspanel.tft or nspanel_eu.tft. I marked it as nspanel_3_0.tft, so that I can distinguish between.

Then I downloaded the blueprint in this version.

In the ESP Config I used just the first part:

substitutions:

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

  device_name: "YOUR NSPANEL_NAME" 
  wifi_ssid: "YOUR WIFI SSID"
  wifi_password: "YOUR WIFI PASSWORD"

  nextion_update_url: "http://HOME-ASSISTANT-IP: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 #####

Don’t forget to insert the right tft file. In my case it was nspanel_3_0.tft.

After this part I added the whole esphome.yaml.
In case of 3.0 this file:
https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/v.3.0.0/nspanel_esphome.yaml
copy the whole text into the esp config under the part mentioned before.

After this you can flash it by wire und update the tft successfully.

@Azimuth0r
Copy link

Thanks, I tried 3.1 with the US TFT. This got me further, now I have an error that says "Model does not match Device Model: NX4832F035_011C"
I updated via OTA, do you think direct serial is required?

@EvilDemos
Copy link

EvilDemos commented Apr 6, 2023

Looks like flashing the 3.0 worked then I updated the tft via link and it works perfect now

From what I saw the Service ESPHome: nspanel2_upload_tft_url does not save the url to update the panel. I have to manually type it in when its time up update the panel

@deejaybeam
Copy link
Collaborator

Thanks, I tried 3.1 with the US TFT. This got me further, now I have an error that says "Model does not match Device Model: NX4832F035_011C" I updated via OTA, do you think direct serial is required?

This usually happens, when the upload of the tft is broken and the nextion firmware is defect.
try to upload blank.tft to "repair" the nextion-code, than try again to upload the full-tft.
Also had this case with bad WLAN - uploading blank.tft with another WLAN solved this.

@edwardtfn
Copy link
Collaborator

Please take a look at this: #619 (comment)

It looks quite similar and the user solved with another Web server hosting the TFT file temporarily.

@edwardtfn
Copy link
Collaborator

So, I believe everyone here got to a solution, right?

@T3mplate-wow, are you ok about closing this thread?

@T3mplate-wow
Copy link
Author

In my opinion there is still a bug in 3.2.2 which prevents to install the tft file, when the original sonoff display software is installed. So this is an open bug for all new users of this project.

So if you ask me these all here are just workarounds and the bug is still valid.
If you want to close it I would prefer, if this find a way into the official troubleshooting/known issues page with a clear way to solve the problem. As far as I know the solution is to install 3.0 first and go to 3.2.2 with an OTA Update.

I can try this if you want.
But of course you can also say that this is not an bug and just close this.

@edwardtfn
Copy link
Collaborator

You are right, this is still an issue with v3.2.2 and new panels. We have a work around, but not really a fix. For reference, you don't have to install v3.0, you can simply follow those steps from this comment and the result should be the same: #641 (comment)

But of course you can also say that this is not an bug and just close this.

No, I think you are totally right and this should be kept open until it is fixed. 🙂

@edwardtfn edwardtfn linked a pull request Apr 26, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants