From 52a4941c9190a527058dc98037ea25b64973d411 Mon Sep 17 00:00:00 2001 From: danw87 <123868814+danw87@users.noreply.github.com> Date: Mon, 30 Jan 2023 21:45:02 +0000 Subject: [PATCH] Updated (EN) Common Issues | Stuck on Initializing (markdown) --- (EN)-Common-Issues-|-Stuck-on-Initializing.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/(EN)-Common-Issues-|-Stuck-on-Initializing.md b/(EN)-Common-Issues-|-Stuck-on-Initializing.md index ac87789..d054690 100644 --- a/(EN)-Common-Issues-|-Stuck-on-Initializing.md +++ b/(EN)-Common-Issues-|-Stuck-on-Initializing.md @@ -17,5 +17,13 @@ You must add the ESPHome integration in Home Assistant for each NSPanel
#### 4. Blueprint installed and Automation deployed +Make sure the blueprint is installed.
+ [![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)
![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) + +


+ +Once these steps are complete the display should connect after a short delay \ No newline at end of file