This commit is contained in:
Edward Firmo
2024-01-05 11:44:19 +01:00
parent f12d4c1eea
commit 1896e4fc68

View File

@@ -7,27 +7,37 @@ If something happens during this process, your panel may get stuck on this page.
Understanding what is shown on the boot page can be useful to find the cause of the problem or when you are looking for help.
## Understanding the boot page
Your boot page probably looks like this:
#### Before ESPHome is connected:
#### Before ESPHome is connected
![Boot page Initializing](pics/eu_boot_initializing.png)
#### When ESPHome is connected:
#### When ESPHome is connected
![Boot page with IP](pics/eu_boot_with_ip_address.png)
### What is shown on the screen
#### Initializing or IP address
In the top, you will see the message "Initializing..." while the display is executing it's boot sequence or waiting for a connection from ESPHome.
Once ESPHome is connected to both the display and the Wi-Fi network, that text will be replace by the IP address, which can be useful for troubleshooting.
#### Baud rate (bps)
On the top right corner, it's shown the baud rate used by the display to communicate to ESPHome. By default, all the communication should happens at 115200 bps, but as 921600 bps is also supported, the display will alternate between these 2 rates every 30 seconds until ESPHome gets connected.
#### Framework
Right bellow the baud rate information, you may see the framework used by ESPHome, which is either `esp-idf` (default for new installations) or `arduino` (default for installations prior v4.1.4).
That information will be available only when ESPHome establishes communication with the display. If you cannot see that information after a couple of seconds then you may have an issue on the communication between ESPHome and the display (explained later).
#### Versions
Here you may see the version of TFT, ESPHome and Blueprint used by this project.
If some of those versions are not shown, you can have an indication of where a possible communication issue is.
@@ -39,10 +49,13 @@ If some of those versions are not shown, you can have an indication of where a p
In normal situation, all the versions should be displayed and should be the same. Different patch versions are supported.
#### Reboot button
You can use this button to force a reboot of your panel. This button is available when ESPHome establishes communication with the display.
## Common issues
### ESPHome cannot establish communication to your panel's Nextion display
**Symptoms:** The ESPHome version (and other info) won't be shown in the boot page.
| Possible causes | Suggestions |
@@ -52,6 +65,7 @@ You can use this button to force a reboot of your panel. This button is availabl
| Baud rate mismatch. | Make sure your yaml settings don't have any specific baud rate set or, if a custom baud rate is set, make sure it is one of the supported rates (115200 bps or 921600 bps). |
### Blueprint is not detected
**Symptoms:** The ESPHome version is shown, but not the blueprint version.
| Possible causes | Suggestions |
@@ -61,8 +75,8 @@ You can use this button to force a reboot of your panel. This button is availabl
| Your panel is not selected in the automation. | Open the automation related to your panel and make sure the right device is set on the **NSPanel device** field. |
| Reconnect the Panel's device to Home Assistant. | 1. Go to **Settings** --> **Devices & Services** --> **ESPHome**<br>2. Delete the device<br>3. Restart Home Assistant host<br>4. Go back to **Settings** --> **Devices & Services**<br>5. Click **Add integration**<br>6. Select **ESPHome**<br>7. Enter your panel's hostname or IP address.|
## Additional Tips and Resources
After troubleshooting, if issues persist, consult the [Issues](https://github.com/Blackymas/NSPanel_HA_Blueprint/issues) and feel free to create a new one asking for more personalized assistance.
Please share as much info as possible, like:
@@ -72,4 +86,5 @@ Please share as much info as possible, like:
4. Describe what you have already tried.
## Important note
Remember, these steps are a guideline and might vary slightly based on your specific setup and previously installed system.