v4.2.5

[autoSteve]

What's Changed

New feature

You can now specify hard limit per-API key. Ask the readme for details. (The units have changed from Watts in options to kilowatts, and the existing value is migrated...) Thanks @ChirpyTurnip.

Key issues fixed

Transition to and from daylight time was not being handled correctly, and this has now been corrected.

The total sites tally of kWh expected for a given day was not right when a hard limit was set, which has now been corrected.

If the integration, or Home Assistant, or the whole server itself was restarted just prior to an auto-update then that update would be missed. This is now not the case, as auto-update checks on startup for a missed update and does so if needed.

• Add multi-API key hard limit by @autoSteve
• Proportionally limit site breakdowns by @autoSteve
• Calculate daily site tally correctly based on hard limit by @autoSteve
• Immediate application of dampening to future forecasts by @autoSteve
• Fix daylight time transition issues by @autoSteve
• Fix system health output exception by @autoSteve
• Logging improvements for info situational awareness by @autoSteve
• Auto-update tolerate restart right before scheduled fetch by @autoSteve
• Update Polish translation, with thanks to @erepeo

Full Changelog: v4.2.4...v4.2.5

[autoSteve]

Notifying the usual early-adopting-and-reporting folk about v4.2.5 being released. @dtswk, @EddieSpaghettie, @ffm777, @gcoan, @hwb45, @iainfogg, @isorin, @jeffb1974, @ladaan, @Markyt77, @Nilogax, @Noodleyman, @ProphetOfDoom, @rholligan, @sh00t2kill and @wimdebruyn.

As always, do ping if you would like to be off the list.

Notifying @ChirpyTurnip and @erepeo who contributed. Thanks for your help!

[autoSteve]

Known issues with v4.2.5

Logged updates for tomorrow.

When daylight savings transition occurs, auto-update will calculate forthcoming updates for tomorrow incorrectly. These are only logged for information if the integration is restarted either during the day or after the last auto-update today has occurred. This issue does not impact correct scheduling of auto-update.

Double usage counter reset

It is possible for a forecast update occurring at UTC midnight to cause the usage counter to reset twice. The chances of this are small, but if this issue is encountered then usage will be reset twice, potentially resulting in confusion if the logs are examined. The issue does not impact correct API usage counting, but does result in two file writes.

Both the updates for tomorrow and double reset issues are already fixed, and will be included in a future version.

Restoring from backup

If a restore from backup of Home Assistant occurs when auto-update is enabled, and the time that the backup had been taken preceeds a later forecast update that had occurred then the integration will update the forecast on integration start because it will detect a stale forecast cache.

This is an unusual situation to arise, so it is not planned to alter the integration behaviour. At worst, there will be one instance of API quota exhaustion on update before the next UTC midnight reset of the used count.

A note has been added to the "Troubleshooting FAQ".