Closed MelleD closed 3 weeks ago
I guess currently you're using a sum helper, unfortunately there's no easy way to do this from this integration.
I guess currently you're using a sum helper, unfortunately there's no easy way to do this from this integration.
Currently i just create a template sensor and add it.
- name: "energy_production_today_all"
state: >
{{ (states('sensor.energy_production_today') | float(default=0) + states('sensor.energy_production_today_2') | float(default=0)) | round(2) }}
unit_of_measurement: "kWh"
device_class: energy
But für the date (e.g. peak time) I have no good idea
Unfortunately، this is a very difficult problem to solve and will need to be handled by the library not the integration.
Unfortunately، this is a very difficult problem to solve and will need to be handled by the library not the integration.
You mean the aggregation over all or just the peak time?
Off course I can open a ticket there. Do you know where is the best place? :)
Heh, it's also my library: https://github.com/rany2/open-meteo-solar-forecast/issues
Heh, it's also my library: https://github.com/rany2/open-meteo-solar-forecast/issues
Ah ok I thought you mean something different. Ok then I move the ticket later ;)
Done :)
If you have different directions, it would help enormously if there were sensors that aggregate the direction to make it easier to continue working with it, e.g. forecast next 30 minutes, power forecast etc.