issue-triage-workflows[bot]
commented
12 months ago There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
I acknowledge that timezones are hard, especially where they move due to the Earth's tilt and humans wanting more time in the sun when they're awake.
However, not all of the world is on an hour aligned timezone. India Standard time, for example, is UTC+530, South Australia is UTC+930, Newfoundland, Canada is UTC-3.30. Nepal is UTC+545.
The upshot of this is that, Energy in a non-hour aligned timezone is not shown as hour aligned.
I know it's been raised before - https://github.com/home-assistant/frontend/issues/10902 is at least one.
Maybe a straightforward fix is to do the calculations on 15mins boundaries, then sum appropriately for the timezone? This would deal with all current global timezone cases that I am aware of. Doing 30min "slices" would solve all but Nepal, but the Nepalese are nice people and deserve hour alignment too.
What version of Home Assistant Core has the issue?
core-2023.8.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
N/A
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response