-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time-zone issue with "total load" #97
Comments
This is known about, unfortunately the devs seem pretty stubborn about total load being able to be calculated by the end user, not them. |
I have the same issue except its for all my stats [Solar Production, Solar to Grid, Usage, all of it]. I'm in GMT +10 and my stats don't reset each day till then. Which then screws up all my dashboards |
Are you on the newest version of the HACS add-on (4.8)? this should of been fixed |
Haven't gotten back to looking at this till recently. Currently just living with it as is. will try and spend a bit more time digging around this weekend as its still annoying me |
What version are you on? i dont have this issue anymore. try updating 0.5.5 |
Unfortunately updating to 0.5.5 hasn't resolved it for me. Unless there's something else I need to do as well? |
Hmm interesting, wonder if your inverter is thinking its on a different timezone? total_load comes from the getSumDataForCustomer call in the OpenAPI, which doesnt take in any parameters (eg any date from the integration) what inverter you got? and do you know any way to check it is in the same timezone as you are in? not in daylight saving or somehow in UTC+0:30? |
So, the data is getting pulled directly from the inverter on my AlphaESS battery. Looking at the web console for my inverter it’s set to my Timezone here in Brisbane and the time restrictions I have set up for when it can discharge all work correctly. It just seems to be this integration with HA. I can recreate the integration if I need to to see if that fixes it. |
Yeah right, odd. i mean there isnt much we can do i dont think, something must be thinking you are in ACST, rather than AEST? could try to recreate the integration, but seems odd? coz the integration is calling No time/date data is being sent, and the timestamp is being generated from calling time.time(), which would be the current time/date that your NTP (time server) has set it to in HAOS, which should be brissy Im not trying to blame you here, but it seems to be something on your end? haven't seen anyone else with any issues since it was originally fixes a bit ago? you could try contacting alpahess themselves and see what they say? could be some mismatch caused by the installer |
Yeah all good. Completely get it’s bizarre and highest chances are it’s something in my setup. I’m just scratching my head cos of how weird it is. 😂 |
Ah thats right, just did a bit of digging, mine also resets at 9:30 (im in ACST), seems to be a issue on their end, where the total load is only updated at midnight GMT, not local midnight 😢 |
It seems that all the "daily sensors" work as expected (resetting at 00:00) except for "total load", it resets at 01:00.
So I suspect some kind of time-zone issue. I am in GMT+1 (winter time).
An example here from 00:30 is seen below:
So "grid to load", "discharge" etc. don't have any issues but this one does.
The text was updated successfully, but these errors were encountered: