There is a bug in v4.7.0 whereby if you select, for example "Etc/GMT-6", router time shows 12 hour difference. In this case router time shows UTC+6.
Although UTC is a standard and GMT is a timezone, they must display the same time if implemented correctly.
I selected the UTC-8 for comparison test on my router, as my time zone is east of eight.
UTC-8 on the router is the correct real-time. UTC-6 I think should also be correct.
Thanks for your reply. Please refer to your photos and notice that you have selected Etc/GMT-8 but your router time shows UTC+8. This is a 12 hour difference and is not correct. Put most simply, UTC is a standard and GMT is a timezone, however they always represent the same time. (In fact, the choice to use GMT instead of UTC further confuses things and if changes are made, it would make a lot more sense to use "Etc/UTC" followed by the offset rather than Etc/GMT.)
Your selected option is Negative Eight but your router time shows Positive Eight. These are not the same things. Negative Eight is most commonly known as Pacific Time or PST. Think Los Angeles. Positive Eight is on the other side of the globe such as Australian Western Standard Time (AWST). Think Perth. I assure you that the times indicated in your example photos are not correct. In one you show timezone for Los Angeles while router time indicates the offset is in Australia. Please understand that I'm not saying the time is incorrect. The time zones are incorrect. With your current setup of Etc/GMT-8, it might very well be displaying the correct time for Los Angeles but at the end of the day, Los Angeles is UTC -8. Therefore the router should not say UTC+08:00. UTC+8 is on the other side of the globe and can never represent Los Angeles or GMT-8.
The reason this is becoming such an issue is that I was using the 12 hour offset without any real consequences until I plugged a Philips Hue Bridge into the router. This Bridge controls automated and scheduled lights that come on at specific times during the day for various reasons. I don't know where exactly the Bridge is pulling the timezone from but it appears that the router's incorrect timezone (UTC offset) is having some effect because my preset schedules are out by many hours. I believe that the Bridge is reading the router's stated offset rather than the actual time. Now you can see my issue. If I'm living in Etc/GMT-6 and my router shows the correct time but also shows in brackets that the UTC is +6, there's going to be issues. Your photos show that the selected timezone is not accurately reflected in the UTC offset of "Router Time" irrespective of the correct time being displayed. This is less about time and more about timezone.
I hope this makes sense. I'm not the best at explaining things. And thanks again for your reply.
The router’s time is just used for the router itself, there is not even an NTP server running on it.
So I doubt that the wrong time will make the Bridge to malfunction.
Even if you don't set the right time, everything will be fine - except the schedule tasks on the router itself.
Hmm, it seems I have greater issues then. Even so, the router's timezone selection when selecting any of the "Etc/GMT" variables results in an incorrect offset displayed in the "Router Time" (despite the actual time being displayed correctly). Based on what you're saying and given this does not effect functionality, it's a bottom-of-the-list bug to fix but if/when devs get around to this bug, I encourage them to abandon the use of an offset based of GMT (eg. GMT-8) and use UTC with offset (eg. UTC-8) as it is now the standard.
Thanks for your help.
