h3n3/NSPanel_HA_Blueprint
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated (EN) Common Issues | Stuck on Initializing (markdown)

danw87
2023-01-30 21:45:02 +00:00
parent 1f27557588
commit 52a4941c91
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
(EN)-Common-Issues-|-Stuck-on-Initializing.md

@@ -17,5 +17,13 @@ You must add the ESPHome integration in Home Assistant for each NSPanel
<br> <br>
#### 4. Blueprint installed and Automation deployed #### 4. Blueprint installed and Automation deployed
Make sure the blueprint is installed.<br>
[![Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.](https://my.home-assistant.io/badges/blueprint_import.svg)](https://my.home-assistant.io/redirect/blueprint_import/?blueprint_url=https%3A%2F%2Fgithub.com%2FBlackymas%2FNSPanel_HA_Blueprint%2Fblob%2Fmain%2Fnspanel_blueprint.yaml)<br>
![Screenshot 2023-01-30 213511](https://user-images.githubusercontent.com/123868814/215600277-4c66bc36-91d5-40c9-9d81-21bd8be4b114.png) ![Screenshot 2023-01-30 213511](https://user-images.githubusercontent.com/123868814/215600277-4c66bc36-91d5-40c9-9d81-21bd8be4b114.png)
Make sure you have created an automation for the NSPanel and that the **ESP Node Name** matches the name from ESPHome exactly
![Screenshot 2023-01-30 214156](https://user-images.githubusercontent.com/123868814/215601843-bb5c31f7-6827-4c95-ac01-6b94e6dfdff4.png)
<br><br><br>
Once these steps are complete the display should connect after a short delay