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.33k stars 247 forks source link

[W][nextion:077]: Nextion is not connected! #1214

Closed pillemats closed 9 months ago

pillemats commented 9 months ago

hi

i tried to reflash and flash the blank tft. but everyytime is the same Display shows "waiting for content" this is taking longern then usual.... my config:

`substitutions:`

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

  device_name: "nspanel-dachboden" 
  wifi_ssid: "xxx"
  wifi_password: "xxx"

  nextion_update_url: "http://192.168.178.205: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 #####

##### 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! #####`

i actually flashed my display with the newest fw from blacky and now i want to flash the tft file and i get this error:

[21:28:44][C][wifi_info:012]: WifiInfo BSSID 'nspanel-dachboden BSSID'
[21:28:44][C][wifi_signal.sensor:009]: WiFi Signal 'nspanel-dachboden RSSI'
[21:28:44][C][wifi_signal.sensor:009]:   Device Class: 'signal_strength'
[21:28:44][C][wifi_signal.sensor:009]:   State Class: 'measurement'
[21:28:44][C][wifi_signal.sensor:009]:   Unit of Measurement: 'dBm'
[21:28:44][C][wifi_signal.sensor:009]:   Accuracy Decimals: 0
[21:28:44][W][nextion:077]: Nextion is not connected! 
[21:28:45][W][nextion:077]: Nextion is not connected! 
[21:28:45][W][nextion:077]: Nextion is not connected! 
[21:28:46][W][nextion:077]: Nextion is not connected! 
[21:28:47][W][nextion:077]: Nextion is not connected! 
[21:28:47][W][nextion:077]: Nextion is not connected! 
[21:28:48][W][nextion:077]: Nextion is not connected! 
[21:28:48][W][nextion:077]: Nextion is not connected! 
[21:28:49][W][nextion:077]: Nextion is not connected! 
[21:28:49][D][button:010]: 'nspanel-dachboden Update TFT display' Pressed.
[21:28:49][D][main:1556]: Button pressed: Update TFT display
[21:28:49][D][nextion_upload:169]: Connected
[21:28:49][D][nextion_upload:175]: Requesting URL: http://192.168.178.205:8123/local/nspanel_eu.tft
[21:28:49][D][nextion_upload:209]: Updating Nextion ...
[21:28:49][D][nextion_upload:235]: Waiting for upgrade response
[21:28:49][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:49][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:50][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][E][uart:015]: Reading from UART timed out at byte 0!
[21:28:51][D][nextion_upload:239]: Upgrade response is  20
[21:28:51][D][nextion_upload:242]: Available 0 : 0x00
[21:28:51][D][nextion_upload:242]: Available 1 : 0x00
[21:28:51][D][nextion_upload:242]: Available 2 : 0x00
[21:28:51][D][nextion_upload:242]: Available 3 : 0x00
[21:28:51][D][nextion_upload:242]: Available 4 : 0x00
[21:28:51][D][nextion_upload:242]: Available 5 : 0x00
[21:28:51][D][nextion_upload:242]: Available 6 : 0x00
[21:28:51][D][nextion_upload:242]: Available 7 : 0x00
[21:28:51][D][nextion_upload:242]: Available 8 : 0x00
[21:28:51][D][nextion_upload:242]: Available 9 : 0x00
[21:28:51][D][nextion_upload:242]: Available 10 : 0x00
[21:28:51][D][nextion_upload:242]: Available 11 : 0x00
[21:28:51][D][nextion_upload:242]: Available 12 : 0x00
[21:28:51][D][nextion_upload:242]: Available 13 : 0x00
[21:28:51][D][nextion_upload:242]: Available 14 : 0x00
[21:28:51][D][nextion_upload:242]: Available 15 : 0x00
[21:28:51][D][nextion_upload:242]: Available 16 : 0x00
[21:28:51][D][nextion_upload:242]: Available 17 : 0x00
[21:28:51][D][nextion_upload:242]: Available 18 : 0x00
[21:28:51][D][nextion_upload:242]: Available 19 : 0x00
[21:28:51][D][nextion_upload:248]: preparation for tft update failed 0 ""
[21:28:51][D][nextion_upload:310]: Restarting Nextion
[21:28:53][D][nextion_upload:313]: Restarting esphome
WARNING nspanel-dachboden.local: Connection error occurred: [Errno 104] Connection reset by peer
INFO Processing unexpected disconnect from ESPHome API for nspanel-dachboden.local
WARNING Disconnected from API
INFO Successfully connected to nspanel-dachboden.local
[21:29:09][W][nextion:077]: Nextion is not connected! 
[21:29:10][W][nextion:077]: Nextion is not connected! 
[21:29:10][W][nextion:077]: Nextion is not connected! 
[21:29:11][W][nextion:077]: Nextion is not connected! 
[21:29:11][W][nextion:077]: Nextion is not connected! 
[21:29:12][W][nextion:077]: Nextion is not connected! 
[21:29:12][W][nextion:077]: Nextion is not connected! 
[21:29:13][W][nextion:077]: Nextion is not connected! 
[21:29:13][W][nextion:077]: Nextion is not connected! 
[21:29:14][W][nextion:077]: Nextion is not connected! 
[21:29:14][W][nextion:077]: Nextion is not connected! 
[21:29:15][W][nextion:077]: Nextion is not connected! 
[21:29:15][W][nextion:077]: Nextion is not connected! 
[21:29:16][W][nextion:077]: Nextion is not connected! 
[21:29:17][W][nextion:077]: Nextion is not connected! 
[21:29:17][W][nextion:077]: Nextion is not connected! 
[21:29:18][W][nextion:077]: Nextion is not connected! 
[21:29:18][W][nextion:077]: Nextion is not connected! 
[21:29:19][W][nextion:077]: Nextion is not connected! 
[21:29:19][W][nextion:077]: Nextion is not connected! 
[21:29:20][W][nextion:077]: Nextion is not connected! 
[21:29:20][W][nextion:077]: Nextion is not connected! 
[21:29:21][W][nextion:077]: Nextion is not connected! 
[21:29:21][W][nextion:077]: Nextion is not connected! 
[21:29:22][W][nextion:077]: Nextion is not connected! 
[21:29:22][W][nextion:077]: Nextion is not connected! 
[21:29:23][D][api:102]: Accepted 192.168.178.205
[21:29:23][D][api.connection:1050]: Home Assistant 2023.11.0 (192.168.178.205): Connected successfully
[21:29:23][D][time:045]: Synchronized time: 2023-11-01 21:29:23
[21:29:23][D][sensor:094]: 'nspanel-dachboden API uptime': Sending state 1698870528.00000  with 0 decimals of accuracy
[21:29:23][D][sensor:094]: 'nspanel-dachboden Device uptime': Sending state 1698870528.00000  with 0 decimals of accuracy
[21:29:23][D][main:1764]: System clock synchronized
[21:29:23][W][nextion:077]: Nextion is not connected! 
[21:29:23][W][nextion:077]: Nextion is not connected! 
[21:29:24][W][nextion:077]: Nextion is not connected! 
[21:29:24][W][nextion:077]: Nextion is not connected! 
[21:29:25][W][nextion:077]: Nextion is not connected! 
[21:29:26][W][nextion:077]: Nextion is not connected!

i dont know whats happend. i am totally new with the display. it is my first one....

sorry for the "noob" questions :-)

THX!!!

edwardtfn commented 9 months ago

Everything looks fine with your yaml.

I'd like to ask you to use dev to get more logs, then you set your system back to main:

  1. On your YAML, in the remote_package area, change from ref: main to ref: dev
  2. Flash your panel (it can be wireless)
  3. Try to transfer TFT again (using the same process), but please make sure you capture the logs from ESPHome
  4. Change your YAML back to ref: main
  5. Flash your panel again.
pillemats commented 9 months ago

u are the godfather :-)

Thank you so much! now it works!

the only message i get in HA it this

Bildschirmfoto 2023-11-02 um 08 30 47

but there is no update.... what should i do ? Ignore?

edwardtfn commented 9 months ago

You have updated the TFT from dev, but my plan was to use dev code to upload the TFT file from main. Try to repeat the process, but now using the tft file you find on main branch.

pillemats commented 9 months ago

ok thanks.... so i changed dev to main and clicket install. Then i download the main tft file and uploaded to my www folder. Then i push the upload button in devices.

i get these errors:

logs_nspanel-dachboden_run.txt

edit: i switchet back to dev and tried it again (with the tft file from main) and i think it works. here is the log:

logs_nspanel-dachboden_run.txt

then i switched back to main in config file and installed it and get this log logs_nspanel-dachboden_run.txt

in HA i dont get an missmatch error message

edwardtfn commented 9 months ago

It's weird that you still getting [11:45:23][W][nextion:322]: Nextion reported invalid instruction!. Everything else looks good. If you restart your panel, which versions (TFT, ESPHome and Blueprint) you see in the blue boot page?

pillemats commented 9 months ago

i am not at home.... i will try in the afternoon

pillemats commented 9 months ago

Everything is on 4.0.2

edwardtfn commented 9 months ago

Is everything working fine so far?

pillemats commented 9 months ago

of course! everthing works finde so far

edwardtfn commented 9 months ago

I have the same Nextion reported invalid instruction here... Investigating...

haywiremk commented 9 months ago

I have flashed many of these. I just went to flash another factory one and got the

[D][nextion_upload:248]: preparation for tft update failed 0 ""
[D][nextion_upload:310]: Restarting Nextion
[D][nextion_upload:313]: Restarting esphome

The old pr#2956 trick would not compile. Found in logs the updated pr# and the below added to the yaml worked first try. The Exit reparse button without below code reported it did something but would still always get the preparation for tft update failed 0 for either the regular or blank tft files.

external_components:
  - source: github://pr#5016
    components: [nextion]
    refresh: 1h
Jack187 commented 9 months ago

Everything looks fine with your yaml.

I'd like to ask you to use dev to get more logs, then you set your system back to main:

  1. On your YAML, in the remote_package area, change from ref: main to ref: dev
  2. Flash your panel (it can be wireless)
  3. Try to transfer TFT again (using the same process), but please make sure you capture the logs from ESPHome
  4. Change your YAML back to ref: main
  5. Flash your panel again.

This helped me as well. I was alwasy trying with main (both ref: and eu.tft file). It always reseted the connection in at around 17% while updating the tft. Setting ref: dev and also using the dev tft file solved that issue for me. So after 4 hours my first nspanel seems to work. Thx!

Next I'm going to try flashing ref: dev but use the tft file from main. If that works I'll move back to ref: main. Let you know if it works. Thx to all wo support and develop here!

edwardtfn commented 9 months ago

Next I'm going to try flashing ref: dev but use the tft file from main. If that works I'll move back to ref: main. Let you know if it works.

That's ideal, as it is the stable version. I wouldn't expect any issue, as the engine on dev is where the problem was, not the TFT file, although the TFT on dev is slightly smaller.

Jack187 commented 9 months ago

Next I'm going to try flashing ref: dev but use the tft file from main. If that works I'll move back to ref: main. Let you know if it works.

That's ideal, as it is the stable version. I wouldn't expect any issue, as the engine on dev is where the problem was, not the TFT file, although the TFT on dev is slightly smaller.

Everything worked fine. Now I'm no back on main. Thx again.

pillemats commented 9 months ago

any to do for me?

edwardtfn commented 9 months ago

Not yet... I still have to investigate that... But everything is working, right?

pillemats commented 9 months ago

yes pretty well

tupelotech commented 9 months ago

I have the same "nextion is not connected issue". I have flashed using the ref: dev switch. (I attach the log). I can see that nextion does respond to some extent. When switching back to ref: main - the nextion error was solved - however I was still not able to load the tft file using the UI. After a few attempts the nextion issue returned - I am on a circular journey. any ideas?.

logs_nspanel1_run.txt

tupelotech commented 9 months ago

Sorry guys : its solved : I found the Exit Reparse button : which is not mentioned in the main instructions , just in th default finding section : Im happy but it lost me a lot of time - oh well

edwardtfn commented 9 months ago

I have the same "nextion is not connected issue". I have flashed using the ref: dev switch. (I attach the log). I can see that nextion does respond to some extent. When switching back to ref: main - the nextion error was solved - however I was still not able to load the tft file using the UI. After a few attempts the nextion issue returned - I am on a circular journey. any ideas?.

After loading the TFT with ref: dev, you don't have to load it again when back to ref: main. 😉

edwardtfn commented 9 months ago

I believe this issue is already resolved on dev, so I will close this and we reopen if needed.