[Feature request] Support multiple arrays

[FredericMa]

Hi,

First of all; thanks a lot for your awesome work!

I was wondering if it would be possible to support multiple arrays/inverters?
In my case we have one inverter with two strings.
One string of 12 panels with a 45° inclination and a second string of 6 panels with a 15° inclination.
Both do have the the same azimuth but I can imagine that there are people that have even more strings or multiple inverters with different orientations and inclinations.

Thanks!

Greetings,
Frederic

[FredericMa]

Now I think about it, am I supposed to create two config entries in my case?
I was comparing with the Solcast integration which exposes one set of sensors in one config entry, even if you have multiple rooftops configured in the Solcast portal.
Looking at Forecast solar, it also requires you to create multiple config entries for multiple arrays.

On the other hand it can also give incorrect results since it will also assume you have multiple inverters, which is not the case in my setup.
I have a 5 kW inverter and a total of 7.02 kWp so clipping occurs in my setup.

[rany2]

For now, you will need to create two config entries and a template sensor (working examples are in the forum thread) to combine the data but in the future I will add support for it via configuration.yaml.

[ChirpyTurnip]

I second this - I have two inverters with two strings each, pointing in different directions. North + East to one inverter, North + West to a second inverter. Like FredericMa my inverters are 5kW and will clip the solar panel output....

I really need to be able to combine the two strings, then set a maximum to clip the forecast. The forecast though is in the attribute data, rather than the state so it's not easy. What would be ideal is to be able to define the integration to match the real world - that is, specify the inverter limit and efficiency, and then add string definitions (as per the current setup). There's a lot of twin string inverters, but very very few that have more than four strings....and from an integration perspective it probably doesn't make big difference whether a user specifies one or four strings - just forecast for each supplied string and then spit out the sum of each period (or the inverter max, whichever is less).

[iainJersey]

Mind you - I have a 6kw SolarEdge inverter with one string (in the usual sense of the word)
That single string however has 4 distinct ‘segments’ - different roofs different azimuths, different angles, so I currently have them set up as 4 ‘strings’, and use a group sum helper to add them up. Sub optimal, but useable
Can’t wait for one inverter with separate strings (and I have another inverter with two more ‘real strings’

[md-gh]

I'd also be interested In reading forecast relating to two string / 1 inverter.

[PulsarFX]

my take on combining 3 strings into one sensor to get the estimated values using configuration.yaml:

(I created 3 entries in open meteo solar integration)

sensor to get the wattage timeline for today:

  - sensor:
      - name: "solar_today_timeline"
        unique_id: "solar_today_timeline"
        state: "{{ states('sensor.all_solar_prognose_now') }}"
        unit_of_measurement: "W"
        device_class: power
        attributes:
        #like '2025-06-02T06:15:00+02:00': 104
            watts: >-
              {% set listA = state_attr('sensor.energy_production_today', 'watts') %}
              {% set listB = state_attr('sensor.energy_production_today_2', 'watts') %}
              {% set listC = state_attr('sensor.energy_production_today_3', 'watts') %}
              {% set result = namespace(watts={}) %}
              {% for s in listA %}
                {% set a = listA[s]|int %}
                {% set b = listB[s]|int %}
                {% set c = listC[s]|int %}
                {% set result.watts = result.watts | combine({s: (a+b+c) }) %}
              {% endfor %}
              {{result.watts}}

this can be used in apex charts like this (gray line):

  - entity: sensor.solar_today_timeline
    name: Prognose
    data_generator: |
      return Object.entries(entity.attributes.watts).map(
        ([key, value]) => [new Date(key).getTime(), value]
      );
    type: line
    extend_to: end

here is the template sensor to combine the estimation for 7 days into one sensor from 3 strings:

  - sensor:
      - name: "solar_forecast_timeline"
        unique_id: "solar_forecast_timeline"
        state: "{{ states('sensor.all_solar_prognose_today') }}"
        unit_of_measurement: "kWh"
        device_class: energy
        attributes:
            day_1: "{{ states('sensor.all_solar_prognose_d2') }}"
            day_2: "{{ states('sensor.all_solar_prognose_d3') }}"
            day_3: "{{ states('sensor.all_solar_prognose_d4') }}"
            day_4: "{{ states('sensor.all_solar_prognose_d5') }}"
            day_5: "{{ states('sensor.all_solar_prognose_d6') }}"
            day_6: "{{ states('sensor.all_solar_prognose_d7') }}"

can be used in apex charts like this (yellow bars):

  - entity: sensor.solar_forecast_timeline
    name: PV
    type: column
    color: "#FFBF00"
    show:
      datalabels: true
    data_generator: |
      return [
          [moment().add(0, 'days'), entity.state],
          [moment().add(1, 'days'), entity.attributes.day_1],
          [moment().add(2, 'days'), entity.attributes.day_2],
          [moment().add(3, 'days'), entity.attributes.day_3],
          [moment().add(4, 'days'), entity.attributes.day_4],
          [moment().add(5, 'days'), entity.attributes.day_5],
          [moment().add(6, 'days'), entity.attributes.day_6]
        ]

to get the all sensors, I used helpers in HA to sum them up from open meteo solar sensors.
The template sensor in config file is needed, as there is currently no way to treat attributes via helper templates.

Lots of work - a combination from the integration would be nice to have ;)