Hi.
I have the latest update from source as of now. Starting (I suppose) from version 5.1.0, time conditions are firing off an hour late. I have set;
- time_zone in default settings
- system time of Debian
- user time zone
I checked that system time, switch time and Fusion time are all correct matching with what I set (basically UTC+3). But nevertheless, all time conditions are firing off one hour later (as if the timezone is set to UTC+2)
I don't know if it has anything to do with Turkey omitting DST for good. But it has been a couple of years and everything was actually working fine. Turkey was switching to UTC+2 for DST and then UTC+3 back. But starting from 2016, Turkey never switched to UTC+2 again and UTC+3 prevailed the whole year. And nonetheless, all times are correct already, what could cause this time lapse?
I have the latest update from source as of now. Starting (I suppose) from version 5.1.0, time conditions are firing off an hour late. I have set;
- time_zone in default settings
- system time of Debian
- user time zone
I checked that system time, switch time and Fusion time are all correct matching with what I set (basically UTC+3). But nevertheless, all time conditions are firing off one hour later (as if the timezone is set to UTC+2)
I don't know if it has anything to do with Turkey omitting DST for good. But it has been a couple of years and everything was actually working fine. Turkey was switching to UTC+2 for DST and then UTC+3 back. But starting from 2016, Turkey never switched to UTC+2 again and UTC+3 prevailed the whole year. And nonetheless, all times are correct already, what could cause this time lapse?