From a97ee1a1a8d5581fbab72ede37959d08d8645f9d Mon Sep 17 00:00:00 2001
From: Edward Firmo <94725493+edwardtfn@users.noreply.github.com>
Date: Thu, 11 Jan 2024 18:31:52 +0100
Subject: [PATCH] Updated (EN) Common Issues Stuck on Initializing (markdown)
---
(EN)-Common-Issues-Stuck-on-Initializing.md | 30 +--------------------
1 file changed, 1 insertion(+), 29 deletions(-)
diff --git a/(EN)-Common-Issues-Stuck-on-Initializing.md b/(EN)-Common-Issues-Stuck-on-Initializing.md
index d054690..79358da 100644
--- a/(EN)-Common-Issues-Stuck-on-Initializing.md
+++ b/(EN)-Common-Issues-Stuck-on-Initializing.md
@@ -1,29 +1 @@
-A number of different things needs to be setup, if they are either not setup or setup incorrectly the NSPanel will stay on Initializing.
-
-
-
-#### 1. Flashed ESPHome
-Make sure you have installed the ESPHome config onto the NSPanel
-
-
-#### 2. ESPHome Name
-The device_name in ESPHome must only use lowercase letters, numbers or underscore (\_). If you use hyphens (-) then it will 100% not work.
-
-
-
-#### 3. NSPanel added to Home Assistant
-You must add the ESPHome integration in Home Assistant for each NSPanel
-
-
-
-#### 4. Blueprint installed and Automation deployed
-Make sure the blueprint is installed.
- [](https://my.home-assistant.io/redirect/blueprint_import/?blueprint_url=https%3A%2F%2Fgithub.com%2FBlackymas%2FNSPanel_HA_Blueprint%2Fblob%2Fmain%2Fnspanel_blueprint.yaml)
-
-
-Make sure you have created an automation for the NSPanel and that the **ESP Node Name** matches the name from ESPHome exactly
-
-
-
-
-Once these steps are complete the display should connect after a short delay
\ No newline at end of file
+This page was moved: https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/main/docs/error_initializing.md
\ No newline at end of file