Timeseries Array (Tibber prices) have double entries with getAllStatesBetween?

[rlkoshak (Rich Koshak)]

@binderth

Ah. Ok. That’s new for me. But still I think we’re facing two different scenarios then.

1. the same Item is used for forecasts and present and historic states.
2. the Item solely predicts states and measured states are done by a different Item (and mostly also different binding)

They are not so different though.

In scenario 1 the Item gets updated by the actual measurement at some point by the binding. That value gets saved to persistence and the predicted value gets removed.

In scenario 2, the Item gets updated by what ever updates the Item from persistence when the time comes for that entry to become the current state of the Item. Again, that “new” value gets saved to persistence and the predicted value gets removed.

It’s the same action. The only difference is where the update comes from. But whatever mechanism manages this shouldn’t care where the update comes from. It probably couldn’t even know if it wanted to.

But the fact that you have three entries sometimes makes me thing something else is going on.

@Mherwege

Can you create an issue for this in core? I think it should be possible to avoid this. It looks like when setting the current state from the forecast, it doesn’t consider the time and restores with current time.

I was going to suggest the same. I think core is not handling this correctly, but I’m still not 100% certain what’s causing the behavior.

@binderth

is this then for “persistence” or “timeseries”? or does it matter?

Really, it’s for what ever mechanism updates the Item from the timeseries. It needs to either prevent that update from being saved, or, as I suggested, remove the predicted value prior to updating the Item. Then the update will replace the predicted value through the usual mechanisms according to the persistence strategy.

It occurs to me you can work around this right now by changing the persistence strategy to not save on everyChange. Then the database will only contain those predicted values because the updates won’t get saved as duplicate records.