Hi team,
I had three questions on the new VRM API node function to adjust consumption forecasts:
-
To change the forecast using the Node Red “Adjust consumption forecast” option, is it necessary to inject all 3 elements (base, hp, ev) for a given offset? When I try injecting only 1 or 2 of these elements, they don’t seem to be “sticking”. Though when injecting all 3, it seems to work fine.
I read somewhere in the code that if you insert all 3, the ‘total’ gets re-calculated but some clarification on this would be helpful. Is the base load shown in VRM simply the calculation ofbase = total - hp - ev? -
After adjusting the forecast, is there a way to retrieve un-adjusted base load? In my example below, for this one hour I adjusted the base load to 2kWh, and the EV load to ~27kWh. I’m a bit surprised to see
vrm_consumption_fcshow the same value asvrm_consumption_fc_adj. When looking at the two EV arrays, the original value is showing in the unadjusted array.
-
When using the Node Red “Adjust consumption forecast” option, if the incoming wires include other parameters in addition to msg.payload being set to
{offset: ...}, I get a successful API response with the full installation stats, but the adjusted values were ignored. This may be user error…
I have a flow that first pulls the VRM DESS “installation stats” (to get the forecasts), which then goes through a function that outputs a newmsg.payloadcontaining the offset object. I had to spin off the call to “Adjust consumption forecast”, to its own “clean” path for the API call to succeed (which returns only a success message, and not the new installation stats).
This is more of an observation than a question…
