Example HEMS upload only consumption/production data until forecast date

[luckv]

When I setup the HEMS example, I noticed that the simulation made forecasts of time frames for data already uploaded.

This makes the graphs so cluggy that is not possible to read correctly the data.
To make the situation more real, I thought to remove in the data uploaded from consumption and production sensors, the records relative to timestamps happened before the value of FORECASTING_START.

Before:

After:

[luckv]

@nhoening i fixed the pre commit hooks. I didn´t read the contribution guidelines, I'm sorry.

[BelhsanHmida]

@luckv Thanks for the PR. I’m taking a closer look at how this interacts with the HEMS flow. I’ll get back to you with feedback soon.

[nhoening]

@BelhsanHmida I believe you forgot about giving feedback here.

[BelhsanHmida]

@BelhsanHmida I believe you forgot about giving feedback here.

@nhoening Yes, you’re right. Sorry, I forgot to follow up here. It completely slipped my mind.

I’ll give final review and feedback when I’m back by the end of the week.

Thanks for the reminder.

[BelhsanHmida]

Sorry for taking so long to review this.

I tested the HEMS dashboard output against main. The PR improves the visual story by hiding future measured values, but it appears to break the self-consumption KPI: main reports 87.15% average self-consumption for My Home 1, while this branch reports 0%.

It looks like electricity-production is filtered after FORECASTING_START, but the self-consumption reporter still uses that same sensor during the reporting window. Could you either keep the production data needed by the reporter, or update the reporting flow to use the intended forecast/scheduled PV data?

Also, I think site-power-capacity should not be filtered. It is capacity/config data, not forecasted measured data.