Skip to content

Support point forecasts in external sensor schema v2 - #75

Draft
InventoCasa wants to merge 1 commit into
feat/price-forecast-sensorfrom
feat/price-forecast-points
Draft

InventoCasa wants to merge 1 commit into
feat/price-forecast-sensorfrom
feat/price-forecast-points

Conversation

@InventoCasa

Copy link
Copy Markdown
Owner

The external forecast sensor currently requires numeric lower and upper bounds, so a producer cannot supply a point estimate without inventing an uncertainty band. Schema version 2 accepts explicit lower: null and upper: null together and requires a bounded source label on each interval. Numeric bands remain supported; version 1 retains its existing validation and output format.

This extends #74 and targets its feature branch, so the diff contains only the version 2 addition. Forecasts remain diagnostic; the existing freshness, interval coverage and control restrictions apply to both versions. English and German documentation are synchronized.

Validation:

  • 1380 tests passed on each pinned Home Assistant stack (2025.8 / Python 3.13 and 2026.8 / Python 3.14).
  • Added regression coverage for explicit point bounds, mixed bounded/point intervals, source validation, v1 compatibility and diagnostic-only ingestion.
  • Public tree, commit-range and component-package checks passed.

@oocube

oocube commented Nov 7, 2026

Copy link
Copy Markdown

Just out of curiosity: What happens if you introduce helpers that calculate 90% and 11% of the point estimate? How does PV Excess control behave?
Advantage: You control the margin of certainty and can use even different values for min and max.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants