From dae6b85c716afff05d28f1323cd8c01f1f8f1d7b Mon Sep 17 00:00:00 2001
From: danw87 <123868814+danw87@users.noreply.github.com>
Date: Mon, 30 Jan 2023 21:54:38 +0000
Subject: [PATCH] Created (EN) Common Issues | AccuWeather Setup / Blank
weather pages (markdown)
---
...AccuWeather-Setup---Blank-weather-pages.md | 27 +++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 (EN)-Common-Issues-|-AccuWeather-Setup---Blank-weather-pages.md
diff --git a/(EN)-Common-Issues-|-AccuWeather-Setup---Blank-weather-pages.md b/(EN)-Common-Issues-|-AccuWeather-Setup---Blank-weather-pages.md
new file mode 100644
index 0000000..1ec352f
--- /dev/null
+++ b/(EN)-Common-Issues-|-AccuWeather-Setup---Blank-weather-pages.md
@@ -0,0 +1,27 @@
+## Expected configuration
+
+#### In Home Assistant Automation
+The integration should be Accuweather and you weather entity selected
+
+
+
+#### Enable Accuweather forcasts
+
+
+
+#### Confirm source in Developer Tools States
+In developer tools the weather entity should have the attribute 'attribution: Data provided by AccuWeather'
+
+
+
+
+
+## If you are still having issues
+Its likely you weather integrations are clashing. 1 method we have found to resolve this is to delete ALL weather integrations and just re add Accuweather - Be aware you will lose your existing weather integrations and any associated data / entities.
+
+#### 1. Delete the Standard and AccuWeather integrations
+
+#### 2. Add Accuweather & Enable forcasts
+
+#### 3. Set the Weather entity in the Automation
+