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

I can not update my NSPANEL's anymore? #706

Closed
edwardtfn opened this issue Apr 21, 2023 · 4 comments · Fixed by #675
Closed

I can not update my NSPANEL's anymore? #706

edwardtfn opened this issue Apr 21, 2023 · 4 comments · Fixed by #675
Labels
Bug Identifies an issue where the system is not functioning as expected.

Comments

@edwardtfn
Copy link
Collaborator

          **@Blackymas could it be that something tipped over in the latest config changes?

I can not update my NSPANEL's anymore with the following YAML;**
substitutions:

DIT GEDEELTE AANPASSEN

device_name: nspanel01
wifi_ssid: !secret wifi_ssid
wifi_password: !secret wifi_password

EIND AANPASBARE SECTIE

#nextion_update_url: "https://weap.nl/ha/nspanel_blank.tft"
#nextion_update_url: https://192.168.2.3:8123/local/eunspanel.tft
nextion_update_url: https://github.com/Blackymas/NSPanel_HA_Blueprint/raw/main/nspanel_eu.tft
packages:
remote_package:
url: https://github.com/Blackymas/NSPanel_HA_Blueprint
ref: main
files: [nspanel_esphome.yaml]
refresh: 300s

The output in the log is as following;

[16:28:25][D][button:010]: 'nspanel01 Update TFT display' Pressed.
[16:28:25][D][nextion_upload:169]: Connected
[16:28:25][D][nextion_upload:175]: Requesting URL: https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_eu.tft
[16:28:26][D][nextion_upload:209]: Updating Nextion ...
[16:28:26][D][nextion_upload:235]: Waiting for upgrade response
[16:28:26][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:26][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:26][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:27][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][E][uart:015]: Reading from UART timed out at byte 0!
[16:28:28][D][nextion_upload:239]: Upgrade response is 20
[16:28:28][D][nextion_upload:242]: Available 0 : 0x00
[16:28:28][D][nextion_upload:242]: Available 1 : 0x00
[16:28:28][D][nextion_upload:242]: Available 2 : 0x00
[16:28:28][D][nextion_upload:242]: Available 3 : 0x00
[16:28:28][D][nextion_upload:242]: Available 4 : 0x00
[16:28:28][D][nextion_upload:242]: Available 5 : 0x00
[16:28:28][D][nextion_upload:242]: Available 6 : 0x00
[16:28:28][D][nextion_upload:242]: Available 7 : 0x00
[16:28:28][D][nextion_upload:242]: Available 8 : 0x00
[16:28:28][D][nextion_upload:242]: Available 9 : 0x00
[16:28:28][D][nextion_upload:242]: Available 10 : 0x00
[16:28:28][D][nextion_upload:242]: Available 11 : 0x00
[16:28:28][D][nextion_upload:242]: Available 12 : 0x00
[16:28:28][D][nextion_upload:242]: Available 13 : 0x00
[16:28:28][D][nextion_upload:242]: Available 14 : 0x00
[16:28:28][D][nextion_upload:242]: Available 15 : 0x00
[16:28:28][D][nextion_upload:242]: Available 16 : 0x00
[16:28:28][D][nextion_upload:242]: Available 17 : 0x00
[16:28:28][D][nextion_upload:242]: Available 18 : 0x00
[16:28:28][D][nextion_upload:242]: Available 19 : 0x00
[16:28:28][D][nextion_upload:248]: preparation for tft update failed 0 ""
[16:28:28][D][nextion_upload:310]: Restarting Nextion
[16:28:30][D][nextion_upload:313]: Restarting esphome

I have tried several things like uploading a small .tft file first etc.

I have / had two nspanels working fine with the old config, but when trying to update it to the latest tft file for one of the existing nspanels, it fails also.

I did notice some changes in the blueprint UI;
image
image

Originally posted by @nielsvlaarhoven in #655 (comment)

@edwardtfn
Copy link
Collaborator Author

edwardtfn commented Apr 21, 2023

@nielsvlaarhoven, as I understood you are trying to update a new panel for the first time following the same procedure you used before with your other panels, is that correct?

If that is the case, please try this with this new panel:

substitutions:

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

  device_name: "nspanel01" 
  wifi_ssid: !secret wlan_name
  wifi_password: !secret wlan_password

  nextion_update_url: "https://weap.nl/ha/nspanel_blank.tft"
  #nextion_update_url: https://192.168.2.3:8123/local/eunspanel.tft
  #nextion_update_url: https://github.com/Blackymas/NSPanel_HA_Blueprint/raw/main/nspanel_eu.tft

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

###### USE THIS ONLY FOR YOUR FIRST TFT UPLOAD, ONCE IT WORKED, REMOVE THESE LINES ######
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! #####

@nielsvlaarhoven
Copy link

@edwardtfn this is correct, it used to work like a charm.. but as we speak i am making progress after troubleshooting this for approximately 2 weeks.
I have followed your posts on this post;
https://community.home-assistant.io/t/sonoff-nspanel-blueprint-configure-your-own-custom-nspanel-easy-via-a-blueprint/500577/282
at least i see progress now, still get a lot of errors while trying to upload the TFT but it seems to work.

@nielsvlaarhoven
Copy link

@edwardtfn i have commented on a thread that is concerning many of the issues i encountered and i tried my best to describe what to do to solve it (it worked for me) i used your comment from the home assistant community also.
If you like, you could find it at esphome/issues#3519 (comment)
If i made any mistakes maybe i should correct it.

@edwardtfn
Copy link
Collaborator Author

That looks great, @nielsvlaarhoven.
Thank you so much for sharing your experience and help other users.
This problem with the first transfer of a TFT is really challenging and is so unfortunate that ESPHome team don't look at this to remove this pain from users.

@edwardtfn edwardtfn added the Bug Identifies an issue where the system is not functioning as expected. label Apr 23, 2023
@edwardtfn edwardtfn linked a pull request Apr 25, 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
Bug Identifies an issue where the system is not functioning as expected.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants