Closed MKme closed 10 months ago
Please set it back to esp-idf, install it into your panel, wait 3 minutes after the boot, so we make sure the boot sequence completed), then press the Upload TFT button. I woukd appreciate the logs of this try.
Absolutely. Here they are.
PS- Thanks for your work on this. By far the most powerful and useful interface to HA. Incredible work.
Eric logs_nspanel_run.txt
In case it is relevant
Another note- The automation doesnt seem to update the ESP function either. My lights can toggle via the slider for relay 1 but the phsical button doesnt toggle then despite being set so
Tried another depower (nspanel is hardwired in light switch). Left power off for ~20 minutes. Noting different on boot so tried again to validate/install. No change. Re-imported blueprint manually from web page and chose overwrite- run automation and still no change.
Not sure what to say. Im totally confused. It was indeed fine on the previous version as were 2 more fresh purchases (all required an upload of blank tft via the Nextion Editor when they were new) One since has been upgraded fine (~3 weeks ago maybe). But this one just wont play ball.
Still trying but low on ideas :)
My apologies for my late reply here.
In fact, I'm a bit out of ideas now, but based on your logs, the issue is in the communication between ESPHome and the Nextion display:
[21:08:55][E][uart:015]: Reading from UART timed out at byte 0!
[21:08:55][W][nextion:077]: Nextion is not connected!
With that said, I don't think upload the Blueprint or change it settings woukd help. In the end, while Nextion isn't connected, the ESPHome part won't inform the Blueprint about it's availability, so the Blueprint itself will not run. You can still control the relays as this is onky using the ESPHome APIs, and not the Blueprint.
Focusing on the Nextion communication, there are 3 things I would suggest:
uart:
Those are all the different baud rates support by Nextion:
Valid values are: 2400, 4800, 9600, 19200, 31250, 38400, 57600, 115200, 230400, 250000, 256000, 512000, and 921600
Thanks. Will report back. Fingers crossed I can baudrate around it. Since the display is still working I doubt it has a connection problem with the flatflex but it is always possible.
Since the display is still working I doubt it has a connection problem with the flatflex but it is always possible.
Well, the display have it's own processor, firmware and programing and running independently of ESPHome, so once a TFT in installed and the display is powered, it will show exactly what you are seeing, including the counting of retries for the Blueprint (which is executed by the disokay/tft, not by ESPHome).
Brain fart yeah 100% it would show just that. Thanks. Going hunting....
You=My hero (again).
Safe bet this was not the software after all. Fatflex was perfectly seated so I took a look around under my trinocular microscope (sorry hdmi was down so no pics)
Surfed around the board for a bit and was just about to give up when I noticed a small whisker of solder laying on the board by the radio module right by the rx/tx pads for the display. It looked like it might have been from the can to board contact. Cant tell if it was connected since it fell right off. Removed. And reassembled.
Validate>Install then display started talking. Upload TFT and full logs of upload. Finsish and now I have connected in ESPhome.
Finally :) Doubt there is anything of use in the logs since I think rx/tx were possibly shorted together. Shouldnt be any harm as uarts are usually protected by design for a short condition. Just in case anyone finds value in making a no-com supervision or whatever Ill attach the log here for you.
Happy logs...
Thanks again. Chalk one up to a very sneaky hardware fault (probably shorted in the act of installing the switch just from carrying it around). logs_nspanel_run (1).txt
Thanks again for the amazing integration/functions.
Nice! I'm happy to hear you found the issue. Enjoy your panel.
Well I finally installed my second panel which was working fine in early Nov but after update I cant connect to the TFT. Followed the guide for everything that you need to know, tried all the tricks in recent closed issues (I think), swapped to ESP-IDF, reimported, power cycled, tried beta, tried the older branch mentioned in closed issue, etc etc. Havent found the trick yet, just refuses to make any ack of the update attempts. Triple verified the file size, location, tried blank tft with triple verify size and location. Both act the same like the tft simply isnt connected but it it showing init screen just fine.
Thanks very much in advance. Tearing my hair out.
esp32dev by Espressif Firmware: 2023.11.6 (Dec 9 2023, 21:03:45)
trace automation.nspanel_garage 2023-12-10T02_26_51.128940+00_00.json