list indices must be integers or slices, not str

[Mariusthvdb]

getting errors in the log since 2026.1.0bx (I think..)

Deze fout is ontstaan door een aangepaste integratie.

Logger: custom_components.solaredgeoptimizers.coordinator
Bron: custom_components/solaredgeoptimizers/coordinator.py:80
integratie: SolarEdge Optimizers Data (documentatie, problemen)
Eerst voorgekomen: 09:54:52 (5 gebeurtenissen)
Laatst gelogd: 09:57:59

Error in updating updater

and

Deze fout is ontstaan door een aangepaste integratie.

Logger: custom_components.solaredgeoptimizers.coordinator
Bron: custom_components/solaredgeoptimizers/coordinator.py:81
integratie: SolarEdge Optimizers Data (documentatie, problemen)
Eerst voorgekomen: 09:54:52 (5 gebeurtenissen)
Laatst gelogd: 09:57:59

list indices must be integers or slices, not str

could also be because there is a a lot of snow on the Solar panels currently, and we have no production at all?

site is not offline, and the core integration connects just fine

[gjdv]

I'm using the package without Home Assistant and noticed that since yesterday (january 4th was the last day it ran without issues) requestSystemData fails due to the json_object being empty. Today I dug into it and notice that https://monitoringpublic.solaredge.com/solaredge-apigw/api/sites/<siteid>/publicSystemData gives a 404 error. Let's hope it is a temporary issue at SE side, but I'm affraid they removed this endpoint as it is not as intermittent as typically their issues are.

The graphing page in the SE portal does show more recent optimizer data. I glanced at the endpoint used to retrieve the graph data (/services/charts/site/<siteid>/devices-measurements; note: only 1 hour resolution) but unfortunately the authentication seems to be different from the other pages; at least not an easy swap of just the endpoint.

[Mariusthvdb]

that doesnt sound too promising.... might be the end of this then?

I use Bdraco's fork of the CC, which has proper coordinator implementation, but of course uses the same endpoint.

the Statisics option in the core integration is still functional, maybe we can use that to replace the main functionality of the integration, the production per panel/optimizer although we can only show them in the statistics-graph

entity: solaredge:<siteid>_<optimizer>
name: 1.0.9

but these are invalid for a regular entities card, as per design, see https://www.home-assistant.io/integrations/solaredge/#known-limitations

[al090187]

I just came on here to say the same thing. Since about 7am yesterday it has not worked. Glad I'm not the only one.

There were rumours of them allowing the optimiser data to come through the standard Modbus route. I'm not actually sure why they didn't do that anyway 🤷 would save us all hammering their API every 15 minutes.

[dbolte63]

Same here. Just noticed, that there are no values from the panels since evening of Jan 4th and while troubleshooting, I ended up here in this thread. I hope, it's only a temporary issue or a code bug due to changes on SolarEdge's servers 🤔

[sonnstein]

same here!

Logger: homeassistant.components.sensor
Quelle: helpers/entity_platform.py:451
Integration: Sensor (Dokumentation, Probleme)
Erstmals aufgetreten: 10:50:06 (1 Vorkommnis)
Zuletzt protokolliert: 10:50:06

