Solar Forecast PV

[binderth (Thomas Binder)]

@weymann

I assume you didn’t have a look into the mentioned readme, right?
There’s no json parsing at all. It’s a one liner to get Power or Energy for any point of time and for any desired duration.

oh. I did read the docs, but this slipped somehow (I shouldn’t always read so fast…).
A binding offering Actions for calculation is a very elegant solution! I guess, that’s really something to consider also for other bindings dealing with loads of identical data - like dynamic pricing like aWATTar, Tibber, …

Just a thought:

        while(startTime.isBefore(sunset) && delta > 0.0) {
                 val energy = solarforecastActions.getEnergy(startTime,startTime.plusMinutes(duration))
                 val actualDelta = kwhNeeded - (energy as Number).doubleValue
                 if(actualDelta < delta ) {
                      bestPickTime = startTime
                      delta = actualDelta
                 }
                 startTime = startTime.plusMinutes(granularity)
        } 

I see this like in many use cases: finding the best hours for Tibber/aWATTar/ENTSO-e/Energi/…
Presently the aWATTar binding offers this as seperate Bestprice Things, others would like to follow suit or streamline the effort as discussed here:

Tibber-Binding: get "Best Price" items like aWATTar-Binding?

While trying to get a hang into this dynamic energy pricing thing, I installed the aWATTar-Binding, as they don’t require a personal API-Key connected with a client status. The aWATTar-Binding already features some functions via Thing/Channel configuration, which come in handy for having your high-volume consumption-devices wait for “cheap” hours. I can define some device and configure the “Best Price” hours for that device: UID: awattar:bestprice:awattar:WhirlpoolLaden label: "aWATTar Bestpr…

Do you see a chance to reuse similar requirements (“Find best time for XX amount of energy and YY amount of duration within ZZ interval”) over multiple bindings?