||Stian (VP Product Excellence)|
Schedules are stored on chargers in UTC, which does not factor in daylight savings time.
When creating schedules though, the user interacts with and adjusts it according to their own timezone. This is then transmitted to the charger in UTC. This used to mean that the schedule would have to be adjusted manually twice a year, but at least for some territories this is no longer required.
Our system will now automatically adjust the stored schedules to compensate for daylight savings time in the following countries:
Norway, Sweden, Finland, Denmark, Switzerland, Germany, Austria, Poland, UK, Ireland, Netherlands, Belgium, Luxembourg, France.
We will continue to expand this list of countries + cater for countries with more than 1 timezone going forwards.
====== Old Info
Charger schedule does not take into account summer/Winter-time changes
The charger currently does not currently take into account changes in time due to daylight savings (Winter/Summer) time. Any re-occurring schedule will be 1 hr wrong every time the time is changed from Summer to winter and vice versa.
Please ensure that you manually update your schedules as daylight savings time is changed.
The Easee app takes into account what the current time zone is when setting a schedule in the app. The charger just does not know if the time is changed due to daylight saving.
When setting a schedule in the Easee app you should use the start and stop time you want as presented by the app.
Activity Newest / Oldest
I live in the UK and are now on Daylight Savings Time - however the app shows the schedule times as an hour later than what I had set previously and the charger is charging at those later times so it has not adjusted automatically.
Same here.. in the Netherlands
I have the same but I don't know if it's just the push notifications from Easee that are wrong because I think from my Octopus app the power usage is still starting at 00:30 rather than 1:30
Hello. I suspect some behaviour I saw tonight is related to this topic. Scheduled charge started 1 hour late. Charge end time was displayed differently, in different parts of the app. I uploaded the behaviour I saw in my Android app to YouTube. Please have a look and let me know what you think? Thanks very much, Paul. youtu.be/K4C5Yyp9VNo
Maybe to give clarity when start/ end times are either side of a winter/summer time change, the app could display the scheduled charge _duration_, in addition to the start and finish times. Thanks.
Status changed to: Fixed & released
Problem fixed with Easee App update 1.5.6 Thank you!
Charging schedule shows wrong time at startup of the app (one hour delayed) After opening the charing schedule it shows the correct schedule time. I will investigate further to find out which time is valid in reality. Attached you’ll find a screenrecording of the issue: share.icloud.com/photos/0265tF-XEc7RwhGdYRpV93BDg
Ramiro, if you disable, and re-enable the schedule, it will most likely fix the issue yer experiencing here.
If it does not, I know there's an upcoming update coming in the following days to our Cloud that might address the problem that should solve it going forward.
Thank you Alek for your quick response.
I tried disable and reanable already. Also tried deleting a charging schedule completely and add a new one again. Nothing helped. Found out that the time shown in the beginning after a fresh launch of the app is wrong and the one when loading the charging schedule is correct. So basically it is just shown wrong in the beginning after relaunching the app. Hope the update will fix this. Thank you for your support.
Could it be possible that todays major outage of the Cloud and App had something to do with the time change?
It could probably appear so, but our system now automatically adjusts for daylight savings time for some territories, which occurred at 0100 UTC. Outtage occurred around 0800 UTC so not related.
One year - and the charger still does not know about correct time zones? Is there no configTime() in time.h? Timezone could be passed by the app, so it‘s only 1 line of code for the charger!
Wait. You did "Use phone's timezone when generating consumption reports for chargers instead of UTC." (changelog V1.4.0) but you struggle to use the phone´s time zone for the charging schedule?
The schedules are transmitted from the app to the the cloud as UTC and then stored in chargers as UTC.
Converting from UTC to local time for things like reports is easy. But for schedules especially repeating schedules, they will sometimes need to factor in daylight savings time twice a year to compensate. Which isn’t that easy when chargers have no knowledge of time zones or daylight savings time to manage this themselves.
But the Cloud will automatically corrrect the schedules on the chargers depending on the country defined on the charging site’s address, so should be fixed for some territories, and we will continue to improve this process to make it work for more territories, and for territories with multiple time zones.
It is a major setback that i cannot change the time manually. Why is that?
The charging roboter has a connection to the internet. Why not use time servers?
This problem is brought up 1,5a ago and confirmed at least a year ago but not adressed in the slightest. How can that be?
Even if it is over your heads and you are unable to implement an automated shift, at least give us the opportunity to manually set the time like on our mothers ninties microwave ovens.
(Or give up and go by UTC/GMT Z alltogether.)
If you cannot fix this in over 1,5 years, which othe major flaws in your software/app keeps you from solving this one? Should we know about them? Can we recommend you to other people?
I am quite frankly underwhemled.
The app won't let me set 01:30-5:30, it keeps changing it to 02:30. I need it to be the equivalent of 00:30-04:30 which is what my car tariffs time is, can you fix this please.
Try again now, if you were trying to set it on the Sunday, then 01:30 was still in wintertime (because the wintertime to summertime conversion actually took place between 02:00 to 03:00 on Sunday) - Meaning any time you pick on that Sunday before 03:00 will still be considered wintertime, and thus shifted according to wintertime rules.
Sorry for the inconvenience.
Svein Gunnar Gotfredsen
They are sending pictures and sound from the planet Mars back to earth...and easee cant fix summer/winter time change?
Please add an time function in the app. Is a bad joke that I must manually change every Winter/change the whole schedules
last night I setup a delayed charged at 5:00, after save it was smartly changed to 6:00. But it is not starting chargimg today as the first day of summer time. I think it is not so hard to code it!
Per Øyvind Håvelsrud
Ok... The code is the easy part. Knowing what time zone to follow, and if and when that zone actually changes is another thing.
you are joking of the logic, to check time change and automatically fit the schedule, max 10 lines could fix this problem. is that so hard for you?
I have a planned charge every night of the week from 00:05-06:00. The app won't let me configure this after switching from winter to summer time. I can configure it for 03:05-06:00. I'm from Denmark.
Try again now, if you were trying to set it on the Sunday, then 00:05 was still in wintertime (because the wintertime to summertime conversion actually took place between 02:00 to 03:00 on Sunday) - Meaning any time you pick on that Sunday before 03:00 will still be considered wintertime, and thus shifted according to wintertime rules.
Whut? Two years ago and Not solved? It is a quite repetitious phenomenon.
Good to know but come on team, it's 2022 and we expect this to just work.
Stian (VP Product Excellence)
Status changed to: Identified