Solaredge intergation not working
The problem
Since today morning 10am the solar edge integration is not working anymore. All entities are down. New start neither integration nor Home Assistant helps.
What version of Home Assistant Core has the issue?
2025.6.3
What was the last working version of Home Assistant Core?
2025.6.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Solaredge
Link to integration documentation on our website
https://www.home-assistant.io/integrations/solaredge
Diagnostics information
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
Hey there @frenck, @bdraco, mind taking a look at this issue as it has been labeled with an integration (solaredge) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of solaredge can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleRenames the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign solaredgeRemoves the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
solaredge documentation solaredge source (message by IssueLinks)
I can confirm that it's down here too (UK) with HAOS core 2025.7.2.
Hey together,
I suspect this is caused by a change performed on the end of SolarEdge. They took down the admin section of monitoring.solaredge.com (words from the supporting agent: "it's phased out"). You now have to request your API key via support 🫤
edit: spelling mistake
That would mean they not only took that section down, they also invalidated all existing API keys. Or something else changed that doesn't allow the integration to work anymore.
Sure hope it doesn't mean getting a new API key cause the integration doesn't allow you to change your key. Don't really want to remove and re-add the device and potentially lose all my data.
Mine has now sprung to life again, so I suspect that it was just maintenance/fault at Solaredge.
Can confirm, mine started working again too.
Mine started working too 👍
Yes, working again. Thanks.
Mine working fine again, down between 09:30 and 12:10 NL time
Mmmm, I've woken up this morning to find that it's down again. Anyone else?
Mine has been down since approx 06:30 this morning. Getting the ”could not retrieve details from solaredge api” error message in HA logs. 🤦🏻
Mine is down too.
But iOS Solaredge App and tibber power up are working fine
Same here - such a shame it's not possible to have an easy local solution.
Oh, how can we rise a ticket to solaredge, as a lot of EMS working with this data?
And strange again, Tibber power-ups is still working.
Mine has been down since approx 06:30 this morning. Getting the ”could not retrieve details from solaredge api” error message in HA logs. 🤦🏻
![]()
I have the same issue. Tried to contact solaredge support, but I'm not able to create a case, as the bot goes into a loop and cannot verify my serial number. But I guess it's the same as stated above, that they changed the API url.
En insistant et les menaçants de couper moi aussi l'onduleur du réseau, ils m'ont données une autre clé API.
J'ai supprimé l'adon puis remis, mais mes capteurs sont toujours indisponibles malgré un mail que j'ai reçu m'accordant full access.
Exactly same issue here... but a small sign of life back around 6:34:30 AM central european summer time (GMT +2) today.
I have opened a case at SolarEdge via their website / chat.
I also have a 'self-installer' account and I have the possibility to enable/disable API-access / regenerate a API key if needed.
Mine was also down this morning, but after restart of integration it's working again. Let's see how long, It's definately not stable. For gridpower I use the Solaredge modbus integration, which is not dependend on any API or Cloud. For solar power it's also possible, but the result has a changing factor dependend on the power. So it's a bit more complicated to get reasonable results.
Hey together,
I suspect this is caused by a change performed on the end of SolarEdge. They took down the admin section of monitoring.solaredge.com (words from the supporting agent: "it's phased out"). You now have to request your API key via support 🫤
edit: spelling mistake
just checked and admin is still available in my account. Can also see the API and generate a new API. (did not do, no need to do). I have an installer account so maybe that is different.
With a new api key it is working for me. For my parents not. It is complaining about "Ignoring invalid energy value 1050864.0 for lifeTimeData"
Cela signifierait qu’ils ont non seulement supprimé cette section, mais qu’ils ont également invalidé toutes les clés API existantes. Ou quelque chose d’autre a changé qui ne permet plus à l’intégration de fonctionner.
J’espère que cela ne signifie pas obtenir une nouvelle clé API, car l’intégration ne vous permet pas de modifier votre clé. Je ne veux pas vraiment supprimer et rajouter l’appareil et potentiellement perdre toutes mes données.
Moi, je n'ai rien perdu, car c'est le même ID !
It just started working again for me.
@mauerwinkel, I have also modus but I didn't set up this in the energy grid. Wich entitie did you set up for tracking solar production in the energy grid?
I suspect this is caused by a change performed on the end of SolarEdge. They took down the admin section of monitoring.solaredge.com (words from the supporting agent: "it's phased out"). You now have to request your API key via support
Do you think it helps to ask for new ID and API-Key?
@mauerwinkel, I have also modus but I didn't set up this in the energy grid. Wich entitie did you set up for tracking solar production in the energy grid?
This needs to configured directly in configuration.yaml, here is an example:
modbus: -name: solaredge type: tcp host: 192.168.178.68 (put your adress of solaredge inverter here) port: 502 sensors: - name: se_solar_power unit_of_measurement: W address: 40083 (adress can be different for different inverters, see manual) data_type: int16 scale: 0.1 scan_interval: 60 slave: 1 - name: se_grid_power unit_of_measurement: W address: 40206 (adress can be different for different inverters, see manual) data_type: int16 scale: 1 scan_interval: 60 slave: 1
@mauerwinkel @LuXc-NL I had the same problem, for the API. Then I contacted SolarEdge via the chat on the website and they give me the API key as requested by me. Took me 5 minutes.
Yesterday morning (Tue 22), the SolarEdge integration also didn't work for me; last reading was from Mon 21 around sunset. But, like for OcinO88, since later in the morning (Tue 22) at 10.30 I'm getting data again. I didn't change anything in the config. It all seems to be working stably now.
Here in Italy it doesn't work anymore, they changed the policies, now only the installers' ones work, but when you try to configure it again with the right keys you can't connect.
It also restored to normal without any change of keys at 22 july 10:34 AM (CET) (again, I have a 'self-installer' account).
edit: spelling mistake