Error while setting up solaredgeoptimizers platform for sensor: list indices must be integers or slices, not str
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/solaredgeoptimizers/sensor.py", line 97, in async_setup_entry
    info = await hass.async_add_executor_job(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        my_api.requestSystemData, optimizer.optimizerId
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.13/site-packages/solaredgeoptimizers/solaredgeoptimizers.py", line 64, in requestSystemData
    raise errortje
  File "/usr/local/lib/python3.13/site-packages/solaredgeoptimizers/solaredgeoptimizers.py", line 56, in requestSystemData
    if json_object["lastMeasurementDate"] == "":
       ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
TypeError: list indices must be integers or slices, not str

[Mariusthvdb]

Of course…

The endpoint has been changed, so it’s breaking for all, no need to add anything further …

Just add your thumb to indicate the amount of users troubled

Unless someone forks this and fixes, we can consider this integration deprecated and non-functional. last update was more than 2.5 years ago?

[al090187]

OK, I saw your mention there of the actual API address, and realised I had set up a public monitoring page years ago. That no longer works either. I have been speaking to "Chetu" on Solaredge support, and apparently I have disabled my public access page, and only my installer can reenable it. They have ignored any mention of the API so far, probably because they are only Tier-1, and have no idea what an API is.

Did anyone else enable their public site before being able to access the numbers? I am just asking my installer now to enable the public page, so I'll let you know shortly if that fixed it.

[Mariusthvdb]

fwiw, and for the time being, I've tried to hack some Optimizer info back using core integration (and its statistics option) and get the statistics into a response_variable, which allows me to create hourly trigger based template sensors:

though not a complete replacement for the CC (it only provides the hourly power) , it can be useful for representing these power readings in other cards than the statistics-graph, which is the only card that can use the statistics as provided by the core Solaredge integration. I now have actual entities, can track those, and do anything with them in any card/integration I'd like.

I didnt yet pursue the SQL integration, which could probably be used also. It requires more study in regard to the syntax and querying the DB....

note, we can not use mean, min, or max statistic options. Even with larger period settings and start_time. We can use the Sum option, but that is meaningless in this context, as it doesnt really sum useful data at all, hence I commented that.

template:
  - triggers:
      - trigger: time_pattern
        minutes: 0
      - trigger: homeassistant
        event: start
      - trigger: event
        event_type: event_template_reloaded

    actions:
      - action: recorder.get_statistics
        response_variable: optimizer_stats
        data:
          start_time: >
            {{now()- timedelta(hours=1)}}
          end_time: '{{now()}}'
          period: hour
          types:
            - state
#             - sum
          statistic_ids:
            # ZW
            - solaredge:<site-id>_257024037 #1.0.8
            - solaredge:<site-id>_257024042 #1.0.3
            etc
            # ZO
            - solaredge:<site-id>_257024040 #1.0.1
            - solaredge:<site-id>_257024034 #1.0.7
            etc
            # Z
            - solaredge:<site-id>_37551358 #1.1.1
            - solaredge:<site-id>_37551360 #1.1.2
            etc
      - variables:
          site: !secret solaredge-site-id

    sensor:

##########################################################################################
# ZW
##########################################################################################
      - name: SolarEdge optimizer 1.0.8
        unique_id: solaredge_optimizer_1.0.8_statistics
        variables:
          panel: 257024037

        <<: &optimizer_config
          unit_of_measurement: W
          device_class: power
          state_class: measurement
          state: >
            {{this.attributes.stats[0].state|round(0) if this.attributes.stats is not none else -1}}
          attributes:
            stats: >
              {{optimizer_stats.statistics.get('solaredge:'~site~'_'~panel)}}
#             site-id: >
#               {{site}}
            panel: >
              {{panel}}
#             sum: >
#               {{stats[0].sum|round(0) if stats|length > 0 else 'Niet beschikbaar'}}
            last_updated: '{{now()}}'

      - name: SolarEdge optimizer 1.0.3
        unique_id: solaredge_optimizer_1.0.3_statistics
        variables:
          panel: 257024042
        <<: *optimizer_config

      - name: SolarEdge optimizer 1.0.2
        unique_id: solaredge_optimizer_1.0.2_statistics
        variables:
          panel: 257024035
        <<: *optimizer_config

      - name: SolarEdge optimizer 1.0.4
        unique_id: solaredge_optimizer_1.0.4_statistics
        variables:
          panel: 257024036
        <<: *optimizer_config

      - name: SolarEdge optimizer 1.0.9
        unique_id: solaredge_optimizer_1.0.9_statistics
        variables:
          panel: 257024039
        <<: *optimizer_config

etcetc

I can at least show my panels again (still nothing produced as covered in Snow.....):

community thread where this is described in more detail https://community.home-assistant.io/t/per-panel-pv-power-energy-visualization-solaredge-optimizer-data/

[gjdv]

See ProudElm/packaging_solaredgeoptimizers#13

[Schlichi83]

Is there anything I can do to help? I can't code ... but I'm willing to test something. Need this to work again :-(

[AndrewTapp]

I've created another post with my fix https://github.com/ProudElm/solaredgeoptimizers/issues/108