Our, and i’ll assume that your clocks “moved forward an Hour” this weekend, GMT+?
Living in the UK i had selected the timezone Europe/ London with timezone sync on.
So when the clocks moved forward an hour, i was expecting the routers’ system time to auto advance 1hr.
Instead, the timezone automatically changed to etc/GMT+1, but the system time was 2hrs behind.
So system time slipped back an hour whilst the time jumped forward an hour!
So i re-selected Europe/London, applied and saved. I then noticed that the timezone changed to etc/GMT-1, this as i understand things would move the system time back an hour and 2hrs out of sync with the actual time, but the system time is in fact correct???
Auto update of the time is enabled and auto updated incorrectly, the system time was 2hrs behind actual time. I’ve had to manually correct it by selecting as i understand things incorrectly. British Summer Time (BST) is GMT+1 not GMT-1.
When i select GMT+1 which as i understand things is correct for all those within the UK the system time is 2hrs behind the correct time!!
GMT-1 at my longitudinal position, means the system time is 1hr behind the meridian as the globe moves round and GMT+1 at my longitudinal position, means the system time is 1hr before the meridian as the globe moves round.
So at my longitudinal position with a setting of GMT+1 i would be 2hrs adrift.
My Brain hurts, where’s the Brandy Bottle and those Paracetamol tablets!!?
The system time still auto updated incorrectly though!
Apologies for any inconvenience this issue may have caused. I have forwarded it to our R&D team, and I will let you know as soon as I receive feedback from them.
Hello and welcome to the wacky world of time zones.
There’s a very nice explanation here:
Copying the the important part, so it can be found later:
Positive versus negative numbering
Different protocols in various industries have varied in their numbering, with some considering offsets ahead of UTC to be positive numbers while others used negative. Symmetrically, some considered offsets behind UTC to be negative while others used positive.
In most modern protocols I’ve seen, such as the ISO 8601, offsets ahead of UTC (towards the east) are positive, while offsets behind UTC (towards the west) are negative. So the offsets used by zones in the Americas have negative numbers such as America/Los_Angeles having an offset of -07:00 or -08:00 nowadays (varies during the year because of Daylight Saving Time (DST)).
I suggest you learn to think of this manner (right of UTC is positive, left of UTC is negative) as mainstream, and the opposite as a minor annoying variation.
Time zone names are generally in the format Continent/Region, such as America/Edmonton, Europe/Paris, Africa/Tunis, Asia/Kolkata, and Pacific/Auckland. See this list on Wikipedia (may not be up-to-date). There are some exceptions. The Etc/GMT… names carry the opposite plus/minus convention:
Etc/GMT+1 = -01:00 offset = One hour behind UTC
Etc/GMT+12 = -12:00 offset = Twelve hours behind UTC
…and…
Etc/GMT-1 = +01:00 offset = One hour ahead of UTC
Etc/GMT-12 = +12:00 offset = Twelve hours ahead of UTC
So the time format is correct. Is it confusing? Absolutely
However when the clocks moved forward an hour the other weekend the system time auto updated and became 2hrs behind BST.
I’ve changed the time manually so that the system time is now correct so it’s not an ongoing issue until the autumn perhaps when the clocks drop back an hour.
It was emails and texts the system was sending me that were being sent at an incorrect time and highlighted the issue.
