David

> To me these 2 config options seem mutually exclusive: you either replace NaN with 0, or you interpolate NaN values. Cannot do both. > (or if one is applied...

When using MPC, even if you provide your own forecast at runtime, the system needs to fetch some data from Home Assistant to implement the current/now values, see here: https://emhass.readthedocs.io/en/latest/forecasts.html#now-current-values-in-forecasts

Ok I will see what can be done

It could be that we need to apply the efficiency factor before publishing the battery power sensor? It is something we have missed all along the way. In the meantime...

> Also maybe it would be a good idea for user to define the target temp and also add a constant of how much it can go below that for...

> Oh I didn't realise it was a draft. I'll rebase it onto trunk so it can be merged. Great, thanks!

Yes it can be done and could be interesting. It will need some code tweaking to get it done. I will look into it when I have the time

Yes probably something to do better directly in HA. Closing

I just went to the link provided my Mark and saw that he is able to separetly compute PV saving, Battery saving and PV+battery savings. So the missed savings of...

Ok. If you are interested a manual script could also achieve the kind of comparison that you are looking for. For example this script here does just that, compare different...