If it's up to me I'll just jump to this setting.
The zones like "Etc/GMT-4" are 4 hours ahead of GMT. This matches standard POSIX time zone names. Why they did that, I don't know, other that that I think it was decided earlier than the ISO standard format that is now much more common...
1 Like
Go for it, but its going to be wrong. The library loaded in Hubitat will keep using the old rules until they update the time zone library. I think that is your current time zone, or maybe the one next to you? According to Google that zone just switched to permanent MST (aka PDT) as of March 2026.
You will want to use "etc/GMT+7 GMT-07:00" to be on permanent UTC-7, according to my searching the change happening gives you permanent PDT (Pacific Daylight Time) UTC-7.
Probably the same way they handle Arizona and Hawaii.
The Yukon is directly above BC and it has changed to permanent DST UTC-7.
So changing my location for time resolution won't work if I just say that's where I live?
The whole reason for this topic was just to find out where the "Fix" lay.
So it's up to Hubitat to amend their code.
That's the answer then.
Fort Nelson changed a while back, 2015.
It should be a quick check on your hub. Not too sure of the relevance but... 
58°48â˛21.3âłN 122°41â˛47.3âłW
I already stated the interim fix twice, not sure why you refuse to accept it. I know from past posts of this same nature that even after many months (possibly had been a year) the users original time zone still was using the old rules. The direction from staff was to use the correct etc/GMT time zone because they didn't know when it would be corrected on the hub.
