Describe the bug
It looks like the api node requests an additional hour if you try to fetch (forecast) data. With other data the same will probably happens, but then the api endpoint simply has no data to return, so this is less of an issue.
To Reproduce
With the following settings:
The following request is send to the vrm api:
stats?type=custom&attributeCodes[]=solar_yield_forecast&interval=hours&start=1731315600&end=1731405599
But this returns and array with 25 items.
The timestamps send also request this:
(1731405599-1731315600)/3600 = 24h 59m
Expected behavior
24h of data, not including the same hour the next day.
Describe the bug It looks like the api node requests an additional hour if you try to fetch (forecast) data. With other data the same will probably happens, but then the api endpoint simply has no data to return, so this is less of an issue.
To Reproduce With the following settings:
The following request is send to the vrm api:
stats?type=custom&attributeCodes[]=solar_yield_forecast&interval=hours&start=1731315600&end=1731405599But this returns and array with 25 items.
The timestamps send also request this: (1731405599-1731315600)/3600 = 24h 59m
Expected behavior 24h of data, not including the same hour the next day.