Then we come back to the question of how user-friendly such a system would be for a normal user outside our tech bubble. Just look at how many problems the current configuration already causes for newcomers. There are several threads about this in the forum. I’m also not sure if the last factor and the need for accuracy make sense. Even though I pushed the discussion a bit further earlier, I think we should limit ourselves to global factors. I’ll mention a few examples that come to mind spontaneously, without claiming to be exhaustive. And without knowing how far these factors have been taken into account so far. Weeks and holidays, outside temperatures… I think electric heating will increase, and for me, as mentioned above, PV production and price levels. Perhaps others can think of something else. But personally, I find the values from the past 28 days insufficient as a data basis. But all of this is just my personal opinion.
The adjustable forecast is a great addition to VRM (and NodeRED) and works great to give DESS the data (e.g. EV charging) it needs to make good decisions. However, there is one issue I’m running into. It’s not possible to update the forecast for the current hour, not from VRM and not from NodeRED (offset = 0).
This basically means that you face a delay of 1 hour for loads which have less predictable timing. E.g. EV loads can have a significant impact on the DESS planning if it starts charging with 11kW and DESS feels zero import is the best mode based on scheduled load for the current hour.
I understand you cannot change history, but the remaining time of current hour could still be changed. Or maybe allow forecast on quarterly basis so the delay is only 15minutes.
@Barbara Are there any plans in this direction? To allow for ad-hoc adjustments in forecast (and strategy).
I agree, it is quite annoying to wait for one hour as the current hour cannot be changed.
Btw I’m also facing the issue that the forecast of VRM is not that accurate, as we only charge with 10,8 kW at the lowest prices.
It takes already so long, in the beginning it started with 3,2 kW forecast. Now it is moving on to 7 kW or so.
But it should quicker recognize your charging behavior. Maybe good to mention, I am using another brand charging station with a victron meter in between. [set as charging station].
It was sad, Victron doesn’t have a charging station with the MID meter inside, as we get around €0,10 per charged kWh in the Netherlands from the government. (And this is a requirement so that they can give you the money).
Otherwise I would’ve chosen a Victron charger!
George
Also a third party charger here. I push the same baseload forecast (without EV) every midnight via NodeRED. EV forcast is scheduled on demand, accordingly the EV charger is controlled automatically based on VRM forecast via NodeRED.
This works really well with DESS. Issues start when you interrupt this schedule, because there is no way to adjust the current hour.
Hi, that sounds good!
Which charger do you have?
I have the Easee charge max.
can I see your flows in Nodered, I actually want it to behave like a Victron charger, I already have all the data from the charger in the debug in NodeRed.
The only thing is that I’m quite new with NodeRed, and don’t know how to get it working properly…
Thank you in advance!
George
Thanks!
I have found it.