v4.1.9
Pre-releasePre-release.
What's Changed
TL>DR:
- Granular dampening to dampen per half hour period by @autoSteve and @isorin
- Dampening applied at forecast fetch and not to forecast history @autoSteve and @isorin
- Retrieve un-dampened forecast values using service call by @autoSteve (thanks @Nilogax)
- Get presently set dampening factors using service call by @autoSteve (thanks @Nilogax)
- Migration of un-dampened forecast to un-dampened cache on startup by @autoSteve
Granular dampening
The only option to set dampening previously was at per-hour increments, and not the half hour forecast periods that Solcast provide to hobbyists. This can now not be a thing, because you can specify a total of 48 dampening values, corresponding to one for every half-hourly forecast period.
Plus, you can now dampen per Solcast site if desired, either hourly or at half-hourly resolution.
Implementation is by way of two methods. Either calling the set dampening service call, or by creating and maintaining a file of dampening factors. (More in the updated readme.)
Dampening at forecast fetch
Previously, dampening when seen was applied to all forecasts, but not saved in a cache for history. It was for display purposes only. Yes, the 730 days of history, today and the up-coming seven days were calculated and shown as dampened with the current values. Yuck. This is no more.
The history of dampened forecasts is now preserved, and only newly fetched forecasts have dampening adjusted for that refreshed data.
At 'day one' there will be no dampening applied to your history, but this will build over time. A nice segue into...
Retrieve un-dampened forecast values
Because history is now dampened as-at the dampening values set at the time, automations might actually need undampened data to calculate future dampening based on past performance. So the 'get forecasts' service call is extended to allow this by specifying undampened: true
.
At upgrade, the past fourteen days of undampened history will be saved, allowing this modified call to be used immediately. Undampened forecasts get saved to a different cache than the dampened forecasts, and are kept at fourteen days of history. Additionally at upgrade, current 'today' and beyond forecasts will be dampened and saved to the dampened history cache, allowing a seamless display transition to this new mode of applying dampening.
Get currently set dampening values
To avoid an automation needing to keep track of dampening set, the current dampening values can be retrieved with a new service call.
Some bug fixes
There have also been some v4.1.8 corner-case bugs fixed that nobody noticed or reported.
Full Changelog: v4.1.8...v4.1.9