-
Notifications
You must be signed in to change notification settings - Fork 23
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
TFT demo file issues, baud rate #7
Comments
Thanks for the note and for diagnosing the issue. I wonder if there was some external change that triggered this problem, since I haven't run into it. Though realistically, once I got my panels working, I haven't done any more with them. I'm not sure if/when I'll have the time to dive back into this, so if you want to send a PR I'll merge it. Or you can add a note to the Wiki. |
I'll add another issue resolution if you want to add it the wiki. Changes to the yaml file to make it work.
Needed to exit reparse mode after the display connected, so the tft file upload would work. This is possible via the display config.
Configured one of the physical buttons to trigger the tft upload
|
Hey, firstly thanks for the video, really helped with getting this thing flashed with ESPHome.
During this process however, I found an issue with the demo TFT files. In Nextion you need to set the baud rate in the Project.s settings to
bauds=115200
. Without this, after flashing your demo TFT onto the NSPanel, ESPHome can no longer connect to the Nextion display as your ESPHome config tries to communicate at 115200, but the default Nextion rate is 9600. This took me a long while to figure out, and in the process I think I found a few other people who have posted about this same problem around the internet but gave up.Steps to fix:
bauds=115200
in the Project.s config file. (blank to reduce size, takes a long time at 9600 baud rate)bauds=115200
is in the Project.s config, or you'll have to repeat this process again.Hopefully even if this doesn't get fixed in the demo files, this will help out some other people who stumble across this same problem.
The text was updated successfully, but these errors were encountered: