Open JvdMaat opened 1 year ago
Hey there @frenck, 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!
(message by CodeOwnersMention)
solaredge documentation solaredge source (message by IssueLinks)
Hi there, FYI, I cam to this thread, because it seems there is the same problem on some other sensors : sensor.solaredge_production_energy sensor.solaredge_solar_power
Same here
Hi, I have the same problem with sensor.solaredge_energy_today
None of the 21 entities created on my solar edge integration have any values and most if not all are disabled on HA.
None of the 21 entities created on my solar edge integration have any values and most if not all are disabled on HA.
I have exactly the same problem. I also don't understand why we don't have to fill in our siteid in Hassio? In the API-manual of SolarEdge it states you need this for your API calls.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Statistics are still not enabled on these entities. Issue is still valid.
Likewise, I only have 2 entities available: sensor.solaredge_current_power and sensor.solaredge_lifetime_energy . The others are not enabled.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Can confirm this still isn't fixed yet.
this isn't a bug, yes they are disabled, and why they would be disabled by default I don't know, however, you can simply (re)enable the disabled entities you require and then start to consume the data from them - see blue toggle widget at bottom of screenshot included below. toggle from disabled to enabled for each of the entities you require to ingest.
1/ select the entity you want to enable
2/ then click on cog item to configure
3/ then toggle widget from disabled to enable and press update
4/ tha sibh deiseil! (scots gaelic!) you can now consume these stats/data in your dashboards, for e.g. your energy maps.
I am trying to get a yearly data for exported power. There is a sensor for yearly energy that was created automatically. The three entities that are hidden are for battery which i don't have. I would like to create a custom sensor to display how much power my solar plant have to produce but i cannot get yearly exported power statistic. If i set the date from 1.12024 to 31.12.2024 in history graph or programmatically on sensor exported energy or sensor produced energy only shows me the statistic for last 10 days. How can i achieve to get yearly export power?
I am trying to get a yearly data for exported power. There is a sensor for yearly energy that was created automatically. The three entities that are hidden are for battery which i don't have. I would like to create a custom sensor to display how much power my solar plant have to produce but i cannot get yearly exported power statistic. If i set the date from 1.12024 to 31.12.2024 in history graph or programmatically on sensor exported energy or sensor produced energy only shows me the statistic for last 10 days. How can i achieve to get yearly export power?
i don't think SolarEdge allow large data drops to come back via their monitoring API, i tried attempted to bring back a years worth and the server told me to go away !
you can play around with it if you haven't already, using
https://monitoringapi.solaredge.com/equipment/< your site id >/< your inverter serial number >/data?startTime=2023-01-01%0000:00:00&endTime=2023-12-31%2359:00:00&api_key=< your API key >
only option might be to grab the excel export from the monitoring UI website in csv format then parse and ingest yourself
I am trying to get a yearly data for exported power. There is a sensor for yearly energy that was created automatically.
The yearly energy sensor does not have long term statistics enabled. (Which is the crux of this issue). It is limited by your recorder's purge_keep_days setting.
However you can look at the lifetime one, and that should get you the data you are looking for. It has some long term statistics so you can look at it for the past year. I use that one to show me a comparison of this month to the same month last year:
The problem
I'm trying to get some YoY graphing on solar production, and while the lifetime energy has longterm statistics, I don't know how to reconciliate that to a monthly basis. The sensor.solaredge_energy_this_month entity doesn't seem to be enabled for long term statistics, which honestly it should. That would allow plotting of the current month against last month, or the same month last year. (Daily energy can already be plotted against recent history without statistics, and has very limited value to compare to values from a year ago).
What version of Home Assistant Core has the issue?
core-2023.5.4
What was the last working version of Home Assistant Core?
N/A
What type of installation are you running?
Home Assistant Container
Integration causing the issue
solaredge
Link to integration documentation on our website
https://www.home-assistant.io/integrations/solaredge
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No logging or diagnostics, as it's just a missing configuration on the solaredge_energy_this_month sensor preventing it from being eligible for long term statistics.