@Mariusthvdb, I could try to add an additional timeout to the requests but I’m not sure that’ll help (plus this would be better in the library it’s using). Maybe try the current release (link) which does not have the site/inventory details. At least we can exclude if it has something to do with the latest version.
sure, will do later on, have to walk the dogs first. 10km per day (next to HA experimenting) keeps the doctor away ;=)
For this the component (at least the custom component I guess you added) is using something like https://monitoringapi.solaredge.com/site/[YOUR_SITE_ID]/inventory?api_key=[YOUR_API_KEY].
Since there can be more inverters I did not want to restrict to only one inverter as an sensor entity. Instead the sensor entity state for the inverters will show the number of inverters (1 in my case - see figure below).
All inverters (and their properties) are then available as an attribute. You can for example do something like this:
{{states.sensor.solaredge_inventory_inverters.attributes.inverters[0].name}}
With the new update this will be included and provides an overview like this:
Thanks, very helpful!
Anyone who also has a battery/storage?
{“siteCurrentPowerFlow”:{“updateRefreshRate”:3,“unit”:“kW”,“connections”:[{“from”:“LOAD”,“to”:“Grid”},{“from”:“PV”,“to”:“Load”}],“GRID”:{“status”:“Active”,“currentPower”:0.28},“LOAD”:{“status”:“Active”,“currentPower”:1.92},“PV”:{“status”:“Active”,“currentPower”:2.2}}}
and reverse:
{“siteCurrentPowerFlow”:{“updateRefreshRate”:3,“unit”:“kW”,“connections”:[{“from”:“PV”,“to”:“Load”},{“from”:“GRID”,“to”:“Load”}],“GRID”:{“status”:“Active”,“currentPower”:0.94},“LOAD”:{“status”:“Active”,“currentPower”:3.13},“PV”:{“status”:“Active”,“currentPower”:2.19}}}
I think we all are seeking something like this:
and of course, other than accessing the application, I would like to ask to google home “how much power do I have left”… of course it is not instantaneous but it gives you an idea about how much you are loading and how much you have left 
this is what Used for Site details:
se_site_details_resource: https://monitoringapi.solaredge.com/site/ID/details?api_key=KEY
and:
- platform: jsonrest
resource: !secret se_site_details_resource
method: GET
name: SolarEdge Site Details
scan_interval: 3600
the inventory was:
se_inventory_resource: https://monitoringapi.solaredge.com/site/ID/inventory?api_key=KEY
and
- platform: jsonrest
resource: !secret se_inventory_resource
method: GET
name: SolarEdge Inventory
scan_interval: 3600
never thought about people having more than 1 inverter… so I have 1 going up to 7K and that would be rather a large installation, but I guess for sunnier countries, it would be easier to top that 
we are in the Low Countries.
believe @CCOSTAN might be able to help you out here? He has rather an impressive installation and Ha setup
Hiya, can confirm we’re talking about the same api calls to SE. I see you’re also only updating every few hours for the equipment and site details.
Moreover, I might have an idea about the SE/Hue issue. Once in a while the api call to SE takes a while and you’ll see a log message like this:
WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.solaredge_last_month_data is taking over 10 seconds
Some other components report similar warnings hence I never paid attention to it, plus HA seems to be handling the issue internally. However, I was thinking this might have an effect on the Hue component (which unfortunately I cannot test). Are you able to confirm whether the issues you are having arise after a similar warning?
Nice thank you, I think I have most cases now. Do you also have an example when no electricity is generated?
Of course:
`{"siteCurrentPowerFlow":{"updateRefreshRate":3,"unit":"kW","connections":[{"from":"GRID","to":"Load"}],"GRID":{"status":"Active","currentPower":0.78},"LOAD":{"status":"Active","currentPower":0.78},"PV":{"status":"Idle","currentPower":0.0}}}`
I think it’s really important to know current load to know how much juice left…
Hiya, based on the data from @divirg and @wmaker I have been working on adding the power flow to the SolarEdge component. I split the data into two groups, producers and consumers and assume that total consumer power - total producer power = 0. For the consumers and producers I’ve made the following new sensors.
Consumers
-
solaredge_power_consumption(i.e. LOAD)
Producers
-
solaredge_solar_power(i.e. PV) -
solaredge_grid_power(i.e. GRID) -
solaredge_storage_power(i.e. STORAGE)
The states of these sensors will contain the currentPower.
For the solaredge_power_consumption and the solaredge_solar_power sensors the states will always be a positive number (I assumed you cannot consume or produce a negative amount of energy).
For the solaredge_grid_power and solaredge_storage_power sensors this can be a positive or negative number. For solaredge_grid_power this shows the difference between importing and exporting energy and for solaredge_storage_power whether it’s discharging or charging.
For example, using the following input, will result in the image below.
{“siteCurrentPowerFlow”:{“updateRefreshRate”:3,“unit”:“kW”,“connections”:[{“from”:“LOAD”,“to”:“Grid”},{“from”:“PV”,“to”:“Load”}],“GRID”:{“status”:“Active”,“currentPower”:0.28},“LOAD”:{“status”:“Active”,“currentPower”:1.92},“PV”:{“status”:“Active”,“currentPower”:2.2}}}
Love to hear your feedback and once my other changes have been accepted I will include these as well.
2 Likes
Sounds good to me, if it helps I can grant access to my inverter API KEY.
Looks good to me too.
Hi @divirg, that’ll be great to properly test the new sensors. Could you send me the details in a private message?
Done. Let me know if you have got them.
Got it, thanks! Seems to be working with real-time data, will try to include it in the next HA update.
If you could, I would also add monthly production. Every PV system as a target monthly production and I use to ask Google Home how much we have produced this month. That would be great… At least for me
Hi @divirg, the component does have an “energy_this_month” state which comes from the site overview api endpoint. Would this be the same or are you looking for something else?