Hi there,
I would love to share with you the latest changes that were just added to production VRM:
Hope you enjoy these added functionalities!
Have a great day,
Barbara
Hi @Barbara
What are those “Now” shaded regions mean?
I’ve tried to graph the current and previous month periods (November and December).
Also the battery SOC evolution is displayed in a quite random manner, sometimes without at all.
See second picture, where I lost patience and captured the screen without.
A small visual issue I noticed, which popped up on the last few weeks. On occasion it seems that DESS Energy chart shows an arbitrarily reduced value for the “Now” section. The underlying system still behaves as expected for the given hour (I think). Please see below.
Notice in this chart, at 11am, the “Solar to consumption” and “Grid to battery” bars are quite low. However, when the time was 10am, the 11am plan was displayed with values in-line with preceding 1 hour (e.g., with Grid to Battery planned around 10kWh)
And when we hit 12pm, we can see the system actually behaved as expected at 11am (with Solar to Consumption and Grid to Battery in-line with what was expected).
This isn’t a case where my DESS parameters are incorrect (e.g., charging faster than expected) as we’ve been using DESS for many many months now, and the chart was showing values correctly in the past.
I don’t think this is a change in forecast / plan either, as I’ve observed it many days now.
Thanks!
More interesting looking graphs… Set for year 2024.
First half of the graph year 2024 for production. Then second half, the next year 2025 (!!), but for battery…
Come on…
Hi!
It looks like we had a bit of a bump in database loads, probably due to people running a lot of ‘year recap’ reports this morning after the Christmas holiday. Could you refresh the screen? I tried to reproduce your bug just now and it showed the battery graph at the correct position.
Indeed, not always happens…
But take a look at a few messages above, on Dec. 26. The same strange behavior.
For sure it has to do with database access, but, I believe, something about concurrency.
Probably you want to display as quickly as possible, for a smooth experience, but data doesn’t come always when we want.
Probably this is something related.
Some “back-refresh”…
Hey, we are experiencing some database load issues currently (see: VRM might be slower than usual now - #4 by Barbara ), so let’s pick up debugging your issue once that is resolved, so we know if it happens in normal conditions still.
Hi,
I will forward this to the forecasting team. There recently was a change to “rectify” some things in a 15 minute / hourly data-issue. Without seeing details on your system my quick guess would be: The VRM forecast for the next hour (note that also solar and solar2consumption seems too low) is only considering the first 15 minute quarter to be displayed for the whole hour. And when the hour passed, values are are kind of 4 times what was predicted.
Hours more in the future are fine, because the mentioned change just affects the “current hour”.
What is your systems reporting interval?
Because if you have set that to hourly or something the cause may as well be just “delay”: As the hour goes by, the forecasted value (for the remaining time of the active hour) goes down, while VRM did not yet receive data about actual flows. So, for example at 11:30, the graphs should be made out of 50% forecast values and 50% actual values - where VRM just does not yet see your actual values?
Edit: I can see that on my system as well. Issue seems to be as described: The active hour is lacking actual values, so at x:45, only 25% of the forecasted amount is shown, but not the 75% that already happened. But that seems to be just a “display-issue” of the graph, internal values of the scheduler are fine.
I’ve send you a pn, if you could give me your site ID (the numeric one in the url), that may help to review the exact issues.
Hi @Barbara
Another thing…
When selecting for zoom a graph zone, the graph is also scaling and some of the graph remain obscured. See below.
