Hi,
I might have found a bug in the VRM, where the automatically calculated timespan is invalid.
I started with ‘previous month’ and navigated back some months. The result is:
Best regards
Are we both wrong? Are we the only users facing this issue?
Best regards
Perhaps add the bug report tag and maybe @Barbara or one of her collegues will see it.
It happens when you pass over February
Yes, we recognized that too.
Same here on some situation…
Somehow the system “rounds up or down” the start time, making it miss even an entire hour…
Example:
Set “Last 3 hours” - it says “Last 3 hours”
Now press the “before” button, the one with “<” in front of the time interval.
It shows only the previous 2 hours and some, not 3 hours…
The same with 6 hours, 12 hours, etc.
Not to mention that the start of the interval is rounded.
Initial
Previous 2 hours and 5 minutes… NOT 3 hours.
It should be from 18:05, not from 19:00
The same further…
It should be from 15:05, not from 16:00
So the interval between 18:05 and 19:00 is never plotted in this situation… Almost an hour.
Or from 15:05 and 16:00…
And so on and so forth…
Seen it long before together with many others, but because of various reasons, lost the drive to report bugs…
Dear all,
Apologies for the late response, but the VRM team is picking this up.
Hi @alexpescaru , @Xela , @lxonline , @Buzzy @koni ,
An adjustment of how we count ‘last x hours’ is now on beta. Now it won’t round the whole hours, but for instance from 9:20, last 3 hours will go from 6:20 to 9:20.
Would appreciate your feedback on this before we move forward to putting this live.
Very happy, with the last x hours.
Appreciate that the last month skip backwards and forwards is more complex as the different month lengths are not regular.
All modern programming languages (mostly the managed ones used by today programmers) have functions for computing this…
Hi @Barbara - I did some testing this morning, and again a few minutes ago. This seems to be working nicely now. No surprises. No obvious problems.
I tested some unusual time ranges, checked totals, and stepped through time, and got expected results except for the following:
When I selected Last 3 hours, at 18:57EDT, it gave me almost 4 hours worth. Is this as expected?
It looks like it is giving 3hrs 45min. I was expecting it to give me the most recent 3 hrs worth of reported data
Is this expected ? The good news is the totals are correct for what is shown, and there are no identifiable gaps or problems observed.
(EDIT: The above has always bothered me, not just with last 3 hours, but with other intervals, where it always seems to show almost +1 extra block).
Yesterday and this morning I saw a problem where the [>] arrow failed to move forward in time, but it is working now. (20:00 UTC). If it happens again, I’ll document exact steps to reproduce the issue.
Hi @Amirreza - I did some quick testing and it appear the ranges are behaving as expected. The intervals appear correct.
I have not validated the math yet - not enough sunshine. Thanks for your help on this.
Hopefully some other people can do some tests to validate.
A bit later today, the math at the bottom works with rounding, so I’m happy about that.
Am curious why there are no consumption/solar bars yet in the last position at right - but the battery is there.
I checked again a couple minutes later, and still no consumption/solar data. Will check again in a few minutes in case there was some kind of outage.
It showed up at about 12:20, so I guess it’s just a system lag.
Hi all, these changes have just been rolled out to production VRM.
Thank you for thinking along!