Skip to content

Commit d911596

Browse files
artspbjunie-agentfdmarcin
authored
Update Forecast.Solar documentation for multi-plane support (#44464)
Co-authored-by: Junie <junie@jetbrains.com> Co-authored-by: Marcin Sędłak-Jakubowski <fdmarcin@gmail.com>
1 parent 80eb09f commit d911596

1 file changed

Lines changed: 20 additions & 6 deletions

File tree

source/_integrations/forecast_solar.markdown

Lines changed: 20 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ As an example automation idea, you could determine if:
3737
Forecast.Solar relies on data provided by the [EU Photovoltaic geographical information system](https://re.jrc.ec.europa.eu/pvg_tools/en/tools.html) and your solar panels must be in a location that is covered by this tool. Data is available for almost the entire world.
3838

3939
To use the Forecast.Solar integration, it will need some information about your
40-
solar panel system: **latitude**, **longitude**, **declination**, **azimuth**
41-
and **total modules power**.
40+
solar panel system, such as **latitude**, **longitude**, and details about your
41+
solar planes, such as **declination**, **azimuth**, and **total modules power**.
4242

4343
It needs the specific location (defined by **latitude** and **longitude**),
4444
which by default is taken from your Home Assistant configured "home" location.
@@ -62,7 +62,20 @@ value.
6262

6363
{% include integrations/config_flow.md %}
6464

65-
If you have more than one plane of solar modules with different properties (e.g. several sides of the roof on different strings or on different buildings, with different directions or declinations) you can add the integration multiple times setting parameters accordingly. You can then use [template sensors](/integrations/template/) to combine the data, e.g. adding up production on different planes into one value to base your planning on.
65+
### Adding multiple solar planes
66+
67+
If your solar setup has multiple planes (for example, an east-west setup),
68+
you can add these as separate planes within the same integration instance.
69+
This requires a [paid Forecast.Solar plan](#using-your-forecastsolar-account),
70+
which allows you to configure up to 4 solar planes.
71+
72+
The integration automatically combines the data from all configured planes into
73+
a single set of sensors, taking into account your inverter's maximum power if specified.
74+
75+
To add a solar plane:
76+
77+
1. Go to {% my integrations title="**Settings** > **Devices & services**" %} and select **Forecast.Solar**.
78+
2. Select **Add solar plane**.
6679

6780
## Sensors
6881

@@ -93,11 +106,12 @@ default. Enable those entities in the user interface if you like to use these:
93106

94107
The [Forecast.Solar](https://forecast.solar/) public plan can be used for free, but
95108
the resolution of the data used is more limited and thus, there are less
96-
details for this integration to work with.
109+
details for this integration to work with. Also, only a single plane can be configured.
97110

98111
If you like the Forecast.Solar service, or are interested in more frequent data
99-
updates (based on a higher data resolution), you could [sign up for one
100-
of their plans](https://doc.forecast.solar/doku.php?id=account_models#compare_plans).
112+
updates (based on a higher data resolution) or multiple solar planes, you could
113+
[sign up for one of their plans](https://doc.forecast.solar/doku.php?id=account_models#compare_plans).
114+
The Personal Plus tier and above allow you to configure up to 4 solar planes within the same integration instance.
101115

102116
To enable the use of the API key with this integration, go to {% my integrations %}.
103117
Select the Forecast.Solar integration, then select **Configure**. Enter the

0 commit comments

Comments
 (0)